id v. intent title / description
RQ0 details RQ0 1.12 MUST Effective Requirements CommunicationXuse shall - above all else - focus on delivering a toolset that allows for effective communication of requirements between all the stakeholders.
RQ3 details RQ3 1.4 MUST Use-cases supportXuse shall provide a use-case centric view of requirements
RQ4 details RQ4 1.6 MUST Requirements supportXuse shall support the concept of uniquely identifiable requirements
RQ5 details RQ5 1.2 MUST Requirements relationshipsXuse shall support parent/child relationships between requirements
RQ6 details RQ6 1.1 MUST Xuse derived viewsXuse shall support multiple derived views on the data model both in terms of format (HTML/PDF etc.) as well as content
RQ7 details RQ7 1.1 SHOULD Extended viewsXuse should facilitate easy extension or additional views that can be customised or created by XSLT proficient end users
RQ9 details RQ9 1.1 MUST HTML ViewXuse shall provide a navigable (static) HTML view on the XML data model
RQ10 details RQ10 1.1 MUST Self documentingXuse shall be self documenting to prove that your are what you eat.
RQ11 details RQ11 1.1 MUST Build toolsXuse shall provide the appropriate build tools to effectively marry the XML data model with the stylesheets that provide the different views.
RQ12 details RQ12 1.0 MUST JavaDoc style viewXuse shall provide an integrated HTML view of the requirements model similar to JavaDoc .
RQ13 details RQ13 1.1 MUST RUP ArtefactsXuse shall support the creation of the standard set of RUP requirements documentation artefacts.
RQ14 details RQ14 1.1 MUST Vision DocumentXuse shall support the definition and creation a RUP style Vision Document.
RQ15 details RQ15 1.1 MUST Software Requirements DocumentXuse shall support the definition and creation a RUP style Software Requirements Document ( SRS ).
RQ16 details RQ16 1.1 MUST Project GlossaryXuse shall support the definition and creation a Project Glossary.
RQ17 details RQ17 1.2 MUST Narrative TextXuse shall support the merging of narrative text with the structured data model such that produced documents can be free flowing and intuitive to read.
RQ18 details RQ18 1.1 MUST Boiler Plate TextXuse shall support a "boiler plate" narrative text repository such that documents are easy to create with stock phrases.
RQ19 details RQ19 1.1 MUST HTML Vision DocumentProvide an HTML view of the vision document.
RQ21 details RQ21 1.2 MUST Upgrade PathXuse shall provide the necessary tools to allow an easy upgrade path between different versions of the data model.
RQ22 details RQ22 1.1 SHOULD Duplicate RequirementsXuse should provide a tool that allows for duplicate requirements to be identified via some sort of text matching algorithm.
RQ24 details RQ24 1.1 SHOULD Tool IntegrationXuse should provide adaptors to integrate with many other software applications such as case (design) tools and test tools.
RQ25 details RQ25 1.1 SHOULD XMI SupportXuse should provide an XMI export of the requirements model suitable for import into case tools. view comments
RQ26 details RQ26 1.2 MUST Navigable relationshipsXuse shall provide navigable relationships between: use-cases and use-cases; requirements and requirements; and requirements and use-cases. This relationships will be available in the HTML view
RQ27 details RQ27 1.2 MUST Reverse relationshipsXuse shall be able to derived items that reference the requirement or use-case under focus. For instance, Xuse shall be able to trace which use-cases reference a particular requirement without that information being held directly against the requirement in the data model.
RQ28 details RQ28 1.2 MUST Use-case relationshipsXuse shall support relationships between use-cases.
RQ29 details RQ29 1.1 MUST use-case include Xuse shall support use-case <<include>> relationships.
RQ30 details RQ30 1.2 MUST use-case extend Xuse shall support use-case <<extend>> relationships.
RQ31 details RQ31 1.1 SHOULD use-case specialisationXuse should support use-case specialisation (inheritance).
RQ32 details RQ32 1.2 MUST Document annotationXuse shall support document annotation to record thoughts and issues.
RQ33 details RQ33 1.1 MUST Use-case annotationXuse shall support the annotation of use-case at a top level, property level as well as step level.
RQ34 details RQ34 1.1 MUST Requirement annotationXuse shall support the annotation of individual requirements.
RQ35 details RQ35 1.2 MAY Activity diagramsXuse may support auto-generation of activity diagrams.
RQ36 details RQ36 1.1 MUST Use-case structureXuse shall support the following use-case structure: a use-case description, use-case properties, main flow, alternate flows and exception flows.
RQ37 details RQ37 1.1 MUST Use-case propertiesXuse shall support the following properties to be held against a use-case : trigger; goal; primary-actor; secondary-actor(s); pre-requisites; success-outcome; failure-outcome; priority; and complexity.
RQ38 details RQ38 1.1 SHOULD Screen registerXuse should provide a screen register to allow use-cases to cross reference this screen register for GUI applications.
RQ39 details RQ39 1.2 MUST Document versioningXuse shall provide facilities to record standard document versioning information such as version, author, date and change description.
RQ40 details RQ40 1.1 MUST Project templateXuse shall provide a new project template, including example use-cases, requirements and screen-register.
RQ41 details RQ41 1.2 MUST Use-case templateXuse shall provide a new use-case template to save time when creating new use-cases.
RQ42 details RQ42 1.1 MUST Use-case packageXuse shall provide the mechanism for classifying use-cases into packages.
RQ43 details RQ43 1.1 MUST Requirements classificationXuse shall support the classification of requirements for ease of management and to allow for targeted views.
RQ44 details RQ44 1.2 MUST Requirement typeXuse shall classify requirements into types. The list of types supported is: functional; non-functional; technical; architectural; constraint and inverse requirement types.
RQ45 details RQ45 1.1 MUST Requirement packageXuse shall support classification of requirements into packages.
RQ46 details RQ46 1.2 MUST Requirement statusXuse shall support a status held against a requirement. Valid statuses are: proposed, agreed, on-hold, rejected, implemented and validated. Where a requirement has child requirements it will have a composite state - i.e. a composite of all the statuses of the children including children whose state is iteself a composite state.
RQ47 details RQ47 1.1 MUST Arbitrary requirements classificationXuse shall support arbitrary classification extensions beyond those explicitly supported.
RQ48 details RQ48 1.1 MUST Model validationXuse shall provide validation tools to provide validation not covered by the schema.
RQ49 details RQ49 1.1 MUST Duplicate Use-Case ValidationXuse shall make sure that use-case identifiers are unique within the documentation set.
RQ50 details RQ50 1.1 MUST Missing requirements referencesXuse shall validate that requirement references (within use-cases and the requirements repository) are valid - i.e. that the requirement exists within the requirements repository.
RQ53 details RQ53 1.2 SHOULD Text customisationXuse should allow users to customise the text output of the XSLTs for text defined in XSLTs such as headings.
RQ54 details RQ54 1.2 MUST Unique use-case identifiersXuse shall support the concept of unique use-case identifiers.
RQ55 details RQ55 1.1 MUST Use-case namesXuse shall support names for use-cases in addition to use-case identifiers. The use-case name should convey the purpose of the use-case
RQ57 details RQ57 1.1 MUST Glossary LinkingXuse shall automatically recognise glossary entries in narrative text and provide hyperlinks to the appropriate glossary entry. Additionally mouse over text should show a summary of the glossary entry such that the user does not have to navigate the link to get a description of the glossary item.
RQ58 details RQ58 1.1 MUST PDF Use-caseXuse shall allow use-cases to be generated as individual PDF documents.
RQ59 details RQ59 1.1 MUST PDF SRSXuse shall allow for a PDF version of the SRS .
RQ60 details RQ60 1.2 MUST HTML SRSXuse shall allow for an HTML version of the SRS with hyperlinking for ease of navigation.
RQ61 details RQ61 1.2 MUST Command line supportXuse shall provide a Java command line interface to execute the common build functions.
RQ62 details RQ62 1.2 MUST Maven 1.x supportXuse shall provide a Maven 1 plugin such that all the standard xuse functionality is offered to maven 1.x users.
RQ63 details RQ63 1.2 MUST Maven 2 supportXuse shall provide a Maven 2 plugin such that all the standard xuse functionality is offered to maven 2 users.
RQ64 details RQ64 1.0 MUST Specialisation supportXuse shall provide facilities to support specialisations or varients. This is useful where the standard "product" is specialised for a particular situation - e.g. for a specific implementation
RQ65 details RQ65 1.0 MUST Flow of events specialisationXuse shall provide facilities to support specialisations or varients on individual steps within a use case flow, allowing steps to be altered, added or removed.
RQ66 details RQ66 1.0 MUST Requirements specialisationXuse shall provide facilities to support specialisations or varients on individual requirements, allowing requirements to be altered (specialised), added specifically for the variant or removed in the context of the specific implementation.
RQ67 details RQ67 1.0 MUST Notification registerXuse shall support the documentation of notifications. This allows such things as the layout and content of emails or similar to be easily included in the requirements documentation pack.
RQ68 details RQ68 1.0 MUST Report registerXuse shall support the documentation of grid style reports. This allows such things as the layout and content of report to be easily included in the requirements documentation pack.
RQ69 details RQ69 1.0 MAY Example graphicsXuse may support standard graph images for inclusion in report entry to help visualise the report.
RQ70 details RQ70 1.0 SHOULD Screen specific requirementsXuse should implement traceability of requirements to specific screens.
RQ71 details RQ71 1.0 MUST Requirements traceabilityXuse shall support full requirements traceability.
RQ72 details RQ72 1.0 MAY Requirements reportsXuse may support a set of reports that help manage requirements.
RQ73 details RQ73 1.1 MAY Requirements (RAG) status reportXuse may support a report that shows the status of requirements (higlighting them as red/amber or green).
RQ74 details RQ74 1.0 MUST Composite statusXuse shall derive status for artefacts with children using the following rules;
RQ75 details RQ75 1.0 MUST Powerful authoring toolsXuse shall provide powerful tools for authoring requirements, use-cases and documents
RQ76 details RQ76 1.0 MUST VersioningXuse shall provide powerful versioning tools
RQ77 details RQ77 1.1 MUST enter title hereenter description here
RQ78 details RQ78 1.5 MUST enter title hereenter description here


id v. intent title / description
RQ1 details RQ1 1.5 MUST XML datastoreXuse shall use XML as the medium for storing all requirements related information
RQ2 details RQ2 1.17 MUST TransformationsTransformations shall be accomplished using XSLT version 2.0
RQ8 details RQ8 1.2 MUST Schema definitionsXuse shall use XML Schema to define the XML data models


id v. intent title / description
RQ20 details RQ20 1.2 MUST Data Model VersioningXuse shall provide versioning information on the data model to facilitate tool interoperation (translation) and upgrade paths.
RQ23 details RQ23 1.2 MUST Build timeXuse shall be able to compile the XML data model into the disparate views in a timely fashion (i.e. within a matter of one or two minutes or less) - no strict performance requirements are necessary.
RQ51 details RQ51 1.1 MUST InternationalisationXuse shall support internationalisation of textual outputs that are not derrived from user documents (i.e. headings, fixed text defined in XSLTs).
RQ52 details RQ52 1.1 SHOULD TranslationsXuse should provide translations for headings and other text defined in XSLTs in five or more common languages.
RQ56 details RQ56 1.2 MUST Version ControlXuse shall allow easy integration with existing version control systems. Use of version control systems is not manadatory with Xuse but is possible