Discussion Topic

Well-defined business requirements are essential building blocks to any system project. If requirements are not written well, the input to design and development phases will be poor. However, well-written requirements will lead to a much better project outcome in relation to stronger designs and system solutions.
What are 2 key attributes to well-written requirements? How do these attributes impact the quality of requirements? How might you assess system requirements based off these attributes?
Post your answers to the discussion forum.
Respond to at least three of your peers. In your response, consider providing other impacts of the attributes listed. 

Peer 1

Hello everyone!
What are 2 key attributes to well-written requirements? How do these attributes impact the quality of requirements? How might you assess system requirements based off these attributes?
Usability in one of the important attributes because the users can see directly how well this attribute of the system is worked out. Example list of supported devices, operating system versions, screen solutions, browser and their versions. Elements that accelerate user interaction. Average time user needs to perform individual actions. Support of accessibility.
Consistent, system functions and performance level must be compatible and the required quality features ( reliability, safety, security, etc) must not contradict the utility of the system. Performance defines a metric that states the amount of work an application must perform in a given time. Qualities of application can be readily quantified and validated. Performance is a key quality attributes needed to be considered in architect, it affects the entire system and can affect many parts of the architectural solution.
Quality attributes include functional suitability, performance, compatibility, usability, reliability, security, maintainability, and portability they affect the systems behavior, design and user interface during work. And attributes affect the development and support of the system.

Peer 2
Based of attributes, Assessing he well written project will relay on concise, Flexibility of that project and implementing certain phases for instance: waterfall or agile steps that can be extremely helpful. Also inappropriate use of that particular design maybe compromise to certain extent, if it not being apply as clear understanding of what type of project you want to measure.

Peer 3

In relation to a stronger designs and systems solution, consistency and testable are the most exceptional attributes to Well-written requirement. Furthermore, software developers may apply these concepts to verify whether the requirements is simple enough to integrate correctly. These attributes of well-written requirements particularly methodology software system and depending on certain design or external interface that directly relate to the project. In addition to their subject matter, they may be design as additional description of function which might be important for stakeholders.