0% found this document useful (0 votes)
41 views12 pagesSE Unit 3
Uploaded by
palaksirfmerihaiCopyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
0% found this document useful (0 votes)
41 views12 pagesSE Unit 3
Uploaded by
palaksirfmerihaiCopyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
/ 12
fining the Sof
sing Software solution
De ectural, an
“Architectural ar?
concept for data ject oriented de ign paradigm
svare Specificati
ir pesign approaches. Proves
fiware Measurement.
~~ A B&C
SECTION - A, B &
= Application of fundamental desig,
jens using software blue prin
wral desi
du Review of conformance
-reating design document
——————
er Questions
Very Short, Short & Long A Q
(3, 7.5 &15 Marks Eac! |
ortant parts
fer Stare Dose (b) Detailed design.
= ss through (4) preliminary (or high-level) Design
Software design is an iterative process through
which requirements are translated into a““blue print”
for constructing the software.
‘Software design must deal with transforming | the:
‘customer requirements, as described in SRS into a
form that is implementable using a programming
language.
The following items must be designed during the
design phase
> Different modules required to implement the
design solution.
> Control relationship among the identified
modules
> Interface among different modules,
> Data structures of different modules.
* Algorithms required to implement different
‘modules.
Hey ee oreo design phase is to take the
locument as input and produce above
‘mentioned documents before c i
ir ‘ompletion of design
2. What are the design activities ?
he ; Imp. [3 Marks
'. good software design is seldom achieved
usinga singe ste
emia Procedure but requires several
8CA Vth Semester/ Software "gineering Units w 96
lester/ Engineering 7
.
‘By high-level design, we would mean identification
of different modules, the control relationships ang
the definitions of interfaces among them. Many
different types of notations have been used to
represent a high-level design.
‘A popular way is to use a tree-like diagram called)
the structure chart to represent the control}
hierarchy in high-level design.
(b) Detailed Design :
During detaile design, the data structure and the
algorithms of different modules are designed, The’
outcome of the detailed design stage is usually|
known as the module specification document. |
Q3. What are the characteristics of,
t a
software design? Imp. [3 ert
i The notion of goodness of a design itself varies |
widely across software engineers and!
academicians. The
Boodness of a design is
dependent on targeted application, s |
pie characteris 's of good design are |
; ea ‘800d design should correctly
Mall the functionalities ofthe system.
Understandabili
lity: A :
beeasiy Under goed design should
Efficieney : It shoulg be efficient,
> BCA Mth Somoster/
} "Ain / Software Engineering / Unie 37
iatulnability © It should be easi
Mall eh ipaherah Id be easily representation ofa ys which can be used later
\ © anonable ‘o build that system. The produced model is call
the ‘design’ ofthe system. The design of a system
D a, state the Design Principtes. Inemsemaly a'btnspriat”ora’pla’ fora sro
4 : Imp. 3 Marks} forthe systern
’ a Principles
an ean Pn ae ts to fol The goal of the design phase is to transform the
rhe design process needs to follow certain requirements specified in the SRS document into a
principles ant practices in order to be effective ‘ ; Necuiameae
ciples state
These P
4 Adsign should cle
ly be verifiable, complete,
-onsistent, efficient and simple
traceable
«The design architectural structy
sutfer from “lack of vision’
€ should not
A good design pl
ust consider all the possible design approaches,
judging each against system requirements,
availability of resources and the identified system
constrain
+ An ide hould not reinvent the
wheel : If reusable design components are
available within a system, Then, they must be
used, instead of wasting precious time and efforts
involved in recreating them.
«The design should exhibit uniformity :The design
process should follow the design standards for
coding, presentation etc
is not coding and coding is not design :
The design decision made at the coding level
the small implementation details that
enable the procedural design to be coded.
} «The design must be readable : It should be an
tw understandable guide for those who generate the
design code and also for those who list and
maintain the system thereafter.
@ + The design should be reviewed to minimise
'® conceptual errors: The designer must necessarily
© checkall the conceptual elements of design such
® as ambiguity, omission, and see that
F inconsistencies have been taken care of before
worrying about the syntax of the design model.
s
design proc
¢ Q5. Explain Design phase. [3 Marks}
i Ans. Design Phase :
¥ Design in software engineering is essentially the
bridge between requirements specification and the
final solution for satisfying the requirements. The
2 Boal of the design process is to produce a model or
structure that is suitable for implementation in some
programming language. During the design phase the
software architecture is derived from the SRS
document. Software design is a process to
conceptualize the software requirements into
software implementation, Software design takes the
User requirements as challenges and tries to find
optimum solution.
Q6. What are the approaches to software
design? V. Imp. [3 Marks]
Ans. Software Design Approaches
There are fundamentally two different approaches
to software design —
(@) — Function-oriented design
Gi) Object-oriented design
Function-Oriented Design =
In this approach, a system is viewed as something,
that performs a set of functions. Starting at this high
level view of the system, each function is
successively refined into more detailed functions. The
system state is centralized and shared among different
functions
‘Several function-oriented design approaches have
been developed. For example:
> Structured design by Constantine and Yourdon
(1979).
> Jackson's structured design by Jackson
(1975).
Object-Oriented Design :
Inthe object-oriented design approach, the system
is viewed as a collection of objects (i.e., entities)
The system state is decentralized among the objects
tnd each object manages its own state information.
Objects have their own internal data which define
their state. Object is a member of some class. Classes,
‘may inherit features from super class. Conceptually,
objects communicate by message passing, ‘aca Mth Semester / Softwar
nderstand by
Q7. What do you UnQr Ts Marks!
Structured Design?
Ans, Structured Design +
Structured design isa “
methodology. The approach begins with a sett
specification that identifies inputs and outputs aE
describes the functional aspects of the system. The
system specifications are then used asa bass OF
the graphic representation-data flow diagram |
data and processes. From the DFD, the next step
is the definition of the modules and their
relationships to one another in a form called
structure chart using a data dictionary and other
structured tools.
‘Structure design partitions a program into small
independent modules. tis an attempt to minimize
complexity and make a problem manageable by sub-
dividing it into smaller segments which is called
modularization or decomposition.
data-flow based
Q8. What is Structure chart ?
Ved. [3 Marks}
‘Ans, The aim of structured design isto transform
the results of structured analysis into a structure
chart.
A structure chart represents the software
architecture which means various modules making
up the system, the module dependency, and the
parameters that are passed among the different
modules
‘The main focus ina structure chart representation
is on the module structure of a software and the
interaction among the different modules.
In any structure chart, there is one and only one
‘module at the top called the root.
+ Q9. What are the basic building blocks of
structure chart? Imp. [3 Marks]
Ans. Basie Building Blocks of Structure Chart:
«* Rectangular Box : Represents a module. It is
annotated with the name of the module it
represents.
A
+ Arrow : An arrow connecting 2 module implies
that during program execution, control is passed
‘from one module to the other in the direction of
ve Engineering /Unit lt / 38
connecting arrow.
«Data Flow Arrows : Represents that the n
lata passes from one module t0 the ther in
direction of the ar
|
«Library Modules : Library comprises th
aaa Med codelee and Te otf
represented by a rectangle with double edges, | @
|
|
|
x
ad
is
w
as
w
a
« Selection: Shown by diamond symbol represent
that one module or several modules connected wil
diamond symbol isare invoked depending ont!
condition satisfied.
‘+ Repetition : A loop around the control flow arrows
denotes that the respective modules are invoked!
repeatedly.
A
of
Q10. Give the hierarchical form:
at of
Structure chart Temp rk
Ans. Hierarchical Format of Structure Chart :
The hierarchical format of a structure chart is
shown using an example where custamer’s safety
deposit file is to be updated.
D BCA IVth Semester/ Software Engineering / Unit /™ 39
Uae Sue Deport]
Customer ite |
Vilidated
wie
go Feansaction
aS) s4\ & Up
sO £4 > rated
Siew Gi a OSS
the vais) < File =
the Get Valid Get New Validate Update
ate Deposit Transaction Transtction Sale Deposit
ner File - e 7 Customer File
4 Transaetion aa
Read 9 ai
rransactions Read % OK
fee Transaction], “p>
Read from Edit 0 TNerify
Transaction Transaction | -
Pi
Tape Syntax
ina in )
leg Inany structure chart, there is one and only one module atthe top, called the root. There is at mostone
central relationship between any two modules i the structure chart. This means that if module A invokes
module B, module B cannot invoke module A. The programmer may’ use predefined library modules.
Thisis indicated in the structure chart by a rectangular box with double vertial lines.
Q14. List the basic elements of structure chart. V Imp, [3 Marks]
rem, Ats: Basie Elements of Structure Chart:
‘reps "Module + A module is a contiguous set of statements. It can categorised into few classe:
“Ase Input Mode: They oan information fo thst anton paso tse
digs
ff.
©
Input] Superiordinate
Module
« Output Module: They take information from their superiordinate and passion o its subordinates
Data
tone oa
i Superiordinate [Output
" Module
« Transform Module : Transform data into some other form.
Transform
Module
orm « Coordinate Module : Manages the flow of data to and from different subordinates,
3!
feo Coordinate
my Module
& = Composite Module ¢
Connection : It is represented by #
module.
Couple : It is represented by an arrow with a
module to another.
Q12. Briefly explain modular design.
Ans. A modular design involves decomposi
divide and conquer approach.
‘A modular design reduces complexity,
encouraging parallel development of different parts
Functional independence is a key to good design an
It is a com!
ination of above all modules.
veetor linking.
ition of a problem
facilitates cht
tative criteria :
Independence is measured using two qualitative a
(@) Cohesion : It is a measure of the relative functional strength of modi
(b) Coupling : It is a measure of relative strength of the modules.
Q13. Differentiate between cohesion, coupling and adaptability.
+ modules. It means one module has called ang,
Jar trail. It represents data items moved from gy
circular
Im. 13 Mary
n into modules, then arranging them usin
ange and results in easier implementation
vofasystem. Independent modules are easy to many
id design is the key to software quality,
V. Imp. [3 Mar
Ans.
Cohesion Coupling ‘Adaptability -
Tt is a property _or| It isa property of a collection of | It is a property by virtue of
characteristics of an individual | modules. which a software becomes
module adaptable to changes that occur
after its development.
Tris @ measure of strength of
Ttis measure of the degree of the
Itis a measure of the degree of
| instruction in a module relate
to a single function is called
cohesion,
Tt is also called intramodule
cohesion,
interdependent is called coupling,
Kt is also called intermodule
coupling.
the association of elements | interdependence between | change that a software can
within a module modules handle after implementation
‘The extent to which all [The extent to which modules are
The extent to which software
can be modified or enhanced
due to internal or extemal
factors during maintenance is
called adaptability.
The greater the adaptability of
software, the better itis,
Cohesion “in modules should
Coupling.
a software procedures,
requiring little interaction with
procedures being performed in
‘other parts of a program.
complexity between modules, the
Point at which entry or reference
4s made to a module and whee
data pass across the interface
between modules
be maximized | should be minimised, :
performs a single task within [It depends on the interface [It upgrades or enchance the
software to provide _ more
services, | ano,
mo
"Man,
™ Usp
ation 5
aint,
\
4. Briefly explain the process,
ented design. oss sofa:
‘ans. The Process of Object-Oriented Design
‘sep 1 # Partition the analysis model tent
wen
Step 2: KentifyConcureney, thats dictated by
the problem.
‘ep 3 : Allocate subsystem to processors and
tasks
step 4: Develop a design forthe user interface.
sep $ Choose abasic strategy for implementing
the data management
‘Step 6 : Identify global resources and thecontrol
mechanisms required to access them
‘Step 7: Design an appropriate control mechanism
forthe system, including task management.
‘Step 8: Consider how boundary condition should
behandled.
‘Step 9 : Review and consider trade-offs,
Q15. Give design issues for object-
oriented para ‘Imp. [3 Marks]
Ans. Design Issues for object-oriented
paradigan:
‘There isajudging method for designing ability to
achieve modularity and relate these to object
oviented design
© Decomposability : The facility with which a
design method helps the designer to decompose
a large problem into subprograms that are easier
to solve,
Composabil
ty + The degree to which a design
method ensures that program component, once
designed and built, can be secured to create ther
system.
Understandability : The case with which a
program component can be understood without
reference to other information or other module.
Continuity : The ability to make small changes
ina program and have these changes manifest
themselves with corresponding changes in just
fone or a very few modules.
Protection : An architectural characteristic that
will reduce the propagation of side effects, if
an error does occur in a given module.
Q16. Briefly explain design review.
imp [3 Marks
Ans. Design Review : - 7
After a design is complete, the design is required
to be reviewed. The review team usually consists
‘of members with design, implementation, estingand
maintenance. Perspectives, who may or may not
be the members of the development team, The
members of team would code the design, and test
the code, analysts and maintainers attend the review
meeting. The review team checks the design
documents for the following
Traceability : The members of the team check
‘whether each bubble of the DFD can be traced to
‘ome module in the structure chart and vice-versa.
Correctness : They check whether all the
algorithms and data structures of detailed design
are correct
Maintainability : They check whether design
‘can be easily maintained in future.
Implementation : They check whether design
can be easily and effectively implemented
Q17. List the fundamental design
principles for designing of large system.
Imp. 17.5 Marks}
‘Ans. Proceeding the design of large system can be
an extremely complex task. For this we have also
used following design principles :
‘+ Problem Partitioning : When solving small
problem, entire problem can be solved at once.
But its not same with large problem For large
complex problem, “Divide and conquer” approach
isused. The principle means, “divide into smaller
pieces so, that each piece can be conquered
separately.” Partitioning decomposes a problem
into constituent parts. The different pieces
cooperates and communicate in order to solve
the problem. The hierarchical representation of
function is established and then partition is done.
Two types of partitioning can be “vertical
partitioning” and “horizontal partitioning”,
« Abstraction : is a tool that permits a designer to
considera component at an abstract level without
worrying about detail of implementation of
component. An abstraction of a component ———==——————
cA Ith Semester Software Engineering /Unitl/ 42
he internal details that produce
functional abstraction”
tes the external behaviour ofthat component without bother
describes the exte ering te nt
tpchaviour. Two common abstraction mec
Jap-town and Bot highest level component of
hierarchy and proceeds thro
up Design : Top-down design stars from the
aac level This approach stars by identifying the major components
aera ccomposing them int thei lower level component and iterating until the desired evel
crdetad is achieved, Whereas, bottom-up design starts with lower level component of hierarchy and
proceeds through progressively higher eels totop-level components, This approach tarts with designing
Frost basic or primitive component and then proceeds to higher level component that use lower level
component.
« Modularity A system is considered tobe modula iit consists of disrete component, so that each
component Sonera ety and chaige to one component has minimal impact on other
component can be implemented separately and change t0one ©
component. Tis independence is measured using and qualitative criteria. cohesion and coupling
Q18. Briefly explain Cohesion. V. Imp. [7.5 Marks}
Ans. Cohesion
Cohesion of module represents how tightly bound the internal elements of the module are 10 one
idea, about whether the different element of a module
another. Cohesion of a module give the designer a i : if
the greater the
belong together in the same module. Cohesion and coupling are clearly related. Usually,
lower the coupling between the modules.
coh
jon of each module in the system, t
Classification of Cohesiveness +
‘The different classes of cohesion that a module may possess are depicted in following figure =
Functional
Coincidental | Logical | Temporal | Procedural | Communicational | Sequential
Low) > igh
Figure : Classification of Cohesion
These classes of cohesion are elaborated below
Coincidental Cohesion : A module is said to have coincidental cohesion, if it performs a set of tasks
that related to each other very loosely, if at all. In this case, the module contains a random collection of
functions. Its likely that the functions have been put in the module out of pure coincidence without any
thought or design
Logical Cohesion : A module is said to be logically cohesive, if all elements of the module perform
similar operations, example error handling, data input, data output, ete. An example of logical cohesi
the case where ast of prin irtion generating dierent output reports are aranged inf a sng
Temporal Cohesion : When a module contains functions that are related by the fact that all the
fenetions must be exceed inthe sane ine span the modules ad to exhibit temporal cohesion. The
set of functions responsible for initialization, start-up, shut-down of some process,
mitt ation, start-up, shut-down of some process, etc. exhibit tempor
Procedural Cohesion : A module is said to possess procedural coh
i Ss procedural cohesion, if the set of functions of he
rodule areal part of procedure (algorithm) in which cena sequence of eg ceauaee
achieving an objective, example the algorithm for decoding amessage, PO PecarTied om
Commuakadosel Gabon: Ameae aa eae
of the module refer to or update the same data structure,
array or a stack. :
m cohesion, if all the functions
example the set of functions defined on 2°
oil
i
we
Use
types.
ts. €0
coupling
ltpende
dept
Modu
tec
le,
Pees
Mls
been 1
le
he
tan
fom
ions
singe
AL the
spot
oft
ont
sai
Lott
BCA Mth Semester / Software Enginee
sequential Cohesion : A module is sid to
canes sequential Cohesioh, if the elements of a
reste frm the PUG of a sequence, wee a
