"Requirements Shell" Please respond to the following:

Computer Science
Tutor: None Selected Time limit: 1 Day

Think of some cases in which the functional requirements contradict environmental requirements and give examples of how the contradiction occurs.

May 23rd, 2015

Functional requirements are statements of the capabilities that a system must have (“functions”), geared to addressing the business needs that a system must satisfy.

  • Necessary. Something that must be included or an important element of the system is missing and other system components can’t compensate for its absence.
  • Concise (minimalunderstandable). Stated in language that is easy to read, yet conveys the essence of what is needed.
  • Attainable (achievable or feasible). A realistic capability that can be implemented for the available money, with the available resources, in the available time.
  • Complete (standalone). Described in a manner that does not force the reader to look at additional text to know what the requirement means.
  • Consistent. Does not contradict other stated requirements nor is it contradicted by other requirements. In addition, uses terms and language that means the same from one requirements statement to the next.
  • Unambiguous. Open to only one interpretation.
The National ITS Architecture was developed to address user needs that were ultimately articulated as User Service Requirements.User Service Requirements are high-level functional requirements and the various elements of the National ITS Architecture deal with ways of satisfying them.Since User Service Requirements are included in the distribution media for the National ITS Architecture material, you can compare them to the functional requirements your own users provide, to see if your users may have overlooked any important requirements.However, the National ITS Architecture may address requirements that your region doesn’t have.For example, a rural area may not have the same requirements for transit information as does an urban area.

Example, an ease of learning requirement might translate into the functional requirement of having the system display pop-up help when the user hovers the cursor over an icon. A quality attribute may also translate into product-level nonfunctional requirements that specify the characteristics the software must possess in order to meet that attribute. For example, an ease-of-use requirement might translate into nonfunctional requirements for response time to user commands or report requests.

May 23rd, 2015

Studypool's Notebank makes it easy to buy and sell old notes, study guides, reviews, etc.
Click to visit
The Notebank
...
May 23rd, 2015
...
May 23rd, 2015
Dec 9th, 2016
check_circle
Mark as Final Answer
check_circle
Unmark as Final Answer
check_circle
Final Answer

Secure Information

Content will be erased after question is completed.

check_circle
Final Answer