Systems Development Life Cycles: Private to Public Sector

Systems Development Life Cycles: Private to Public Sector

University of Phoenix

CIS/319 Assignment #1

Introduction:

The Systems Development Life Cycle (SDLC) is defined by dictionary.com as "Any logical process used by a systems analyst to develop an information system, including requirements, validation, training, and user ownership." However this definition significantly simplifies the process involved in obtaining an 'end' product. The SDLC is so complicated that it can be compared to that of the development of a child. It is on-going process and must be facilitated by the parental figure (i.e. a systems analyst). Without the parent, the child will most likely fail, being unable to learn how it can efficiently complete tasks; much like a business would most likely fail if it did not continually try to improve the quality, cost, and efficiency of producing it's end product.

The steps involved in the SDLC vary depending on the chosen approach taken by the company, which may be a Traditional route to the use of the Rapid Application Development process. Each varies based on the manner they are delivered to the consumer/company.

The Traditional SDLC:

The traditional systems development life cycle employs a five step process which is dependent upon various factors including the training of faculty for success. This method's success requires that the company be flexible in a continually changing environment. The process at times requires cycling which may result in a period of decreased efficiency.

The process begins with a systems investigation in which the company determines its current problem and the cost to benefit ratio for correction. If a new system is found to be more beneficial than the current system, the next step is initiated which is termed systems analysis. The current system is examined for its "strengths, weaknesses, and opportunities for improvement" (Fundamentals of Information Systems, 313). Once these factors are identified the design of a new system begins. This phase is fairly general, however, it seeks to answer the question of how the new system will function. After this point the system is implemented by the company, and training