Systems Development Lifecycle (SDLC)
The Systems Development Lifecycle (SDLC) is a process for planning, creating, testing, and deploying an information system (IS). ‘Systems development is a structured kind of problem solved with distinct activities’ (Laudon and Laudon, 2019). (Taylor, 2004), states "the project life cycle encompasses all the activities of the project, while the systems development life cycle focuses on realizing the product requirements".
The systems development Lifecycle (SDLC) is the framework or process used to develop new information systems (IS) for an organisation to meet business needs. The goal of the new system and the SLC are to create value for an organisation. A new system may include implement a new enterprise resource planning system such as Oracle or implement ing a new sales process using Hubspot Sales Hub. It help IS professionals and developers to design the new system with some level of user engagement over the lifecycle, build the new system based on the design and deliver the system to the users.
The SDLC is can be iterative as the system is design and released, changes made be made based on new developments or user feedback making it a more adaptable and favoured approach for many organisations.
The systems analyst can be seen as a key team member on the SDLC. The assess the user requirements, design how the system will work (to meet these requirements), analyse the situation, identify improvements required, and design the IS. They will also be involved in user training, adoption and ongoing maintenance.
The key phases in the SDLC include:
- Requirement Analysis
- Design
- Implementation
- Testing
- Evaluation
(Note: Requirement Analysis and Design can also be combined into a ‘Planning’ phase)
Requirement Analysis
This phase involves identify the business needs for the IS - what the IS must do. This involved requirements elicitation from managers/users and requirements determination. Requirements may be functional and non functional.
Requirement elicitation involves the project team engaging with managers and users to identify what the new IS must do/achieve. Various methods are used such as: interviews, Joint Application Development (JAD) sessions, questionnaires, document analysis and observation. Next, requirements determination is an analysis performed by the project team in which they translate user requirements into a precise list of requirements which guide the design and function of the IS.
Design
In this phase, a design or layout of the new IS is created to identify how it work technically work. This includes the data inputs/outputs, other systems it must interact with and the processes/steps it will go through. This is more technical in nature and relates to system architecture that is used to achieve business outcomes. Screenshots, process diagrams and other documentation are created. Managers and users will likely be consulted again to ensure the system design is sufficient before proceeding to build/implementation.
Design includes 4 phases:
- Develop a design strategy
- Develop the basis architecture design for the system
- Develop Database and file specifications
- Develop the program design
Implementation
This phase involves the build or development of the new system and includes 3 steps:
- System construction - This can be time consuming and requires coordination. The IS is being build by developers who may be in-house, outsourced or a combination.
- System installation -Once the new system is built, the old system is replaced. This may be done on a phased basis, dual running based or an over night bases.
- Establishment of a Support Plan - for the system by the analyst team e.g. post-implementation review
Testing
Testing assesses the new systems functionality compared to desired results. Based on results, changes may be required to the IS. Flexible methods such as agile allow for more frequent testing and iteration cycles that older methods such as waterfall, therefore it may be favoured by many organisations.
Evaluation and maintenance
As the new IS is rolled out across the department or organization it is assessed and management receives an implementation report. Modifications may be required to correct errors, meet unidentified user requirements or improve efficiency according to Laudon and Laudon (2019).
To find out more about how we can help with training click here.
