Qualified Software Demand Specifications
Software demand specifications must have a comprehensive result of the product demand: All requirements must be included. Developers and customers cannot make any assumptions. If any desired function or non-functional requirement is not written to a software requirements specification, it will not be part of the protocol and cannot appear in the product.
Construct and write software requirements specifications and enable users and other readers to understand it in mind the following readability:
• Number, section, section, and single demand must be consistent.
• Leave a text annotation area on the right part.
• Use spaces to be used without restrictions.
• Correctly use a variety of visual emphasis markers (eg, black body, underscore, slope, and other fonts).
• Creating a directory table and an index table helps readers find the information they need.
• Specify the number and identification number of all the diagrams and tables, and you can check it by number.
• Use the functions of the cross-references in the word handler to see other items or locations in the document, not by the page number or ninth.
1.5 Excellent demand features
How to distinguish between good demand specifications and problem specifications for problems? The characteristics of a single demand statement statement will be discussed below (Davis 1993; IEEE 1998). Let the risk bearers conduct serious review from different angles to S R s requirements, which can determine which needs are indeed. As long as you are writing and reviewing demand, you will write better (although not very perfect) demand document, it will also develop better products.
1.5.1 Characteristics of Demand Instructions
Integrity
Each requirement must clear the description of the functionality to be implemented to enable developers to get all the necessary information needed for design and implementing these features.
2. Correct
Each requirement must accurately state its function to develop. References to make the correct judgment are the source of demand, such as user or high-level system requirements specifications. If the software requirements are in contrast to the corresponding system demand, it is incorporated. Only the user represents to determine the correctness of the user's needs, this is the reason for the active participation of users. The need for users will have such statements: "Those who are meaningless, these are probably what they want." In fact, this is exactly the reviewers to guess.
3. Feasibility
Each requirement must be implemented within the known system and environmental and restrictions. In order to avoid unpasquility needs, it is best to have a member of a software engineering team in the process of acquiring the demand (collecting requirements), working with people who need to analyze or consider the market, by him responsible for inspecting technical feasibility. .
4. Necessity
Each requirement should record the criteria required by the customer's truly needed and the final system. "Necessity" can also be understood as "root" that each requirement is used to authorize you to write documents. To enable each requirement to retroactive into a customer's input, such as using instances or other sources.
5. Division priority
Assign an implementation priority to each requirement, feature, or using an instance to indicate the components of it in a particular product. If all the needs are as important as it is equally important, then project managers lose control in the development or saving budget or scheduling.
6. ignore
The readers who have instructions for all needs can only have a clear unified explanation. Since the natural language is extremely easy to lead to erliness, they try to express each demand with a simple and clear user's language. Avoiding an erliness method comprises forming a regular review, writing test cases, development prototypes, and design specific scheme scripts for demand documents.
7. Authenticity
Check if each requirement can be achieved by designing test cases or other verification methods, such as demonstration, detection, etc. to determine if the product is actually implemented. If the demand cannot be verified, it is determined whether it is the subjective precaution, not an objective analysis. An implicit needed for a conflict before and after, unpredictable needs.
1.5.2 Characteristics of requirements specifications
Integrity
You cannot miss any necessary requirements. I miss the demand will be difficult to find. Focus on the user's tasks instead of the system's functionality will help you avoid incompleteness. If you know a missing information, use T B D ("to be determined" as a standard identification to indicate this lack. Before starting development, you must solve all T b D items in the demand. 2. Consistency
Consistency refers to non-contradictions with other software requirements or high-level (system, business) demand. You must solve the inconsistency between all requirements before development. Only a survey study can only know if a requirement is indeed correct.
3. Changeable
When necessary or when the history is changed to maintain the history of each requirement, S R is revised. This requires every need to be independently marked and distinguishes out of other needs, so that there is no meaning. Each requirement should only appear once in S R s. This is easy to maintain consistency when changing. In addition, using the directory table, index, and mutual reference list method will make the software requirements specifications are easier to modify.
4. Trackability
The link chain should be established between each software demand with its root and design elements, source code, and test cases, which requires every demand with a structured, granularity (Fine - grained) Writing and indicated separately, not the narrative of the large segment.
