Requirements_ch6_Part2

Requirements_ch6_Part2 - Chapter 6 - Software Requirements...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
Lucent Technologies – Proprietary Use pursuant to company instruction © 2006 Lucent Technologies. All Rights Reserved. Chapter 6 - Software Requirements Software Engineering - Phases
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Lucent Technologies – Proprietary Use pursuant to company instruction © 2006 Lucent Technologies. All Rights Reserved. Objectives To introduce the concepts of user and system requirements To describe functional and non-functional requirements To explain how software requirements may be organised in a requirements document
Background image of page 2
Lucent Technologies – Proprietary Use pursuant to company instruction © 2006 Lucent Technologies. All Rights Reserved. Requirements engineering Requirements are: the descriptions of the system services and constraints that are generated during the requirements engineering process. Requirements reflects the needs of the customer and they solve some problem Requirement Engineering 1. The process of establishing the services that the customer requires from a system and 2. the constraints under which it operates and is developed. the process of finding out, analysing, documenting and checking these services is called requirement
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Lucent Technologies – Proprietary Use pursuant to company instruction © 2006 Lucent Technologies. All Rights Reserved. What is a requirement? It may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification. This is inevitable as requirements may serve a dual function May be the basis for a bid for a contract - therefore must be open to interpretation; May be the basis for the contract itself - therefore must be defined in detail; Both these statements may be called requirements.
Background image of page 4
Lucent Technologies – Proprietary Use pursuant to company instruction © 2006 Lucent Technologies. All Rights Reserved. Types of requirement 1. User requirements Statements in natural language plus diagrams of the services the system provides and its operational constraints. Written for customers. 1. System requirements A structured document setting out detailed descriptions of the system’s functions , services and operational constraints . Defines what should be implemented so may be part of a contract between client and contractor.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Lucent Technologies – Proprietary Use pursuant to company instruction © 2006 Lucent Technologies. All Rights Reserved. Library System Example - User and System requirements 1. The softw are m ust pr ovide a means of representing and 1. accessing e xternal files cr eated b y other tools . 1.1 The user should be pr ovided with facilities to define the type of 1.2 external files. 1.2 Each e xternal file type ma y have an associa ted tool w hich ma y be
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 04/23/2010.

Page1 / 39

Requirements_ch6_Part2 - Chapter 6 - Software Requirements...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online