•This is still fundamentally a software project because so many of the other elements associated with this type of project are present. Usually, there are three successive processes that bring a new system into being:
i) The feasibility study: This is an investigation to decide whether a prospective project is worth starting. The probable developmental operational costs, along with the Value of the benefits of the new system are estimated. With a target system, the feasibility study could be treated as a project in its own right.
ii) Planning: If the feasibility study produces results that indicate that the prospective project appears viable, then planning of the project can take place. In fact, for a large project, we would not do all our detailed planning right at the beginning.
iii)Project execution:The project can now be executed, Individual projects are likely to differ considerably but a classic project life-cycle.
vRequirements analysis: Thisis finding out in, detail what the users require of the system that the project is to implement Some work along these lines will almost certainly have been carried out when the project was evaluated but now the original information obtained need to be updated and supplemented.
vSpecification: Detailed documentation of what the proposed system is to do.
vDesign: A design that meets the specification has to he drawn up. This design activity will be in two stage. One will be the external or user design.
vCoding: This might refer to writing code in a procedural language such us C or Ada. or might refer to the use of a high level application builder. Even where software is not being built from scratch, some modification to the base application might be required to meet the need of the new application.
vVerification and Validation: Whether software is developed specially for the current application or not. Careful testing will be needed to check that the proposed system meets its requirements.
vImplementation/Installation:Some system development practitioners refer to the whole of the project after design as 'implementation' (that is, the implementation of the design) while others insist that the term refers to the installation of the system after the software has been developed.
vMaintenance and support: Once the system has been implemented there will be a continuing need for the correction of any errors that may have crept into the system and for extensions and improvements to the system.
•These are people who have a slake or interest in the project. It is important that they be identified as early as possible, because you need to set up adequate communication channels with them right from the start.
•The project leader also has to be aware that not everybody who is involved with a project has the same motivation and objectives.
•The end Users might, for instance, he concerned about the ease of use of the system while Iheir managers might be interested in the staff savings the new system will allow.
•Stakeholders might be internal to the project team, external to the project team but in the same organization, or totally external to the organisation.
q Internal to the project team: This means that they will he under the direct managerial control of the project leader.
qExternal to the project team but within the same urbanization: For example, the project leader might need the assistance of the information management group in order to add some additional data types to a database or the assistance of the users to carry out systems testing.
qExternal to both project team and organization:External stakeholders might be customers (or users) who will benefit from the system that the project implements or contractors who will carry out work for the project.