This is where they put the ideas together from the planning and start to make the system, into something that is almost workable and usable.
To generate a high-level view of the project and determine the goals of the project. Figure out what the want done, what the need done, and how to get it done.
Once the new system is up and running for a while, it should be evaluated. Maintenance must be kept up rigorously at all times. Users of the system should be kept up-to-date concerning the latest modifications and procedures. This is also where the maker works with the people that need the system to make sure everything works like its suppose to. Routine changes are not as complex as major modifications and can usually be implemented in the normal course of business. Routine change controls should include procedures for requesting, evaluating, approving, testing, installing, and documenting software modifications.
Find out what they system they need or figure out the problem so they can start to think about a solution.
Take the over all project in a working form and put it to work, maybe that is plugging in information to solve the problem, finding away to sell the program, or giving it to the person who needed the system made.