Blog 9 (Pawandeep Kaur)
CHAPTER – 10 Functional Requirements
Functional
Requirements: Functional
requirements describe what the product has to do to support and enable the
owner’s work. They should be, as far as possible, independent of the technology
used by the eventual product. The functional requirements specify the product
to be developed, so they must contain sufficient detail for the developer to
build the correct product with only the minimum of clarification and
explanation from the requirements analyst and the stakeholders.
Description
and Rationale: in simple
words I can say that a statement, picture in
words, or account that describes; descriptive representation. the act or method
of describing. Here is an example of description:
Description: The product shall record
roads that have been treated.
now to describe the rational: The rationale indicates whether
the requirement is worthy of some attention. Its different keywords to define it:
having reason or understanding, relating
to, based on, or agreeable to reason, involving only multiplication,
division, addition, and subtraction and only a finite number of times.
Example of rational:
Rationale: To be able to schedule
untreated roads and highlight potential danger.
Exceptions and Alternatives:
Alternatives arise when you wish the user to have a
choice of possible actions, and these choices are intentional as these are
wanted and define by the business. These alternatives are used to make the
business use case more attractive and convenient to the participants.
Exceptions are unwanted variations but inevitable
deviation from normal case. You can find the exceptions by examining each step
of normal case and by asking the questions on each step like what went wrong in
this step? Here is an exception condition as example:
If there are
no trucks available, the product shall generate an emergency request to truck
depots in adjacent counties.
Conditional
Requirements: the conditional
expectation, conditional
expected value, or conditional mean of a
random variable is its expected value – the value it would take “on average”
over an arbitrarily large number of occurrences – given that a certain set of "conditions" is known to
occur. Sometimes, you need to add
a condition to a requirement. This happens when the requirement comes into play
only if certain processing circumstances have occurred. For example:
If a road scheduled for treatment has
not been reported within 30 minutes of its scheduled time, the product shall
issue an untreated road alert.
Technological Requirements: Technological
requirements are functionality that is needed purely because of the chosen
technology. In the example of the use case that produces the de-icing schedule,
the product interacts with the thermal mapping database. Suppose the designer
decides that handling this interaction via an Internet connection is the best
option. Because of this technological choice, the product has a need to
establish a secure connection. Technological requirements arise purely because
of the chosen technology. As an example, for our project like we are using a
virtual reality to give online training to drivers so we also need technical
requirements like: we need better
operating system, best quality of 3D screens, and better headset for effective
training.
Grouping Requirements: by using functional requirements it becomes easy to discover
related groups of requirements and to test the completeness of the
functionality. Nevertheless, sometimes other groupings may prove more useful.
The word “feature” springs to mind here. The meaning and scope of a feature
vary depending on the situation. A feature could be as small as turning on an
indicator light or as large as allowing the user to navigate across a
continent. Indeed, the feature itself is often important from a marketing point
of view. Even so, different features have different degrees of value to the
organization.
I want to talk about functional requirements. A functional requirement describes the functionality of a system or one of its subsystems. It also depends upon the type of software, expected users and the type of system where software is used. Moreover, functional requirements may be high-level statements of what the system should do but functional system requirements should also define clearly about the system services in detail. Functional requirements break down the steps needed to meet business requirements. Functional requirements specify particular results of a system.
ReplyDeleteI want to talk about the technological requirements which arises when the project is using some kind of the technology in it. It is not chosen for the business purpose but used when the project needs the technology to used in it. So, these requirements are recorded in the separate paper or template. This is because it is important for the stakeholders to understand the business requirements first rather than the technological requirements. As in our project as well we are defining the sensing gloves, high-tech headset are listed under the output devices.
ReplyDeletei want to talk about exception and alternatives means alternatives describes a possible actions other than the basic flow that results in a user completing his or her goal. It is often considered to be an optional flow. It implies that the user has chosen to take an alternative path through the system whereas Exceptions means represent an undesirable path to the user that have no link to desirable goals.
ReplyDelete