1. ––––––––– software is designed to be sold on open
market.
(a) Custom software
(b) Generic software
(c) Embedded software
(d) None of these

2. ––––––––– are also known as clients.
(a) Customers              (b) Users
(c) Developers             (d) Managers

3. ––––––––– is a process by which a software
engineer learns background information.
(a) Domain analysis
(b) Requirement analysis
(c) Specification analysis
(d) Information analysis

4. ––––––––– is a statement about what the
proposed system will do.
(a) Task                                  (b) Order
(c) Requirement                   (d) Interface

5. ––––––––– is used to show how two classes are
related to each other.
(a) Association               (b) Generalization
(c) Multiplicity                (d) None of these

6. Aggregations are specified using a –––––––––
symbol.
(a) rectangle                 (b) circle
(c) diamond                  (d) line

7. In ––––––––– design, you start with very high
level structure of the system.
(a) top-down               (b) bottom-up
(c) architecture          (d) class

8. ––––––––– occurs when there are inter
dependencies between one module and another.
(a) Cohesion              (b) Coupling
(c) Utility                    (d) Network

9. ––––––––– chart shows the sequence in which
tasks must be completed.
(a) PERT                        (b) Gantt
(c) Earn value               (d) None

10. ––––––––– is the process of deciding the sequence
a set of activities will be performed.
(a) Scheduling                   (b) Tracking
(c) Testing                           (d) Planning