1.2.3

Question 1

Stakeholder

Answer 1

A person or group of people who may be impacted by decisions made during a software development project. They often get a say in important project decisions

Question 2

Waterfall Lifecycle Approach

Answer 2

Each stage in the SDLC lifecycle is completed before moving onto the next. Suited to large-scale projects where it would be costly to revisit earlier stages mid-way through the project.

Question 3

Prototype

Answer 3

A working model used to test a design or concept. Used to help identify exactly what the user requires by giving them a good example of what the finished system might be like.

Question 4

Spiral Approach

Answer 4

An extension of the waterfall approach with a focus on risk management. It consists of producing a series of prototypes which are reviewed and evaluated before developing the final system. Risk analysis is performed on every cycle to minimise the likelihood of overall project failure.

Question 5

RAD (Rapid Application Development)

Answer 5

Less emphasis on analysis and design and more emphasis on the development phase. The development phase consists on producing a series of prototypes in quick succession where user-feedback is taken into account. The process aims to make each prototype as re-usable as possible.

Question 6

Agile Software Approach

Answer 6

A family of SDLC approaches with a focus on producing multiple iterations of software where stakeholders are involved in every part of the process. Feedback from users is explicitly factored into this methodology so that clients can see progress and shape the development as it happens.

Question 7

Extreme Programming (XP)

Answer 7

A type of agile software development with a focus on short development cycles and high quality code. Techniques such as pair programming are used to ensure high quality code. It works well on small projects or when a certain amount of flexibility as to when certain features get added.

Question 8

Functional Requirement

Answer 8

Statements of services or features the system should provide and how it will respond to certain inputs

Question 9

Non-functional Requirement

Answer 9

Constraints on the services provided by a system e.g. reliability, availability, performance, usability and efficiency.

Question 10

Analysis

Answer 10

The process of establishing the system requirements by investigating the problem you are trying to solve and involving the end-user

Question 11

Design

Answer 11

Using the requirements to produce a model for the system to be produced. This involves decomposing your proposed system into a series of modules as well as establishing the algorithms that will be used for each component of the system.

Question 12

Implementation

Answer 12

Building the system itself from the designs produced.User Acceptance Testing

Question 13

User Acceptance Testing

Answer 13

Testing the system matches the user’s requirements. This may include performing usability testing so that they can check the interface/s meet their needs.

Question 14

Unit Testing

Answer 14

Testing each module of the system in isolation to all other parts of the system.

Question 15

Integration Testing

Answer 15

Testing that each unit works with all other units of the system.

Question 16

Normal Data

Answer 16

The type of data that will be entered into the system during normal day-to-day operation

Question 17

Boundary Data

Answer 17

Data that will be entered rarely, but which the system should be designed to handle. E.g. bigger than expected number for age (E.g. 100)

Question 18

Invalid Data

Answer 18

Data that is of the wrong format. E.g. entering text where the system requires a number

Question 19

Extreme Invalid Data

Answer 19

Data that is of the wrong format but could do severe damage to the system e.g. SQL entered in a text field.

Question 20

Black-box Testing

Answer 20

Testing without reference to the program code itself