Software Engineering 2 91.412 - Lecture 3 Georges Grinstein Olsen 301E Class materials:

Slides:



Advertisements
Similar presentations
Intelligent Technologies Module: Ontologies and their use in Information Systems Revision lecture Alex Poulovassilis November/December 2009.
Advertisements

ITEC 370 Lecture 24 Lifecycles. Review Questions? –Grades for Requirements/Design Doc F give prototype demonstration –Testing plan for your software Maintenance.
8 September Announcements  GIT Class: Friday 3-5 SN 115 (Peter Parente)  Information for Project Links PageProject Links Page  Hot Topics Teams.
8 September Your Architecture First level diagram: how components fit together.
The Assignments. A good assignment is one that… Permits creativity Gets me a good grade Requires me to think …
UML CASE Tools - StarUML -
Software Engineering Lecture 4 Georges Grinstein Olsen 301E Class materials:
Introduction to Software Engineering Dr. Basem Alkazemi
18 January Writing a Functional Spec. Administrivia How many teams will want departmental web space vs links to your own space? Please send me your CS.
Software Engineering Georges Grinstein Olsen 301E Class materials:
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
Slide 7C.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
1 SWE Introduction to Software Engineering Lecture 11 - Requirements Engineering Processes.
CSCI 639 Topics in Software Engineering Assignment #4 Fall 2006.
Adding the Detail Filling in Use Case Templates. Use Case Template The use case diagram is important for visualizing a system and as a communication tool.
Nathaniel Neitzke Lighthouse1, LLC
ONLINE TECHNICAL REPORT SYSTEM Team Crash Course Ryan Ashe, Eileen Balci, James Kirk, Taylor Paschal.
Object Oriented Analysis By: Don Villanueva CS 524 Software Engineering I Fall I 2007 – Sheldon X. Liang, Ph. D.
Module CC3002 Post Implementation Issues Lecture for Week 6 AY 2013 Spring.
ZEIT2301 Design of Information Systems
COMP 523 DIANE POZEFSKY 20 August AGENDA Introductions Logistics Software Engineering Overview Selecting a project Working with a client.
Software Engineering 2003 Jyrki Nummenmaa 1 CASE Tools CASE = Computer-Aided Software Engineering A set of tools to (optimally) assist in each.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 12.
COMP 523 DIANE POZEFSKY 19 August CHAOS REIGNS.
Supplementary Specifications (Chapters 20,22 - Requirements Text) 1.
ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces.
Requirements Engineering Requirements Elicitation Process Lecture-8.
21 August Agenda  Introductions  Logistics  Selecting a project  Working with a client.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
CS Tutorial 4 Frid. Oct 16 th, 2009 Prototype Tutorial.
Software Requirements (Advanced Topics) “Walking on water and developing software from a specification are easy if both are frozen.” --Edward V Berard.
How to start Milestone 1 CSSE 371 Project Info There are only 8 easy steps…
LECTURE 14: USE CASE BASICS CSC 212 – Data Structures.
The Case Police vs. Jack Jones Theft? Murder? Breaking and Entering?
1-1 User Stories Much taken from User Stories Applied: For Agile Software Development Mike Cohn Mountain Goat Software.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Chapter 7 The Object-Oriented Approach to Requirements.
Telerik Software Academy Software Quality Assurance Binding business requirements to.NET code.
CT1404 Lecture 2 Requirement Engineering 1 1. Today's Lecture Definition of a Software Requirement Definition of Software Requirements Management Characteristics.
WEEK INTRODUCTION CSC426 SOFTWARE ENGINEERING.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Use Cases CS 6961 – Lecture 4 Nathan Dykman. Neumont UniversityCS Lecture 102 Administration Homework 1 is due –Still reviewing the proposal, but.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
IS3320 Developing and Using Management Information Systems Lecture 1: Introduction to IS3320 Rob Gleasure
 Friday, September 07, 2012  Standard: Narrative Elements  Objective: I will be able to identify the elements of narrative in a story.  Due today:
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
SmartPosition Customer Review and Feedback Presentation.
17 January Requirements. The Plan Quick Pass on Software Engineering “Just enough” context Start with what you need for your first deliverables Back up.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Software Engineering Lecture 10: System Engineering.
SmartPosition Customer Review and Feedback Presentation.
Week 16 BIO Finals. No First Five Learning Target: Everything!! Today’s Activities: ● Review on your own...Tomorrow Questions! Notecard: ● Front side.
Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.
TWFTV What Makes for a Good Continuing TV Narrative?
Developing Business Processes Developing an activity diagram of the business processes can provide us with an overall view of the system.
Project management Software development typically includes:
Reading Assignment 6th Gifted Mrs. Kercher
Requirement Engineering
What Makes for a Good Continuing TV Narrative?
BSA 385 Competitive Success-- snaptutorial.com
BSA 385 Competitive Success-- snaptutorial.com
BSA 385 Education for Service-- snaptutorial.com
BSA 385 Education for Service-- snaptutorial.com
BSA 385 Teaching Effectively-- snaptutorial.com
BSA 385 Teaching Effectively-- snaptutorial.com
BSA 385 Inspiring Innovation-- snaptutorial.com
Lect02 – Designing a Program
Developing Web Specifications
Agenda – week 3 6:00 – 6:30 Documenting an Architecture Project discussion 6:30 – 7:40 Lecture: Qualities vs functionality 7:40 – 8:00 Break 8:00 – 8:20.
Presentation transcript:

Software Engineering Lecture 3 Georges Grinstein Olsen 301E Class materials:

September 10 Today –UVP –Weave User stories and use cases for Weave –Ask me questions ArgoUML

Weave Documents Discussion Demos Your need to decide 1. what area you like 2. what you will document/test 3. what you might be able to implement

User Story Templates As a [role], I can [feature] so that reason] As a [role], I want [feature] because [reason] As a [role], I can [feature] As a [role], I can [feature] so that [reason]

Acceptance Story Make user story testable with acceptance stories (or tests) These can be written using the template: Scenario 1 Title Given [context] and [some more context] When [event] Then [outcome] and [another outcome]

Homework 2 - due Tuesday 9/15 Read Weave Documents Play with demo site On the area you want to work on identify 5 use cases and user stories for each of –current Weave version (0.5) –year 2 Weave (1.0) We will develop these use cases, activity and sequence diagrams next week

So ask me questions about Weave and write your use cases/user stories/…