The Software Process

Question 1

The Software Process

Answer 1

1. Specification
2. Architecture
3. Design
4. Implementation
5. Testing
6. Evolution

Question 2

Types of Approaches

Answer 2

1. Plan-driven
2. Agile
3. Hybrid (most realistic)

Question 3

Plan-Driven Approach

Answer 3

Phased, software works only in final phase, overhead communication, testing only at final stage, predictive planning

Question 4

Agile Approach

Answer 4

Iterative and incremental, always have MVP, less overhead communication, validation driven, adaptive planning

Question 5

Software Process Model Examples

Answer 5

1. Waterfall model
2. Incremental development
3. Reuse-oriented SWE

Question 6

The Waterfall Model

Answer 6

Linear and plan driven.
PROS: Used mostly for large projects.
CONS: Inflexible for responding to changing customer requirements. Working program only available at end of process.

Question 7

Incremental Development

Answer 7

Multiple concurrent activities.
PROS: Can easily accommodate changing customer requirements. Consistent feedback loop. Usable software is available early in the process.
CONS: Process not visible. System structure can degrade over time if initial is low quality. Hard to define common features.

Question 8

Prototyping Model

Answer 8

Involves creating and possible dumping many designs to find optimal one.
PROS: Improved usability, matches user needs, high design quality, high maintainability, reduced development effort
CONS: not working product may confuse customer, implementation compromises to get quick model

Question 9

Spiral Model

Answer 9

Each loop is a phase in process, no fixed phases (like specs or design) can be chosen by team, risk assessment is integral part of process
CONS: hard to convince customers that process is controllable, requires risk management expertise

Question 10

Specification Phase

Answer 10

• Feasibility study
• Requirements elicitation/analysis
• Requirements specification
• Requirements validation

Question 11

Architecture Phase

Answer 11

Create level of abstraction between:
- User needs/requirements
- Design Elements (data structures & algorithms)

Question 12

Layered Architecture

Answer 12

All components in separate layers. Most important in core. Outer layers must communicate w all layers before getting to core.

Question 13

Design and Implementation Phase

Answer 13

Converting system specs to executable system

Question 14

Testing Phase

Answer 14

Uses VERIFICATION and VALIDATION. Testing the entire system.

Question 15

Verification

Answer 15

Is the system built the right way? Meets requirements, right process, meets standards.

Question 16

Validation

Answer 16

Are we meeting the customers needs and intent?

Question 17

Testing Stages

Answer 17

1. Development testing
2. Release testing
3. User testing

Question 18

Development Testing

Answer 18

Test driven development, component testing (how pieces work together), system testing

Question 19

Release Testing

Answer 19

Testing entire system together. All testers are from outside the team. I.E. black box testing

Question 20

Black Box Testing

Answer 20

Testing the program without access to the code

Question 21

Evolution Phase

Answer 21

Software must be able to be easily changed and updated. Many projects start from existing program