Chapter 2

Question 1

4 core software activities

Answer 1

Specification
Design and implementation
Validation
Evolution

Question 2

What does process descriptions target, besides technical aspects like data model, user interface? (3 important aspects)

Answer 2

Products created by the software
Roles given to the users
Pre- and post- conditions for procesess activities and product creation

Question 3

2 main software processes types

Answer 3

Plan-driven
Incremental/Agile

Question 4

3 software process models

Answer 4

Waterfall (plan-driven)
Incremental (step-by-step)
Integration and configuration (component/software reuse)

Question 5

5 steps in the waterfall model

Answer 5

Requirements definition
Design of software and system
Implementation and unit testing
Integration and system testing
Operation and maintanance

Question 6

Benefits (3) and drawbacks (1) of the waterfall model

Answer 6

B: Easy management
B: Efficient development of small systems
B: Easier to make a high quality software
D: Costly changes (require a lot of time and money)

Question 7

What should developers/managers focus on, when obeying the waterfall model?

Answer 7

Focus on upper levels, because bugs there spread onto the rest of the steps

Question 8

What is the first step in agile software development?

Answer 8

Software outline description/ baseline

Question 9

What are the 3 concurrent activities done during agile development?

Answer 9

Specification
Development
Validation

Question 10

Benefits (3) and drawbacks () of agile development

Answer 10

B: Low costs of implementing a change
B: Easy access to customer’s feedback
B: Quicker delivery and deployment
D: Hard to manage (low visibility)
D: Quality degradation with each change

Question 11

What is the integration and configuration model about?

Answer 11

Already existing software/components reuse

Question 12

What does the acronym COTS stand for?

Answer 12

Commercial Off The Shelt - software buyable on general market (for direct use and reuse in the software development)

Question 13

3 types of software, that can be reused for development

Answer 13

Standalone apps
Packages with objects and functions integrated using frameworks
Web services available for remote invocation

Question 14

What are the 4 activities (2 done concurrently) done at the beginning of the reuse-oriented software engineering?

Answer 14

Requirement specification
Software discovery
Software evaluation
Requirements refinement

Question 15

In reuse-oriented software engineering, there are 2 types of appropriate software to reuse:

Answer 15

Whole application system
Certain components

Question 16

What to do in the reuse-oriented software engineering, when an appropriate application system is available?

Answer 16

Just configure it to your needs

Question 17

What to do in the reuse-oriented software engineering, when you find certain appropriate components (3 steps)?

Answer 17

Adapt components
Create missing ones
Integrate them all

Question 18

Benefits (2) and drawbacks (2) of reuse-oriented software development

Answer 18

B: Reduced costs and development risks
B: Fast delivery and deployment
D: Possibly a need for compromises
D: Loss of control over reused component evolution

Question 19

What 3 tasks are done concurrently when creating requirements document?

Answer 19

Elicitation and analysis (What the customer wants; What the system could do)
Specification (Describing the details)
Validation (Checking the feasibility of requirements)

Question 20

Give 3 main design “steps”:

Answer 20

Design inputs
Design activities
Design outputs

Question 21

Give 3 design inputs (1st phase of the design info)

Answer 21

Platform info (Windows, Linux Server)
Customer’s requirements (Customer wants a secure, company-internal, web-based data repository)
Data description (User will store pdf documents)

Question 22

What are the 4 design activities (2nd phase of design process):

Answer 22

Architectural design
Interface design
Component design
Database design

Question 23

Give 4 design outputs (3rd phase in design process)

Answer 23

System architecture
Database specification
Interface specification
Component specifcation

Question 24

3 stages of software testing

Answer 24

Component testing (unit testing)
System testing (system as a whole)
Acceptance testing (with customer’s data)

Question 25

Plan-driven software process (V-model) 4 design/specification stages:

Answer 25

Requirements specification System specification System design Detailed design

Question 26

Plan-driven software process (V-model) 4 test stages

Answer 26

Unit/Module tests Sub-system integration tests System integration tests Acceptance tests

Question 27

Plan-driven software process (V-model) 3 test plans (give names of specification/design stages and test stages for each plans)

Answer 27

Acceptance plan (from Requirements specs. and System specs. to Acceptance tests) System integration test plan (from System specs. and System design to System integration tests) Sub-system integration test plan (from System design and Detailed design to Sub-system integration test)

Question 28

4 stages of system evolution process

Answer 28

Define system requirements Assess existing/newly created systems (from the 4'th stage) Propose system changes Modify/Create systems

Question 29

Give 3 main sources of the need for change in software projects

Answer 29

Business changes New technologies Changing platforms

Question 30

2 ways of rework cost reduction

Answer 30

1. Change anticipation - help customer(s) and/or developer(s) find out possible changes earlier (ex. prototypes help with requirement specification [creating, modifying, checking the feasibility]) 2. Change tolerance - structure allowing for easier changes (i.e. less convoluded; standardised; generalised)

Question 31

2 ways of dealing with changing requirements

Answer 31

1. Prototyping 2. Incremental delivery (interleaved specification and development)

Question 32

4 uses of software prototype

Answer 32

1. Requirements assessing 2. Design aiding (exploring options) 3. Testing back-to-back 4. Training users

Question 33

5 prototyping benefits

Answer 33

1. Improved usability 2. Help in finding the real customer needs 3. Better quality 4. Better maintainability 5. Reduced development effort

Question 34

Describe the prototype development process (4 steps - What they are and what they produce?)

Answer 34

1. Establish objectives -> (Plan) 2. Define functionality -> (Outline) 3. Develop -> (Executable prototype) 4. Evaluate -> (Evaluation report)

Question 35

What can be left out during prototyping? (3)

Answer 35

1. Well understood aspects 2. Error checking 3. Non-functional requirements (visuals; performance)

Question 36

Why are prototypes bad as a basis for production? (4 reasons

Answer 36

1. Lack of documentation (typically) 2. Degraded structure due to rapid development 3. Insufficient quality 4. Non-functional requirements may be impossible to fulfill

Question 37

What's the main difference between incremental development and incremental delivery?

Answer 37

Inc. dev. - Whole product delivered Inc. del. - Product delivered in increments

Question 38

In incremental delivery what are the 3 steps before an increment development step?

Answer 38

1. Define outline reqs 2. Assign reqs to incs 3. Design system architecture

Question 39

In incremental delivery what are the 3 steps between an increment development and deployment?

Answer 39

1. Validate increment 2. Integrate increment 3. Validate system

Question 40

In incremental delivery what to do if system is complete and what to do if system is incomplete?

Answer 40

System complete -> System is finished System incomplete -> Develop another system increment

Question 41

4 incremental delivery advantages

Answer 41

1. Functionalities avaliable earlier 2. Practical feedback 3. Lower risk of project failure 4. Most important components recieve most testing

Question 42

2 main incremental delivery problems

Answer 42

Difficult to create general components Impossible to provide the complete initial software specification (sometimes required by some clients)

Question 43

What does process improvment require and result in?

Answer 43

Requires understanding of the processes Affects overall product quality - Higher performance and lower cost

Question 44

Steps in the cycle of process improvement

Answer 44

1. Measure 2. Analyze 3. Change

Question 45

How can you approach the improvement from 2 different software dev. areas?

Answer 45

1. Management - Using software dev. methods and practices (process maturity) 2. Engineers - Iterative software improvement (agile)

Question 46

List the process metrics

Answer 46

Time taken (May and June; 6 hours) Resources required (200 man-hours; 30k $) Number of occurances of a particular event (15 bugs detected; 6 customer complaints)

Question 47

List (software engineering institute) capability maturity levels

Answer 47

1. **Initial** *(Uncontrolled)* 2. **Repeatable** *(Process broadly characterised)* 3. **Defined** *(Process taillored to company needs)* 4. **Quantitavely managed** (Process measured and controlled) 5. **Optimising** (Process under improvement)