Software Requirements Validation: Checklists, Prototyping, User Manuals, Model Testing, Slides of Software Project Management

Download Software Requirements Validation: Checklists, Prototyping, User Manuals, Model Testing and more Slides Software Project Management in PDF only on Docsity!

1

Requirements Validation – II

Lecture # 17

2

Today’s Topics

• Validation techniques

• Review checklists– Prototyping– User manual development– Model validation– Requirements testing

4

Review Checklists - 2

• Completeness

• Does the checker know of any missing

requirements or is there any informationmissing from individual requirementdescriptions?

5

Review Checklists - 3

•^

Ambiguity–

Are the requirements expressed using termswhich are clearly defined? Could readers fromdifferent backgrounds make differentinterpretations of the requirements?

•^

Consistency–

Do the descriptions of different requirementsinclude contradictions? Are there contradictionsbetween individual requirements and overallsystem requirements?

7

Review Checklists - 5

•^

Conformance to standards–

Does the requirements document andindividual requirements conform to definedstandards? Are departures from the standards,justified?

•^

Traceability–

Are requirements unambiguously identified,include links to related requirements and tothe reasons why these requirements havebeen included?

8

Checklist Questions & Quality

Attributes - 1

• Is each requirement uniquely identified?
  • Traceability, conformance to standards
    • Are specialized terms defined in the

glossary– Understandability

• Does a requirement stand on its own or do

you have to examine other requirements tounderstand what it means?– Understandability, completeness

10

Checklist Questions & Quality

Attributes - 3

•^

If a requirement makes reference to someother facilities, are these describedelsewhere in the document?–

Completeness

•^

Are related requirements grouped together?If not, do they refer to each other?–

Organization, traceability

11

Prototyping

• Prototypes for requirements validation

demonstrate the requirements and helpstakeholders discover problems

• Validation prototypes should be complete,

reasonably efficient and robust. It should bepossible to use them in the same way as therequired system

• User documentation and training should be

provided

13

Prototyping Activities - 1

• Choose prototype testers

• The best testers are users who are fairly

experienced and who are open-mindedabout the use of new systems. End-userswho do different jobs should be involvedso that different areas of systemfunctionality will be covered

14

Prototyping Activities - 2

• Develop test scenarios

• Careful planning is required to draw up a

set of test scenarios which provide broadcoverage of the requirements. End-usersshouldn’t just play around with thesystem as this may never exercise criticalsystem features

16

User Manual Development - 1

•^

Writing a user manual from therequirements forces a detailed requirementsanalysis and thus can reveal problems withthe document

17

User Manual Development - 2

• Information in the user manual

• Description of the functionality and how

it is implemented

• Which parts of the system have not been

implemented

• How to get out of trouble– How to install and get started with the

system

19

Model Validation

• Validation of system models is an essential

part of the validation process

• Some checking is possible with automated

tools

• Paraphrasing the model is an effective

checking technique

20

Objectives of Model Validation

• To demonstrate that each model is self-

consistent

• If there are several models of the system, to

demonstrate that these are internally andexternally consistent

• To demonstrate that the models accurately

reflect the real requirements of systemstakeholders. This is very difficult