System development lifecycle
In my next few blogs I will be discussing each stage of the system development lifecycle in more detail. Today I will be talking about the first stage Planning.
Before a system analyst can begin to design a system for a business they must first identify the problem to be solved. They normally receive a request from users seeking a system. Once they have identified the problem, they then start looking for ways of solving it. This stage is very important because it would be a waste of valuable time to try and solve the wrong problem. The analyst must examine the business carefully and work with the users to fully understand the problem. The analyst may also come across areas of the business which could be improved by the introduction of a system, and this may give the business a competitive edge. Once a team is established it must develop appropriate documents such as a business case and project feasibility, these contain a problem definition and a summary of objectives. It is then up to management to decide whether or not to go ahead with the project and provide the necessary resources.
I will be blogging about the next stage soon.