Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

Rules

The following rules should be observed by each confluence user in RS project space:

  • Every confluence user in RS project space, unless when working on tasks requiring other than that, is contributing in RS Components page.
  • RS Components page is split on sub pages by components: [ResearchSpace:01 Core], [ResearchSpace:02 UI Navigation], 03 Security, etc.
  • For each component in page "<NN> <Component>" you could have pages such as:
    • <Component> Req Items: This page is subset of initial business requirements, created by the BM in the ResearchSpace Business Requirements & Specification, restricted only to those requirements which will be included in the Stage 3 of ResearchSpace Project. A text about a component is gathered into one section and duplications are removed. The requirements are extracted based on the commitments that were given in Ontotext ResearchSpace Tender Offer and ResearchSpace Best and Final Offer for Stage 3.
      For each requirement is supported the following additional information:
      • Requirement ID -this will be unique requirement identificator. It will be used for referencing the requirements, as well as for requirements traceability during the project.
      • Requirement priority - the requirement priority shows the iteration based on the project plan, for which the requirement is planned for development. For example RS3.2 means that a requirement will be implemented during the second iteration of Stage3, RS4 – means that a requirement will be implemented during Stage, RS? means that a requirement is not yet finally prioritized. Requirements could be reordered during the project and their priorities would change then also.
        This list with requirements is not a final one, and could be changed, extended or reduced within project continuance.
        Before each project iteration, based on these initial high level business requirements and their priorities, will be created a detailed functional specification.
    • <Component> Concepts: In this page will be kept any conceptual ideas and considerations that have not crystallized into a specification yet for the given component. Any user is free to contribute in this page any idea or new requirements he has at any time. See [ResearchSpace:Data Annotation Concepts] as an example.
    • <Component> Tools: In this page are kept researches on existing open source tools/ approaches/ ontologies for the given component. See Search Tools
    • <Component> Spec (RS3.1): In this page will be kept crystallized and detailed requirements, use cases, state chart diagrams for the component area. This page is the functional specification addressed to the developers.
    • <Component> Others: Users could create other pages for a given component if they find it necessary and if the information in the new page could not be classified in any of the above pages.

Notations

The following notations are used:

  • A "tag" at the end of the page name in parentheses, to indicate its status:
    • RS3.1 : this sprint
    • RS3 : in scope, involves several sprints
    • RS3.? : in scope, sprint not yet determined
    • RS4 : out of scope: functionality and thinking for next stage
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.