Read time: 2 mins
What are the phases in a Systems Development Life Cycle (SDLC)? | FAQs
Mastering the Systems Development Life Cycle (SDLC) is crucial if you want to stand out as a BSA in this lucrative and competitive industry. Brent Combrink, Head Tutor of the University of Cape Town Business Systems Analysis online short course, explains more about the SDLC and how it affects a business analyst’s role. Watch the video to find out more about how your understanding of the SDLC could affect your role as a systems analyst:
As a systems analyst you need to be able to identify the generic phases of the SDLC including feasibility, requirements development and systems specification design. You will also be required, as a BSA, to integrate this SDLC process with a project life cycle to ensure that all the business objectives are met and that systems and process are ultimately improved. This includes reviewing the project and ensuring that its implementation has led to improvement within the business case. The SDLC relies heavily on including and supporting the relevant stakeholders to ensure all parties are satisfied.
If you want the skills to become a top BSA and be able to make the most of the SDLC for your organisation’s success, find out more about this UCT business analyst course.
Transcription
The generic phases in a Systems Development Life Cycle (SDLC) are typically, start with feasibility then develop your requirements then design the system specifications and then implement the system. When you integrate the SDLC with a typical project life cycle, you may include the project review for example, that includes a review of the system’s effectiveness once it is implemented, as well as a post review so after the system has been implemented and used for a few months, you will actually compare the effective change in the organisation compared with the business case and the intentions of that change.