Unit 6 - Explain the role of software design principles and software structures in the IT systems development lifecycle
The waterfall model
Requirement Analysis
Systems Design
Implementation
Testing
Development
Maintenance
Requirement Analysis
Systems Design
Implementation
Testing
Development
Maintenance
The waterfall model a design process that goes through its stages in a sequential manner. It starts from the top and flows downwards, hence the name “waterfall model”. After a stage is done, there is no going back. This makes it so it is mainly used for smaller projects or projects where the requirements are know well. This is also because it is very simple to use and understand, but lacks the stability to use for long/ongoing projects.
Having a very linear development lifecycle model had its strengths and weaknesses.
Strengths:
The time it took for planning was short because people can plan one stage at a time.
Most over development lifecycle models wasted time and effort with going over already complete stages, this did not.
Weaknesses:
Once the process starts, there is very little room for change. This makes it inflexible.
Due to it not going over completed stages, it made clearing up mistakes a lot harder.
Stages of a waterfall model
Requirement Analysis:
All the requirements of the new system will be listed.
System Design:
All the requirements are discussed and studied before the system design is prepared.
Implementation:
Multiple small programs called units are developed and tested for their functionality.
Testing:
The units are combined into one system. This is then tested for faults.
Development:
After everything is done being developed and tested, the system will be released or given to the business that wanted it.
Maintenance:
There will always be bugs; these will be fixed in patches.
Unit 6 - Explain the importance of the quality of code
Ronnie Marsciapharoas
Unit 6 -...