SYS466 Systems Use Case Specifications. Systems Use Case Diagrams and Specifications  Based on the dialog metaphor.

Slides:



Advertisements
Similar presentations
Groups vs. Teams. Groups Groups are a normal part of life. Every group is different: -Different purposes -Different people -Different relationships.
Advertisements

SYS366 The Last Stage in Analysis: System Use Case Descriptions created through the Use Case Authoring Process.
Actors and use cases Use-case diagram Brief notation Prioritization Fully dressed notation Requirements Functional requirements  Use-cases.
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1/18 Use Case Analysis – continued Control Classes.
Object-Oriented Analysis and Design
Introduction To System Analysis and Design
Summary Class responsibility cards can be used to help allocate responsibilities between different classes. The use of stereotype classes, such as entity,
Slide 1 Systems Analysis & Design CS183 Spring Semester Dr. Jonathan Y. Clark Course Website:
Lecture 4 Class Responsibility Collaboration Cards
COST G9 - Work group 2 Cadastral science meeting Aalborg, Dk Modeling methodology for real estate transactions Radoš Šumrada Faculty.
Essentials of interaction diagrams Lecture Outline Collaborations Interaction on collaboration diagrams Sequence diagrams Messages from an object.
PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
CSCI928 Software Engineering Requirements & Specifications Modeling System Interactions Tri A. Kurniawan, M.Eng. Ph.D Candidate
Chapter 21 Object-Oriented Analysis
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
Slide 1 Chapter 8 Behavioral Modeling. Slide 2 Key Ideas Behavioral models describe the internal dynamic aspects of an information system that supports.
Slide 7E.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
TK2023 Object-Oriented Software Engineering CHAPTER 6 SYSTEM SEQUENCE DIAGRAMS.
User Interface Theory & Design
SYS366 Systems Use Case Descriptions. SYS3662 Contents Review Systems Use Case Descriptions Systems Use Case Authoring.
Requirements Elicitation. Requirement: a feature or constraint that the system must satisfy Requirements Elicitation: specification of the system that.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa USE CASES In this lecture: Use cases - What are use.
Use Cases 2 ENGR ♯10 Peter Andreae
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
The Next Stage in Analysis: Systems Use Case Diagrams 1 SYS366.
BTS330 Documenting Use Cases.
Prepared by Afra`a Sayah. Introduction. Weekly Tasks. Plane Phase. Analysis Phase. Design Phase. Report Rules. Conclusion. 2.
Understanding User Requirements. Documenting Use Cases 2 At this stage of the exploration, the participants should be thinking of essential use cases.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 8: Behavioral Modeling.
Lecture 7: Requirements Engineering
Behavioral Modeling: Sequence and Communication Diagrams Copyright © 2009 John Wiley & Sons, Inc. Copyright © 2005 Pearson Education Copyright © 2009 Kannan.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Behavioral Modeling Chapter 8.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 8: Analysis Modeling Software Engineering: A Practitioner’s Approach, 6/e Chapter.
UML-1 8. Capturing Requirements and Use Case Model.
1 Objectives  Define key concepts of use-case modeling.  List the benefits of use-case modeling.  Find actors and use cases.  Describe their relationships.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
User Interface Theory & Design Lecture 6a 1.  User interface is everything the end user comes into contact with while using the system  To the user,
Use Cases Use Cases are employed to describe the functionality or behavior of a system. Each use case describes a different capability that the system.
Chapter 7 The Object-Oriented Approach to Requirements.
Interaction Diagrams Interaction Diagrams allow the designer to show how groups of objects collaborate in some behavior. –Interaction Diagrams will show.
SYS466 Casual Use Case Specifications. Systems Use Case Diagrams and Specifications Based on the dialog metaphor Based on the dialog metaphor The process.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Microsoft Visual Basic 2010: Reloaded Fourth Edition Overview An Introduction to Programming.
Winter 2007SEG2101 Chapter 31 Chapter 3 Requirements Specifications.
Identifying Needs and Establishing Requirements Presenters: Veronica Gasca Jennifer Rhough.
Prof. Hany H. Ammar, CSEE, WVU, and
Order of Details Transitions Types.  A paragraph has coherence when readers can tell how and why ideas are connected.
UML - Development Process 1 Software Development Process Using UML.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
1 BTS330 Visual Modeling. What is Visual Modeling? 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 8: Behavioral Modeling.
Slide 1 Project team 1. gathers requirements from the users (Ch. 4) 2. models the overall business process using __________ 3. identifies _________ using.
Use Cases Defining user requirements in chunks. Introduction Presentation on Use Cases, includes: Presentation on Use Cases, includes: What is a use case.
Lecture 5d: Systems Use Case Descriptions.  Review  Systems Use Case Descriptions  Systems Use Case Authoring SYS3662.
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.
Systems Analysis and Design with UML Version 2.0, Second Edition
The Next Stage in Analysis: Systems Use Case Diagrams
The Next Stage in Analysis: Systems Use Case Diagrams
SYS366 Documenting Use Cases.
UML Overview Part 2.
Unified Modeling Language
CRC Modeling (class-relationship-collaborator)
Object Interaction Diagrams
Chapter 4 Sequence Diagrams
Presentation transcript:

SYS466 Systems Use Case Specifications

Systems Use Case Diagrams and Specifications  Based on the dialog metaphor

Dialog Expresses that the User and Computer Interact by Sending Messages

Designing Dialogs  The process of designing the overall sequences that users follow to interact with an information system  the sequence in which information is displayed to and obtained from the user

Sequence  understanding how the user will interact with the system clear understanding of user, task, technological and environmental characteristics

Questions to ask to identify system use cases*  What are users in this role trying to accomplish?  To fulfill this role, what do users need to be able to do?  What are the main tasks of users in this role?  What information do users in this role need to examine, create, or change?  What do users in this role need to be informed of by the system?  What do users in this role need to inform the system about? *

Systems Use Case Diagram Place holder for the Systems Use Case Specification A visual index, providing a context for the Specifications * Systems Use Cases Modeling by Bittner & Spence, Pages

Systems Use Case Specifications  The (systems) use case specifications provide the substance of the (systems) use case model and they are the basis for most of the …modeling work…More than 90% of the (systems) use-case model lies beneath the surface, in the textual use- case specifications themselves. * *Use Case Modeling, Kurt Bittner & Ian Spence, Addison-Wesley, 2003, p. 30

Systems Use Case Specifications  “(Systems) use cases are more than just a named ellipse and a brief Specification. For each (systems) use case there will also be a (systems) use-case specification where the full story of the use case is told.”* *Use Case Modeling, Kurt Bittner & Ian Spence, Addison-Wesley, 2003, p. 30

Systems Use Case Specifications  “The use case specification tells a story of how a system and its actors collaborate to achieve a specific goal  This collaboration takes the form of a dialog between the system and its actors  It is a step-by-step description of a particular way of using a system”* *Use Case Modeling, Kurt Bittner & Ian Spence, Addison-Wesley, 2003, p. 24

Systems Use Case Specification  Not a complete specification of all possible ways that some task is performed  Describes typical ways (or scenarios) of using the system* *Use Case Modeling, Kurt Bittner & Ian Spence, Addison- Wesley, 2003, pp

WIKPEDIA EXPLANATION OF USE CASES AND USE CASE SPECIFICATIONS  An excellent explanation of use cases and use case specificationsexplanation

Systems Use Case Specifications  Discussion of formal and informal use case specifications – Ambler Discussion  Discussion of the essential use case specification - Ambler Discussion

Systems Use Case Specifications  The systems use case specification must include: Who the actors are and how many of them are interacting with the system at any point in time What data is used and how All normal logic

The Use Case Specification  One of the best checks of whether a use case specification is finished is to ask if you could use the use case to derive system tests.  The best way to tell if the use cases fit the purpose is to pass them along to the…test team for test design.  If the team is satisfied that they can use the use cases to support this activity, then the use case specifications contain sufficient levels of detail.