Informal approach
Introduction: The informal approach to analysis is that where no defined method is used. Like any approach, information about the system is obtained through the client, end users, questionnaires, study of existing documents, thought-churning etc. However, no formal model system is built with this approach. Problems and system models are essentially made up of analysts (or analysts can use some informal notation for this purpose) and are analyzed directly from the minds of analysts in SRS.
Often, with such an approach, the analyst will have a series of meetings with customers and end users. In the initial meetings, the client and the end user will explain to the analyst about their work, their environment and their needs, as they understand them. Any document describing the work or organization can be given with the output of existing methods of performing tasks. In these early meetings, analysts are basically listeners, absorb the information provided. Once the analyst understands the system to some extent, he uses the next few meetings to get an explanation of those parts which he does not understand. He can document information in any way (if he wants to make a model too), and he may have some brainstorming or thinking about what the system should do. In the last few meetings, the analyst essentially explains to the client what he understands what the system should do and uses as a means of verifying the meetings if he proposes that the system is actually in the customer's Must be in accordance with the objectives. In the final meetings, the initial draft of SRS can be used. Also read
Choosing an informal approach for specification, analysis is not very risky - the errors that can be presented are not necessarily slipping from the stage of the requirements. Therefore, such approaches can be the most practical approach to analysis in some situations.
Often, with such an approach, the analyst will have a series of meetings with customers and end users. In the initial meetings, the client and the end user will explain to the analyst about their work, their environment and their needs, as they understand them. Any document describing the work or organization can be given with the output of existing methods of performing tasks. In these early meetings, analysts are basically listeners, absorb the information provided. Once the analyst understands the system to some extent, he uses the next few meetings to get an explanation of those parts which he does not understand. He can document information in any way (if he wants to make a model too), and he may have some brainstorming or thinking about what the system should do. In the last few meetings, the analyst essentially explains to the client what he understands what the system should do and uses as a means of verifying the meetings if he proposes that the system is actually in the customer's Must be in accordance with the objectives. In the final meetings, the initial draft of SRS can be used. Also read
PROBLEM ANLYSI
The informal approach for analysis is widely used and can be quite useful. The reason for its usefulness is that conceptual modeling-based approach often does not model all facets of the problem and is not always well suited for all problems. Apart from this, as SRS is to be validated and further analysis may be needed to respond to the verification activity orChoosing an informal approach for specification, analysis is not very risky - the errors that can be presented are not necessarily slipping from the stage of the requirements. Therefore, such approaches can be the most practical approach to analysis in some situations.
from Technology development http://bit.ly/2YlHW5S
Comments
Post a Comment