|Home | Copyright Notice and Legal Disclaimers | Navigation Help | Tour! | Downloads | Contact Us | Site Index | Search|
|Forecast/Planning Models Index | Supporting Documentation | Downloads | FAQs ||
Forecast Contents - UML Class Diagrams for Basic (Common) Data
The following is a conceptual model. It does not necessarily represent how we would really construct a UML class diagram for conversion to an executable XML DTD/Schema. We leave it to standards bodies such as RosettaNet and OAGI to develop executable schema. The conceptual model can be used as a basis for developing executable models.
What the following is intended to illustrate is that the three forecast document types, Planning Forecast, Consumption Schedule, and Material Release Schedule, have a lot of common data attributes at both the header and line item. Additionally, each forecast type has some unique content. In an Object-Oriented paradigm, the three forecast types "inherit" data from the Basic Forecast. The different forecast types are an aggregation of basic (inherited) and unique data attributes. Notation used here is described on the Legends page.
Class Diagram: Basic Forecast Data Requirements
The following diagram shows the data that is basic to all forecast types. All forecast types "inherit" this basic data. A particular forecast type is made up of data it inherits plus data that is unique to that forecast type. See Data Requirements by Forecast Type.
Last updated 05 January 2003