Requirements specificationRequirements specification

Copyright, 2001 © Jerzy R. Nawrocki

Jerzy.Nawrocki@put.poznan.pl

www.cs.put.poznan.pl/jnawrocki/mse/quality/

Quality ManagementQuality Management

Lecture Lecture 55

Quality ManagementQuality Management

Lecture Lecture 55

J. Nawrocki, Quality Manag. (5)

McCalls Quality FactorsMcCalls Quality FactorsMcCalls Quality FactorsMcCalls Quality Factors

• Correctness – tst• Reliability (precision, accuracy) – tst• Efficiency – tst• Integrity (security) – tst• Usability ?• Maintainability – insp• Flexibility ?• Testability ?• Portability (interoperability) – spec• Reusability x

J. Nawrocki, Quality Manag. (5)

McCalls Quality FactorsMcCalls Quality FactorsMcCalls Quality FactorsMcCalls Quality Factors

• Communication commonality ?• Completeness – tst report• Conciseness ?• Consistency – doc c.: audits• Data commonality ?• Error tolerance ?• Instrumentation – spec + tst• Security – tst• Self documentation: spec?, audits

J. Nawrocki, Quality Manag. (5)

Requirements document (1)Requirements document (1)Requirements document (1)Requirements document (1)

1. Introduction

1.1 Purpose of the document

1.2 Scope of the product

1.3 Definitions, acronyms and

abbreviations

1.4 References

1.5 Overview of the document

J. Nawrocki, Quality Manag. (5)

Requirements document (2)Requirements document (2)Requirements document (2)Requirements document (2)

2. General description 2.1 Product perspective 2.2 Viewpoints 2.2.1 Stakeholders 2.2.2 Users 2.2.3 Domain 2.2.4 Components 2.3 System architecture and use cases in UML 2.4 General constraints 2.5 Assumptions and dependencies

J. Nawrocki, Quality Manag. (5)

Requirements document (3)Requirements document (3)Requirements document (3)Requirements document (3)

3. Technical requirements

3.1 Functional requirements

3.1.1 Requirement 1

3.1.1.1 Introduction

Viewpoint and source(s)

Firmness and importance

Verifiability and clarity

3.1.1.2 Inputs

3.1.1.3 Processing

3.1.1.4 Outputs

J. Nawrocki, Quality Manag. (5)

Requirements document (4)Requirements document (4)Requirements document (4)Requirements document (4)

3.1.2 Requirement 2

. .

3.2 External interface requirements

3.2.1 User interfaces

3.2.2 Hardware interfaces

3.2.3 Software interfaces

3.2.4 Communication interfaces

3.3 Performance requirements

J. Nawrocki, Quality Manag. (5)

Requirements document (5)Requirements document (5)Requirements document (5)Requirements document (5)

3.4 Design constraints

3.4.1 Standards compliance

3.4.2 Hardware limitations

. . .

3.5 Attributes

3.5.1 Security

3.5.2 Maintainability

. . .

J. Nawrocki, Quality Manag. (5)

Requirements document (6)Requirements document (6)Requirements document (6)Requirements document (6)

3.6 Other requirements

3.6.1 Database

3.6.2 Operations

3.6.3 Site adaptation

3.6.4 Training

. . .

3.7 Non-technical requirements

Appendixes

Index

J. Nawrocki, Quality Manag. (5)

Quality assessmentQuality assessmentQuality assessmentQuality assessment

1. What is your general impression? (1 - 6)

2. Was it too slow or too fast?

3. What important did you learn during the lecture?

4. What to improve and how?