Retrun to HomePage

---

Summary

Frequently asked question related to any technology, product, technique.

---

Schema

* Title - In the form of Question
* Applies to
* Answer:
* Additional Resources
* Related Items

---

Test Cases

Title
* Is the title in the form of a question?

Applies to
* Do you list technology and version? (e.g. ASP.NET 2.0)
Answer:
* Does it completely and scussefully address the question?
* Is the Answer decription brief anf to point with relevant pointers for more information?
Additional Resources
* Are the links from trusted sites?
* Are the links correct in context of the FAQ?
Related Items
* Are the correct items linked in context of the FAQ?
Additional Tests to Consider When Writing a Checklist Item

* Does the title read like a Question?
* Does the title represent a frequently asked question?
* 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

* FAQ Example

---

Template

* FAQ Template

---

Links

* FAQ Example
* FAQ Template

---

Return to HomePage