Pick of the day 23 Jan 2003 Lecture 9 E/B/C Use Case Analysis Telesterion.

Slides:



Advertisements
Similar presentations
Use Case Modeling SJTU. Unified Modeling Language (UML) l Standardized notation for object-oriented development l Needs to be used with an analysis and.
Advertisements

Appendix Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Object-Oriented Analysis and Design
Information System Engineering
Practical Business Modeling in the Unified Process Tom Morgan Software Architect, Fidelity National Information Services
CS3773 Software Engineering Lecture 03 UML Use Cases.
Pick of the day 24 Jan 2003 Lecture 10 Make it as simple as possible, but no simpler.
1 Use Cases 1 CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 17, 2004.
Pick of the day 30 Jan 2003 Lecture 13 Mini Case Study.
Pick of the day 27 Jan 2003 Lecture 11 Visitor. January Lecture 112 Outline Previous Business HW1 now available via my.wpi.edu Lecture Contents.
Use Cases Elizabeth Bigelow CS C 9/15/2000.
1 CS 426 Senior Projects Chapter 4: Use Case Modeling [Arlow and Neustadt, 2002] February 8, 2007.
Systems Analysis and Design in a Changing World, Fourth Edition
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 5, Analysis: Dynamic Modeling.
Chapter 10 System Sequence Diagrams. What is a System Sequence Diagram? A way of modeling input and output events related to systems It is a picture that.
Documenting Requirements using Use Case Diagrams
1 CS 426 Senior Projects Chapter 4: Use Case Modeling [Arlow and Neustadt, 2005] February 5, 2009.
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Chapter 3 Object-Oriented Analysis of Library Management System(LMS)
UML Sequence Diagrams Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
Requirements Elicitation. Requirement: a feature or constraint that the system must satisfy Requirements Elicitation: specification of the system that.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Business Modeling : basic concepts Extracted from Rational UML Profile for business modeling.mht.
Chapter 5 Analysis Model. Analysis model (AM) The first step in describing how the system will implement the requirements specification The first step.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis Activity (Identifying Objects, Scenarios) Janice Regan,
Interaction Modeling. Introduction (1) Third leg of the modeling tripod. It describes interaction within a system. The class model describes the objects.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
McGraw-Hill/Irwin © 2013 The McGraw-Hill Companies, Inc., All Rights Reserved. Chapter 7 Data Flow Diagramming.
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
1 Object-Oriented Analysis Use Case Driven. 2 The outline method for OOA 1.Identify object classes within the problem domain 2.Define the behaviour of.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Requirements Documentation CSCI 5801: Software Engineering.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Lecture 3 Uses Cases Topics UML Use Cases pop quiz Readings: Chapter 3 January 24, 2008 CSCE 492 Software Engineering.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML: Review Session (Optional)
For accurate communication, since a project can have several participants, each from different background. Represent a given aspect of the system We will.
IS3320 Developing and Using Management Information Systems Lecture 9: Use Cases and Scenarios Rob Gleasure
1 Structuring Systems Requirements Use Case Description and Diagrams.
The Unified Modeling Language Part II Omar Meqdadi SE 2730 Lecture 9 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
CS 4233 Review Feb February Review2 Outline  Previous Business – My.wpi.edu contains all grades to date for course – Review and contact.
Use Cases CS 6961 – Lecture 4 Nathan Dykman. Neumont UniversityCS Lecture 102 Administration Homework 1 is due –Still reviewing the proposal, but.
Systems Analysis and Design in a Changing World, Fourth Edition
IS3320 Developing and Using Management Information Systems Lecture 16: Data-Flow Diagrams 1 (Intro to Context-Level diagrams) Rob Gleasure
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
Unit-3 Identifying use cases Object Analysis Classification
UML Review of Use case diagrams. 2 Unified Modeling Language The Unified Modeling Language™ (UML) was developed jointly by Grady Booch, Ivar Jacobson,
Pick of the day 13-Jan-2003 Lecture 3 Common Patterns in Static Design.
OOAD (part 2) diagrams CSCI577a TAs: Alexey. Outline UML diagrams: – Use case diagrams – Robustness diagrams – Sequence diagrams – Artifacts diagrams.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
Summary from previous lectures
Use Case Diagrams. Introduction In the previous Lecture, you saw a brief review of the nine UML diagrams. Now that you have the clear, you'll start to.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
SYSTEM-LEVEL SEQUENCE DIAGRAMS Sys466. System-Level Sequence Diagrams  Use cases describe how external actors interact with the software system…  An.
1 After the scenarios are formulated Find all the use cases in the scenario Describe each of these use cases in more detail Participating actors Describe.
LECTURE # 7 : STRUCTURED PROGRAMMING Selection Statements Tr.Hadeel.
IS3321 Information Systems Solutions for the Digital Enterprise Lecture 12: Revision Lecture Rob Gleasure robgleasure.com.
Use cases, tests classes, …
BTS430 Systems Analysis and Design using UML
Object-Oriented Systems Analysis and Design Using UML
Chapter 4: Use Case Modeling
IMPORTANT NOTICE TO STUDENTS:
Unified Modeling Language
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
Object Oriented Analysis and Design
Chapter 4, Requirements Elicitation: Functional Modeling
Software Design Lecture : 15.
Interaction Modeling Extracted from textbook:
Chapter 4, Requirements Elicitation: Functional Modeling
Presentation transcript:

pick of the day 23 Jan 2003 Lecture 9 E/B/C Use Case Analysis Telesterion

January Lecture 92 Outline Previous Business HW1 to be returned today (hopefully) Electronic submission for HW2 using digital drop box Reading Questions Lecture Contents Use Case Analysis Entity/Boundary/Controller

January Lecture 83 Requirements Analysis Identifying Actors Identifying Use Cases identify scenarios first  general use cases Refine Use Cases Identify Relationships among use cases «include» «extends»

January Lecture 84 Actors External entities that interact with system Define boundaries of system ensures all perspectives taken into account

January Lecture 85 Identify Actor Scenarios What functionality is available to each actor? Concrete Scenarios read like a narrative forms the basis for more abstract use cases list all participating actors

January Lecture 86 Breakout Too much lecturing! Break into groups to develop scenarios

January Lecture 87 Use case analysis Review Use case namename Entry ConditionWhat must be true for applicability Flow of Events1. Enumerated set of events 2. … 3. … Exit ConditionResult of use case

January Lecture 88 Friday Assignments HW2 get started

January Lecture 89 References