3.5 Systems Analysis Flashcards
Waterfall
linear approach to systems development implying one stage of the project has to be done before proceeding. High investment in early stages and fixed requirements are set.
Suitbale for simple project with set requirements (not innovative and complicated).
Extensive documentation is both good and bad as it allows for clarity and ** traceability** for each stage but it distracts developers from actually coding **
and can be time consuming.**
The waterfall method has lack of user involvement and only involves them when signing off.
Heavily dependent on spec. Client cant fully articulate what is wrong with the system or what they really want. Client cant really understand understand system or capbiltiy of technlogy and can put them at **risk of being an early adopter. **
Development can take so long that orignal requirements no longer reflect what is needed.
Testing is towards end so if** issues are found may not be enough time to fix them**
Stakeholders only get to see product until after realease.
Stages of Waterfall Method
Analysis - requiremnts documentation is created, outlining functionilaty and user needs, client must sign off this
Design - A design spec is produced, used as blueprint for developers, includes DFD’s and data dictonaries
Development - Code documentation is created to help write code ( comments technical description)
Testing - A test plan is developed and executed, heavy documentation
Implementation - A user guide to help users understand how it works
Maintanance - change request logs and update reports are maintained
Agile
**Adaptive approach, focusing on iterative development **
It involves creating numerous prototypes and then get feedback ASAP he user to identify good and bad things which is used to refine the prototype. There is** light documentation** the** user story** which gives the user a perspective on a feature. This documenation **also supports collbaration and adaptability **and actually **allows developers to focus on coding. **
The user is the priority however if they give too much input then they can become a scope creep and continually add requiremtns and overload work.
Much more interaction between stakeholders and developers teams, which speaking of the** teams have breaks** and regroup to discuss efficiecncy.
Promotes sustainable development and is a simplistic process by maxismising amount of work not done is essential
Downsides include scope creep (as mentioned) and lack of documentaion can be prove to be difiicult for tracebality and adpabiltoy as th ceratin **projects that require long term mainatnce or tracked regualraly **
