Retrun to HomePage

---

Summary

Inspection checks are question driven inspection checks, for example for code review or deployment review.

---

Schema

* Title
* Applies to
* Description
* <<Additional questions>>
* Additional Resources
* Related Items

---

Test Cases

Title
* Is the Title in the form of a question?
* Is the Question part of a bigger question driven checklist? For example for Code Ewview or Deployment review.

Applies to
* Do you list technology and version? (e.g. ASP.NET 2.0)

Description
* Does the desciption details the options for the questions and what needs to be done for achieving the best results?
* Does the desciption list additional questions so as to derive the check to logical ending?

<<Additional questions>>
* Does it help in driving the check for logical ending?

Additional Resources
* Are the links from trusted sites?
* Are the links correct in context of the Inspection Check?

Related Items
* Are the correct items linked in context of the Inspection Check?

Additional Tests to Consider When Writing a Checklist Item

* Does the title read like a question?
* Does the title lead correctly to appropriate check?
* If the item is a MUST, meaning it is prevelant and high impact, is Priority = p1?
* If the item is a SHOULD, meaning it has less impact or is only applicable in narrower circumstances, is Priority = p2?
* If the item is a COULD, meaning it is nice to know about but isn't highly prevelant or impactful, is Priority = p3?
* If this item will have cascading impact on application design, is Type = Design?
* If this item should be followed just before deployment, is concerned with configuration details or runtime behavior, is Type = Deployment?
* If this item is still in progress or not fully reviewed, is Status = Beta?

---

Example

* Inspection Check Example

---

Template

* Inspection Check Template

---

Links

* Inspection Check Example
* Inspection Check Template

---

Return to HomePage