Systems development life cycle
[2] There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation.
Various SDLC methodologies have been created, such as waterfall, spiral, agile, rapid prototyping, incremental, and synchronize and stabilize.
Sequential or big-design-up-front (BDUF) models, such as waterfall, focus on complete and correct planning to guide larger projects and limit risks to successful and predictable results.
The list of phases is not definitive, but typically includes planning, analysis, design, build, test, implement, and maintenance/support.
In the Scrum framework,[8] for example, one could say a single user story goes through all the phases of the SDLC within a two-week sprint.
By contrast the waterfall methodology, where every business requirement[citation needed] is translated into feature/functional descriptions which are then all implemented typically over a period of months or longer.
Information systems activities revolved around heavy data processing and number crunching routines".
Analyze end-user information needs and resolve inconsistencies and incompleteness:[16] At this step, desired features and operations are detailed, including screen layouts, business rules, process diagrams, pseudocode, and other deliverables.
This may involve training users, deploying hardware, and loading information from the prior system.
Related information and infrastructure must be repurposed, archived, discarded, or destroyed, while appropriately protecting security.
[18] In the following diagram, these stages are divided into ten steps, from definition to creation and modification of IT work products: Systems analysis and design (SAD) can be considered a meta-development activity, which serves to set the stage and bound the problem.
This high-level description is then broken down into the components and modules which can be analyzed, designed, and constructed separately and integrated to accomplish the business goal.
SDLC and SAD are cornerstones of full life cycle product and system planning.
During the analysis phase, a programmer develops written requirements and a formal vision document via interviews with stakeholders.
The conceptual model that results from OOAD typically consists of use cases, and class and interaction diagrams.
Customers in remote rural areas are finding difficulty to access the bank services.
The feasibility study should address operational, financial, technical, human factors, and legal/political concerns.
This step involves decomposing the system into pieces, analyzing project goals, breaking down what needs to be created, and engaging users to define requirements.
In systems design, functions and operations are described in detail, including screen layouts, business rules, process diagrams, and other documentation.
Modular design reduces complexity and allows the outputs to describe the system as a collection of subsystems.
The final phase of the SDLC is to measure the effectiveness of the system and evaluate potential enhancements.
Control objectives are clear statements of the desired result or purpose and should be defined and monitored throughout a project.
Control objectives can be grouped into major categories (domains), and relate to the SDLC phases as shown in the figure.
[22] Baselines[clarification needed] are established after four of the five phases of the SDLC, and are critical to the iterative nature of the model.
