Requirements Process

Objectives

• To identify new integration profiles/actors to be emulated from standardization bodies

Pre-requisites

• N/A

Inputs

• Needs of a new tool for testing an integration profile/actor implementation
• Requirements from the technical framework concerning the chosen integration profile

Actions

• Writing needs in specification document or an accessible documentation to be analysed by development team

Outputs

• Technical Framework
• Formal requirements

Specification Process

Objectives

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

Pre-requisites

• Requirements are identified by bodies standardization

Inputs

• Requirements Documents
• Technical Framework

Actions

• Analysis requirements documentation/technical framework to identity existing tools that can be used, and, in the contrary, new developments to be performed
• Create a lis of features to be offered by the new simulator
• Specify the graphical user interface

Outputs

• Gap analysis (gathers the support tools which required but missing and required by the new simulator)
• Features list
• Mock-up of GUI

Design Process

Objectives

• Design receive specifications

Pre-requisites

• Specfication Documents are delivered and analysed

Inputs

• Formalized requirements / technical framework

Actions

• Design how the new simulator will be integrated within Gazelle platform (new application, integrated in an existing application) and how it will communicate with some of the others tools of the platform
• Design the modules hierarchy, that means, will new simulator 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 simulator model: which are the needed entities, how they are linked together, CRUD schema...

Outputs

• Interactions diagram
• Class and components diagrams

Realisation Process

Objectives

• Develop new or existing simulator module respecting normatives

Pre-requisites

• Specfication documents are validated

Inputs

• All specification documentation

Actions

• Develop simulator features

Outputs

• JAVA code + XHTML
• JAVA code documentation of module

Test Process

Objectives

• Verify if module respect all rules and specifications

Pre-requisites

• JAVA and XHTML code is produced

Inputs

• JAVA/XHTML Code
• Simulator webservice
• Message validated with suitable validator

Actions

• Unit Test
  • Static analysis

• Integration Test
  • Message exchange (allows to test the IHE interface and the correct integration of the message in the database if required)

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

• Acceptance Test
  • Beta testing by vendors according to their needs

Outputs

• Test report with all part of test levels