The Analysis Phase: identification and description of problem areas in the current system | Diploma in Project Management
Navigate To
Prev: The Analysis Phase: identification and description of the types of information needed to analyse the system | Next: The Analysis Phase: information flow and needs documented using system modeling tools
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 problem areas in the current system The Analysis Phase: identification and description of the types of information needed to design the system The analyst must ensure the new system meets all relevant regulations and standards - and to do this, they must first identify who the appropriate authorities are, and investigate and document the standards that are relevant to this system. Having established the type and sources of information needed to analyse the existing system, the next step is to identify and describe the information that will be needed to design the new system. While this sounds very similar to the previous step, there are some differences that must be noted. Much of the information needed to design the new system will come from the same sources used previously. The designer of the new system must take into account information from all relevant sources. Some of this information will relate to mandatory standards (that is, minimum standards imposed by government or regulatory authorities - usually relating to Occupational Health and Safety issues, or data security/privacy law). The analyst must ensure the new system meets all relevant regulations and standards - and to do this, they must first identify who the appropriate authorities are, and investigate and document the standards that are relevant to this system. There will be other external sources of information that an analyst may need in the design of a new system. These sources will usually provide the analyst with expert advice on various aspects of the proposed system - focusing on areas where time and/or money can be saved through applying skills or designs from other projects to this system. In essence, the system allows for the incorporation of developments in other projects into this one to ensure that the final product uses the most appropriate technologies available. Previous | NextView Comments and Reviews >>