Testable Architecture Methodology

Version 5

    Purpose

     

    The purpose of this document is to describe a development process, or methodology, for creating Testable Architectures using Project SAVARA tooling.

     

    This wiki version of the methodology document is intended to help refine the phases and steps within the methodology, prior to it being fully documented using the Eclipse Process Framework (and generated into HTML and PDF documents). The sections of this wiki "document" are initially just descriptive, but it is expected that more precise definitions will be added.


    To comment on various sections, simply post a comment on the relevant page. You may also want to raise attention to the suggestion via the SAVARA User Forum, to direct users to the relevant page where they can add further comments.

     

    The rationale for describing a development methodology in conjunction with Project SAVARA is to

     

    a) provide a means to validate Project SAVARA tooling

    b) provide an example of how to use Project SAVARA tooling

     

    The scope of the development methodology will be the development life cycle associated with the creation and use of services in a Service Oriented Architecture. Testable architectures are broader than SOA, however for the purposes of the SAVARA tooling and this methodology, the focus is on SOA.

     

    The development methodology described is the Red Hat SOA Development Process. General characteristics of this methodology are that it is light-weight, iterative, and open. It is understood that customers and other organization may choose variations of this methodology, or their own methodology to use with SAVARA tooling and SOA Platform. The documenting of the Red Hat SOA methodology in conjunction with Project SAVARA is not meant to preclude this in any way. Rather  it is meant to serve as an “out of the box” methodology, for those organizations that don't have their own development process, and an example for organizations that do want to use their own methodology.

     

    This document outlines the use of this example of a “testable architecture” methodology as applied to the Purchasing example distributed with the current Overlord CDL tooling (http://www.jboss.org/overlord). This example is simple enough to be easily described and managed, but more complex than the typical “hello world”.

     

     

    Terminology

     

    Business process – the end to end process that delivers a particular business objective – not the process definition that may run in an orchestration engine.

     

     

    Contents

     

    1. Overview
    2. Business Analysis
    3. Architecture
    4. Service Oriented Analysis
    5. Service Oriented Design
    6. Service Development
    7. Service Testing
    8. Service Deployment
    9. Service Monitoring