Software Requirements: ©ian Sommerville 2006

Software Requirements
Ian Sommerville 2006
Software Engineering, 8th edition. Chapter 6
Slide 1
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
Slide 2
Topics covered

Functional and non-functional requirements User requirements System requirements Interface specification The software requirements document
Slide 3
Requirements engineering
The process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed. The requirements themselves are the descriptions of the system services and constraints that are generated during the requirements engineering process.
Slide 4
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.
Slide 5
Requirements abstraction (Davis)
If a company wishes to let a contract for a large software development project, it must define its needs in a sufficiently abstract way that a solution is not pre-defined. The requirements must be written so that several contractors can bid for the contract, offering, perhaps, different ways of meeting the clien t organisation s needs. Once a contract has been awarded, the contractor must write a system definition for the client in more detail so that the client understands and can validate what the software will do. Both of these documents may be called the requirements document for the system.
Slide 6
Types of requirement
User requirements
Statements in natural language plus diagrams of the services the system provides and its operational constraints. Written for customers. A structured document setting out detailed descriptions of the systems functions, services and operational constraints. Defines what should be implemented so may be part of a contract between client and contractor.
System requirements
Slide 7
Definitions and specifications

Us er requ ir emen t d efinitio n 1. The so ftw are m us t p rovid e a means o f representin g and 1. acces sing e xtern al files cr ea ted b y o th er to ols .
Sy stem requ ir emen ts sp ecif icatio n 1.1 The us er sh ould b e pr ovid ed with facilities to defin e the ty pe o f 1.2 external files . 1.2 E ach e xtern al file typ e ma y h ave an ass ocia ted to ol w hich ma y b e 1.2 applied to the file . 1.3 E ach e xtern al file typ e ma y b e r epr esented as a sp ecific ico n on 1.2 th e u ser s d is play . 1.4 Facilities s ho uld be pr o vid ed for the ico n r epresentin g an 1.2 extern al file typ e to be def in ed b y the us er . 1.5 Wh en a us er selects an icon r epr esentin g an e xtern al file, th e 1.2 effect o f that s election is to apply the to ol as so ciated with th e typ e of 1.2 th e extern al f ile to th e file repres ented b y the s elected icon .
Slide 8
Requirements readers
Slide 9
Functional and non-functional requirements
Functional requirements
Statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations. constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc. Requirements that come from the application domain of the system and that reflect characteristics of that domain.
Non-functional requirements
Domain requirements
Slide 10
Functional requirements

Describe functionality or system services. Depend on the type of software, expected users and the type of system where the software is used. Functional user requirements may be high-level statements of what the system should do but functional system requirements should describe the system services in detail.
Slide 11
The LIBSYS system
A library system that provides a single interface to a number of databases of articles in different libraries. Users can search for, download and print these articles for personal study.
Slide 12
Examples of functional requirements
The user shall be able to search either all of the initial set of databases or select a subset from it. The system shall provide appropriate viewers for the user to read documents in the document store. Every order shall be allocated a unique identifier (ORDER_ID) which the user shall be able to copy to the accounts permanent storage area.
Slide 13
Requirements imprecision
Problems arise when requirements are not precisely stated. Ambiguous requirements may be interpreted in different ways by developers and users. Consider the term appropriate viewers
User intention - special purpose viewer for each different document type; Developer interpretation - Provide a text viewer that shows the contents of the document.
Slide 14
Requirements completeness and consistency
In principle, requirements should be both complete and consistent. Complete They should include descriptions of all facilities required. Consistent There should be no conflicts or contradictions in the descriptions of the system facilities. In practice, it is impossible to produce a complete and consistent requirements document.
Slide 15
Non-functional requirements
These define system properties and constraints e.g. reliability, response time and storage requirements. Constraints are I/O device capability, system representations, etc. Process requirements may also be specified mandating a particular CASE system, programming language or development method. Non-functional requirements may be more critical than functional requirements. If these are not met, the system is useless.
Software Engineering, 8th edition. Chapter 6 Slide 16
Non-functional classifications
Product requirements
Requirements which specify that the delivered product must behave in a particular way e.g. execution speed, reliability, etc. Requirements which are a consequence of organisational policies and procedures e.g. process standards used, implementation requirements, etc. Requirements which arise from factors which are external to the system and its development process e.g. interoperability requirements, legislative requirements, etc.
Organisational requirements
External requirements
Slide 17
Non-functional requirement types

Non-functiona l re quir e ments
Product re quir e ments
Organisa tiona l re quir e ments
Externa l re quir e ments
Effic iency re quir e ments
Re lia bility re quir e ments
Porta bility re quir e ments
Inte r ope r a bility re quir e ments
Ethica l re quir e ments
Usa bility re quir e ments
De live ry re quir e ments
Imple menta tion re quir e ments
Sta ndar ds re quir e ments
Le gisla tive re quir e ments
Pe rforma nc e re quir e ments
Spa ce re quir e ments
Priva cy re quir e ments
Safety re quir e ments
Slide 18
Non-functional requirements examples
Product requirement
8.1 The user interface for LIBSYS shall be implemented as simple HTML without frames or Java applets.
Organisational requirement
9.3.2 The system development process and deliverable documents shall conform to the process and deliverables defined in XYZCo-SPSTAN-95.
External requirement
7.6.5 The system shall not disclose any personal information about customers apart from their name and reference number to the operators of the system.
Slide 19
Goals and requirements
Non-functional requirements may be very difficult to state precisely and imprecise requirements may be difficult to verify. Goal
A general intention of the user such as ease of use. A statement using some measure that can be objectively tested.
Verifiable non-functional requirement
Goals are helpful to developers as they convey the intentions of the system users.
Slide 20
Examples
A system goal
The system should be easy to use by experienced controllers and should be organised in such a way that user errors are minimised. Experienced controllers shall be able to use all the system functions after a total of two hours training. After this training, the average number of errors made by experienced users shall not exceed two per day.
A verifiable non-functional requirement
Slide 21
Requirements measures
Property Speed Measure Processed transactions/second User/Event response time Screen refresh time M Bytes Number of ROM chips Training time Number of help frames Mean time to failure Probability of unavailability Rate of failure occurrence Availability T ime to restart after failure Percentage of events causing failure Probability of data corruption on failure Percentage of target dependent statements Number of target systems
Size Ease of use Reliability
Robustness
Portability
Requirements interaction
Conflicts between different non-functional requirements are common in complex systems. Spacecraft system
To minimise weight, the number of separate chips in the system should be minimised. To minimise power consumption, lower power chips should be used. However, using low power chips may mean that more chips have to be used. Which is the most critical requirement?
Slide 23
Domain requirements
Derived from the application domain and describe system characteristics and features that reflect the domain. Domain requirements be new functional requirements, constraints on existing requirements or define specific computations. If domain requirements are not satisfied, the system may be unworkable.
Slide 24
Library system domain requirements
There shall be a standard user interface to all databases which shall be based on the Z39.50 standard.
Because of copyright restrictions, some documents must be deleted immediately on arrival. Depending on the users requirements, these documents will either be printed locally on the system server for manually forwarding to the user or routed to a network printer.
Slide 25
Train protection system
The deceleration of the train shall be computed as:

Dtrain = Dcontrol + Dgradient
where Dgradient is 9.81ms2 * compensated gradient/alpha and where the values of 9.81ms2 /alpha are known for different types of train.
Slide 26
Domain requirements problems
Understandability
Requirements are expressed in the language of the application domain; This is often not understood by software engineers developing the system. Domain specialists understand the area so well that they do not think of making the domain requirements explicit.
Implicitness
Slide 27
User requirements
Should describe functional and non-functional requirements in such a way that they are understandable by system users who dont have detailed technical knowledge. User requirements are defined using natural language, tables and diagrams as these can be understood by all users.
Slide 28
Problems with natural language
Lack of clarity
Precision is difficult without making the document difficult to read. Functional and non-functional requirements tend to be mixed-up. Several different requirements may be expressed together.
Requirements confusion
Requirements amalgamation
Slide 29
LIBSYS requirement
4..5 LIBSYS shall provide a financial accounting system that maintains records of all payments made by users of the system. System managers may configure this system so that regular users may receive discounted rates.
Slide 30
Editor grid requirement

2.6 Grid facilities To assist in the positioning of entities on a diagram, the user may turn on a grid in either centimetres or inches, via an option on the control panel. Initially, the grid is off. The grid may be turned on and off at any time during an editing session and can be toggled between inches and centimetres at any time. A grid option will be provided on the reduce-to-fit view but the number of grid lines shown will be reduced to avoid filling the smaller diagram with grid lines.
Slide 31
Requirement problems
Database requirements includes both conceptual and detailed information
Describes the concept of a financial accounting system that is to be included in LIBSYS; However, it also includes the detail that managers can configure this system - this is unnecessary at this level.
Grid requirement mixes three different kinds of requirement

Conceptual functional requirement (the need for a grid); Non-functional requirement (grid units); Non-functional UI requirement (grid switching).
Slide 32
Structured presentation
2.6.1 Grid facilities The editor shall provide a grid facility where a m atrix of horizontal and vertical lines provide a background to the editor window. This grid shall be a passive grid where the alignment of entities is the user's responsibility. Rationale: A grid helps the user to create a tidy diagram with well-spaced entities. Although an active grid, where entities 'snap-to' grid lines can be u seful, the positioning is imprecise. T he user is the best person to decide where entities should be positioned. Specification: ECLIPSE/WS/ T ools/DE/FS Section 5.6 Source: Ray Wilson, Glasgow Office
Slide 33
Guidelines for writing requirements
Invent a standard format and use it for all requirements. Use language in a consistent way. Use shall for mandatory (expressing a command) requirements, should for desirable requirements. Use text highlighting to identify key parts of the requirement. Avoid the use of computer jargon.
Slide 34
System requirements
More detailed specifications of system functions, services and constraints than user requirements. They are intended to be a basis for designing the system. They may be incorporated into the system contract. System requirements may be defined or illustrated using system models discussed in Chapter 8.
Slide 35
Requirements and design
In principle, requirements should state what the system should do and the design should describe how it does this. In practice, requirements and design are inseparable
A system architecture may be designed to structure the requirements; The system may inter-operate with other systems that generate design requirements; The use of a specific design may be a domain requirement.
Problems with NL (native language) specification
Ambiguity
The readers and writers of the requirement must interpret the same words in the same way. NL is naturally ambiguous so this is very difficult. The same thing may be said in a number of different ways in the specification. NL structures are inadequate to structure system requirements.
Over-flexibility
Lack of modularisation
Slide 37
Alternatives to NL specification
Notation Structured natural language Design description languages Graphical notations Description This approach depends on defining standard forms or templates to express the requirements specification. This approach uses a language like a programming language but with more abstract features to specify the requirements by defining an operational model of the system. This approach is not now widely used although it can be useful for interface specifications. A graphical language, supplemented by text annotations is used to define the functional requirements for the system. An early example of such a graphical language was SADT. Now, use-case descriptions and sequence diagrams are commonly used . These are notations based on mathematical concepts such as finite-state machines or sets. These unambiguous specifications reduce the arguments between customer and contractor about system functionalit y. However, most customers dont understand formal specifications and are reluctant to accept it as a system contract.
Mathematical specifications
Figure 6.1
Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 6 Slide 38
Structured language specifications
The freedom of the requirements writer is limited by a predefined template for requirements. All requirements are written in a standard way. The terminology (technical expressions) used in the description may be limited. The advantage is that the most of the expressiveness of natural language is maintained but a degree of uniformity is imposed on the specification. May incorporate control constructs derived from programming languages and graphical highlighting to partition the specification.
Slide 39
Form-based specifications

Definition of the function or entity. Description of inputs and where they come from. Description of outputs and where they go to.
Description of all action that you will do.
Indication of other entities required. Pre and post conditions (if appropriate). The side effects (if any) of the function.
Slide 40
Form-based node specification

Insulin Pump/Control Software/SRS/3.3.2 Function Compute insulin dose: Safe sugar level Description Computes the dose of insulin to be delivered wh en the current measur ed sugar level is in the safe zone between 3 and 7 units. Inputs Current sugar reading (r2), the previous two readings (r0 and r1) Source Current sugar reading from sensor. Other readings from memory. O utputs CompDose the dose in insulin to be delivered Destination Main control loop Action: CompDose is zero if the sugar level is stable or falling or if the level is increasing but the rate of increase is decreasing. If the level is increasing and the rate of increase is increasing, then CompDose is computed by dividing the difference between the current sugar level and the previous level by 4 and rounding the result. If the result, is rounded to zero then CompDose is set to the minimum dose that can be delivered. Requires Pre-condition Post-condition Side-effects Two previous readings so that the rate of change of sugar level can be computed. The insulin reservoir contains at least the maximum allowed single dose of insulin.. r0 is replaced by r1 then r1 is replaced by r2 None
Slide 41
Tabular specification

Used to supplement natural language. Particularly useful when you have to define a number of possible alternative courses of action.
Slide 42
Tabular specification
Condition Sugar level falling (r2 < r1) Sugar level stable (r2 = r1) Sugar level increasing and rate of increase decreasing ((r2-r1)<(r1-r0)) Sugar level increasing and rate of increase stable or increasing. ((r2-r1) (r1-r0)) Action CompDose = 0 CompDose = 0 CompDose = 0 CompDose = round ((r2-r1)/4) If rounded result = 0 then CompDose = MinimumDose
Slide 43
Graphical models
Graphical models are most useful when you need to show how state changes or where you need to describe a sequence of actions. Different graphical models are explained in Chapter 8.
Slide 44
Sequence diagrams
These show the sequence of events that take place during some user interaction with a system. You read them from top to bottom to see the order of the actions that take place. Cash withdrawal from an ATM
Validate card; Handle request; Complete transaction.
Slide 45
Sequence diagram of ATM withdrawal

ATM Card PIN request PIN Opt ion menu <<exception>> invalid card Withdraw request Amount request Amount Debit (amount) <<exception>> insufficient cash Card Card removed Cash Cash removed Receipt Complete t ransact ion Debit response Balance request Balance Handle request Validate card Database Card number Card OK
Slide 46
Interface specification
Most systems must operate with other systems and the operating interfaces must be specified as part of the requirements. Three types of interface may have to be defined
Procedural interfaces; Data structures that are exchanged; Data representations.
Formal notations (discussed in Chapter 10) are an effective technique for interface specification.
Slide 47
PDL interface description

interface PrintServer { // defines an abstract printer server // requires: interface Printer, interface PrintDoc // provides: initialize, print, displayPrintQueue, cancelPrintJob, switchPrinter void initialize ( Printer p ) ; void print ( Printer p, PrintDoc d ) ; void displayPrintQueue ( Printer p ) ; void cancelPrintJob (Printer p, PrintDoc d) ; void switchPrinter (Printer p1, Printer p2, PrintDoc d) ; } //PrintServer
Slide 48
PDL-based requirements definition

A PDL is a language derived from a PL like Java or Ada The advantage of using a PDL is that it may be checked syntactically and semantically by SW tools Requirements may be defined operationally using a language like a programming language but with more flexibility of expression PDL result in very detailed spec. Its too close to the implementation for inclusion in a requirement document Use PDL appropriate in two situations
Where an operation is specified as a sequence of actions and the order of execution is important When hardware and software interfaces have to be specified
Slide 49
Part of an ATM specification

class ATM { // declarations here public static void main (String args[]) throws InvalidCard { try { thisCard.read () ; // may throw InvalidCard exception pin = KeyPad.readPin () ; attempts = 1 ; while ( !thisCard.pin.equals (pin) & attempts < 4 ) { pin = KeyPad.readPin () ; attempts = attempts + 1 ; } if (!thisCard.pin.equals (pin)) throw new InvalidCard ("Bad PIN"); thisBalance = thisCard.getBalance () ; do { Screen.prompt (" Please select a service "); service = Screen.touchKey () ;
Slide 50
switch (service) { case Services.withdrawalWithReceipt: receiptRequired = true ; case Services.withdrawalNoReceipt: } } while (service != Service.quit) . } Catch(InvalidCard e) { Screen.printmsg(Invalid card or PIN); } } // main() }// ATM
Slide 51
PDL disadvantages
PDL may not be sufficiently expressive to express the system functionality in an understandable way Notation is only understandable to people with programming language knowledge The requirement may be taken as a design specification rather than a model to help understand the system PDL may be used to define control sequences or interfaces in more detail
Slide 52
The requirements document
The requirements document is the official statement of what is required of the system developers. Should include both a definition of user requirements and a specification of the system requirements. It is NOT a design document. As far as possible, it should set of WHAT the system should do rather than HOW it should do it
Users of a requirements document
Slide 54
IEEE requirements standard
Defines a generic structure for a requirements document that must be instantiated for each specific system.
Introduction. General description. Specific requirements. Appendices. Index.
Reference p137-138
Requirements document structure

Preface Introduction Glossary (collection of notes that explaining a text) User requirements definition System architecture System requirements specification System models System evolution Appendices Index
Figure 6.17 p139

Key points
Requirements set out what the system should do and define constraints on its operation and implementation. Functional requirements set out services the system should provide. Non-functional requirements constrain (drive) the system being developed or the development process. User requirements are high-level statements of what the system should do. User requirements should be written using natural language, tables and diagrams.
Slide 57
Key points
System requirements are intended to communicate the functions that the system should provide. A software requirements document is an agreed statement of the system requirements. The IEEE standard is a useful starting point for defining more detailed specific requirements standards.
Slide 58
Exercises
Slide 59
Ex6.3 Discover ambiguities and omissions for part of a ticket-issuing system. (p141)
An automated ticket-issuing system sells rail tickets. Users select their destination and input a credit card and a personal identification number. The rail ticket is issued and their credit card account charged. When the user presses the start button, a menu display of potential destinations is activated, along with a message to the user to select a destination. Once a destination has been selected, users are requested to input a personal identifier,\. When the credit transaction has been validated, the ticket is issued.
Slide 60
6.3(Ans) Ambiguities and omissions include:

Can a customer buy several tickets for the same destination together or must they be bought one at a time? Can customers cancel a request if a mistake has been made? How should the system respond if an invalid card is input? What happens if customers try to put their card in before selecting a destination (as they would in ATM machines)? Must the user press the start button again if they wish to buy another ticket to a different destination? Should the system only sell tickets between the station where the machine is situated and direct connections or should it include all possible destinations?
Slide 61
Ex 6.4
rewrite the above description using the structured approach described in this chapter. Resolve the identified ambiguities in some appropriate way. ps : use a standard form as figure 6.12
Slide 62
Ex 6.5
Draw a sequence diagram showing the actions performed in the ticket-issuing system. You may make any reasonable assumptions about the system. Pay particular attention to specifying user errors. (see p134. figure 6.14)
Slide 63
Ex 6.6
Using the technique suggested here, where natural language is presented in a standard way, write plausible (seem to be true) user requirements for the following functions:
Slide 64
Ex 6.6.1 the Cash-dispensing function in a bank ATM
Ans: The system must provide a facility which allows a specified amount to cash to be issued to customers. The amount is requested by the customer but the system may reduce this amount if the customers daily limit or overdraft limit is reached. The sequence of actions to dispense cash should be:
1. 2. 3.
4. 5.
The customer inputs the amount of cash required The system checks this against daily card limits and the customers overdraft limit. If the amount breaches either of these limits, then a message is issued which tells the customer of the maximum amount allowed and the transaction is cancelled. If the amount is within limits, the requested cash should be dispensed The customers account balance and daily card limit should be reduced by the amount of cash dispensed.
Slide 65
Ex 6.6.2 the Spelling-check and correcting function in a word processor
Ans: The system shall provide a user-activated facility which checks the spelling of words in the document against spellings in the system dictionary and user-supplied dictionaries. When a word is found in the document which is not in any dictionary, a user query should be issued with the following options:
Ignore this instance of the word Ignore all instances of the word Replace the word with a suggested word from the dictionary Replace the word with user-supplied text Ignore this instance and add the word to a specified dictionary
7.2.3 When a word is discovered which is not in the dictionary, the system should propose 10 alternative words based on a match between the word found and those in the dictionaries.
Slide 66
Ex 6.6.3
An unattended petrol (gas) pump system that includes a credit card reader. The customer swipes the card through the reader and then specifies the amount of fuel required. The fuel is delivered and the customers account debited.
Slide 67
Ex 6.6.3 (Ans) Fuel delivery system
Ans: The system should provide an unattended fuel delivery service where a specified amount of fuel is delivered to customers, The cost is deducted from the customers credit card account. The sequence of actions to dispense fuel should be:
The customer selects the type of fuel to be delivered. The customer inputs either a cash limit or a maximum amount of fuel to be delivered The customer validates the transaction by providing credit card account details.
Rationale: The amount of fuel allowed depends on the credit limit but customers may wish to fill up rather than have a specified amount of fuel. By specifying a maximum, the system can check if credit is available. Note that the definition does not set out how credit card details should be provided.
4. The pump is activated and fuel is delivered, under customer control. 5. The transaction is terminated either when the pump nozzle is returned to its holster for 15 seconds or when the customers fuel or cash limit is reached.
Rationale: Termination should not be immediate when the nozzle is returned as the customer may wish to restart the transaction e.g. to fill a fuel can as well as the car fuel tank. If a pump display is available, it may be appropriate to issue a Please wait for your receipt message.
6. A receipt is printed for the customer. 7. The fuel stock is updated.
Slide 68
EX 6.7
Describe four types of non-functional requirements that may be placed on a system. Give examples of each of these types of requirement.
Slide 69
6.7 (Ans): There are many possibilities here. Some suggestions are shown in Figure 6.4.
Slide 70
Ex 6.8
Write a set of non-functional requirements for the ticket-issuing system, setting out its expected reliability and its response time.
Slide 71
Ex 6.8 (Ans)
Possible non-functional requirements for the ticket issuing system include: 1. Between 0600 and 2300 in any one day, the total system down time should not exceed 5 minutes. 2. Between 0600 and 2300 in any one day, the recovery time after a system failure should not exceed 2 minutes. 3. Between 2300 and 0600 in any one day, the total system down time should not exceed 20 minutes. All these are availability requirements note that these vary according to the time of day. Failures when most people are traveling are less acceptable than failures when there are few customers.
Slide 72
Ex 6.8 (Ans)
5. The ticket issuing time after credit card validation has been received should not exceed 10 seconds. 6. When validating credit cards, the display should provide a status message for customers indicating that activity is taking place. This tells customer that the potentially time consuming activity of validation is still in progress and that the system has not simply failed. 7. The maximum acceptable failure rate for ticket issue requests is 1: 10000.
Slide 73
Ex 6.9
Suggest how an engineer responsible for drawing up a system requirements specification might keep track of the relationships between functional and non-functional requirements.
Slide 74
Ex 6.9 (Ans)
Slide 75
Slide 76
End
Slide 77

Software Requirements: ©ian Sommerville 2006

Uploaded by

Copyright:

Available Formats

Software Requirements: ©ian Sommerville 2006

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Requirements: ©ian Sommerville 2006

Uploaded by

Copyright:

Available Formats

Software Requirements

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Requirements abstraction (Davis)

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Definitions and specifications

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Functional and non-functional requirements

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

The LIBSYS system

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Examples of functional requirements

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Requirements completeness and consistency

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Ian Sommerville 2006

Ian Sommerville 2006

Software Engineering, 8th edition. Chapter 6

Non-functional requirement types

Product re quir e ments

Organisa tiona l re quir e ments

Externa l re quir e ments

Effic iency re quir e ments

Re lia bility re quir e ments

Porta bility re quir e ments

Inte r ope r a bility re quir e ments

Ethica l re quir e ments

Usa bility re quir e ments

De live ry re quir e ments

Imple menta tion re quir e ments

Sta ndar ds re quir e ments

Le gisla tive re quir e ments

Pe rforma nc e re quir e ments

Spa ce re quir e ments

Priva cy re quir e ments

Safety re quir e ments

Ian Sommerville 2006