SEPM – MODULE 2 Ch 2 : Requirement Analysis

MODELLING CONCEPTS
DATA MODELING CONCEPTS
 The entity-relationship diagram (ERD) addresses these issues and represents all data
objects that are entered, stored, transformed, and produced within an application
 1 Data Objects : A data object is a representation of composite information that must
be understood by software. By composite information, I mean something that has a
number of different properties or attributes
 2 Data Attributes Data attributes define the properties of a data object and take on one
of three different characteristics. They can be used to (1) name an instance of the data
object, (2) describe the instance, or (3) make reference to another instance in another
table. In addition, one or more of the attributes must be defined as an identifier—that
is, the identifier key
3 Relationships : Data objects are connected to one another in different ways. Consider the two data
objects, person and car.
OBJECT
ORIENTED
ANALYSIS
 Object-Oriented Analysis and Design
(OOAD) is a software engineering
methodology that employs object-
oriented principles to model and
design complex systems. It involves
analyzing the problem domain,
representing it using objects and their
interactions, and then designing a
modular and scalable solution.
 some important aspects of OOAD:
1. Object-Oriented Programming: Object-oriented programming involves modeling
real-world objects as software objects, with properties and methods that represent the
behavior of those objects.
2. Design Patterns: Design patterns are reusable solutions to common problems in
software design.
3. UML Diagrams: Unified Modeling Language (UML) is a standardized notation for
creating diagrams that represent different aspects of a software system.
4. Use Cases: Use cases are a way of describing the different ways in which users interact
with a software system.
SCENARIO-BASED MODELING
 Although the success of a computer-based system or product is measured in many ways,
user satisfaction resides at the top of the list.
 Requirements modeling with UML6 begins with the creation of scenarios in the form of use
cases, activity diagrams, and swimlane diagrams
 1 Creating a Preliminary Use Case : “[Use cases] are simply an aid to defining what exists outside the
system (actors) and what should be performed by the system (use cases). ”
 use case describes a specific usage scenario in straight forward language from the point of view
of a defined actor. But how do you know (1) what to write about, (2) how much to write about
it, (3) how detailed to make your description, and (4) how to organize the description?

 Developing Another Preliminary User Scenario The scene: A meeting room, during the second
requirements gathering meeting.
 2 Refining a Preliminary Use Case A description of alternative interactions is
essential for a complete understanding of the function that is being described by a
use case. How do I examine alternative courses of action when I develop a use
case?
 3 Writing a Formal Use Case : Use case: Access camera surveillance via the
Internet—display camera views (ACS-DCV). The ACS-DCV use case shown in
the sidebar follows a typical outline for formal use cases.
UML MODELS THAT SUPPLEMENT
THE USE CASE
 There are many requirements modeling situations in which a text-based model— even
one as simple as a use case—may not impart information in a clear and concise
manner. In such cases, you can choose from a broad array of UML graphical models.
 1 Developing an Activity Diagram The UML activity diagram supplements the use
case by providing a graphical representation of the flow of interaction within a
specific scenario.
 2 Swimlane Diagrams The UML
swimlane diagramis a useful variation
of the activity diagram and allows you
to represent the flow of activities
described by the use case and at the
same time indicate which actor (if there
are multiple actors involved in a
specific use case) or analysis class
(discussed later in this chapter) has
responsibility for the action de scribed
by an activity rectangle.
FLOW-ORIENTED MODELING
 Although data flow-oriented modeling is perceived as an outdated technique by some software engineers, it
continues to be one of the most widely used requirements analysis notations in use today Although the data flow
diagram (DFD) and related diagrams and information are not a formal part of UML, they can be used to
complement UML diagrams and provide additional insight into system requirements and flow.
 1 Creating a Data Flow Model The data flow diagram enables you to develop
models of the information domain and functional domain.
 2 Creating a Control Flow Model For some types of applications, the data model and
the data flow diagram are all that is necessary to obtain meaningful insight into
software requirements. How do I select potential events for a control flow diagram,
state diagram, or CSPEC?

 3 The Control Specification A control specification (CSPEC) represents the behavior

of the system (at the level from which it has been referenced) in two different ways.3
The CSPEC contains a state diagram that is a sequential specification of behavior. It
can also contain a pro gram activation table—a combinatorial specification of
behavior.
1. CLASS BASED MODELING
2. CREATING A BEHAVIORAL MODEL
 SLT
------ *---------*--------- MODULE 2 ------ *---------*---------

THANK YOU