business processes

A graphical representations of problems to be solved

new proposed product
describe software requirements
establish a basis for the
Requirements/Analysis Objectives creation of a software design
Model define a set of requirements
that can be
validated
software
specification
Bridges the gap between analysis model
design model

information domain of a problem

must be represented and
understood
functions that the software
performs must be defined.
behavior of the software must
be represented
models must be partitioned
analysis task move from
essential information toward
implementation detail
Requirements Modeling visible within the problem or
Principles business domain
add to an overall
understanding
information domain
Arlow and Neustadt in
provide insight , function and behavior of the
Rules of Thumb Pressman (2009):
system
provides value to all
stakeholders
Keep the model as simple as
possible

identification, analysis, and specification of

common requirements from a specific Donald Firesmith in
application domain Pressman (2009):
Module 3: Requirements Engineering
Defining the domain (part 4)
Collecting sample of Involves Represents how data objects are
applications transformed as they move through the
What is Domain Analysis system
Analyzing each application
use DFD as diagramatic form
Developing an analysis model Flow-oriented Modeling Pressman (2009):
used to supplement other
descriptions of a product and analysis model elements
its environment
Domain Analysis
supplemented with
detailed-level models Context (conceptual-level)
modeling
. E.g.: Architectural model
usable to non-technical
people and decision-makers use-case diagram
show how end-users interact
processes that transform Scenario-based with the system example : activity diagram
the data as separate
entities swim-lane diagram
two main levels Requirements Analysis Modeling
Includes data models, specify classes and objects, attributes, class diagram
data flow models and Structured Analysis Classifications of OO operations, and associations and collaboration diagram
behavioral models modeling elements Class-based dependencies example:
OO Analysis Approach (Pressman, 2005): class responsibility
E.g.: ERD, DFD, state collaborator (CRC) model
machine model
model objects, classes, and the Technical (detailed-level)
two main levels modeling
relationships and behavior associated with event-driven use case
how the system reacts to
them Behavioral state diagram
external event example:
known as Unified Modelling
sequence diagram.
Language (UML)
use-case diagrams Object-oriented Analysis
activity diagrams (swim-lane
diagram)
eg:
sequence diagram
class diagram
state diagram