EVALUATION
At least three evaluations must be made
Product
Resources
Process
Goal of this course: Evaluation of the software development process.
Side goal: Evaluation of the course delivery process
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community
Ask the community for help and clear up your study doubts
University Rankings
Discover the best universities in your country according to Docsity users
Free resources
Our save-the-student-ebooks!
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
Evaluation of Software Development & Course Processes: Boeing 737 Crashes Study, Study notes of Computer Science
The importance of evaluating software development and course processes through various means, including standard evaluations, post-accident reviews, and product evaluations. It uses the case study of boeing 737 crashes to illustrate the significance of identifying and addressing issues in the development process. The document also explores different evaluation methods, such as formal experiments and process evaluations.
Typology: Study notes
Pre 2010
1 / 6
This page cannot be seen from the preview
Don't miss anything!
Partial preview of the text
Download Evaluation of Software Development & Course Processes: Boeing 737 Crashes Study and more Study notes Computer Science in PDF only on Docsity!
EVALUATION
At least three evaluations must be made Product Resources Process Goal of this course: Evaluation of the software development process. Side goal: Evaluation of the course delivery process
STANDARD EVALUATION
The process could use improvement. We need to examine our deliverables. We could use more resources. Not enough (clerical) staff support. Too much time in meetings and/or meetings not well focused. Why was the product delivered late and over budget?
EVALUATING PRODUCTS
The “Dilbert Evaluation”: If it breaks, we can blame Microsoft. Questions: How much should your software rely on the proper operation of someone else’s software? Do you have to evaluate the Operating System every time you evaluate your product? Case Studies: Good if enough data. Apples can sometimes be compared to oranges. These can be retrospective, using existing data. Formal Experiments: More costly and time–consuming. Give much more reliable data.
EXPERIMENT DESIGN
Mathematical design theory focuses on an outcome dependent on a number of factors. How does one isolate the effect of a single factor when other factors may complicate the result. Agricultural design theory speaks of “treatments”, which has become the term of choice in many cases. Testing the effect of N pesticides and M fertilizers on cotton growth. Do we have NM patches of cotton, one for each combination of pesticides and fertilizer. What about soil conditions and watering?