SWEBOK decomposes the software engineering tools and methods knowledge area into two subareas: tools and methods. The tools subarea is decomposed as with SWEBOK itself. The methods subarea is decomposed into heuristic methods, formal methods, and prototyping methods.
Formal Methods (13)
- Formal methods provide a rigorous, mathematical based framework for specifying, defining, and verifying systems. These methods provide the basis for the precise definition of consistency, completeness, specification, implementation, and correctness.
Inspections (9)
- A Software Inspection is a formal review of a work product by the work product owner and a team of peers looking for errors, omissions, inconsistencies, and areas of confusion in the work product. A formal inspection is performed according to established procedures and schedules. A typical inspection includes the following stages: Planning, Overview Meeting (Kickoff), Preparation, Inspection Meeting, Rework, and Follow-up. A formal inspection has well-defined roles for participants, such as moderator, recorder, reader, author, and inspector.
See also DACS Gold Practice href="https://www.goldpractices.com/practices/fi/index.php">Formal Inspections.
DACS Gold Practice Initiative
