The Analysis Phase: identification and description of the types of information needed to analyse the system | Diploma in Project Management
Navigate To
Prev: The Analysis Phase: identification and evaluation of sources of information | Next: The Analysis Phase: identification and description of problem areas in the current system
Topics
The Analysis Phase of the SDLC The Analysis Phase: creating the project team The Analysis Phase: defining information needs The Analysis Phase: identification and evaluation of sources of information The Analysis Phase: identification and description of the types of information needed to analyse the system The Analysis Phase: identification and description of problem areas in the current system The Analysis Phase: information flow and needs documented using system modeling tools The Analysis Phase: identification and description of problem areas in the current system The Analysis Phase: defining system performance criteria The Analysis Phase: creating a design proposalModules
Project management overview Project management methodology Project management toolset Project management documentation System development life cycle The planning phase The analysis phase The design phase The implementation phase The use/evaluation phase Project management case study Information Technology case study Toolset case study GANTT charts case study Documentation case study System development life cycle case study The planning phase case study Feasibility study case study The planning phase case study The analysis phase case study The analysis phase case study 2 The design phase case study Implementation phase case study 1 Implementation phase case study 2 Evaluation phase case study Implementation phase case study Case study conclusion Project Management Assessment
Transcript
XSIQ * Information Technology - The Analysis Phase: identification and description of the types of information needed to analyse the system The Analysis Phase: identification and description of the types of information needed to analyse the system Having identified the sources of information, the next step the analyst must take is to establish what information can be gained from them. The information which can be gained from the manager will be different from the data entry clerk, which will be different from the customers and so on. The analyst must decide what information should be obtained from each source identified. It is unusual for one user to be the exclusive source of information about the system. Most aspects of the system will have some degree of overlap - it may be that significant detail will come mainly from one source, but there will usually be other users who are also impacted, and information must be collected from them as well. As well as identifying who will be capable of supplying what information in this step, the analyst must also make decisions about the reliability and suitability of the sources. Information collected must be evaluated for bias and relevance and given the appropriate weighting in the overall analysis of the system. For example, while a manager and a data clerk would both have opinions on the usefulness of the financial reports produced by a particular system, the manager's opinion would have more weighting, but conversely, the data clerk's opinion has more significance in areas relating to the ease of data entry. Sometimes, the analyst will identify the need for other information in order to fully analyse the system. In this case, they would need to document where this information can be obtained. An example of this would be the need to conform to government privacy regulations with regard to the release of confidential data on individuals. Previous | NextView Comments and Reviews >>
