Requirement Analysis Checklist

Requirement Analysis Checklist

This requirement checklist contains a series of self-testing questions about your project requirements. This book does not discuss how to make a good requirement document, nor does this checklist. But with this checklist, you can check whether your work foundation is solid and reliable when creating a job. Not every problem listed in the table applies to your project. If you are engaged in an informal project, you will find that you do not need to consider this question at all, and you will also find some questions that need to be considered but not answered. However, if you are working on a large project, we suggest you carefully consider every problem.

 

Requirement content
· Are all inputs of the system defined? What are their sources, precision, value range, and frequency?
· Have all the outputs of the system been defined? What are their goals, precision, value range, frequency, and format?
· Are all report formats defined?
· Are all hardware and software interfaces defined?
· Are all communication interfaces defined? Including handshakes, error checks, and communication conventions?
· Is the response time of all necessary operations defined from the user's point of view?
· Have you defined time problems, such as processing time, data transmission rate, and system throughput?
· Does the User Require the task department to be completed?
· Are the data required and generated for each task specified?
· Do you set the confidentiality level?
· Is the reliability specified? Includes the consequences of software errors, critical information to be protected in case of errors, and error testing and recovery policies.
· Is the maximum memory required?
· Is the maximum storage capacity required?
· Do we have provisions on system maintainability? Does the system define the system's ability to adapt to changes in the runtime environment, precision, performance, and other software interfaces?
· Does it stipulate the principles of compromise between conflicting designs, for example, how to compromise between robustness and accuracy?
· Have we set standards for system success or failure?

Perfection of requirements
· What information is temporarily unavailable before development starts? Is there a well-defined region?
· Has the requirement definition been completed to the point where it can become a software standard?
· Is there any disturbing demand? Is there anything that can't be achieved, but is added only to please the boss and users?

Requirement Quality
· Is the requirement determined in the user's language? Does the user think so?
· Do I have to avoid conflicts between each line of a requirement?
· Do you need to pay attention to avoiding the design work?
· Is the requirement consistent in terms of detail? Should there be more detailed requirements? Should it be simpler?
· Is the requirement clearly divided into some independent executable parts, and each part is clear?
· Are each question and answer related? Is each entry traceable to the environment in which it is generated?
· Can each requirement be used as a test basis? Can I perform an independent test on each entry to determine whether it meets the requirements?
· Are possible changes specified? Including the possibility of each change?

 

 

This article from: http://dev.rdxx.com/SoftProject/SystemsAnalysis/Demand/2005-9/13/054155831.shtml