Furps model

 This model tells us in what way we can collect requirements of our

project.
 In the unified process the requirements are categorized according to
FURPS+ model
 It is useful as the checklist for your project to reduce further risks.
 Some of the requirements are collectively called quality
attributes/requirements.

Functional requirement:
Functional requirements define the basic system behavior. Essentially, they are
what the system does or must not do, and can be thought of in terms of how
the system responds to inputs. Functional requirements usually define if/then
behaviors and include calculations, data input, and business processes.
 What are the features of requirements?
 What will be the capabilities of your requirement?
 What will be the security requirement?
 How will you want to secure your project and to what extent?
 These are also called behavioral requirements.

Usability requirement:
Usability Requirements for an interface design should support the following
from the perspective of its primary users:
 Efficiency of use: goals are easy to accomplish quickly and with few or
no user errors
 Intuitiveness: the interface is easy to learn and navigate; buttons,
headings, and help/error messages are simple to understand
 Low perceived workload: the interface appears easy to use, rather than
intimidating, demanding and frustration.
 The project should be easy to use and user friendly.
 Documentation: how much details you want about your project’s
documentation (number of chapters, depth)
 After this we will know if the software is useable or not.
Reliability Requirement:
 How much reliable your project is?
 Frequency of failure
 We will choose a project with less frequency of failure, but if failure
occurs the second step will be Quick and easy recovery.
 Recoverability: how quick and easy a failure can be required.
 Predictability: we will be able to predict that this project will take this
much time.
 Accuracy: we have an expected state and an actual state. If the
difference between these two states is zero, we will have accuracy.
 Availability of resources: you will have resources available to effectively
meet new orders or requirements.
 Resource usage: better management if resources
 Example: we have 2 photocopy machines, ABC and XYZ
 ABC is reliable, xyz is not.
 We give both machines a task to photocopy 1000 copies. We knowing
the reliability of ABC, we will be able to predict that this machine will
take 10-15 minutes in completing the task. On the other hand, we will
not be able to make any statement about XYZ.

Performance requirement:
Performance requirements define how well the system performs certain
functions under specific conditions. Examples are speed of response,
throughput, execution time and storage capacity.
 Response time: quick, response time.
 Throughput: number of tasks completed in per unit time.
 Example: a photocopy machine copies 100 copies in minute it’s the
throughput.
Supportability requitement:
 Adaptability: portable, can be transferred.
 Maintainable: easily maintainable
 Internationalization: if you want to present your product in international
or to bigger audience.
 Configurability: changeability, your product should be configurable
(changes should be easily made).