Specifying System Requirements Clause Samples

Specifying System Requirements. In the eDIANA approach, we provide two options to specify requirements: either by using Word documents or using individual items of a RequisitePro project database. For tracking requirements attributes and traceability, it is not necessary to have them in documents. They may just reside in the database. However, also having them in documents offers some advantages: • Easier access to the requirements by team members who do not have access to RequisitePro • Opportunity to visually group and organize the requirements • Presenting them in a more readable form • Easy to add comments and explanations An alternative to managing requirements in documents is the use of filters and queries in RequisitePro, with an organization scheme similar to that of the corresponding RequisitePro template. Importing documents in RequisiteWeb can be done either by using predefined document formats (eDIANA Word Templates stored by default in the RequisitePro project) or by using the original document format. This feature allows for importing existing eDIANA deliverables without worring on formatting issues. Additionally, some imported documents might already have requirement bookmarks (a requirement bookmark is a RequisiteWeb mark in the Word document pointing to requirements stored in a RequisteWeb database). To avoid encountering errors in a document that contains requirement bookmarks, you must select the option to remove the bookmarks while importing the document. The following requirement types are usually stored in corresponding documents, not just in the database: • Because of their descriptive nature, scenarios should be associated with the documents— one document per scenario. • Features are included in the deliverables of T1.3. • Needs documents (T1.1) can be better explained with diagrams and examples.