Requirement process
Introduction: -The essential process is the sequence of activities that need to be executed in the stage of the requirements and which create a high quality document containing the software requirements specification (SRS). The process of requirements usually consists of three basic functions: problem or Requirements analysis, requirement specification, and requirements verification
Problem analysis often begins with a high-level "problem statement". During the analysis, the problem is modeled in an effort to understand the behavior of the domain and the environment in the system, barriers to the system, its input and output, etc. To get the full understanding of the need to provide the software to the activity. The understanding gained by problem analysis is the basis for the specificity of the requirements, in which the focus is on clearly specifying the requirements in the document. Issues such as representation, specification language More tools are addressed during this activity. Since the analysis produces large amounts of information and knowledge with possible redundancy, properly arranging and describing the requirements is an important goal of this activity. Requirements Verification is focused on ensuring what is specified in the SRS. In fact, all the requirements of the software and to ensure that SRS is of good quality, the revision process ends with the production of valid SRS.
Linear So it seems that the process of requirements is a linear sequence of three activities, in fact this is not something other than the Trivialist system. In most of the actual systems, these activities have considerable overlap and feedback. Therefore, some parts of the system are analyzed and the other parts are analyzed, while thesecapsifid is done. Apart from this, if verification activities occur in SRS due to verification activities, then it is likely to lead toforter analysis and specification. However, in general, for a part of the thesis system, the analysis provides predetermined specification and specification prior verification.
This happens when parts of the problem are analyzed and then the other parts are specified before analyzing and specifying. In addition, the specification process often shows an in-depth knowledge of the problem, which requires further analysis. Oncethe specification is "complete" it goes through verification activity. This activation can disclose problems in specifications, for which there is a need to return to the specification phase, or may reveal the shortcomings in understanding the problem, for which the need to return to the analysis activity.
During analysis of needs, the focus is on understanding the system and its requirements. For a complex system, this is a difficult task, and the time-tested method "Divide-end-Conquer," that is, dismantling the problem or the system into smaller parts and then understanding the parts and their relationships, essentially to manage The complexity is applied to Apart from this, for the management of complexity and large quantities of information available during analysis, different structures are used during the analysis so that information is represented to help the system look as a series of abstract. Could
From the analysis to the specification, however, it seems like it should be simple; It's not like this. In fact, this infection can be quite difficult. Due to the difficulties of this transition, the two activities have different objectives. In the specification, we have to specify only what the software has to do, i.e., focus on the external behavior of the system.
It is worth noting that some similarities exist in the analysis activity and design activity. The approach used is similar decomposition and construction structures to represent the system's essence. Due to this similarity, the approaches used for problem analysis and design are often the same. However, although the perspectives are the same, the purpose of the two activities is completely different.
Finally, the level of detail is the issue to highlight and specify the need process. This is also a problem which can not be easily solved and this requirement depends on the purpose of the specification phase. If the objective is to define the overall comprehensive requirements of the system, then the requirements can be said very briefly.
Problem analysis often begins with a high-level "problem statement". During the analysis, the problem is modeled in an effort to understand the behavior of the domain and the environment in the system, barriers to the system, its input and output, etc. To get the full understanding of the need to provide the software to the activity. The understanding gained by problem analysis is the basis for the specificity of the requirements, in which the focus is on clearly specifying the requirements in the document. Issues such as representation, specification language More tools are addressed during this activity. Since the analysis produces large amounts of information and knowledge with possible redundancy, properly arranging and describing the requirements is an important goal of this activity. Requirements Verification is focused on ensuring what is specified in the SRS. In fact, all the requirements of the software and to ensure that SRS is of good quality, the revision process ends with the production of valid SRS.
Linear So it seems that the process of requirements is a linear sequence of three activities, in fact this is not something other than the Trivialist system. In most of the actual systems, these activities have considerable overlap and feedback. Therefore, some parts of the system are analyzed and the other parts are analyzed, while thesecapsifid is done. Apart from this, if verification activities occur in SRS due to verification activities, then it is likely to lead toforter analysis and specification. However, in general, for a part of the thesis system, the analysis provides predetermined specification and specification prior verification.
This happens when parts of the problem are analyzed and then the other parts are specified before analyzing and specifying. In addition, the specification process often shows an in-depth knowledge of the problem, which requires further analysis. Oncethe specification is "complete" it goes through verification activity. This activation can disclose problems in specifications, for which there is a need to return to the specification phase, or may reveal the shortcomings in understanding the problem, for which the need to return to the analysis activity.
During analysis of needs, the focus is on understanding the system and its requirements. For a complex system, this is a difficult task, and the time-tested method "Divide-end-Conquer," that is, dismantling the problem or the system into smaller parts and then understanding the parts and their relationships, essentially to manage The complexity is applied to Apart from this, for the management of complexity and large quantities of information available during analysis, different structures are used during the analysis so that information is represented to help the system look as a series of abstract. Could
From the analysis to the specification, however, it seems like it should be simple; It's not like this. In fact, this infection can be quite difficult. Due to the difficulties of this transition, the two activities have different objectives. In the specification, we have to specify only what the software has to do, i.e., focus on the external behavior of the system.
It is worth noting that some similarities exist in the analysis activity and design activity. The approach used is similar decomposition and construction structures to represent the system's essence. Due to this similarity, the approaches used for problem analysis and design are often the same. However, although the perspectives are the same, the purpose of the two activities is completely different.
Finally, the level of detail is the issue to highlight and specify the need process. This is also a problem which can not be easily solved and this requirement depends on the purpose of the specification phase. If the objective is to define the overall comprehensive requirements of the system, then the requirements can be said very briefly.
Software requirements specification
from Technology development http://bit.ly/2Q4kw2l
Comments
Post a Comment