Having described the planning stage of the SDLC in my last blog, today I am going to move on to the second stage which is the Analysis stage.
In the Analysis stage of the SDLC the current system is analysed. The system is analysed by asking questions such as what problems exist and why, is there alternative ways of setting up the system and is the efficiency of the system meeting the needs of the organisation.
The requirements of the new system are developed. The objectives for the system development are defined and structured. The analyst developing the system lobbies the systems users to find out what they want from the new system. The analyst can gather this information by 3 different methods: Traditional, Modern and Radical. The traditional methods of gathering information are interviews, surveys, observation and business documents. Joint Application Design (JAD), Group Decision Support Systems (GDSS) and Prototyping are examples of modern methods of gathering information. Business Process Re-Engineering is an example of a radical method of gathering information.
In the analysis stage the analyst will decide on possible solutions to the problem and ways of building a new system. The analyst can choose to purchase packaged software, develop custom software or outsource the system development to an outside source.
The key deliverables of the analysis stage are:
• A Business Requirements Statement
• Data Flow Diagram and Entity Relationship Diagram of the current system
In my next post I will be discussing the Design Phase of the SDLC.