opencimi / AML

Archetype Modeling Language development repository
4 stars 5 forks source link

Overview of specification #42

Open dksharma opened 9 years ago

dksharma commented 9 years ago

The "specification" model is much more fragmented then it should be. There is a need for AB members as well as other specification reviewers to have easy access to models, including diagrams. The submission document should be driven by the UML models, not by diagrams. There should be a single rfp "specification" module, which may use the AML-UML Profile models, perhaps the ADL/AOM meta-model, perhaps some example UML models, and combine them with other UML-modeled concepts in the "specification" model such as contributers (Actors), glossaries, artifacts, references, etc. The diagrams need to be adjusted/sized/colored to easily map into space available on a submission figure. Diagrams should avoid color coding, patterns, etc., but should contain fully qualified names of elements where appropriate. Full UML notation should be employed in most cases. If a diagram is too big for printing, break it into multiple diagrams.

dksharma commented 9 years ago

Specification.mdzip is composed of multiple shared modules which needs to be combined into one before we submit. Diagram elements with QN, diagrams should scale properly. Big diagrams need to be split up into smaller ones for better/uniform readability. For images - keep ratio and adjust the size.