Building is the process of actually making an application model (or the prioritized parts of the application model) with production strength qualities.

 

You must perform the following activites in parallel that may influence each other:

  • Application Model. Create all neccessary parts of the application model to support the prioritized Use Cases and Impacts.
  • Data Integration. Create interfaces towards surrounding applications and systems.
  • Data Transition. Create procedures to be applied when converting data to/from other systems during the Transition phase.

 

Start working on a test script for each of the activities.

 

The building is to be done in at least three iterations, with one or more workshop sessions per iteration with your Customer Representatives. The agenda for the workshop sessions must contain at least these activites:

  • Walkthrough of use cases and impacts by demonstrating the functionality.
  • Walkthrough of funtionalities without a user interface, like agents and security.
  • Walkthrough of the progress on Data Integration and Data Transition, demonstrating as much of the functionality as possible.
  • Gather customer input and improve the application model before the next workshop.

 

Deliverables

  1. A working application model with no known issues (other than any customer change requests which are decided to move to a later project or to maintenance).
  2. A draft version of the test script
  3. Sign Off Document

 

Application Model

The work must be based on the Initial Application Model created during the Draft phase. During the Draft phase, the focus was Forms (user interface). In the Build phase, all parts of the Application Model must be completed:

  • User Interface: Desktop and Apps Forms, Tables, Navigation pane.
  • Logic: Rules, Tasks, Agents, Web Services.
  • Data: Object Class Diagram, Object Classes, Object Class Properties, Schemas, Hierarchies, Connections.
  • Search and Refine: Search Folders, Refiners.
  • Analyze and Report: Analyses, Reports (Mail Merge), Formulas, Data Filters.
  • Security: Groups, Users, Permissions, Privileges, Security Rules, Security Warnings.

 

You are required to use a detailed check list to make sure all aspects of an application model are covered.

 

The Application Model activity will influence the Data Integration and Data Transition activities, so run these activities in parallel. 

 

Data Integration

The application will probably integrate with other applications and systems, both on a client level and server level.

 

Client level integrations to consider:

  • Drag and drop of documents, email, contacts and similar.
  • Sending of email.
  • Import and export of files.
  • Taking and saving pictures.

 

Server level integrations to consider:

  • Tasks or Web Services calling external systems.
  • Define Web Services to be called from external systems.
  • Import and export of files.

 

The Data Integration activity will influence the Application Model and Data Transition activities, so run these activities in parallel.

 

Data Transition

It is important to focus on Data Transition as early as possible, in order to capture detailed requirements imposed by other systems.

 

Identify all applications and systems that are to send to or receive data from your new application. Then create procedures on how to transport these data during the later Transition phase. The procedures must be as automated as possible, e.g. by using Extract, Transform and Load (ETL) tools.

 

And, once again, remember that the Data Transition activity will influence the Application Model and Data Integration activities, so run these activities in parallel.

 

Sign Off

After at least three iterations of the activities above, you must get the customer's sign off in order to proceed to the next phase. The sign off do not require any formal testing by the customer, but it is required that the customer has had access to the application and has run through all the prioritized use cases during the workshops. 

 

Please Note

It is not required that the application model is installed in other environments than the modeling (development) environment.