FIT4004 Lecture Notes - Lecture 3: Fagan Inspection, Software Development Process, Formal Methods
15 Jun 2018
School
Department
Course
Professor
Week 3 - Reviews, inspections, and walkthroughs
Reviews/inspections/walkthroughs: assess the quality of an (SE project) artefact:
●Formal methods
●Execution-based testing
●Human inspection
*Out of formal methods, execution-based testing and human inspection; inspection is the
most useful for improving software quality.
Why inspect?
●Bugs hardest to fix
○when requirements are misunderstood
○When dumb architectural decisions are made
●Easiest bugs to fix - typos, code does the wrong thing
●Defects detected by testing
Fagan Inspections
A Fagan inspection is a structured process of trying to find defects in development documents
such as programming code, specifications, designs and others during various phases of the
software development process
Who?
●The moderator - a developer, preferably with special training in running Fagan
inspections, but not necessarily directly involved with the feature being
inspected.
●The designer - the person who designed the feature which the code under
inspection implements.
●The coder - the person who wrote the code.
●The tester - the person who is writing the test cases for the code.
Document Summary
Reviews/inspections/walkthroughs: assess the quality of an (se project) artefact: *out of formal methods, execution-based testing and human inspection; inspection is the most useful for improving software quality. Easiest bugs to fix - typos, code does the wrong thing. A fagan inspection is a structured process of trying to find defects in development documents such as programming code, specifications, designs and others during various phases of the software development process. The moderator - a developer, preferably with special training in running fagan inspections, but not necessarily directly involved with the feature being inspected. The designer - the person who designed the feature which the code under inspection implements. The coder - the person who wrote the code. The tester - the person who is writing the test cases for the code. Process: overview - designer explains the design of component under review, preparation - participants study artifact individually and are also provide with.
