Software requirements ano
Introduction: The complexity and size of the software system is constantly increasing. As the scale changes into more complex and larger software systems, new problems arise which were not present in small systems, which redefine the priorities of the activities going to the developing software. One of the software requirements is that in the early days of software development, little importance was attached, because coding and design were emphasized.
As the systems became more complex, it became clear that the goals of the whole system could not be easily understood. Therefore the need for analysis of more stringent requirements arose. Now, for large software systems, analysis of requirements is probably the most difficult and precise activity; This is also very error prone. Many people believe that software engineering discipline is the weakest in this important area.
Some difficulty is due to the scope of this activity. Software project has been started according to client needs. In the beginning, these needs are in the minds of different people of the client organization. Needs analysts need to identify the requirements by talking to these people and understanding their needs. Under the circumstances where the software is currently for automating the manual process, many needs can be understood by looking at the current practice. But there are no methods available for the system for which the manual process is not present or for "new features", which are often while automating the existing manual process. For such systems, the problem of the requirements is complicated by the fact that the requirements and requirements of the system are not very well even the user has to imagine and create them.
Therefore, identifying the requirements is essentially to specify what is in the mind of some people. As the information in their mind, by nature, has not been formally stated or organized, specification of the software requirements specification phase is inherently informal and impermeable, and it is likely to be incomplete. When many inputs of many people are to be gathered, then these inputs are likely to be incompatible.
The phase of requirements translates ideas into the brain (input) of a formal document (output phase of the requirements). Thus, the output of the phase is a set of precisely specified requirements, which are expected to be complete and consistent, whereas none of these properties have input. Obviously, the process of specifying the requirements can not be completely formal; Any formal translation process should have a precise and ambiguous input for a formal production. This is the reason that the activity of software requirements can not be fully automated, and any method for identifying can be a set of best guidelines.
As the systems became more complex, it became clear that the goals of the whole system could not be easily understood. Therefore the need for analysis of more stringent requirements arose. Now, for large software systems, analysis of requirements is probably the most difficult and precise activity; This is also very error prone. Many people believe that software engineering discipline is the weakest in this important area.
Some difficulty is due to the scope of this activity. Software project has been started according to client needs. In the beginning, these needs are in the minds of different people of the client organization. Needs analysts need to identify the requirements by talking to these people and understanding their needs. Under the circumstances where the software is currently for automating the manual process, many needs can be understood by looking at the current practice. But there are no methods available for the system for which the manual process is not present or for "new features", which are often while automating the existing manual process. For such systems, the problem of the requirements is complicated by the fact that the requirements and requirements of the system are not very well even the user has to imagine and create them.
Therefore, identifying the requirements is essentially to specify what is in the mind of some people. As the information in their mind, by nature, has not been formally stated or organized, specification of the software requirements specification phase is inherently informal and impermeable, and it is likely to be incomplete. When many inputs of many people are to be gathered, then these inputs are likely to be incompatible.
The phase of requirements translates ideas into the brain (input) of a formal document (output phase of the requirements). Thus, the output of the phase is a set of precisely specified requirements, which are expected to be complete and consistent, whereas none of these properties have input. Obviously, the process of specifying the requirements can not be completely formal; Any formal translation process should have a precise and ambiguous input for a formal production. This is the reason that the activity of software requirements can not be fully automated, and any method for identifying can be a set of best guidelines.
Process management process
from Technology development http://bit.ly/2vPrxKZ
Comments
Post a Comment