![]() |
NuovoDoc Architecture:Architectural Themes |
version 0.10 last updated 2002-05-14-22:01 -0700 (pdt)
These topics are an outline of explorations and discussions that are being prepared for further development and analysis.
This is a working outline expanded as a basis for discussion. Specific elements will be separated and expanded as analysis continues.
Architectural Themes
MDA: Model-Driven Architecture
Performance Architecture
Confirmable Experience
Requirements Confirmation and Assurance
Trust and Trustworthy Computing
Resources and References
Model-Driven Architecture as a schema/pattern for architectural design
MDA at higher-level than design
MDA related to requirements confirmation and system architecture
Road-show notes on Model-Driven Architecture
What is the Model-Driven Architecture?
How do the Parts Fit together: UML, MOF, and XMI
What does it mean to execute/implement the model
Where do the design rules come from?
The process/activity of Model Driven Architecture
Architecture definition
Architecture confirmation
Architectural design
Architecture maintenance
Lifecycle concerns and considerations
versioned architectural models
preservation concerns and considerations
The materials of MDA
Viewing MDA components as documents
Viewing systems as about documents as instruments of persistence
Relationship between MDA expression and document-processing standards (e.g., XML)
Tools and Resources
Training
Incorporation in Process Practices
CMM
ISO 9000
Three useful levels for architectural perspective
internal architecture of system components
intermediate architecture: boundary between the internal and the external world of the component as instrument
external architecture: system architecture as a configuration of instrumental components (the extent) in the context of the purposive system of situated functions and processes (the intent)
Patterns of Performance Architectures
Behavioral ('Data Flow') Views of Performance Architecture
Tying Performance Architecture to Requirements Confirmation and System Architecture
Tying Performance Architecture into MDA
I dream of computer technology and programming being accessible to anyone: using the technology itself to support people in exploring and mastering as much as they choose; using the technology to be less inscrutable and more open to investigation and understanding by computer users. I'm particularly taken by the idea of having support for customization and programming of our computers be available for anyone to partake of whenever it's needed, for as much as it's needed, and as long as it holds our interest.
Experience-Based Confirmation of Requirements
Systems Architecture and Confirmable Experience
Relationship to Intermediate Architecture
Relationship to Requirements Engineering
Connecting Requirements, Experience, Performance and Architectural Structures
System Requirements Modeling
The definition of trust
Something we do in the face of risk
Risk-free situations do not require trust
What it is to be trustworthy
The experience of trustworthiness
The ultimate requirement for trust and how trust is earned and restored
Trust gained, lost, and restored
Trustworthiness as a confirmable experience
Trustworthiness as an architected experience
Accountability and trust
Design for trustworthiness
The Trust-Point Game
Failure points and the placement of trust
We must trust, there are risks, and little that relieves us of having to trust
Inevitability of trust in decomposition of functions and implementations
Identifying trust points and where trust is given
Looking at where trustworthiness is demonstrable and degrees of necessary trust
Application to the Trustworthy Computing Initiative
Many of these resources are private and not accessible here. The cataloging is for my reference. I use it as a reminder of material to review.
version 0.10 2002-05-14 cloned from topics notes for expansion as an architectural themes placeholder.
created 2002-05-14-22:01 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 05-12-13 20:49 $
$$Revision: 5 $