S D L C
Download as PPTX, PDF1 like205 views
The systems development life cycle (SDLC) describes the process of planning, creating, testing, and deploying an information system. It involves several key phases: preliminary analysis, requirements definition, design, development, integration and testing, deployment, maintenance, and disposal. Each phase serves an important purpose in properly analyzing requirements, designing the system, developing and testing code, deploying the final product, and maintaining or replacing the system. Testing occurs at various stages to ensure quality and identify issues. The SDLC process helps information systems meet goals on time and on budget.
S D L C
- 1. SDLC Systems development life cycle
- 2. What is SDLC The systems development life cycle (SDLC), also referred to as the application development life-cycle, is a term used in systems engineering, information systems and software engineering to describe a process for planning, creating, testing, and deploying an information system.
- 3. Phases ● Preliminary analysis ● Systems analysis, requirements definition ● Systems design ● Development ● Integration and testing ● Acceptance, installation, deployment ● Maintenance ● Evaluation ● Disposal
- 4. Preliminary analysis The objective of this phase is to conduct a preliminary analysis, propose alternative solutions, describe costs and benefits and submit a preliminary plan with recommendations. 1. Conduct the preliminary analysis 2. Propose alternative solutions 3. Describe the costs and benefits
- 5. Systems analysis, requirements definition Defines project goals into defined functions and operation of the intended application. It is the process of gathering and interpreting facts, diagnosing problems and recommending improvements to the system. Analyzes end-user information needs and also removes any inconsistencies and incompleteness in these requirements. 1. Collection of Facts 2. Scrutiny of the existing system 3. Analyzing the proposed system
- 6. Systems design Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.
- 7. Development The real code is written here.
- 8. Integration and testing Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.
- 9. Acceptance, installation, deployment The final stage of initial development, where the software is put into production and runs actual business.
- 10. Maintenance During the maintenance stage of the SDLC, the system is assessed to ensure it does not become obsolete. This is also where changes are made to initial software. It involves continuous evaluation of the system in terms of its performance.
- 11. Evaluation This is where the system that was developed, as well as the entire process, is evaluated. Some of the questions that need to be answered include: does the newly implemented system meet the initial business requirements and objectives? Is the system reliable and fault-tolerant? Does the system function according to the approved functional requirements?
- 12. Disposal In this phase, plans are developed for discarding system information, hardware and software in making the transition to a new system. The purpose here is to properly move, archive, discard or destroy information, hardware and software that is being replaced, in a manner that prevents any possibility of unauthorized disclosure of sensitive data. The disposal activities ensure proper migration to a new system. Particular emphasis is given to proper preservation and archival of data processed by the previous system. All of this should be done in accordance with the organization's security requirements
- 13. Few More Not every project will require that the phases be sequentially executed. However, the phases are interdependent. Depending upon the size and complexity of the project, phases may be combined or may overlap.
- 14. System investigation The system investigates the IT proposal. During this step, we must consider all current priorities that would be affected and how they should be handled. Before any system planning is done, a feasibility study should be conducted to determine if creating a new or improved system is a viable solution. This will help to determine the costs, benefits, resource requirements, and specific user needs required for completion. The development process can only continue once management approves of the recommendations from the feasibility study Following are different components of the feasibility study: 1. Operational feasibility 2. Economic feasibility 3. Technical feasibility 4. Human factors feasibility 5. Legal/Political feasibility
- 15. System analysis The goal of system analysis is to determine where the problem is, in an attempt to fix the system. This step involves breaking down the system in different pieces to analyze the situation, analyzing project goals, breaking down what needs to be created and attempting to engage users so that definite requirements can be defined.
- 16. Design In systems design, the design functions and operations are described in detail, including screen layouts, business rules, process diagrams and other documentation. The output of this stage will describe the new system as a collection of modules or subsystems.
- 17. Environments Environments are controlled areas where systems developers can build, distribute, install, configure, test, and execute systems that move through the SDLC. Each environment is aligned with different areas of the SDLC and is intended to have specific purposes Examples of such environments include the: 1. Development environment 2. Common build environment 3. Systems integration testing environment 4. User acceptance testing environment 5. Production environment
- 18. Testing The code is tested at various levels in software testing. Unit, system and user acceptance testings are often performed. This is a grey area as many different opinions exist as to what the stages of testing are and how much, if any iteration occurs. 1. Unit testing 2. System testing 3. Integration testing 4. Black-box testing 5. White-box testing 6. Regression testing 7. Automation testing
- 19. Training and transition Once a system has been stabilized through adequate testing, the SDLC ensures that proper training on the system is performed or documented before transitioning the system to its support staff and end users.
- 20. More ● Evaluation ● Object-oriented analysis ● Work breakdown structured organization
- 21. Thanks! Contact: Sudipta K Paik Associate Technology Manager [email protected] 01719100070