1.) Three Systems Development Life Cycles are: The traditional system life cycle, the prototype system life cycle, and the application package system life cycle. Each system life cycle will pass through the four phases that any informational system must go through; the initial phase, the development phase, the implementation phase, and the operation and maintenance phase.
In the traditional life cycle, the primary issue addressed is control. Through the course of this cycle, a fixed sequence of steps are taken, followed with a sign-off after each step that is coupled with careful documentation. Ultimately, this approach attempts to solve a control problem by keeping the project in focus and on course. In the prototype life cycle approach, the primary issue addressed is knowledge. In this, a working model of the system is built so that the builders may learn about the systemÆs true requirements. Once this is done, that model is used and tested, ultimately revealing how the final system should function. In the application package cycle approach, the primary issue addressed is one of resources and timing. To achieve this, an information system that already exists is purchased from a vendor and then possibly customized. Application packages are used when a resource and timing problem can be best studied through the utilization of software that is commercially available.
In implementing an enterprise software solution, the traditional approach may be the most comprehensive. The implementation plan includes planning, training, converting to the new business processes, acceptance testing, and post-implementation auditing; these serve to create a structure in which formal acceptance by the users is likely. Because an enterprise system would demand a large amount of information in a unified database, it might be prudent to also initiate a prototype cycle. The task of implementing an enterprise software solution is a large ...