The Systems Development Lifecycle (SDLC) is an older IS development method used for large projects with formal specifications and tight controls. However it is expensive, rigid, time-consuming, expensive and discourages changes once user requirements are done (Morgan, 2020). SDLC works in traditional systems development models in structured environments. According to Morgan (2020), SDLC provides high degrees of control, accountability and error detection. There are alternative methods:
JAD
Joint application design is a group approach used eliciting user requirements and creating new IS designs.
JAD is commonly used in the systems analysis and design stages. It uses meetings to bring users and analysts together to discuss the business needs for the system and its functional design thus saving time on a project and improving overall communication.
RAD
Rapid application development (RAD) can be combined with JAD and other methods such as prototyping, and integrated computer-assisted software engineering (ICASE).
In RAD stage 1, developers collect user requirements and later develop low fidelity prototypes for users to review and provide feedback on. Iterations are later made as required. Additional JAD sessions are required over the project until completion
Agile
Agile software development is used to deliver more frequent user testing/feedback capture and thus IS iterations which can reduce risk, time consumed and cost to a project. Agile involves frequent communication between the development team and users for feedback testing, and delivery. Agile emphasis fast development, lots of testing/feedback and several IS iterations to reduce problems, time, cost to the business. Each iteration presented addresses a specific issue as the core principle of agile is to do only what is required to be successful right now. Scrum is a part of agile, it recognises that users may not fully understand their requirements at the start of a project and that ongoing user engagement/requirement elicitation is required over the project to improve its success.
EUD
End-user development allows users to create their own IS or tools with low code tools/templates and little assist from their IT department. For example: creation and running of the Salesforce CRM system or Mailchimp CRM.
EUD can also be called Shadow IT / Stealth IT / Rogue IT. While freeing up the IT teams time/resources int eh short term, EUD has its drawbacks as end-users may bypass development best practices or the organisations IT policies/procedures. Additionally, is the new IS is highly integrated with other systems in the organisation, it can cause organisation wide concerns if it malfunctions or is incorrectly implemented or risk data leaking from the organisation opening it up to GDPR concerns and reputational damage etc.
To find out more about how we can help with training click here.