Home | Consulting 
1-Intro. | 2-Deliv. | 3-Serv. | 4-Price | 5-Concl. | Ftn. | Apex-A | Apex-B
2: DELIVERABLES
hen come to defining the software architect´s deliverables, it varies from one consulting firm to another consulting firms. The reason for this vagueness are:

  • Lacking universal standard, and

  • The abstractness nature of the software applications.

Since all of GreenTomato Software LLC projects adhere to the S.A.S.4.C architecture, the deliverables are more uniform and better define then most of other consulting firm. Depending on the application scope and complexity, the three key deliverables are:

  1. PRESENTATION
    A presentation of the software architecture to the executive staff.
  2. THE SOFTWARE BLUEPRINT
    The software blueprint answered the seven key questions:

    • What functionality does the product offer to its users?
      Customer Requirement Documentation
    • How is the task of writing the software organized into work assignments or modules?
      High Level Project Plan
    • What changes may be needed in the future?

      What changes are unlikely, and which software modules should not be changed in the future?
      Application Scope Documentation
    • What will the performance of the product be?
      Performance & Testing Matrices
  • How can the software be built as a set of components that can be independently implemented and verified?

    What components should be acquired from external suppliers?
    Components Mapping or UML Diagram
    & Coding Specification
  • If the product will exist in several variations, how can it be developed as a product-line?

    What investment should be made in creating a software product-line? And what is the expected return from creating the options to develop different members of the product-line?

    In particular, is it possible to develop the smallest, minimally useful product first and then develop additional members of the family by adding components without having to change the code that was written previously?
    Version Control Documentation
  • If the product requires authorization for its use, or must restrict access to data, how can security of data be ensured?

    What level of encryption and authentication will be sufficient? And How can "denial of service" attacks or other similar attacks be prevented?
    Security & Authentication Documentation
  1. TRANSITION PLAN
    Meetings with the transition team. If need to, the software architects will interview, assemble and hire the transition team on your behalf.

Next...
About Comments Terms Copyright (C) 1998-2005 GreenTomato Software, LLC. All rights reserved.