Project Delivery Process D383

D383 - Build Core Testing Data for Prototyping

DEFINITION

The purpose of this activity is to set up the data scenarios to be used in the prototyping sessions.

SUMMARY

The process has two main parts:

• define needed data environment for prototyping, and
• develop prototype database.

Its objective is to:

• define a test environment, which mirrors the company´s real business situation, and
• build a basis for testing the prototype to actual business cases.

PATH PLANNING GUIDANCE

Normal practice for projects using prototyping design techniques.

DEPENDENCIES

Prerequisites (Finish-Start):

• Development environment - Process D130

Dependent procedures (Finish-Start):

• Iterative prototyping - Process D400/D450

RECEIVABLES

• Business process descriptions from project model

• Definition of business cases
• Source documents
• Data from systems to be replaced
• Paper files (e.g. customers,  suppliers, material)

DELIVERABLES

• List of business processes to be prototyped
• Business cases to be prototyped
• Prototype Data Structures
• Content for each database or file structure:
• Database number/name
• Database file name
• Logical and physical record structures
• Brief description of data elements (length, format, valid values, etc.)
• Initial data values.

TOOLS

• Refer Application Software documentation

DETAILED DESCRIPTION OF TASKS

Define needed data environment for prototyping

This subtask serves to find business cases, which represent actual business scenarios. Based on the identified business processes identified in the Project Model (see processes R065 through R069) to be used in the prototyping sessions, incidents of those data entities to be used in the process should be identified in the organisation.

Responsibilities:

Project Mgt	Reviews list of business cases and collected test data
Project Mgt	Reviews list of business cases and collected test data
User	Identifies business cases and data incidents to be used in the prototyping database
Team/MIS	Helps users in specifying the right level of detail for data collection and understanding how to collect data

Develop Prototype Database

The purpose of this activity is to develop, implement, and populate the databases and/or file structures needed to support the prototyping process.  This activity includes both the load of data through programs and utilities as well as the initial data entry required to establish desired prototype scenarios.

The objective of this task is to:

• create the database and file structures needed to support the prototypes to the level of sophistication determined by the prototype strategy, and
• populate the databases and file structures with the data needed to support the test cases identified.

Worksteps:

• Review Application Software technical documentation
• Identify required databases and file structures
• Load and configure databases and file structures
• Set initial file setting required for scenarios to be prototyped
• Populate databases as required by test cases.

Information Sources:

• Vendor project team
• Site and vendor technical documentation
• Site standards and procedures
• Application software
• Technical Product Specification (Solution Strategy)
• Application software Prototyping Plan
• Prototyping Schedule

The deliverables from this task are:

• Prototype Data Structures (Create)
• Content for each database or file structure:
• Database number/name
• Database file name
• Logical and physical record structures
• Brief description of data elements (length, format, valid values, etc.)
• Initial data values.

SCOPE:	Entire prototype
DETAIL:	Sufficient to specify physical data structures with the prototyping tool in use.
FORMAT:	Input to prototyping tool, with supporting diagrams and text as documentation.

Responsibilities:

Project Mgt	Reviews data management work
Data Mgt	Creates library and allocates storage space for the system database; develops and executes the data definition language to create the structures in the database management system
User	Identifies business cases and data incidents to be used in the prototyping database. Enters applicable test data
Team/MIS	Develops code and executes programs to load initial test data into database files