I have published a new Requirements Document template for software development projects, aligned with my Requirements-By-Example Guide (http://www.analisi-disegno.com/requisiti/Requirements-By-Example.htm) It is a modular template. Each section can be a separate document, or remain just a section of the composite document. Each section may be more or less formalized, depending on actual needs and preferences. The Requirements Document template is intended to be used in non-life-critical projects, because it does not explicitly require - even if it allows - the traceability of requirements. The template can be found at: http://www.analisi-disegno.com/requisiti/RequirementsDocumentTemplate.htm Adriano Comai www.analisi-disegno.com
Hi Adriano,
Thank you for sharing this with the community! It looks like this is high-quality stuff.
Thanks again and keep on sharing the knowledge.
- Adrian
Adriano, interestings stuff. I'll be readin this next weekend.
Have you seen the Specification by Example stuff by Goijko Adzic?
Adriano,
Thanks for publishing this artifact, I think it's great and will definitely help up and coming (and experienced) BA's navigate through the eliciation process. Even if it is not used as the source of truth for the requirements documentation, per your comment on traceability, it will help. Should all of these questions be proposed to both the business and the technical teams at the same time? Should a BA work with the business first then follow up/clarify with the IT team after?
brought to you by enabling practitioners & organizations to achieve their goals using: