1 / 9

BO Model documentation

BO Model documentation. Version 0.1 Jochen Haenisch. Basics. Scope: Document the BO model as part of AP242 Start preparations Feb 21 real documentation with BO Model v0.2, mid-March Continuous updates as the BO Model is extended End June ..., 2011 Team: Allison, Darla, Günter, Jochen.

eros
Télécharger la présentation

BO Model documentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BO Model documentation Version 0.1 Jochen Haenisch

  2. Basics • Scope: • Document the BO model as part of AP242 • Start • preparations Feb 21 • real documentation with BO Model v0.2, mid-March • Continuous updates as the BO Model is extended • End • June ..., 2011 • Team: Allison, Darla, Günter, Jochen Deadlines for Standing documents?

  3. BO Model Driven Annexes of AP242 • Business Object Model • Capabilities • Business Objects • EXPRESS-G Diagrams • EXPRESS Longform • Derivation of the BO Model XML Schema • General Concepts • XML Configuration Specification • XML Schema • UML Diagrams • Mapping Specification: BO Model  AP 242 ARM

  4. BO Model Driven Annexes of AP242 Annex <X> normative For details see: ”Content of the AP242 BOM related Annexes V0.4.ppt” normative informative normative Annex <Y> informative normative normative informative Annex <Z> normative

  5. Way of working • Regular team telecons • Receive stable releases from BO Model team • Feed completed contents to main AP242 editor • Promote standardization issues through SC4 • ”Guidelines for the content of application protocols that use application modules” • ”Guidelines for the development of mapping specifications” • ”Supplementary Directives”

  6. Resources • Roles: • AP242 BO Model editor • for the three annexes • a.o. P28 configuration options expert • Stepmod programmer • SC4 Standing Documents editor • ... • Allison, Darla, Alexandre, Günter: How many hours can they spend on this task? • Tools: • LKsoft EXPRESS-G editor • UML editor • Stepmod • ...

  7. Notes 2011-02-16 • The BO Model covers the entire scope of AP242, but with varying level of detail. • No correspondence table for AP203 ARM to BO model needed. • Intersection of two capabilities is empty. • XML for all the BO; shape will get high-level BOs only. • A conformance option relates to one or many capabilities. • A capability may be included in one or many conformance options. • How to feed the documentation requirements back into ISO? • How to merge (and document) ”permissive” lists (enumeration items) form 203 and 214? • Make enumeration items visible on E-G diagrams via annotations. • There will be an ARM longform that is navigable (paid by Simon). • Are there documentation bits in the 214 ARM that needs to be preserved, but will not be in the BO model, such as, examples? • Hyperlinks between BO Model and ARM ... probably not. • For v0.2 do include product_view_definition.

  8. Notes 2011-02-16 (2) • The FEA capabilities shall become BOs.

  9. Tasks • Document Business Object Model • Capabilities and BOs • E-G and EXPRESS longform • Document BOM XML Schema • General concept • Relationship to BO and ARM and AIM. How derived? • Short XML names • XML Configuration Specification • XML schema list • UML diagrams • Document Mapping Specification • BOM  AP 242 ARM • Using the ARM to AIM mapping specification

More Related