Software Processes

Question 1

Life Cycle

Answer 1

Refers to the building of the software until the company no longer works/associates with it.

Question 2

Process

Answer 2

A set of actions.

Question 3

Issues with software.

Answer 3

Evolution always equals faults, and if the original programmers leave, then there could be no understanding of the original code.

Question 4

The Waterfall Model

Answer 4

Essentially, you complete the whole software by the requirements you have already been set, allowing no change until it is complete. This is inflexible and is only appropriate when the requirements are final.
Order is:
- Requirements definition
- System and software design
- Implementation and unit testing
- Integration and system testing
- Operation and maintenance

Question 5

Evolutionary Development

Answer 5

Allows development of the software based upon specification, but also allows validation of the software too, which means going to the user and checking if there is anything they like/don’t like etc.
Order is:
- Outline description
- Specification (initial version), development (intermediate version), validation (final version).

Question 6

Agile Development

Answer 6

This is more of a test driven development.
Uses pair programming and self organised teams (one could be tester, the other the developer etc).

Question 7

Software Specification

Answer 7

Establishing what services are required and the constraints on the system’s operation and development.

Question 8

Defect Amplification

Answer 8

Minor wrong details leads to bigger problems down the line.

Question 9

Software Design and Implementation

Answer 9

Designing a software that realises the specification and creating executable code from that design. These may be inter-leaved.

Question 10

Architectural Design

Answer 10

Sub-systems are identified and documented.

Question 11

Abstract Specification

Answer 11

For each sub-system, specification of operational constraints and services are produced.

Question 12

Interface Design

Answer 12

For each sub-system, an unambiguous interface with other sub-systems are produced.

Question 13

Component Design

Answer 13

Services are allocated to components / interfaces of the components are designed.

Question 14

Data structure Design

Answer 14

Data structures used in system implementation are designed in detail and specified.

Question 15

Algorithm Design

Answer 15

Algorithms used in components to provide services are produced.

Question 16

Testing Process

Answer 16

Unit testing
Module testing
Sub-system testing
System testing
Acceptance testing

Question 17

Unit Testing

Answer 17

Testing individual components

Question 18

Module Testing

Answer 18

Testing related collections of components

Question 19

Sub-system Testing

Answer 19

Testing sub-systems (collections of modules)

Question 20

System Testing

Answer 20

The system as a whole is tested

Question 21

Acceptance Testing

Answer 21

Testing with customer data.

Question 22

SCRUM sprints.

Answer 22

We also use SCRUM sprints, which is the development being broken up into increments and focuses more on user testing/requirements.