Posted: January 21st, 2023

Characteristics of a Good Requirement

Characteristics of a Good Requirement

Characteristics of a Good Requirement

The EMBOK Guide (ASEM, 2019: 2024 – Online Assignment Homework Writing Help Service By Expert Research Writers) states that requirements “define thresholds, targets, or criteria for a system… to determine whether a system is effective” (p. 237). Further, the EMBOK Guide states that requirements should be complete, consistent, unambiguous, clear, and verifiable. While this is a good list to start with, there are many other sources that define how to write a good requirement and the criteria for determining the goodness of the requirement.

This terminology for requirements may be confusing since the title of this module is a scope definition. However, scope and requirements are interrelated concepts. That is what you will explore in this forum.

Ace my homework – Write my paper – Online assignment help tutors – Discuss

Provide at least two examples of well-written requirements that apply to your selected project. Explain WHY these are well-written requirements by referring to the EMBOK Guide list and other criteria you have found in your readings.

Feel free to find a checklist of what is considered well-written requirements and include it in the discussion with proper citation).

Use at least three sources for this assignment including the EMBOK Guide. The sources should be academic or professional sources that you find on the Hunt Library or through similar places. The original posting should be at least 300 words and contain terminology from your sources and in-text citations in a format consistent with the Ace homework tutors – APA 7th edition.

NOTE:

My project is to design/build a balloon system capability of providing internet access to rural and remote areas. The real project’s name is Internet Remote Delivery System, formerly known as Project Loon.

One well-written requirement for my selected project, the Internet Remote Delivery System (formerly known as Project Loon), is that the balloon system must be able to provide internet access to remote and rural areas with a minimum of 10Mbps download and 2Mbps upload speeds. This requirement is specific, measurable, and verifiable. It defines a clear threshold for the system’s performance and provides a means to determine whether the system is effective in providing internet access to remote areas.

Another well-written requirement for the Internet Remote Delivery System is that the balloon system must be able to operate at an altitude of 60,000 feet for a minimum of 180 days. This requirement is also specific, measurable, and verifiable. It defines a clear threshold for the system’s operational capabilities and provides a means to determine whether the system can sustain prolonged operation in the stratosphere.

In general, a well-written requirement must be:

Specific: Clearly defines what the requirement is and what it is intended to accomplish
Measurable: Provides a means to determine whether the requirement has been met
Verifiable: Allows for the requirement to be tested or observed
Unambiguous: Avoids confusion or multiple interpretations
Complete: Addresses all necessary aspects of the requirement
Consistent: Does not conflict with other requirements
Clear: Written in simple and easy-to-understand language
Feasible: Realistically achievable within the given constraints
These characteristics are consistent with those identified in the EMBOK Guide (ASEM, 2019: 2024 – Online Assignment Homework Writing Help Service By Expert Research Writers) as well as in other sources such as the IEEE Standard for Software Requirements Specifications (IEEE, 1998) and the ISO/IEC/IEEE 29148:2011 standard for Engineering of Systems (ISO/IEC/IEEE, 2011). These standards provide guidelines and checklists for developing well-written requirements and are widely used in the software development and systems engineering industry.

References:

ASEM. (2019: 2024 – Online Assignment Homework Writing Help Service By Expert Research Writers). Engineering management body of knowledge (EMBOK) guide.
IEEE. (1998). IEEE standard for software requirements specifications.
ISO/IEC/IEEE. (2011). ISO/IEC/IEEE 29148:2011 – Systems and software engineering – Life cycle processes – Requirements engineering.

Order | Check Discount