Establishing
Requirements
Establishing
requirement is the process of establishing the services that the customer
requires from a system and the constraints under which it operates and is
developed. Requirements themselves are the descriptions of the system services
and constraints that are generated during the requirements engineering process.
But identifying requirements is one of difficult tasks in SDLC due to reason.
Above cartoon video demonstrate well why establishing requirements
are not that much easy in real world scenarios. In some cases,
stakeholders fail to articulate requirements well and all the requirements
of the product may not be explored in detail. Requirements as gathered are
invariably incomplete. They are in various stages of preparation; they contain
mistakes, design choices, and ambiguities. All requirements are not of equal
importance to the customers and users of the planned system. Some are critical,
some of relatively high priority, some of normal or average priority, and some
even of lower priority. Fixing error at late stage of SDLC is expensive in
terms of money and time. So establishing complete and consistent set of
requirements is very crucial to project success.
Paper
Prototyping
Paper prototyping is a widely used in the process of user centered
design the attached video demonstrate the process of prototyping and
discuss its advantages of applying into designing UIs.
With paper prototyping,
software products can be tested before its implementation saving time and money
due to its simplicity. Modification to the design is easy and inexpensive. As
no specific experience is required to draw the paper prototype, everybody in
the team can be involved so that it eliminate the chance of missing some key
personal in design process.
Above
cartoon video demonstrate well why establishing requirements are not that much
easy in real world scenarios. In some cases, stakeholders fail to
articulate requirements well and all the requirements of the product may not be
explored in detail. Requirements as gathered are invariably incomplete. They
are in various stages of preparation; they contain mistakes, design choices,
and ambiguities. All requirements are not of equal importance to the customers
and users of the planned system. Some are critical, some of relatively high
priority, some of normal or average priority, and some even of lower priority. Fixing
error at late stage of SDLC is expensive in terms of money and time. So
establishing complete and consistent set of requirements is very crucial to
project success.
No comments:
Post a Comment