

Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
It contains all the steps to understand in system analysis and design under the SYSTEM DEVELOPMENT LIFE CYCLE
Typology: Summaries
1 / 2
This page cannot be seen from the preview
Don't miss anything!


1. Preliminary Investigation The preliminary investigation is the first phase of the System Development Life Cycle (SDLC), during which the need for a new system is identified. This phase involves recognizing problems, opportunities, or directives that require action. These may stem from internal issues, such as inefficiencies, or from external influences, such as government regulations or management decisions. An initial survey is conducted to understand the situation and clearly define the problem. The result of this phase is a clear statement of the project’s scope, objectives, and performance criteria, which guides the rest of the development process. 2. Feasibility Study The feasibility study evaluates whether the proposed system is practical and worth implementing. It examines the existing system and determines if the new system will meet user needs while making effective use of available resources. This phase includes analyzing costs, benefits, and possible alternative solutions. It also assesses the system’s technical, economic, and operational viability. Based on this evaluation, a decision is made on whether to proceed with the project. The system’s scope and objectives may also be refined during this stage to ensure clarity and relevance. 3. System Analysis System analysis involves a detailed study of the current system to understand how it operates and identify its weaknesses. In this phase, data is collected through methods such as interviews, observation, and document review. The goal is to identify problems and determine what improvements are needed. The information gathered is then organized using tools like data flow diagrams (DFDs) and data dictionaries, which help in creating a logical model of the system. This phase ensures that all user requirements are clearly understood before designing the new system. 4. System Design The system design phase focuses on planning how the new system will function. It involves creating detailed specifications for inputs, processes, outputs, and data storage. Alternative solutions are considered and evaluated through cost-benefit analysis to select the most suitable
design. This phase also includes defining hardware and software requirements, security measures, and system procedures. The system is then developed in modules, which are later integrated and tested to ensure they meet user requirements. The design phase results in a complete blueprint that guides the system’s implementation.
5. Implementation Implementation is the phase where the designed system is put into operation. This involves installing the system, converting data from the old system to the new one, and training users on how to use it effectively. User manuals and documentation are provided to guide users during operation. The training program should be user-friendly and prepare users to handle system functions, delays, or errors. Once implementation is complete, the system becomes fully functional and begins supporting organizational activities. 6. Operations and Maintenance After implementation, the system enters the operations and maintenance phase. In this stage, the system is monitored to ensure it performs as expected. Any errors or issues are identified and corrected, and improvements are made to enhance system performance. Maintenance may involve updating software, improving security, or adding new features. User feedback is also considered to ensure that the system continues to meet their needs and operates efficiently over time. 7. Project Termination Project termination occurs when a system development project is stopped before or after implementation. A project may be terminated for several reasons, such as changes in budget, increased costs beyond estimates, delays in completion, or changes in user requirements that cannot be met by the system design. Additionally, if the expected benefits do not justify the cost of implementation, the project may be discontinued. Termination is easier in the early stages but becomes more difficult and costly after the design phase. This phase ensures that resources are not wasted on unviable projects.