0% found this document useful (0 votes)
13 views

Week 4 - Modeling System Requirements

Uploaded by

gieron diwa
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
13 views

Week 4 - Modeling System Requirements

Uploaded by

gieron diwa
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

ADVANCED SYSTEMS DESIGN AND

IMPLEMENTATION
Module 4: Modeling System Requirements
Modeling System Requirements
In this module we will discuss:
• Use Case modeling
• Conceptual modeling
• Other modelling tools
Use Case Modeling
Use-case modeling goes together well with traditional
systems and design tools like data and process modeling. It also
provides great help on architectural and interface design decisions
as well as other activities such as system testing and project
management.

Use-case diagram
It is a diagram used to graphically represent the system as
a gathering of use cases, users (actors) and relationships.
Use Case Modeling
Use-case Narrative
It is an entity that uses textual illustration of
business events and how users will interact with the
system to complete a single or multiple tasks. It also
identifies system events and its interaction with the
users.
Use Case Modeling
Use Cases
These are tools used by use-case modeling to
portray system tasks performed by external users, also
known as actors in the approach they understand.

4 types of actors:
Primary Business Actor
Primary System Actor
External Server Actor
External Receiver Actor
Use Case Modeling
Relationships
Relationships are connections between the
symbols in a use-case diagram.

Relationships on Use Case Diagram


• Associations
• Extends
• Uses (or Includes)
• Depends On
• Inheritance
Associations
Extends
Uses (or Includes)
Depends On
Inheritance
Use Case Modeling
Requirements Use-Case Modeling Process
When preparing the models, every analyst
must not fall into state of over-analyzing (analysis by
paralysis). Systems analysts must act fast, but not all
the requirements can be extracted during the analysis
phase.
Use Case Modeling

Steps on how to produce models

1. Identify business Actors.


2. Identify business requirements use cases.
3. Construct use-case model diagram.
4. Document business requirements use cases.
Conceptual modeling
Concepts are used to simulate models inside the
system, which are represented by physical objects. The
name of conceptual models was formed after
conceptualization phase. There is also a type of
conceptual model called CAM or conceptual agent
model, this type of methodology uses agents as a
feedback system.
Object Oriented Analysis
Object Oriented Analysis is a procedure in systems
development to identify software design and
engineering requirements through objects. An object in
OOA represents actual business interactions that
incorporate data and functions.

Many analysts are also using a general purpose


language called Unified Modeling Language (UML). It
is used to envision the design of the system. Many are
considering that UML as a key factor in object-oriented
software development because it allows system
developers to clearly view the system as a whole.
Object Oriented Analysis
According to the creators of UML Version 2.0, every object
oriented approach to develop an information system must be:

• Use Case Driven


• Architecture Centric
• Iterative and Incremental
Thank You.

You might also like