Skip to content

good practice and innovation
about us infoKits Tools & Techniques Publications Events
You are here: Home » infoKits » Electronic Documents and Records Management » Stage 6: EDRM - defining the statement of requirements » Summary of Requirements

Summary of requirements

You are recommended to start with a high level summary of the requirements. As you get into the detail the document becomes bulky and complex. It is useful if at any stage you can go back to the start and see the overview. You should define the high level functions under the four headings of:

  • input

  • management

  • output

  • collaboration/business process management

You should also define the phases of the preferred implementation plan and assign departments and user numbers to each phase. You should then point to where additional requirements are defined for each function and phase. We generally define the overall functional requirements first and then the specific requirements for each phase.


Bookmark and Share
If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)