A2 ICT: Requirements, Design and System Specifications

Created by: Kay
Created on: 10-06-12 13:03

Requirements, Design and System Specifications

Requirements Specification

The systems analyst generally creates the requirements specification. It gets created once investigations on the current system have been completed.

The requirements specification needs to clearly state what the new system needs to be able to do and how those things can be achieved. It also needs to detail all interactions that the end users will have with the new system.

Both functional and non-functional requirements need to be included too. Functional requirements would be the processes and operations that the new system is expected to do. Non-functional requirements are factors that will have an effect on how functional requirements are carried out. For example, constraints specified by the end user like time, money, hardware and software.

Contents that must be included in a requirements specification are:

System objectives
The system scope
A timescale
Constraints…

Comments

Mr A Gibson

Report Mon 30th December, 2013 @ 13:07

A good set of resources to gain an understanding of the important points covering different stages of the systems development life cycle. Links to all of these are below and they are worth combining as a single reference resource.

A2 ICT: Gantt Charts

A2 ICT: Critical Path Analysis (CPA)

A2 ICT: The Role of Different Members in the Project Team

A2 ICT: Requirements, Design and System Specifications - this resource

A2 ICT: Test Data, Testing & Test Plans