SIT773: Software Requirements and Analysis - Life Cycle Case Study

This report focuses on the selection of an appropriate software development life cycle (SDLC) model for the SIT773 Software Requirements and Analysis course, specifically addressing the Leckie’s Choice (LC) case study. The assignment highlights the waterfall model as the most suitable approach due to its sequential nature, which aligns with the case study's requirements and the need to integrate various departments like sales, inventory, marketing, and supply. The report explains the advantages of the waterfall model, such as its structured approach and suitability for projects with clearly defined requirements, while also acknowledging its limitations, including the potential for errors to be fixed only during specific phases and the challenges in incorporating client feedback during the development process. The report also acknowledges the importance of quality assurance and the challenges associated with software changes during the development cycle. The report references Alshamrani and Bahattab (2015) and Elghondakly, Moussa and Badr (2015) to support its analysis. The report concludes by emphasizing the practical aspects of the waterfall model in this context.

Running head: SIT773 SOFTWARE REQUIREMENTS AND ANALYSIS
SIT773 SOFTWARE REQUIREMENTS AND ANALYSIS
Name of student
Name of university
Author’s note:

1
SIT773 SOFTWARE REQUIREMENTS AND ANALYSIS
Appropriate life cycle for the LC’s case study
The most appropriate model for the LC’s case study is the waterfall model. The
waterfall model could be described as the sequential model that helps in segregating the
software development into various phases. The waterfall model is the most appropriate model
for the project of LC’s case study because this model could be follows the sequential method
of completing the phases. Each of the phase is mainly designed for executing any particular
activity during the SDLC phase. The main advantage of the waterfall model are:
 Prior initiating the next phase of the development, every phase should be
completed
 Typically suited for the smaller project where the main requirements have been
clearly defined (Alshamrani and Bahattab 2015)
 They must perform the quality assurance test prior completing any particular stage
 Significantly elaborate documentation is required to be done at each phase of the
development cycle of the software
 Project is entirely dependent on the project team with the minimum client
intervention
 Any alteration in the software is executed during the main process of the
development
The main risks of this model could be categorised as:
 The errors could only be fixed during the phases (Elghondakly, Moussa and Badr
2015)
 The testing period emerges quite late within the development process
 The documentation occupies significant time of the testers and the developers

2
SIT773 SOFTWARE REQUIREMENTS AND ANALYSIS
 The including of the valuable feedback of the clients cannot be done with the ongoing
development phase
 The small errors or changes that develops within the completed software might cause
significant problems

3
SIT773 SOFTWARE REQUIREMENTS AND ANALYSIS
References
Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall
model, spiral model, and Incremental/Iterative model. International Journal of Computer
Science Issues (IJCSI), 12(1), p.106.
Elghondakly, R., Moussa, S. and Badr, N., 2015, December. Waterfall and agile
requirements-based model for automated test cases generation. In 2015 IEEE Seventh
International Conference on Intelligent Computing and Information Systems (ICICIS) (pp.
607-612). IEEE.