System analysis and design

Slides:



Advertisements
Similar presentations
Ver 1,12/09/2012Kode :CIA-230 Anal-Perc.SistemFASILKOM PERTEMUAN-4 Chapter 4. Use Case Analysis.
Advertisements

© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
© Copyright 2011 John Wiley & Sons, Inc.
Information System Engineering
Lecture 8 – USE CASE ANALYSIS
Documenting Requirements using Use Case Diagrams
Use Case Analysis Chapter 6.
Bina Nusantara 7 C H A P T E R MODELING SYSTEM REQUIREMENTS WITH USE CASES.
Use Cases.
SwE 313 Introduction to Rational Unified Process (RUP)
© Copyright 2011 John Wiley & Sons, Inc.
Functional Modeling Chapter 6.
Systems Analysis and Design in a Changing World, 6th Edition
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.
System analysis and design
USE Case Model.
Modeling System Requirements:Events and Things
Data flow diagrams.
Use Case Diagrams – Functional Models Chapter 5. Objectives Understand the rules and style guidelines for activity diagrams. Understand the rules and.
RUP Requirements RUP Artifacts and Deliverables
1 Lecture 3: Introducing Data Flow Diagrams (DFDs) Section 1 - The Concept of Diagrams Why use Diagrams? Diagrams as Working Documents Systems Analysis.
Systems Analysis and Design in a Changing World, 6th Edition
U SE C ASE A NALYSIS Chapter K EY I DEAS Use cases are a text-based method of describing and documenting complex processes Use cases add detail.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
The Requirement. What is Inception? What is the vision and business case for this project? –not to define all the requirements Feasible? Buy and/or build?
Chapter 9 요구사항 모델링: 시나리오 기반 방법론 Requirements Modeling: Scenario-Based Methods 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim.
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
2131 Structured System Analysis and Design By Germaine Cheung Hong Kong Computer Institute Lecture 8 (Chapter 7) MODELING SYSTEM REQUIREMENTS WITH USE.
Systems Analysis and Design in a Changing World, 6th Edition
Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.
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, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
Information Systems Analysis and Management Modeling Sys. Requirements with Use Cases Arnie Lund, Jeffrey Kim May 5, 2009 INFO380.
Lecture 6: Test-based Use case & Process Modeling December 7, 2014.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
Lecture 6: Chapter 4:Test-based Use case Process Modeling Dr. Taysir Hassan Abdel Hamid November 17, 2013.
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.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Slide 1 Project team 1. gathers requirements from the users (Ch. 4) 2. models the overall business process using __________ 3. identifies _________ using.
TA: Shreya Rawal.  A use case is a description of a system’s behavior as it responds to a request that originates from outside of that system (Usually.
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.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
Chapter 5 – System Modeling
Use Case Analysis Chapter 6.
CompSci 280 S Introduction to Software Development
Business Process and Functional Modeling
Business Processes A business process describes a set of activities that are necessary to complete a response to a stimulus applied to an organization.
Chapter 4: Business Process and Functional Modeling, continued
Chapter 5 System modeling
CMPE 280 Web UI Design and Development August 29 Class Meeting
Storyboarding and Game Design SBG, MBG620 Full Sail University
Unified Modeling Language
Use Case Analysis Chapter 5.
Systems Analysis and Design Third Edition
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Requirements Elicitation and Elaboration
1.Introduction to Rational Unified Process (RUP)
SYSTEMS ANALYSIS Chapter-2.
Systems Development and Documentation Techniques
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Chapter 9 Requirements Modeling: Scenario-Based Methods
Object Oriented Analysis and Design
Software design and architecture
Engineering Quality Software
Use Case Modeling Part of the unified modeling language (U M L)
Chapter 4 System Modeling.
Week 8 Lecture 1: Identifying Actors and Activities
Presentation transcript:

System analysis and design Safaa s.y. dalloul

Use Cases

Unit 5: Use cases Building Use Case Introduction Elements of use case Basic Information Inputs and Outputs Details Building Use Case Identify the major use cases Identify the major steps within each use case Identify elements within steps Confirm the use case Cycle through the above steps iteratively

Introduction A use case is a formal way of presenting how a business system interacts with its environment. A use case depicts a set of activities performed to produce some output result. Each use case describes how an external user triggers an event to which the system must respond.

Why do you think we need to draw the use cases? Introduction Why do you think we need to draw the use cases?

Introduction To help us better understand the situation and help make the following design step simpler. It is also important to create use cases when we are reengineering processes. When creating use cases, the project team must work closely with the users to gather the information needed.

Determine the elements of Use Case

Elements of use case A use case contains fairly complete description of all the activities that occur in a response to a trigger event. While there are numerous pieces of information in the use case, the information is organized into three main parts: basic information, inputs and outputs, and details.

Basic Information Inputs Outputs Details

Elements of use case Basic Information Each use case has a name and number, the number is simply a sequential number that serves to reference each use case. The importance level maybe assigned to indicate the relative significance of the use case in the overall system.

Elements of use case Basic Information The primary actor refers to the external user that triggers the event to which the system response. Another element of basic information is the trigger for the use case. Use cases are written from the bird's eye view of the system.

Elements of use case Inputs and Outputs Each of the major inputs and outputs to the system case described along with their sources or destination. These are all possible inputs and outputs. Building case is a gradual sharing work for analysts and users.

Elements of use case Details These steps are the activities that are performed during the use case, such as taking patient name and address, check for appointment and so on. These steps are listed in the order in which they are performed and any conditional steps are clearly noted.

Building use cases Process of Developing Use Case Identify the major use cases Identify the major steps within each use case Identify elements within steps Confirm the use case Cycle through the above steps iteratively

Building use cases Process of Developing Use Case Identify the major use cases Activities   Start a use case form for each use case. If more than nine, group into packages

Building use cases Process of Developing Use Case Identify the major use cases Questions   Ask who, what, and where about the tasks and their inputs and outputs What are the major tasks performed? What triggers this task? What tells you to perform this task?

Building use cases Process of Developing Use Case Identify the major use cases Questions   What information/forms/reports do you need to perform this task? Who gives you these information/forms/reports? What information/forms/reports does this produce and where do they go?

Building use cases Process of Developing Use Case Identify the major steps within each use case Activities   For each use case, fill in the major steps needed to process the inputs and produce the outputs

Building use cases Process of Developing Use Case Identify the major steps within each use case Ask how about each use case:   How do you produce this report? How do you change the information on the report? How do you process forms? What tools do you use to do this step (e.g., on paper, by email, by phone)?

Building use cases Process of Developing Use Case Identify elements within steps Activities   For each step, identify its triggers and its inputs and outputs

Building use cases Process of Developing Use Case Identify elements within steps Ask how about each step   How does the person know when to perform this step? What forms/reports/data does this step produce?

Building use cases Process of Developing Use Case Identify elements within steps Ask how about each step   What forms/reports/data does this step need? What happens when this form/report/data is not available?

Building use cases Process of Developing Use Case Confirm the use case Activities   For each use case, validate that it is correct and complete Question Ask the user to execute the process using the written steps in the use case – that is, have the user role-play the use case

Building use cases Process of Developing Use Case Cycle through the above steps iteratively For each use case, perform the previous steps, and maybe you'll need to update one use case depending of new information that could catch.

Role-Play

Safaa S.y. dalloul Safaadalloul.wordpress.com Thank You