Using Datamaker in the development lifecycle

From Analyst, to Developer, to DBA to Tester!


Datamaker is an extremely powerful toolset that can be used throughout the entire development lifecycle.  Building, editing, checking, and testing data are activities that are familiar to all IT professionals.

Datamaker can be used from the initial design of your application through to development, testing and ongoing maintenance.  From analyst being able to specify what the application data should look like through to DBAs managing different versions of databases, datamaker can help.

Job Functions and Features

Job Function How would I use it?
Analyst Browsing existing data to verify any  assumptions using business rules.
Analyst By having a formal method of specifying what input and output data should look when specifying new functionality.
Analyst Defining a meta model of table and entity relationships.
Developer Creating appropriate data from specifications created by analysts.
Developer Editing and building accurate data to act as input to screens and batch.
Developer Comparing data before and after tests to verify, delete, insert and update functionality is working as expected.
Developer Comparing differences between table structures and objects between releases.
DBA
Comparing differences between table structures and objects between releases.
DBA Helping to create subset  or smaller versions of development databases.
Testers Generating accurate test data to exercise the majority of code.
Testers
 		Comparing data before and after tests for integrity and changes.
TestersGenerating disparate high volume data for performance testing.
TestersManage Quality centre or other capture replay scripts centrally.
ManagersBuilding a valuable repository of testing assets for use in multiple projects.
Managers Providing structure, re-usability and best practice across projects.