Page 151 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Unit 6: Functional Design

8. Pseudo code can replace ……………….. Notes
(a) flowcharts (b) structure charts
(c) decision tables (d) cause-effect graphs

9. The inter-transformation of the requirements models of abstraction to the design models
of abstraction is shown as the …………...

(a) horizontal arrow (b) vertical arrow
(c) Both of these (d) None of these.
10. A top-down model is often specified with the assistance of “…………….”, these make it
easier to manipulate.
(a) green boxes (b) black boxes

(c) white boxes (d) None of these.
11. In this approach testing is conducted from …………………..
(a) sub module to main module (b) main module to sub module

(c) Both of these (d) None of these.
12. The processes are shown by named circles and data flows are represented by named
arrows entering or leaving the ………………

(a) square (b) bubbles
(c) rectangle (d) None of these.

13. A Structure Chart (SC) in software engineering and organizational theory, is a chart which
shows the …………. of a system to its lowest manageable levels.
(a) step-down (b) up-down

(c) break-down (d) None of these.
14. Abstraction in software engineering where we aim to reduce complexity is certainly not
just limited to the domain of software design.
(a) True (b) False
15. The heuristics are written as hard and fast rules.

(a) True (b) False

6.12 Summary

• A functional design assures that each modular part of a device has only one responsibility
and performs that responsibility with the minimum of side effects on other parts.

• At lower levels of abstraction, a more procedural orientation is taken. Problem-oriented
terminology is coupled with implementation- oriented terminology in an effort to state a
solution.
• Abstraction in software analysis, design and development is to reduce the complexity to
a certain level so that the “relevant” aspects of the requirements, design and development
may be easily articulated and understood.
• Modularity, that is, software is divided into separately named and addressable components,
often called modules that are integrated to satisfy problem requirements.

LOVELY PROFESSIONAL UNIVERSITY 145