loader image

Systam

Linkedin-in
Systam v4
Systam v5
Linkedin-in

SYSTAM INTEGRATION

During this phase, the requirements are established, the plans are structured in order to develop the project plan, and the highest project risks are mitigated in order to complete the design of a prototype, which contains the critical use cases identified in the initial consulting phase.

SYSTAM INTEGRATION

Depending on the project, an evolutionary prototype of a component can also be built to study the feasibility of a module or for demonstrations to end users.

Objectives

  • Knowledge of the entire system to be built:
  • Complete specification and validation of requirements and design.
  • Establish the Architecture.
  • Fully define the scope.
  • Generate the entire development environment based on the System Architecture.
  • Implementar las funcionalidades de mayor riesgo de cada módulo.
  • Definir la gestión del proyecto:
  • Establish the project schedule.
  • Establish the project monitoring strategy.
  • Define the development plan and establish the monitoring strategy.
  • Fully define the project baseline.

Non-critical activities

  • Plan Quality
  • Formal Technical Review (RTF’s)
  • Review deliveries.
  • Process Adjustment Review
  • Plan the Configuration
  • User Documentation
  • Plan the Transition.
  • Develop Training Materials.
  • Monitoring of the Project Baseline.

Critical Activities

  • Specify Requirements.
  • Validate Requirements.
  • Validate with Prototype.
  • Prioritise Requirements.
  • Define System Scope.
  • Define User Interface Guidelines.
  • Design the System.
  • Describe System Architecture.
  • Communicate Design to Implementers
  • Plan integrations
  • Integrate the System.
  • Risk Management.
  • Estimation and Measurement.
  • Define the Project Baseline.
  • Define and generate the controlled environment.
  • Plan the Verification.
  • Specify Test Cases.
  • Unit Verification.
  • Define User Doc Standards.