Unit 1-Introduction to S/W Engineering and S/W Process Models

1.What is software Engineering?

• Designing a software
  
  

• Testing a software

• Application of engineering principles to the design a software

• None of the above

3.Model selection is based on __________.

• 1. Requirements

• 1. Development team & users

• 1. Project type & associated risk

• All of the above

2.What is the first step in the software development lifecycle?

• 1. System Design
     

• 1. Coding

• 1. System Testing

• 1. Preliminary Investigation and Analysis

4.Which of the following activities of the generic process framework delivers a feedback report?

• 1. Deployment

• 1. Planning

• 1. Modeling

• 1. Construction

5.Which of these is not one of the phase names defined by the Unified Process model for software development?

• • Inception phase

• • Elaboration phase

• • Construction phase

• • Validation phase

6.The spiral model of software development

• • Ends with the delivery of the software product.

• • Is more chaotic than the incremental model.

• • Includes project risks evaluation during each iteration

• • All of the above

7.The concurrent development model is

• • Another name for concurrent engineering.

• • Defines events that trigger engineering activity state transitions.

• • Only used for development of parallel or distributed systems.

• • Both a and b

8.The prototyping model of software development is

• • A reasonable approach when requirements are well defined.

• • A useful approach when a customer cannot define requirements clearly.

• • The best approach to use for projects with large development teams.

• • A risky model that rarely produces a meaningful product.

9.The incremental model of software development is

• • A reasonable approach when requirements are well defined.

• • A good approach when a working core product is required quickly.

• • The best approach to use for projects with large development teams

• • A revolutionary model that is not used for commercial products.

10.The waterfall model of software development is

• • A reasonable approach when requirements are well defined.

• • The best approach to use for projects with large development teams

• • A good approach when a working program is required quickly.

• • An old fashioned model that is rarely used any more