1 / 7

The Traditional System Development Life Cycle

The Traditional System Development Life Cycle.

velmaf
Download Presentation

The Traditional System Development Life Cycle

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Traditional System Development Life Cycle There are a number of important steps in the creation of a system, regardless of which approach you use. You may choose to ignore some of these steps and combine others, but all need to be considered. The traditional system development life cycle (SDLC) makes all these steps explicit. At the highest level, there are three steps: • Analysis • Design and construction • Implementation (and continuing Operations)

  2. The Traditional System Development Life Cycle I. Analysis Go? No go? • Initiation (e.g., an RFP) • Feasibility study • Technical – can we build it? • Economic – should we build it? • Operational – if we build it, will it be used? • Schedule – will it be ready in time? • Requirements definition • Specifications • Project plan

  3. The Traditional System Development Life Cycle II. Design 6. Logical design (i.e., the external view) 7. Physical design (i.e., the internal view) 8. Coding (or code acquisition) 9. Testing

  4. The Traditional System Development Life Cycle III. Implementation 10. Documentation – ouch! This should have been done all along! 11. Conversion • Direct • Parallel • Pilot • Phased 12. Training – both initial and continuing • Users • I/S staff • Management 13. Installation

  5. The Traditional System Development Life Cycle IV. Operations 14. Production 15. Post-implementation audit 16. Maintenance

  6. The Traditional System Development Life Cycle Why conduct a post-implementation audit? To answer these four questions: • Did we deliver the system that we promised to deliver; it is working as promised? If not, we should fix it. • If it is working as promised, is the user harvesting the benefits; i.e., achieving the economic results that he promised to achieve? If not, he should be made to do so. • Are there new features that should be added to the system? • What have we learned from this project that can help us with how we do projects in the future?

  7. The Traditional System Development Life Cycle What is maintenance? “It is post-implementation software development, designed to ensure the continued effectiveness of the software in question.” There are three types of maintenance: • Corrective • Adaptive • Perfective How should maintenance be managed? • “Cradle-to-grave”; those who built it, maintain it. • Separate maintenance department. • Outsource the maintenance to a third party.

More Related