In order for the development of an appropriate information system and in accordance with the business requirements of the Organization, its activities analysis undertaken in the initial phases of the development cycle needs to be done carefully. Why is this so? Because accurate results from the investigation of the needs of the business was able to become the cornerstone of a robust and credible in order to become a guide in the development phase of the system further. These are activities that occur in the stage analysis:
Gather information. In this activity, the analyst will perform a collection of a number of information. Information can be gathered through:
- An interview or observation of the users of the system
- Conduct a review of the planning documents and statements related to the policies that apply to your organization,
- Studied carefully against the dokumentassi of the former or the system is running
- Conducting benchmarking with other organizations that have the same business requirements.
In the end, after the activity was completed, the question that should be answered by the analyst to e
nsure that this activity has gone well is: "Do we have all of the information (and insight) we need to define what the system must do?".
Define system requirements. After all the needed information has been collected, all such information should be recorded and stored properly. Some of the information that has been collected can be described as technical requirements (e.g. is the fact on the desired system performance or the number of transactions that can be handle by the system) and functional requirements (subject function of whatever bias done/done by the system). Various types of models are used to assist in the recording of this need. In addition models also facilitates the communication with the technical people about what is needed in the development of the system. In the end, after the activity was completed, the question that should be answered by the analyst to ensure that this activity has gone well is: "What (in detail) do we need the system to do?".
Prioritize requirements. After all the needs of intelligible system together and models which details have been completed, it is important to determine the functional or technical requirements which are the most important for the system. However, users or analysts need to coordinate to determine which requirements are more important to the requirements of prioritasasi made. In the end, after the activity was completed, the question that should be answered by the analyst to ensure that this activity has gone well is: "What are the most important things the system must do?".
Prototype for business feasibility and discovery. Build prototypes of parts of the system will be very useful in order to make it easier to understand the needs of users. Prototypes were made to check the functionality of the system was built, and to ensure that the system is in compliance with the needs of the business. In the end, after the activity was completed, the question that should be answered by the analyst to ensure that this activity has gone well is: "Have we proven that the technology proposed can do what we think we need it to do?" and "Have we built some prototypes to ensure the users fully understand the potential of what the new system can do?".
Generate and evaluate alternatives. Alternatives design and implementation need to be prepared to be evaluated everything possible the best from each of the alternatives. So diprioritasasi, requirements analyst can make some alternative by eliminating requirements that are less important. In addition, technology-related things can also give rise to new alternatives to the system. In addition, the consideration of who will build the system, whether in-house or by using external consultants, will also influence the decisions taken. Each alternative has its costs, benefits, and his characteristics of each. Therefore each of the alternatives need to be measured and evaluated in advance in order to produce the best akternatif. In the end, after the activity was completed, the question that should be answered by the analyst to ensure that this activity has gone well is: "What is the best way to create the system?".
Review recommendations with management. All previous activities can be executed in parallel (gather information, define requirements, prioritize requirements, prototype for the discovery and business feasibility, and generate and evaluate alternatives). Review again the existing recommendations and the management are usually implemented when other analysis activities have been completed or are nearing completion. Management must be kept informed about the progress of the development of a reporting system through the project periodically. And the project manager should be able to recommend a solution to get decisions from the management (whether they agree, disagree, wanting to continue or not to continue the project). In the end, after the activity was completed, the question that should be answered by the analyst to ensure that this activity has gone well is: "Should we continue with the design and implement of the system we propose?".
That Activities in Analysis System. Hopefully helpful and keep Learn Information System
Conversion Conversion Emoticon Emoticon