Requirements Process

Objectives

• Need to formalize a new development, evolution or correction of the platform. 
• Describe the features expected in the form of use cases or defect

Pre-requisites

• N/A

Inputs

• Need a new feature, a change or correction

Actions

• Writing needs in an issue

Outputs

• Requirements / Defects

Specification Process

Objectives

• Identify and analyse impact from requirements process outputs
• Identify features and releases
• Identify tool impacts

Pre-requisites

• Requirements are identified and created

Inputs

• Issue which contains the need

Actions

• Analyse the issue, identitify existing tools that could be used. If there is not existing tools identify the developments to be performed
• Create a list of features to be offered by Test Management
• Specify the graphical user interface

Outputs

• Gap analysis (gathers the support tools which required but missing and required by Test Management)
• Features list
• Mock-up of GUI
• Development and Test plans

Design Process

Objectives

• Design and create specification

Pre-requisites

• A formal expression of the needs is available

Inputs

• Existing specification and design of module
• Existing specification and design of tool
• Existing platform architecture and design
• Change requests (issue)
• Management of documentation process

Actions

• Design the modules hierarchy, that means, will Test Management inherit from existing Gazelle modules, which are the dependencies with other modules/third-party libraries, which are the new modules to be developed and that it would be convenient to keep as much as independant as possible for possible reuse.
• Design the Test Management model: which are the needed entities, how they are linked together.
• Analyse and change state of changement requests
• Analyse impact on other module other than those specify on the change request

Outputs

• Interactions diagram
• Class and components diagrams
• Specification and design of module
• Specification and design of tool
• Platform architecture and design
• Document index up to date

Realisation Process

Objectives

• Develop new Test Mangement features respecting normatives

Pre-requisites

• Specfication documents are validated

Inputs

• Tool specifications or module specifications
• Tool design document or module design document
• Coding rules
• Development repository

Actions

• Creation of new featuers or module, apply the KEREVAL development process available on SMQ

Outputs

• JAVA code + XHTML
• JAVA code documentation of module
• New branch on development repository

Test Process

Objectives

• Verify if new features respect all rules and specifications

Pre-requisites

• JAVA and XHTML code is compiled

Inputs

• JAVA/XHTML Code
• Branch of development on IHE SVN
• Validation strategy
• Validation objectives

Actions

• Unit Test
  • Static analysis
  • Unit testing on critical methods

• Integration Test
  • Verify build integrity (components/modules)

• System Test
  • System testing against Specifications documents (features & GUI)

• Acceptance Test
  • Beta testing according to the expressed needs

Outputs

• Test report with all part of test levels