UBL LCSC Minutes
Tim's Instructions for going through working documents of new model
Updated: Tuesday - 29 October 2002
To assist with understanding these documents it is suggested they are viewed in the following sequence...
- Document design process jpeg file - is a refinement on the slide shown in Burlington indicating the difference between a normalized relational model, it various hierarchical assemblies into documents and the XML schemas that are built from this.
- Class Diagram 0p70 gif file - is the UML Class diagram of the entire normalized model (as it now stands). On the diagram in (1.) this is on the left hand side.
- Normalized Components8 0p70 spreadsheet is the normalized model (as per the class diagram) with all the properties defined. On the diagram in (1.) this is also on the left hand side.
- The document UBL_Library-0p66v2-WIP ex Burlington CHANGE LOG to 0p70 helps explain the changes made to our previous structures as a result of the normalization process, the 0p70 scope statement and some logical refinements (e.g. rationalizing the pricing structures).
- Order Assembly 0p70 powerpoint file is the slide show demonstrating how we get from the normalized model to a document definition (ie a hierarchical model). It is an example of constructing an Order document. This is only a first take on the actual Order structure - it is up to the document assemblers to choose what they think are the most appropriate assemblies of components to make an Order. This is provided as an example - many decisions where based on the previous Order structure and the 0p70 scope statement - BUT IT IS NOT THE ONLY WAY TO BUILD AN ORDER USING THE NORMALIZED COMPONENTS, THIS IS A PROTOTYPE TO DEMONSTRATE THE PROCESS. On the diagram in (1.) this is in the middle.
- The UBL_Library-0p70v1-WIP spreadsheet SHOWS WHAT THE RESULT OF THE DEMONSTRATION ORDER DOCUMENT DEFINITION WILL LOOK LIKE. it is the assembly of normalized components following the path/structures defined in (5.) above. Note, that this is in exactly the same format we have been using all along. When we add other document definitions we should start to see the re-usable ABIEs applied to other documents as well - however what makes a re-usable ABIE is the fact it is re-used not vice versa. Remember that potentially any ABIE (even Order) is re-usable. On the diagram in (1.) this is in the middle.
From all of this I believe the most immediate artifacts for QA are (2) and (3). Once we have agreed on these the actually document assembly is a much simpler process.