02-SoftwareRequirementsSpecification

02-SoftwareRequirementsSpecification - S Software...

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

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

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

View Full Document Right Arrow Icon
Software Requirements Sources: Mastering the Requirements Process , S. Robertson and J. Robertson, Addison Wesley, 1999 Software Engineering , R. Pressman, McGraw Hill, 2001
Background image of page 2
You will learn about …. What is a requirement Requirement Shell Trawling for Requirements Techniques, models (traditional, OO) Properties of Requirements Validation of Requirements Requirements Specifications Phase 1 of your project.
Background image of page 3

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

View Full Document Right Arrow Icon
What is a requirement A requirement is something That the product must do ( functional requirement ). Fundamental reason for the product’s existence » Ex.: The security system shall detect motion That the product must have ( non-functional req. ) These are properties, or qualities. Critical to the product’s success » Ex.: The security system shall make a call in less than 0.25 sec A requirement exists because The type of the product demands it. The customer wants it.
Background image of page 4
What is a requirement Constraints These are global requirements – they apply to the entire product. Examples Passengers on board an aircraft will use the product. The product is for children Users are a constraint. The product shall run on UNIX machines. Summary: Constraints, FRs, NFRs
Background image of page 5

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

View Full Document Right Arrow Icon
Requirement Template Product Constraints The purpose: reason for building the product Stakeholders: people with an interest in the product Users of the product: how they affect usability Requirements Constraints: limitations on the project (must be done in six months), restrictions on the design (world-wide accessibility) Relevant facts: Outside influences that make some difference to the product (Standards being developed?) Assumptions: that the developers are making
Background image of page 6
Requirement Template Functional Requirements The scope of the product: Defines the product boundary , and its connections to adjacent systems Functional and Data requirements: Things the product must do and the data manipulated by the functions Non-functional Requirements Look and feel requirements: appearance Usability requirements: based on the intended users Performance requirements: speed, resource, . .. Operational requirements: operating environment Maintainability Security requirements: confidentiality, integrity, … Legal requirements: conformance to applicable laws
Background image of page 7

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

View Full Document Right Arrow Icon
Requirement Shell Components of a requirement Requirement ID Requirement type Description: 1-sentence statement Rationale: Why is it considered important? Source: Who raised this requirement? Testability: Description of a procedure to determine whether the solution meets the requirement Dependencies: Other requirements with a change effect Conflicts: Requirements that contradict this one Supporting material: Pointer to supporting information History: Origin and changes to the requirement
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page1 / 37

02-SoftwareRequirementsSpecification - S Software...

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

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