Please enable JavaScript.
Coggle requires JavaScript to display documents.
Alternative Development Approaches - Coggle Diagram
Alternative Development Approaches
Waterfall
Requirements Stage
During this stage, the analyst establishes the essential requirements, they should fully understand the requirements and document them, they should do this by analysing any current existing systems and also by getting a comprehensive list of requirements from the end users
The deliverable of this stage is a system specification which is very detailed and outlines what is required in the system
Design Stage
Starts with the system specification and leads to the production of a system that fully complies with it, just with no code at this stage.
The design includes both the software units and the interaction between them, also the design of user interfaces and the identification of hardware needs.
The deliverable of this stage is a highly precise and unambiguous design document
Implementation Stage
This is the stage where the code is developed and implemented into the user interface from the design stage. The implementation team works in accordance with the design document provided by the design stage
The deliverable of this stage is a working system
Testing Stage
The system from the implementation stage is tested to make sure it meets the system specification. The system must be tested to ensure it works in accordance with the specification and there has been no misunderstanding or misinterpretation of the system specification
The deliverable of this stage is a testing record and completed test plan
Maintenance Stage
Made up of 5 distinct stages, each stage must be completed before the next stage can begin and all stages produce a deliverable
Once the system has been developed and passed all the necessary tests, it needs to be installed into the users organisation.
Once it is installed, the short term maintenance includes migrating data from the old system to the new one, and in the long term is fixing any issues, perfecting the system and adapting the system to any changing needs.
RAD
Splits the project up into a series of 'builds'. All requirements are ranked in priority order and the timescale can not be overrun, some requirements may not be completed if they run out of time.
Requirements Phase
Planning and investigative part of the methodology, where all parties meet and agree on the key elements of the project, including the requirements. Can be compared to the waterfall requirements phase, apart from RADs requirements are less rigid and are more flexible
User Design Phase
Characterised by regular interaction between end users and system analysts, with prototypes playing a key role. Prototypes allow the user to get a rough idea of the system and request any changes . The user interfaces are designed in this phase.
Construction Phase
Deals with the actual programming of the software
The users are still involved in this stage and can request changes to be made. Testing also takes place in this phase
Cutover Phase
The transition from the old system to the new system. Once this change of systems has taken place, it involves a significant amount of further testing as the change over of the system is affected
Agile Approach
Brings together the best parts and techniques of existing methodologies. Provides early and continuous delivery of software, has close collaboration between team members and the customer, and welcomes any changes to the user requirements throughout the process
Product Backlog
The project backlog is a 'wish list' of what the product should be able to do. The maintenance of the product backlog is crucial to the methodology
Release Backlog
At the start of each phase in the project, release planning is carried out, this is the planning and selection of what will be in the next software release. All features added to the release backlog will be removed from the product backlog. The release backlog can also include tasks from outside the product backlog such as minor fixes etc
Sprints
After the release backlog is made, a time estimate is made for the next sprint and the tasks are put in order. Over a couple weeks, the sprint aims to make a release of all the items in the release backlog, all tasks completed will be removed from the release backlog and the same process will begin again
Scrum and Scrum Team
refers to the whole framework of carrying out a project in sprints, everyone works as one unit
The scrum team is made of personnel with the necessary skills to perform the sprints
A pivotal member of the scrum team is the scrum master, who is responsible and accountable for the project. they ensure the team functions appropriately and they remove any obstacles getting in the way of the development process. They also arrange meetings and will monitor the process and the work being done
One member of the team will be designated product owner, they are the voice of the client making sure everything is up to standards and they also look after the tasks in the backlog, managing their priority
Daily Scrum
A brief meeting ran daily to ensure the process is running smoothly, all team members are asked:
What did you do yesterday?
What are you planning on doing today?
What obstacles are getting in your way?
Burn Down Charts
A chart that shows the amount of work that still needs to be done against the scheduled timeline. This can deviate as some tasks can take longer than expected due to unforeseen circumstances. This chart allows the scrum master to identify when the project is going off track and that corrective action may be required.