Slide 1 Project team 1. gathers requirements from the users (Ch. 4) 2. models the overall business process using __________ 3. identifies _________ using.

Slides:



Advertisements
Similar presentations
Chapters 7 & 9 System Scope
Advertisements

Chapter 7 Structuring System Process Requirements
Systems Analysis and Design, 7e Kendall & Kendall
Systems Analysis and Design with UML Version 2.0, Second Edition
Prof. Dr. Nizamettin AYDIN
 Need to Gather requirements and other related information  Use case Modeling ◦ What the system will do for the users.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 The.
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Use Case Analysis Chapter 6.
Use Case Systems Analysis & DesignUse Case1 Use case refers to A system’s behavior (functionality) A set of activities that produce some output.
A use case describes one “case” of how a user can use the system.
Chapter 6 Functional Modeling
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Functional Requirements – Use Cases Steve Chenoweth & Chandan Rupakheti (Chapters 14, 21 – Requirements Text)  Quiz question 9 relates to this, when you’ve.
Functional Modeling Chapter 6.
Use Case Modeling. Kendall & Kendall© 2005 Pearson Prentice Hall18-2 Commonly Used UML Diagrams The most commonly used UML diagrams are: – Use case diagram,
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
USE Case Model.
Use Case Diagrams – Functional Models Chapter 5. Objectives Understand the rules and style guidelines for activity diagrams. Understand the rules and.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
ANALYSIS REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Chapter 7 Structuring System Process Requirements
LECTURE 3 USE CASE DESCRIPTION. Use Cases grouped into system modules Note: Same actor interacts with different modules USE CASE DIAGRAM OF THE CUSTOMER.
Software Engineering Chapter 8 Fall Analysis Extension of use cases, use cases are converted into a more formal description of the system.Extension.
ZEIT2301 Design of Information Systems Functional Design: Use Cases School of Engineering and Information Technology Dr Kathryn Merrick.
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Prepared by Afra`a Sayah. Introduction. Weekly Tasks. Plane Phase. Analysis Phase. Design Phase. Report Rules. Conclusion. 2.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Behavioral Modeling Chapter 8.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
1 Structuring Systems Requirements Use Case Description and Diagrams.
1 Modeling System Requirements with Use Cases. 2 Why Do We Need Use Cases? Primary challenge in a system design process –ability to elicit correct and.
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
1 Use-Case Modeling Chapter 6 Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc. Slides by Fred Niederman Edited by Solomon Negash.
Lecture 4 :Use cases III (UC description) 1. Outline CT 1414 * Nouf Aljaffan2  Concept of Use Case Description  Levels of Use Case Description  Reading.
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 6: Functional Modeling.
The College Of Applied Studies And Community Services Lecture 3 :Use cases II (UC description) Systems Analysis & Design Instructor: Nouf Aljaffan CT 1414.
Slide 1 Classes and Objects. Slide 2 Messages and Methods.
Slide 1 What the business needs  How to build it Functional requirements  + Nonfunctional requirements Performance System environment issues Problem.
Business Process and Functional Modeling Teguh Sutanto, S.Kom.,M.Kom.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software.
Unit-3 Identifying use cases Object Analysis Classification
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
UML - Development Process 1 Software Development Process Using UML.
Larman chapter 61 Use cases Larman chapter 6. 2 Fig. 6.1.
Use Case Model Use case description.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
Gerhard Dueck -- CS3013Analysis 1. Gerhard Dueck -- CS3013Analysis 2 Why analysis?  Yield a more precise specification of the requirements.  Introduce.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
CSE Senior Design I Architecture Design Review/Final Exam Template CSE 4316 Final Exam.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 6: Functional Modeling.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Use Case Analysis Chapter 6.
Chapter 4: Business Process and Functional Modeling, continued
The Movement To Objects
Unified Modeling Language
UML Use Case Diagrams.
Process Modelling Chapter 6.
Requirements Analysis: Business Process and Functional Modeling
Unified Modeling Language
Object Oriented Analysis and Design
INFS 6225 Object Oriented Systems Analysis & Design
PHÂN TÍCH THIẾT KẾ HƯỚNG ĐỐI TƯỢNG
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Presentation transcript:

Slide 1 Project team 1. gathers requirements from the users (Ch. 4) 2. models the overall business process using __________ 3. identifies _________ using identified activities, prepares use case ________ and use case _________ for each use case. Logical Model VS Physical Model Ch.5 Use Case Diagrams

Slide 2 Activity Diagram used to model the behavior in a business process independent of objects. Cf. DFD Activity Diagram models 1. high level business _______ that involve many different use cases 2. details of an individual _________ 3. specific details of an individual ________ Fig. 5-1 Syntax of an Activity Diagram

Syntax for an Activity Diagram

Activity Diagram for Appointment System

fig_05_04

Slide 6 Use Case Description - less formal descriptions of the use cases - captures the typical interaction of the system with the ______ - Each use case describe one and only one ______ - Each use cases is associated with one and only one ______ Types of Use Cases (1) Overview Detail (2) Essential Real

Slide 7 Elements of a Use-Case Description Three Basic Parts (1) Overview Information (2) Relationship (3) Flow of Events Fig 5-5 Use Case Description Example

fig_05_05

Slide 9 Guidelines for Creating Use Case Description (1) Write each set in the form of Subject-Verb-Direct Object- Preposition-Indirect Object (2) Make sure it is clear who the initiator of the step is. (3) Write the step from the perspective of the independent observer. (4) Write each step at about the same level of abstraction. (5) Ensure the use case has a sensible set of steps. (6) Apply the KISS principle liberally. (7) Write repeating instructions after the set of steps to be repeated.

Slide 10 Use Case Diagram (1) Actor (2) Association (3) Use Case (4) System Boundary Fig. 5-7 Syntax for Use Case Diagram Ch.5_B Use Case Diagrams

fig_05_07

Use Case Diagram for the Appointment System

Use Case System with Specialized Actor

Extend and Include Relationships

Slide 15 Creating Use Case Descriptions and Use Case Diagrams (1) Identify the Major Use Cases 1. Review the activity diagram 2. Find the subject’s boundaries. 3. Identify the primary actors and their goals 4. Identify and write the overview of the major use cases for the above 5. Carefully review the current use cases. Revise as needed. (2) Expand the Major Use Cases (3) Confirm the Major Use Cases (4) Create the Use Case Diagram 1. Draw the subject boundary 2. Place the use cases on the diagram 3. Place the actors on the diagram 4. Draw the associations.

Use-case Point Estimation Worksheet

Use-case Point Estimation for the Appointment System

Activity Diagram for the CD Selections To-Be Internet Sales System

Overview of Major Use Cases for the CD Selections

Place Order Use Case after Step 8

Place Order Use Case after Step 11

Revised Major Use Cases for CD Selections

Revised Major Use Cases for CD Selections (Continued)

Use Case Diagram for the CD Selections To-Be Internet Sales System

Use Case Points Estimation for the Internet Sales Systems