Scribd
Upload
7 views12 pages

Requirement Specification

The document outlines the requirements specification process in information system design, emphasizing the importance of defining and managing requirements from various sources. It details the need for clear documentation, prioritization of functional and non-functional requirements, and the establishment of verification criteria. Additionally, it highlights the significance of understanding project phases, limitations, integration needs, and risk analysis to ensure successful system development.

Uploaded by

MA7ESTIC
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views12 pages

Requirement Specification

The document outlines the requirements specification process in information system design, emphasizing the importance of defining and managing requirements from various sources. It details the need for clear documentation, prioritization of functional and non-functional requirements, and the establishment of verification criteria. Additionally, it highlights the significance of understanding project phases, limitations, integration needs, and risk analysis to ensure successful system development.

Uploaded by

MA7ESTIC
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Requirement

specification

Information System Design Process


Teppo Saarenpää
Requirements management
• Defining requirements is part of requirements management

• Compilation of requirements from multiple separate sources, such as system owners, users and
existing standards, laws and regulations

• Identifying requirements that need a solution

• Documentation and maintenance of collected requirements throughout the life cycle of the
system

(JHS 173)
What is requirement specification?
• The requirement specification lays the foundation for procurement/development, why and what
needs it must satisfy.
• Requirement specification is an agreement between the client and the producer on what will be
done in the development work.
• In other words, the requirement specification focuses on what is required of the system, not on
how it works technically.
• When defining requirements, it should be possible to assess the use and development of the
system also in the future.
• Procurements/development targets should be scalable, i.e. ones that can be expanded and further
developed without the need to redesign entire systems.
Requirements specification
• It is important to understand the whole range of activities: how different needs are combined,
how the whole process works and what is the role of the information system in the whole.

• Mapping the current state and identifying needs also create a basis for modelling the target state
and its processes.

• The description of the processes often only appears when the supplier has already been selected,
but modelling should be done already at the requirement specification stage.
• The earlier and better the needs can be identified and described, the better the
information system will be able to satisfy these needs.
Requirements specification
• Requirements must be prioritized so that the system can be defined as functional as possible.

• The requirements can be roughly divided into two parts; functional and non-functional
requirements.

• The functional requirements describe what kind of functions are desired from the system and
what requirements it should meet.

• Non-functional requirements are related to quality and performance, such as response and
uptime.
Verification criteria
• Defining the matter, product, service, production, etc. to be developed or
studied. key objectives VERIFICATION CRITERIA from the perspective of
the customer and other stakeholders  test plan.
Documentation of requirement specification
Can be used in
project work…
1. General description of the service to be built
• What is the problem solved by the system being built or the new benefits it brings?
• Who are the users of the service?
• What terminology has been used in the requirement specification?

2. Functional requirements of the service to be built


• Required input data
• Required functionalities
• Expected outgoing data
• If necessary, the different functionalities of the system to be built must be prioritized - which
functionalities are necessary and which are useful

(Tietojärjestelmän ostaminen – käytännön opas yrityksille, 2002)


Documentation of requirement specification
3. Project phases
• If the project is carried out in phases, which parts will be done in the first implementation phase
• Make a preliminary record of the objectives of the next implementation phases. These objectives
will be specified when the first phase is completed.

4. Limitations
• What should the system not do?
• What does not need to be considered at that stage of development?

5. Environment
• What is the IT environment in which the system to be built should be installed (application
architecture environment)?
Documentation of requirement specification
6. Integration needs
• Which information systems should the information system to be built communicate with?

7. Number of users and scalability needs of the service


• What are the estimated number of users of the service?
• What are the estimated amounts of data for the service?
• Response times and time targets set for the service
• The need for scaling

8. Data security requirements


• What security requirements are imposed on the system?

(Tietojärjestelmän ostaminen – käytännön opas yrityksille, 2002)


Documentation of requirement specification
9. Risk analysis
• Risks in technology
• Risks within your organisation
• Risks related to the supplier

10. Other things to consider


• Other issues that may affect the development project (e.g. system owner after the project and
training needs)
• Maintenance after project completion
• Quality requirements for support services

(Tietojärjestelmän ostaminen – käytännön opas yrityksille, 2002)


Lesson assignment 9
• Material: Lesson assignment 9 requirement specification.pdf

• Assess the requirements


• Why is the requirement clear?
• Why is the requirement not clear?
• If possible, formulate the requirement more clearly.

• 45 min, groups
Weekly assignment 9
• Evaluation modeling exercise. The task is to model a case study. Students can choose the notation
themselves.

• To-do:
1. Use case diagram
2. Process flow diagram
3. Data flow diagram
4. ER diagram

• The assignment assesses how the student has utilized the teaching material, lesson assignments
and other material when learning the modelling methods of those selected for the course.
• More details in It’s. Individual task. Maximum 5 points of the task.

You might also like