Experiment Plan

From ZenWiki

This is a template of experiment plan quoted from Architecture Centric Development Method (ACDM).

Element	Content Description
Experiment ID	This is the title or something that uniquely identifies this experiment.
Responsible Engineer	This is the development team member that is responsible for this experiment.
Purpose	Describe the reason for conducting the experiment. It is strongly advised that the author explain how the experiment will be used to refine the architecture.
Expected Outcomes	Describe what the responsible engineer expects the outcome or outcomes will be of the experiment.
Resources Required	List the resources required that include: compute resources (software/hardware), people, time, money, and so forth.
Artifacts	These are the artifacts that will be created as a result of executing the experiment such as software, documentation, and so forth.
Experiment Description	Describe the experiment. This includes software that will be written, research to be performed, studies to be carried out, information that will be collected and how it will be collected and so forth.
Duration	The amount of time that it is expected to complete the experiment. Must include an explicit start date, stop date, and milestones as applicable. This should be a mini-schedule of events that can be tracked by the Chief Scientist. The Managing Engineer can roll up the durations and dependencies for all the experiments.
Results and recommendations	The responsible engineer must document the results of the experiment. Describe deviations from the expected outcomes and reasons for the deviations. Discuss and deviations from the planned experiment description. Describe recommendations as a result of conducting the experiment.

Contents 1 Experiment and Architecture Matrix 2 Proposed Experiments 3 Experiments in Progress 4 Completed Experiments 5 Templates 6 See also

Experiment and Architecture Matrix

Components	Experiments
	ZEN Client SMIG Navigation	ZEN Client Information Gathering	ZEN Client Report Generation	ZEN Client Interview Status	ZEN Client Deployment	ZEN Client UI Layout	SMIG Versioning Solution	ZEN Tool Data Model(s)	Interview Data Protection	Web-based GUI Framework	ZEN Server API Module
ZEN Client : Window-based UI	×	×	×	×	×	×
ZEN Client : Control	×	×	×	×	×	×			×
ZEN Client : Model	×	×	×	×	×	×	×	×	×
ZEN Server : HTML-based UI							×			×
ZEN Server : API											×
ZEN Server : Control									×	×	×
ZEN Server : Model	×	×	×				×	×	×	×	×

Proposed Experiments

Brainstorming ideas

ZEN Server Report Consolidation

• Explore how to consolidate answers from multiple interview answers into a single document.

ZEN Client Local Database

• Explore which database would be best suited on the client side

SMIG Versioning Solution

• Explore the implementation of multiple SMIG versions with the tool.

Experiments in Progress

Completed Experiments

1. ZEN Client SMIG Navigation
2. ZEN Client Report Generation
3. ZEN Client Information Gathering
4. ZEN Client Interview Status
5. ZEN Client Deployment
6. Interview Data Protection (covered in ZEN Client Deployment)
7. ZEN Tool Data Model(s)
8. ZEN Client UI Layout
9. Web-based GUI Framework
10. ZEN Server API Module

Templates

• Architecture View Design Template
• Use case template
• Experiment design template

See also

• Architecture