Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
32 views

Lesson 2

The document discusses modeling requirements using the Unified Modeling Language (UML). It describes use case diagrams, class diagrams, sequence diagrams, and state diagrams. Specifically, it covers: 1. A use case model describes system functionality through use cases that represent interactions between users and the system. Common use cases include login, registration, and order creation. 2. A use case includes general comments, requirements, constraints, and scenarios to describe its workflow and conditions. 3. Actors represent users or other systems that interact with use cases. Actors have access to specific use cases based on their role. 4. Sequence diagrams visually depict object interactions and information flow through messages over time.

Uploaded by

Karl Alvin Reyes Hipolito
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
32 views

Lesson 2

The document discusses modeling requirements using the Unified Modeling Language (UML). It describes use case diagrams, class diagrams, sequence diagrams, and state diagrams. Specifically, it covers: 1. A use case model describes system functionality through use cases that represent interactions between users and the system. Common use cases include login, registration, and order creation. 2. A use case includes general comments, requirements, constraints, and scenarios to describe its workflow and conditions. 3. Actors represent users or other systems that interact with use cases. Actors have access to specific use cases based on their role. 4. Sequence diagrams visually depict object interactions and information flow through messages over time.

Uploaded by

Karl Alvin Reyes Hipolito
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 29

Lesson 2

Modeling requirements
Unified Modeling Language (UML)

Use case diagrams

Class diagrams

Sequential diagrams

State Diagrams
Use Case Model

•The Use Case Model describes the proposed functionality of the new
system

•A Use Case represents a discrete unit of interaction between a user (human


or machine) and the system

•A Use Case is a single unit of meaningful work;


Use Case Model

•For example login to system, register with system and create order to all Use Cases

•A Use Case may ‘include’ another Use Case’s functionality or ‘extend’ another Use Case with
its own behaviour
Use Case Model

A Use Case description will generally include:

1.General comments and notes describing the use case

2.Requirements – Things that the use case must allow the user to do, such as
<ability to update order>, <ability to modify> & etc
What the Use Case Model may include
Constraints – Rules about what can and can’t be done. Includes

•Pre-conditions that must be true before the use case is run –e.g. <create order> must precede
<modify order>;

•Post – conditions that must be true once the use case is run e.g. <order is modified and
consistent>;

•Invariants: these are always true – e.g. An order must always have a customer number
What the Use Case Model may include
•Scenarios – Sequential description of the steps taken to carry out the use case. May include
multiple scenarios, to cater for exceptional circumstances and alternate processing paths;

•Scenario diagram – Sequence diagram to depict the workflow – as above but graphically
portrayed.

•Additional attributes such as implementation phase, version number, complexity rating,


stereotype and status
An Actor

•An Actor is a user of the system


•This includes both human users and other computer system
•An Actor uses a Use Case to perform some piece of work which is of value
to the business
•The set of Use Cases an actor has access to defines their overall role in the
system and the scope of their action
An Actor

•Actors can participate in a generalization relation with


other actors
An Actor

•Actors may be connected to use case only by associations


Use Case Model Example

•Here we have a Student interacting with Registrar and the


Billing System via a “Register for Courses” use case
Constrains, Requirements & Scenarios

•The formal specification of a Use Case includes:


•Requirements.
•These are the formal functional requirements that a Use Case must provide
to the end user. They correspond to the functional specifications found in
structures methodologies. A requirement is a contract that the Use Case will
perform some action or provide some value to the system
Formal Specifications for a Use Case
Formal Specifications for a Use Case
Sequence Diagrams
Elements of a Sequence Diagrams
Sequence Diagrams – Object Symbols
Sequence Diagrams – Message indicators
Sequence Diagram – Iteration Marker
Sequence Diagram - Example
Sequence Diagram – System Login Example
Activity Diagram
Activity Diagram
Activity Diagram
Activity Diagram
Activity Diagram
State Machine Chart
State Machine Chart Notations

There can be only one start state in a state diagram, but there maybe
many intermediate and final states.
State Machine – Course Selection

You might also like