Architected Futures™

Tools and strategies ... for boiling the ocean

Development and Documentation Notes


Project Athena will be a precedent setting project for Architected Futures. For that reason, attention needs to be paid to how the project is structured and documented. Not every project needs to be accomplished as a strict Six Sigma project, but an objective of the "system" being architected here is the be able to tune the architecture of systems based on quality and effectiveness metrics. The current "best practice" for this type of exercise is considered to be based on Six Sigma practices and methodologies. Therefore, work products and techniques used as "standard practice tools" within the tool suite need to be able to be mapped to these or comparable methodologies. 

The intent on project Athena is to subscribe to a general following of the DMAIC methodology. Part of what this will yield is a case example for others who are interested in accomplishing other projects within or related to the Architected Futures domain, again with a DMAIC or related methodology. The Architected Futures infrastructure (EATS) will be expected to support such projects. In that regard, documents and procedures and  related project demands encountered during Project Athena will become the first test case for EATS's ability to provide such support. This does not mean that Architected Futures current support technology used during early stages of development necessarily need to be able to handle the mechanics of such support in all cases. But, what it implies is that those facilities found to be necessary and assistive in the tooling which are available need to be recognized as foundational to such support in future efforts; and that features which are not available, and which have to be handled through non-integrated external tooling be identified for replacement with new architected tooling at some point in the development plan. 

This section of the documentation is a place for the collection of such requirements.


  1. Fundamental to the design of EATS and the Architected Information Repository (AIR) is the capture of information in precise semantic fragments with precise specification around each fragment. Compound and complex information sets are then semantically composed of these fundamental fragments. This concept is fundamental to information modeling and information engineering. (An example of research in this space can be found in Semantic Word Processing for Content Authors.)
    • EATS has an existing editor which accomplishes content management under semantic guidance. However that editor is not integrated with the Drupal tooling used to create the web content for the current Architected Futures web platform.
    • If the EATS editor were integrated, then project documents like the Project Charter would be described as models known to the editor, and the editor would be "aware" of the semantic fragments which make up the content. The content would be captured "in context" and recorded in the repository as atomic information fragments. Thereafter, it would be available for reference or utilization as a set of semantically identified atomic concepts, within the context of whatever larger set of context the element was structurally related. Views such as abstracts, issues, indexes, problem summaries, etc. would be able to be semantically extracted as byproducts of the organizational scheme. This is how the target vision environment should operate.
    • Lacking such editor facilities in the early stages, the Project Athena documents will serve as templates for models of the related documents, forms, etc. Consistency to common formats is critical for being able to read and translate the "unstructured" documentation created in the early stages into "semantically structured" content in AIR at a later date. This is the same as the scheme used in DModel in the 1980's when we uploaded Wang word processing documents to create the database for GCMTAD. 

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.