The Systematic approach to problem solving
No description yet. This curated deck is ready for daily study.
Card preview (10)
Advantages of the agile approach
• If the user isn’t sure what’s possible they can’t define requirements clearly, they are able to change things • If the analyst misunderstands the user’s requirements/ wishes they are able to change things • It is much easier to say what is wrong with a prototype version than to express in advance exactly what you are expecting • Making changes to a finished product is expensive/time consuming so it avoids this.
What will an analyst ask questions about?
• The data: origins, uses, volume, characteristics • The procedures: what is done, where, when, how • The future: development or expansion plans • Problems with existing solutions
Define the system life cycle
Analysis –> Design –> Implementation –> Evaluation –> Testing –> Maintenance
What is the agile approach?
• Getting feedback from the user throughout the development of a system so adjustments can be made at every stage
How are requirements of the new system established?
• The analyst must find out exactly what the user wants by • interviewing users • observing the current system • examining documentation
In the agile approach what may be required when establishing requirements of the new system?
-the process of clarifying requirements may involve building a prototype
What is acceptance testing?
• Where the intended user test the program to ensure the intended solution is met
What is testing boundary data?
• Test data that lies on the boundary of the systems expected range
What is testing erroneous data?
• Test data that lies outside of the systems expected range
What is testing normal data?
• Test data that lies within the systems expected range - It should return the expected output