sonam
Joined: 21 Apr 2007
Posts: 16
|
 Posted: Sat Apr 21, 2007 5:41 am Post subject: What's the big deal about requirements'? |
 |
|
What's the big deal about requirements'?
One of the most reliable methods of ensuring
problems, or failure, in a large, complex software project is to have poorly
documented requirements specifications. Requirements are the details describing
an application's externally-perceived functionality and properties. Requirements
should be clear, complete, reasonably detailed, cohesive, attainable, and
testable. A non-testable requirement would be, for example, 'user-friendly' (too
subjective). A testable requirement would be something like 'the user must enter
their previously-assigned password to access the application'. Determining and
organizing requirements details in a useful and efficient way can be a difficult
effort; different methods are available depending on the particular project.
Many books are available that describe various approaches to this task. (See the
Bookstore section's 'Software Requirements
Engineering' category for books on Software Requirements.) |
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
