requirements

functional

	id	v.	intent	title / description
	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.
type functional status proposed package xuse marks new class class 1 trace from child [RQ26] Navigable relationships trace from child [RQ71] Requirements traceability see also [RQ12] JavaDoc style view stakeholder Business Analyst stakeholder Customer stakeholder Architect stakeholder Developer stakeholder System Tester stakeholder Release Manager
	RQ3	1.4	MUST	Use-cases supportXuse shall provide a use-case centric view of requirements
type functional status proposed package xuse trace from child [RQ28] Use-case relationships trace from child [RQ35] Activity diagrams trace from child [RQ36] Use-case structure trace from child [RQ37] Use-case properties trace from child [RQ41] Use-case template trace from child [RQ42] Use-case package trace from child [RQ54] Unique use-case identifiers trace from child [RQ55] Use-case names stakeholder Business Analyst stakeholder Customer Java method xusej:net.sourceforge.xuse.Xuse#pdfUseCases Java method xusej:net.sourceforge.xuse.Xuse#pdfUseCase
	RQ4	1.6	MUST	Requirements supportXuse shall support the concept of uniquely identifiable requirements
type functional status proposed package xuse trace from child [RQ5] Requirements relationships trace from child [RQ22] Duplicate Requirements trace from child [RQ43] Requirements classification trace from child [RQ73] Requirements (RAG) status ... trace from [UC1] Add Requirement stakeholder Business Analyst stakeholder Customer stakeholder Release Manager
	RQ5	1.2	MUST	Requirements relationshipsXuse shall support parent/child relationships between requirements
type functional status proposed package xuse.model trace to parent [RQ4] Requirements support trace from [UC1] Add Requirement see also [RQ71] Requirements traceability see also [RQ26] Navigable relationships see also [RQ27] Reverse relationships stakeholder Business Analyst
	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
type functional status agreed package xuse.views trace from child [RQ7] Extended views trace from child [RQ9] HTML View trace from child [RQ58] PDF Use-case trace from child [RQ59] PDF SRS stakeholder Xuse user stakeholder Business Analyst stakeholder Customer
	RQ7	1.1	SHOULD	Extended viewsXuse should facilitate easy extension or additional views that can be customised or created by XSLT proficient end users
type functional status proposed package xuse.views.extension trace to parent [RQ6] Xuse derived views stakeholder Xuse user
	RQ9	1.1	MUST	HTML ViewXuse shall provide a navigable (static) HTML view on the XML data model
type functional status proposed package xuse.views.html trace to parent [RQ6] Xuse derived views trace from child [RQ12] JavaDoc style view trace from child [RQ19] HTML Vision Document trace from child [RQ60] HTML SRS trace from [UC2] Build HTML Site stakeholder Xuse user
	RQ10	1.1	MUST	Self documentingXuse shall be self documenting to prove that your are what you eat.
type functional status implemented package xuse stakeholder Xuse user
	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.
type functional status implemented package xuse.tools trace from child [RQ23] Build time trace from child [RQ40] Project template trace from child [RQ61] Command line support trace from child [RQ62] Maven 1.x support trace from child [RQ63] Maven 2 support trace from [UC2] Build HTML Site stakeholder Business Analyst stakeholder Xuse user
	RQ12	1.0	MUST	JavaDoc style viewXuse shall provide an integrated HTML view of the requirements model similar to JavaDoc .
type functional status implemented package xuse.views.html trace to parent [RQ9] HTML View trace from [UC2] Build HTML Site see also [RQ0] Effective Requirements Co ...
	RQ13	1.1	MUST	RUP ArtefactsXuse shall support the creation of the standard set of RUP requirements documentation artefacts.
type functional status proposed package xuse trace from child [RQ14] Vision Document trace from child [RQ15] Software Requirements Doc ... trace from child [RQ16] Project Glossary trace from child [RQ39] Document versioning see also [RQ17] Narrative Text stakeholder Business Analyst
	RQ14	1.1	MUST	Vision DocumentXuse shall support the definition and creation a RUP style Vision Document.
type functional status agreed package xuse trace to parent [RQ13] RUP Artefacts see also [RQ19] HTML Vision Document stakeholder Business Analyst stakeholder Customer stakeholder Architect stakeholder Developer stakeholder System Tester stakeholder Release Manager
	RQ15	1.1	MUST	Software Requirements DocumentXuse shall support the definition and creation a RUP style Software Requirements Document ( SRS ).
type functional status agreed package xuse trace to parent [RQ13] RUP Artefacts see also [RQ59] PDF SRS see also [RQ60] HTML SRS stakeholder Business Analyst stakeholder Customer stakeholder Architect stakeholder Developer stakeholder System Tester stakeholder Release Manager
	RQ16	1.1	MUST	Project GlossaryXuse shall support the definition and creation a Project Glossary.
type functional status proposed package xuse.model trace to parent [RQ13] RUP Artefacts trace from child [RQ57] Glossary Linking stakeholder Business Analyst stakeholder Business Analyst stakeholder Customer stakeholder Architect stakeholder Developer stakeholder System Tester
	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.
type functional status proposed package xuse.model trace to parent [RQ75] Powerful authoring tools trace from child [RQ18] Boiler Plate Text see also [RQ13] RUP Artefacts stakeholder Business Analyst
	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.
type functional status proposed package xuse.model trace to parent [RQ17] Narrative Text stakeholder Business Analyst
	RQ19	1.1	MUST	HTML Vision DocumentProvide an HTML view of the vision document.
type functional status proposed package xuse.views.html trace to parent [RQ9] HTML View see also [RQ14] Vision Document stakeholder Business Analyst stakeholder Customer Java method xusej:net.sourceforge.xuse.Xuse#xuseHtml Java method xusej:net.sourceforge.xuse.build.StylesheetInvoker#invokeBuildHTMLDocuments Java method xusej:net.sourceforge.xuse.Xuse#xuseDocumentsHtml Java method xusej:net.sourceforge.xuse.utils.FileUtils#copyHTMLResources
	RQ21	1.2	MUST	Upgrade PathXuse shall provide the necessary tools to allow an easy upgrade path between different versions of the data model.
type functional status proposed package xuse.tools trace to parent [RQ1] XML datastore stakeholder Business Analyst stakeholder Xuse user
	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.
type functional status proposed package xuse.tools trace to parent [RQ4] Requirements support stakeholder Business Analyst
	RQ24	1.1	SHOULD	Tool IntegrationXuse should provide adaptors to integrate with many other software applications such as case (design) tools and test tools.
type functional status onhold package xuse.tools trace from child [RQ25] XMI Support stakeholder Business Analyst stakeholder Xuse user stakeholder Architect stakeholder System Tester
	RQ25	1.1	SHOULD	XMI SupportXuse should provide an XMI export of the requirements model suitable for import into case tools.	odlingsmee;; 2006-01-19 RQ25Currently it is anticipated that this would be best achieved with XMI 2.0
type functional status onhold package xuse.tools trace to parent [RQ24] Tool Integration stakeholder Business Analyst stakeholder Architect stakeholder Xuse user
	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
type functional status implemented package xuse.views.html trace to parent [RQ0] Effective Requirements Co ... trace from [UC2] Build HTML Site see also [RQ27] Reverse relationships see also [RQ5] Requirements relationships see also [RQ27] Reverse relationships stakeholder Business Analyst stakeholder Customer stakeholder Architect stakeholder Developer stakeholder System Tester
	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.
type functional status implemented package xuse.model trace to parent [RQ71] Requirements traceability trace from [UC2] Build HTML Site see also [RQ26] Navigable relationships see also [RQ5] Requirements relationships see also [RQ26] Navigable relationships stakeholder Business Analyst stakeholder Customer stakeholder Architect stakeholder Developer stakeholder System Tester stakeholder Release Manager
	RQ28	1.2	MUST	Use-case relationshipsXuse shall support relationships between use-cases.
type functional status implemented package xuse.model trace to parent [RQ3] Use-cases support trace from child [RQ29] use-case include trace from child [RQ30] use-case extend trace from [UC4] Edit Use-Case trace from [UC2] Build HTML Site see also [RQ31] use-case specialisation stakeholder Business Analyst
	RQ29	1.1	MUST	use-case include Xuse shall support use-case <<include>> relationships.
type functional status proposed package xuse.model trace to parent [RQ28] Use-case relationships trace from [UC4] Edit Use-Case stakeholder Business Analyst
	RQ30	1.2	MUST	use-case extend Xuse shall support use-case <<extend>> relationships.
type functional status proposed package xuse.model trace to parent [RQ28] Use-case relationships trace from [UC4] Edit Use-Case stakeholder Business Analyst
	RQ31	1.1	SHOULD	use-case specialisationXuse should support use-case specialisation (inheritance).
type functional status proposed package xuse.model trace to parent [RQ64] Specialisation support trace from child [RQ65] Flow of events specialisation trace from [UC4] Edit Use-Case see also [RQ28] Use-case relationships stakeholder Business Analyst stakeholder Customer
	RQ32	1.2	MUST	Document annotationXuse shall support document annotation to record thoughts and issues.
type functional status implemented package xuse.model trace to parent [RQ75] Powerful authoring tools trace from child [RQ33] Use-case annotation trace from child [RQ34] Requirement annotation trace from [UC4] Edit Use-Case stakeholder Business Analyst stakeholder Customer
	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.
type functional status implemented package xuse.model trace to parent [RQ32] Document annotation trace from [UC4] Edit Use-Case stakeholder Business Analyst stakeholder Customer
	RQ34	1.1	MUST	Requirement annotationXuse shall support the annotation of individual requirements.
type functional status proposed package xuse.model trace to parent [RQ32] Document annotation stakeholder Business Analyst stakeholder Customer
	RQ35	1.2	MAY	Activity diagramsXuse may support auto-generation of activity diagrams.
type functional status onhold package xuse.views trace to parent [RQ3] Use-cases support stakeholder Business Analyst stakeholder Architect stakeholder Customer stakeholder Developer stakeholder System Tester
	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.
type functional status implemented package xuse.model trace to parent [RQ3] Use-cases support trace from [UC4] Edit Use-Case stakeholder Business Analyst
	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.
type functional status implemented package xuse.model trace to parent [RQ3] Use-cases support trace from [UC4] Edit Use-Case stakeholder Business Analyst stakeholder Customer stakeholder
	RQ38	1.1	SHOULD	Screen registerXuse should provide a screen register to allow use-cases to cross reference this screen register for GUI applications.
type functional status rejected package xuse.model trace from child [RQ70] Screen specific requirements stakeholder Business Analyst stakeholder Customer stakeholder Architect stakeholder Developer stakeholder System Tester
	RQ39	1.2	MUST	Document versioningXuse shall provide facilities to record standard document versioning information such as version, author, date and change description.
type functional status implemented package xuse.model trace to parent [RQ13] RUP Artefacts trace from [UC4] Edit Use-Case stakeholder Business Analyst stakeholder Release Manager stakeholder Xuse user
	RQ40	1.1	MUST	Project templateXuse shall provide a new project template, including example use-cases, requirements and screen-register.
type functional status implemented package xuse.tools trace to parent [RQ11] Build tools stakeholder Business Analyst Java method xusej:net.sourceforge.xuse.Xuse#newProject Java method xusej:net.sourceforge.xuse.utils.FileUtils#extractTemplateProject
	RQ41	1.2	MUST	Use-case templateXuse shall provide a new use-case template to save time when creating new use-cases.
type functional status implemented package xuse.tools trace to parent [RQ3] Use-cases support trace from [UC3] Add Use-Case stakeholder Business Analyst
	RQ42	1.1	MUST	Use-case packageXuse shall provide the mechanism for classifying use-cases into packages.
type functional status implemented package xuse.model trace to parent [RQ3] Use-cases support trace from [UC3] Add Use-Case stakeholder Business Analyst
	RQ43	1.1	MUST	Requirements classificationXuse shall support the classification of requirements for ease of management and to allow for targeted views.
type functional status proposed package xuse.model trace to parent [RQ4] Requirements support trace from child [RQ44] Requirement type trace from child [RQ45] Requirement package trace from child [RQ46] Requirement status trace from child [RQ47] Arbitrary requirements cl ... trace from [UC1] Add Requirement stakeholder Business Analyst stakeholder Release Manager stakeholder Xuse user
	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.
type functional status proposed package xuse.model trace to parent [RQ43] Requirements classification trace from [UC1] Add Requirement stakeholder Business Analyst
	RQ45	1.1	MUST	Requirement packageXuse shall support classification of requirements into packages.
type functional status proposed package xuse.model trace to parent [RQ43] Requirements classification trace from [UC1] Add Requirement stakeholder Business Analyst
	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.
type functional status proposed package xuse.model trace to parent [RQ43] Requirements classification trace from child [RQ74] Composite status trace from [UC1] Add Requirement see also [RQ73] Requirements (RAG) status ... stakeholder Business Analyst stakeholder Customer stakeholder Release Manager stakeholder Architect stakeholder Developer stakeholder System Tester
	RQ47	1.1	MUST	Arbitrary requirements classificationXuse shall support arbitrary classification extensions beyond those explicitly supported.
type functional status proposed package xuse.model trace to parent [RQ43] Requirements classification trace from [UC1] Add Requirement stakeholder Business Analyst
	RQ48	1.1	MUST	Model validationXuse shall provide validation tools to provide validation not covered by the schema.
type functional status proposed package xuse.tools trace from child [RQ49] Duplicate Use-Case Validation trace from child [RQ50] Missing requirements refe ... stakeholder Business Analyst Java method xusej:net.sourceforge.xuse.Xuse#validateProject Java method xusej:net.sourceforge.xuse.build.StylesheetInvoker#invokeValidateProject
	RQ49	1.1	MUST	Duplicate Use-Case ValidationXuse shall make sure that use-case identifiers are unique within the documentation set.
type functional status implemented package xuse.tools trace to parent [RQ48] Model validation trace from [UC3] Add Use-Case trace from [UC2] Build HTML Site see also [RQ54] Unique use-case identifiers stakeholder Business Analyst
	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.
type functional status implemented package xuse.tools trace to parent [RQ48] Model validation trace from [UC2] Build HTML Site stakeholder Business Analyst
	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.
type functional status proposed package xuse trace to parent [RQ75] Powerful authoring tools stakeholder Xuse user
	RQ54	1.2	MUST	Unique use-case identifiersXuse shall support the concept of unique use-case identifiers.
type functional status implemented package xuse trace to parent [RQ3] Use-cases support trace from [UC3] Add Use-Case see also [RQ49] Duplicate Use-Case Validation stakeholder Business Analyst stakeholder Release Manager
	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
type functional status implemented package xuse trace to parent [RQ3] Use-cases support trace from [UC3] Add Use-Case stakeholder Business Analyst
	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.
type functional status implemented package xuse.views.html trace to parent [RQ16] Project Glossary stakeholder Business Analyst stakeholder Developer stakeholder Architect stakeholder System Tester stakeholder Customer
	RQ58	1.1	MUST	PDF Use-caseXuse shall allow use-cases to be generated as individual PDF documents.
type functional status proposed package xuse.views.pdf trace to parent [RQ6] Xuse derived views stakeholder Business Analyst stakeholder Customer Java method xusej:net.sourceforge.xuse.Xuse#pdfUseCases Java method xusej:net.sourceforge.xuse.build.StylesheetInvoker#invokePDFUseCases Java method xusej:net.sourceforge.xuse.Xuse#pdfUseCase Java method xusej:net.sourceforge.xuse.build.StylesheetInvoker#invokePDFSingleUseCase
	RQ59	1.1	MUST	PDF SRSXuse shall allow for a PDF version of the SRS .
type functional status proposed package xuse.views.pdf trace to parent [RQ6] Xuse derived views see also [RQ15] Software Requirements Doc ... stakeholder Business Analyst stakeholder Customer
	RQ60	1.2	MUST	HTML SRSXuse shall allow for an HTML version of the SRS with hyperlinking for ease of navigation.
type functional status proposed package xuse.views.html trace to parent [RQ9] HTML View see also [RQ15] Software Requirements Doc ... stakeholder Business Analyst stakeholder Architect stakeholder Developer stakeholder System Tester Java method xusej:net.sourceforge.xuse.Xuse#xuseHtml Java method xusej:net.sourceforge.xuse.build.StylesheetInvoker#invokeBuildHTMLDocuments Java method xusej:net.sourceforge.xuse.Xuse#xuseDocumentsHtml Java method xusej:net.sourceforge.xuse.utils.FileUtils#copyHTMLResources
	RQ61	1.2	MUST	Command line supportXuse shall provide a Java command line interface to execute the common build functions.
type functional status implemented package xuse.tools trace to parent [RQ11] Build tools stakeholder Business Analyst stakeholder Xuse user Java class xusej:net.sourceforge.xuse.Xuse
	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.
type functional status implemented package xuse.tools trace to parent [RQ11] Build tools stakeholder Business Analyst stakeholder Xuse user
	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.
type functional status proposed package xuse.tools trace to parent [RQ11] Build tools stakeholder Business Analyst stakeholder Xuse user
	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
type functional status proposed package xuse.model trace from child [RQ31] use-case specialisation trace from child [RQ66] Requirements specialisation stakeholder Business Analyst stakeholder System Tester
	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.
type functional status proposed package xuse.model trace to parent [RQ31] use-case specialisation stakeholder Business Analyst stakeholder System Tester
	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.
type functional status proposed package xuse.model trace to parent [RQ64] Specialisation support stakeholder Business Analyst
	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.
type functional status proposed package xuse.model stakeholder Developer stakeholder Customer stakeholder Business Analyst
	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.
type functional status proposed package xuse.model trace from child [RQ69] Example graphics stakeholder Developer stakeholder Customer stakeholder Business Analyst
	RQ69	1.0	MAY	Example graphicsXuse may support standard graph images for inclusion in report entry to help visualise the report.
type functional status proposed package xuse.model trace to parent [RQ68] Report register stakeholder Developer stakeholder Customer stakeholder Business Analyst
	RQ70	1.0	SHOULD	Screen specific requirementsXuse should implement traceability of requirements to specific screens.
type functional status proposed package xuse.model trace to parent [RQ38] Screen register see also [RQ71] Requirements traceability stakeholder Developer
	RQ71	1.0	MUST	Requirements traceabilityXuse shall support full requirements traceability.
type functional status proposed package xuse.model trace to parent [RQ0] Effective Requirements Co ... trace from child [RQ27] Reverse relationships see also [RQ5] Requirements relationships see also [RQ70] Screen specific requirements stakeholder Release Manager stakeholder Business Analyst
	RQ72	1.0	MAY	Requirements reportsXuse may support a set of reports that help manage requirements.
type functional status proposed package xuse.reports stakeholder Release Manager stakeholder Business Analyst
	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).
type functional status proposed package xuse.reports trace to parent [RQ4] Requirements support see also [RQ46] Requirement status stakeholder Business Analyst stakeholder Customer stakeholder Release Manager stakeholder Architect stakeholder Developer stakeholder System Tester
	RQ74	1.0	MUST	Composite statusXuse shall derive status for artefacts with children using the following rules;
type functional status proposed package xuse.model trace to parent [RQ46] Requirement status stakeholder Business Analyst stakeholder Customer stakeholder Release Manager stakeholder Architect stakeholder Developer stakeholder System Tester
	RQ75	1.0	MUST	Powerful authoring toolsXuse shall provide powerful tools for authoring requirements, use-cases and documents
type functional status proposed package xuse.model trace from child [RQ17] Narrative Text trace from child [RQ32] Document annotation trace from child [RQ53] Text customisation stakeholder Business Analyst stakeholder Customer stakeholder Release Manager stakeholder Architect stakeholder Developer stakeholder System Tester
	RQ76	1.0	MUST	VersioningXuse shall provide powerful versioning tools
type functional status proposed package xuse.model trace from child [RQ20] Data Model Versioning trace from child [RQ56] Version Control stakeholder Business Analyst stakeholder Customer stakeholder Release Manager stakeholder Architect stakeholder Developer stakeholder System Tester
	RQ77	1.1	MUST	enter title hereenter description here
type functional status proposed package xuse
	RQ78	1.5	MUST	enter title hereenter description here
type functional status proposed package xuse

architectural

	id	v.	intent	title / description
	RQ1	1.5	MUST	XML datastoreXuse shall use XML as the medium for storing all requirements related information
type architectural status proposed package xuse.model trace from child [RQ8] Schema definitions trace from child [RQ21] Upgrade Path trace from [UC1] Add Requirement stakeholder Architect stakeholder Xuse user stakeholder System Tester
	RQ2	1.17	MUST	TransformationsTransformations shall be accomplished using XSLT version 2.0
type architectural status proposed package xuse.views stakeholder Xuse user
	RQ8	1.2	MUST	Schema definitionsXuse shall use XML Schema to define the XML data models
type architectural status implemented package xuse.model trace to parent [RQ1] XML datastore stakeholder Xuse user

non-functional

	id	v.	intent	title / description
	RQ20	1.2	MUST	Data Model VersioningXuse shall provide versioning information on the data model to facilitate tool interoperation (translation) and upgrade paths.
type non-functional status proposed package xuse.model trace to parent [RQ76] Versioning stakeholder Xuse user Java method xusej:net.sourceforge.xuse.Xuse#upGrade
	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.
type non-functional status proposed package xuse.tools trace to parent [RQ11] Build tools trace from [UC2] Build HTML Site stakeholder Business Analyst stakeholder Xuse user
	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).
type non-functional status proposed package xuse trace from child [RQ52] Translations stakeholder Xuse user
	RQ52	1.1	SHOULD	TranslationsXuse should provide translations for headings and other text defined in XSLTs in five or more common languages.
type non-functional status proposed package xuse trace to parent [RQ51] Internationalisation stakeholder Xuse user
	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
type non-functional status implemented package xuse trace to parent [RQ76] Versioning trace from [UC4] Edit Use-Case stakeholder Business Analyst stakeholder Developer stakeholder Architect stakeholder System Tester stakeholder Release Manager