lecture3 software req and design 1

lecture3 software req and design 1 - Software Requirements...

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

View Full Document Right Arrow Icon
Software Requirements
Background image of page 1

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

View Full DocumentRight Arrow Icon
Definition of a Software Requirement A software requirement is a property which must be exhibited in order to solve some problem in the real world It is concerned with problems to be addressed by software An essential property of all software requirements is that they must be verifiable
Background image of page 2
Product and Process Requirements A distinction can be drawn between product parameters and process parameters Product parameters are requirements on software to be developed (for example, “ The software shall verify that a student meets all prerequisites before he or she registers for a course. ”) A process parameter is essentially a constraint on the development of the software (for example, “ The software shall be written in Ada. ”). These are sometimes known as process requirements.
Background image of page 3

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

View Full DocumentRight Arrow Icon
Functional and Nonfunctional Requirements Functional requirements describe the functions that the software is to execute For example, formatting some text or modulating a signal They are sometimes known as capabilities Nonfunctional requirements are the ones that act to constrain the solution Nonfunctional requirements are sometimes known as constraints or quality requirements They can be further classified according to whether they are performance requirements, maintainability requirements, safety requirements, reliability requirements, or one of many other types of software requirements
Background image of page 4
Avoidance of Vague and Unverifiable Requirements Software requirements should be stated as clearly and as unambiguously as possible To be avoided the software shall be reliable the software shall be user-friendly Quantifiable Requirements are particularly important for nonfunctional requirements Examples
Background image of page 5

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

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 17

lecture3 software req and design 1 - Software Requirements...

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

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