Page 68 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING
P. 68
Principles of Software Engineering
Notes 11. The testing that focuses on the variables is called:
(a) Black box testing (b) White box testing
(c) Data variable testing (d) Data flow testing
12. Which is not a step of requirement engineering?
(a) Requirements elicitation (b) Requirements analysis
(c) Requirements design (d) Requirements documentation
13. What types of models are created during software requirements analysis?
(a) Functional and behavioural (b) Algorithmic and data structure
(c) Architectural and structural (d) Usability and reliability
14. If every requirement can be checked by a cost-effective process, then the SRS is:
(a) Verifiable (c) Traceable
(c) Modifiable (d) Complete
15. Requirements can be refined using:
(a) The waterfall model (b) Prototyping model
(c) The evolutionary model (d) Spiral model
3.6 Summary
• Software testing is “the process of analyzing a software item to detect the differences
between existing and required conditions (that is, bugs) and to evaluate the features of
the software items.
• A state of a system represents some conditions about the system.
• The SRS is to be validated and the feedback from the validation activity may require
further analysis or specification.
• The object-oriented model is based on a collection of objects. An object contains values
stored in instance variables within the object.
• The object oriented design converts the object oriented analysis model into a design model.
This serves an outline for software construction.
• The prototype is constructed to learn about the software problems and their solutions in
successive steps. The prototype is initially developed to satisfy few requirements.
• The general trends among software developer shows that they have over dependence on
CASE tools.
• A requirements specification for an information system is important for several reasons;
it serves as a means of communication between the user and the systems developer.
3.7 Keywords
Consistent: System functions and performance level must be compatible and the required quality
features (reliability, safety, security, etc.) must not contradict the utility of the system.
Data Flow Diagrams: It is a graphical representation of flow of data through a system. It pictures
a system as a network of functional processes. The basis of DFD is a data flow graph.
62 LOVELY PROFESSIONAL UNIVERSITY