Software Engineering the sp eleme

resultsin system
analysis other
Requirements with
e
interface
indicates software's (S-15,1 W-15,S15 o
must meet. createan
3.1 ANALYSIS MODELING modellingand
analysis how'tofulfillthe: anaysis noden
Software
GUgineer/developer
perform
should do
insteadof
tnat
representthe
reguirements
ianrcfhoirtemctuaaig3
software model
information of'what to createthe
modelingis
The basic aim of analysis translatedint
built. are
and behavior of the: systemtobe
informationofthe
system
These functions, behavior and
i design modeling.
and component tlevel designssin
3.1.1 Analysis Model diagrammaticforms to depict
Analysis model uses acombinationoftextandunderstand overall requirements of
behavior and Tünction so that it will be easv to
built or develop.
This model focuses functions that the software should perform, the behaviow it
requirehrenseonit,
on the
and the constraints that are applied on the software.
The model should focus on requirements that are visible withinthe problem or
Shout,
be written as a relatively high level of abstraction.
Each element of the analysis model should add to the understanding of
busines dolt
the
provide insightinto the information domain, function, and behavior of1the
Analysis model operates as alink between the 'system description' and the system. requiremen
In the
analysis model, information, functions and the behavior of the system design model!.
are translated into the is defined
architecture, interface and component level design in the and
Delay consideration of
functional models untilinfrastructure and other non descripton
'eesign model
design.
throughout the system. Be certain Minimize coupling pa
object
ta
ds

the analysis model

provides value to all stakeholders. Keep the
simple as possible. model as
oces
The analysis model
must Entty
primary objectives or goals:achieve the following three ationship, Data Data
reldiagram fow
diagram
1. To (W-18)
describe what are the dictionary
customer's requirements. customer requires ie.
2. To
establish a basis for the creation of a
design, and software State-transition
3. To diagram
define a set of
requirement
validated once, the software
The Fig.3.1
s which can be
is built or
trol sperhcato CSPEC)

Analysis
shows the structure of
Principles: analysis
developed.
4 modeling, Fig. 3.1
Thei
Model nf
s o rm
thatation domain of a
depict system problem must be
3. The
intormmustation,be functionrepresent
models, (and the problem): and ed understood.
and
in behavior should be
(or hierarchical) fashion.
4. The
analysis process should move partitioned a
manner that developed.
from essential uncovers detail in alaye
 3.3
Software Modeling and Design
Software Engineering
must be defined.
5. The functions that the software is to perform
external events) must be represented.
6. The behavior of the software, (as a consequence of
systematically.
By applyingabove principles, the analyst approaches a problem
(S-18)
3.1.2 Elements of the Analysis Model
Elements of analysis models are Flow-oriented Scenarlo-based Flow-oriented

modeling, Scenario-based modeling, Class elements elements

based modeling and Behavioral modeling as Use-case diagrans DFDs

Use-cases - text
shown in Fig. 3.2. Control-flow diagrarms
Activity diagrams
1. Flow-oriented modeling: Provides an
indication of how data objects are
transformed by a set of processing Analysis Model
functions.
Behavioral
Class-based
2. Scenario-based modeling: Represents the elements elements
system fromthe user's point of view.
Collaboration diagrams Sequence diagrams
3. Class-based modeling: Defines objects, Class diagrams State diagrams
ttributes, and relationships. CRC models
4. Behavioral modeling: Depicts the states of Analysis packages
the classes and the impact of events on
these states. Fig. 3.2: Element of Analysis Model
 all the features of a
class.
Inheritance is the process in which an object inherits some or
form.
superCa
5.
of objects to be used in more than one
A Polymorphismn is an ability
DESIGN MODEL
TRANSLATING REQUIREMENTS MODEL INTO
3.2 S-19, S-22, W-2
process model that is used. Beginnirg
Software design is applied regardless of the software
software design is the first of ..
software requirements have been analyzed and specified,
required to build and verify.
technical activities - design, code generation, and test - that are
ultimately results in valida
software. Each activity transforms information in a manner that
computer software. 3.3
Each of the elements of the analysis model provides information that is necessary to create the f.
design models required for acomplete specification of design.
1. The data/class design transforms analysis classes into design classes along with the #:
structures required to implement the software.
The architectural design defines the relationship between major structural elernents of .
software; architectural styles and design patterns help achieve the requirements defined for .
system
3. The interface design describes how the software communicates with systems that interoperat
with it and with humans that use it
4. The component-level design transforms structural elements of the software
architecture intt:
procedural description of software components
e
Software Engineering 3.5 Software Modeling and Design

The flow of information during software design is illustrated in Fig. 3.3.

description

ProcesSs sS
peci A
Component

Entity
relationship
diagram Data
dictionary
(ePcifSatiPonEC)
Data flow
diagram
level design

Interface
design

Architectural
design
State-transition
diagram
Specification (CSPEC\ Data design

Controi Analysis model Design model

into Design Model
Fig. 3.3: Translating Analysis Model (Requirement Model)
(S-16)
ATA MODELING