1.

THE TRADITIONAL APPROACH is often referred to as structured system

development.
a. True.
b. False.
2. Which of the following techniques that make up the structured approach.
a. Structured analysis.
b. Structured design.
c. Structured programming.
d. All the previous.
3. …. Is system development using structured analysis, structured design, and
structured programming techniques.
a. Structured approach.
b. Structured program.
4. …. Is a program or program module that has one beginning and one ending,
and for which each step in the program execution consists of sequence,
decision, or repetition constructs.
a. Structured approach.
b. Structured program.
5. Top-down programming divides more complex programs into a hierarchy of
program modules.
a. True.
b. False.
6. Structured design technique requires the designer to know how the system
should do?
a. True.
b. False.
7. The … approach, views an information system as a collection of interacting
objects that work together to accomplish tasks.
a. Object-oriented.
b. Structured.
8. In object-oriented approach the system consists of objects?
a. True.
 b. False.
9. … defines all of the types of objects that do the work in the system and
shows what user interactions, called use cases, are required to complete
tasks.
a. Object-oriented analysis (OOA).
b. Object-oriented design (OOD)
c. Object-oriented programming (OOP).
10. … defines all of the additional types of objects necessary to
communicate with people and devices in the system, shows how the objects
interact to complete tasks, and refines the definition of each type of object
so it can be implemented with a specific language or environment.
a. Object-oriented analysis (OOA).
b. Object-oriented design (OOD).
c. Object-oriented programming (OOP).
11. … consists of writing statements in a programming language to define
what each type of object does.
a. Object-oriented analysis (OOA).
b. Object-oriented design (OOD).
c. Object-oriented programming (OOP).
12. Which of the following from structured approach conceptual design?
a. ERDs.
b. DFDs.
c. FDCs.
d. All the previous.
13. Which of the following from object-oriented approach conceptual
design?
a. Use case diagrams.
b. Class diagrams.
c. Both.
14. Which of the following from structured approach logical design?
a. Tables (relations).
b. Columns (attributes)
 c. Primary & foreign keys
d. All the previous.
15. Which of the following from object-oriented approach logical design?
a. Object definition language (ODL).
b. ERD.
c. DFD.
16. Which of the following from structured approach physical design?
a. Files.
b. Records.
c. Fields.
d. Pointers.
e. All the previous.
17. Which of the following from object-oriented approach physical design?
a. Class definitions.
b. Tables.
c. Columns.
18. Requirements are descriptions of how the system should …
a. Behave.
b. Application domain information.
c. Constraints on the system’s operation
d. Specifications of a system property or attribute.
e. All the previous.
19. A ... is a statement of need, something that some class of user or other
stakeholder wants.
a. Requirement.
b. Files.
c. Fields.
20. Why is Requirements Engineering Important?
a. Identifies stakeholder needs to ensure that you are building the right
system.
b. Help you manage the development process to ensure a quality system.
c. Identify defects early, reducing costs.
 d. All the previous.
21. What are the consequences of poor or incorrect requirements are?
a. System delivered later than planned.
b. System cost more than planned.
c. Customers and end-users unsatisfied.
d. Maintenance related costs higher.
e. System is unreliable or does not work.
f. All the previous.
22. What are the Reasons for Poor Requirements?
a. Not well understood.
b. Requirements do not reflect the real needs of the customer.
c. Misunderstanding between various stakeholders.
d. Expensive to make changes to requirements after they have been
agreed upon.
e. Requirements evolution: existing system enhancement not clear.
f. Requirements could be incomplete, ambiguous, inconsistent,
overlapping, not implementable, ...
g. All the previous.
23. Types of requirements.
a. Functional (Behavioral) requirements
b. Non Functional (Non-Behavioral) requirements
c. Both.
24. Functional (Behavioral) requirements specify…
a. The function that the system should provide.
b. How the system should react to particular inputs.
c. How the system should behave in particular situations.
d. All the previous.
25. Non Functional (Non-Behavioral) requirements describe…
a. Constraints on the services or functions offered by the system.
b. Constraints on the development process, standards, etc.
c. Both.
26. … sets out in broad terms what the system should do
 a. General requirements.
b. Functional requirements.
c. Data requirements.
d. Implementation requirements.
27. … define system’s functionality.
a. General requirements.
b. Functional requirements.
c. Data requirements.
d. Implementation requirements.
28. … define the type of data the system shall operate upon or produce.
a. General requirements.
b. Functional requirements.
c. Data requirements.
d. Implementation requirements.
29. … states how the system must be implemented.
a. General requirements.
b. Functional requirements.
c. Data requirements.
d. Implementation requirements.
30. … specify the minimum acceptable performance of the system.
a. Performance requirements
b. Usability requirements
c. Operational requirements
31. ... state user interface and system availability constraints.
a. Performance requirements
b. Usability requirements
c. Operational requirements
32. ... specify constraints that should be satisfied during system usage.
a. Performance requirements
b. Usability requirements
c. Operational requirements