TROST: Open-System Trustworthiness

Project P050406 TROST Pilot
Design I - Life-Cycle Framework

TROSTing>projects>
pilot>design>

P050406>
0.00 2005-04-20 -22:25 -0700


Type: Project Development Project ID: P050406
Style: Abbreviated Status: In Progress
Objective: 
Gather material, tools, references, and other resources for the problem-space and problem-solution crossovers to be addressed in accordance with the TROST Project Specification.
1. Deliver a conceptual design that covers enough of this to situate the TROST work.
2. Specify how it will be applied to TROSTing and also ODMref 1.0 development.
3. Obtain early review of this much and the thinking that is behind it.
Related Information/Projects:
[TROST Project Documents]
P050403: TROST Pilot Design
P050404: TROST Pilot Design Initiation
  
Conditions of Satisfaction:
1. Identification of Life-Cycle Framework Performance Patterns sufficient for completion of templates and their application.
2. Capture of relevant literature and background material.
3. Identification of tasks to be carried out in support of Documenting Templates
 
 
 
Inputs:
Guidelines for Final Project and Dissertation Module, version 7.53 (2005-03-12)
TROST Project Specification (2005-03-20)
TROST Exception Review Report
Dissertation Project Plan 6.0
Outputs:
Design1-LifeCycleFramework.doc
 
Assigned To: Dennis E. Hamilton Defined By: Dennis Hamilton (2005-04-20)
Date Initiated: 2005-03-25 Date Completed: tbd
 

1. Approach (2005-04-20)

This level provides conceptual design for the overall pilot activity covering [Specification: 3.1]

This covers the outside experience and what I think of as the problem-space side of intermediate architecture meeting the solution-space side of the solution product as an instrument in the problem-space situation. It's all about what they want to do with it.

These are from the problem space perspective and we don't do much about these, although we do talk about some elements of the provider-user cycle that has there be various interactions between solution providers and problem workers (I need terms for this). erested in setting the stage for the more-technically specific sections to follow.

We need to characterize how things work between producers and users/operators and the cycle of improvement as well as the cycle of interaction.  We have this challenge about the levels of interaction too.  That is, the request response cycle can be a publish - apply - feedback - plan kind of thing.  See how this maps to the cycle of engagement. We want to speak of engagement in a variety of ways.

I am thinking that the specification material is a bit off, based on what I have been unearthing so far.

We need some diagramming, depiction scheme.  We need a way to identify interactions that happen in a problem-space setting and in the interaction between the user and the provider of the "solution" elements.

2. Activities (2005-04-20)

 


0.00 2005-04-20-17:53 create  placeholder to morph into the necessary material
Incorporate job jar and use it to drive the gathering of materials from this already-completed task.

Construction Zone (Hard Hat Area)

Creative Commons License You are navigating TROSTing.org.
This work is licensed under a
Creative Commons License.

created 2005-04-20-17:53 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 05-07-21 13:36 $
$$Revision: 22 $

Home