- The Solution Frameworks and SID
- The objectives of the Solution Frameworks
- How SID can help achieve these objectives
- Description of the Information Framework
- Issues addressed by SID
- SID description
- Business view
- System view
- Information Model vs. Data Model
- Benefits
- Who can use SID?
- Documentation structure
- Relationships between these Frameworks
- SID to eTOM mapping
- Primary and Secondary Level 2 Processes
- C.R.U.D. relationship
- Frameworx lifecycle
- SID to eTOM mapping
- SID Concepts and Principles
- SID domains
- Market/sales
- Product
- Customer
- Service
- Resource
- Supplier/partner
- Enterprise
- Common Business
- Built-in extensibility
- A review on UML
- UML introduction
- UML Class Diagrams
- UML classes
- UML attributes and operations
- UML associations
- UML aggregations vs. compositions
- UML subclasses
- Understanding SID through its modeling patterns
- EntitySpecification/Entity
- ServiceSpecification/Service
- ProductSpecification/ProductOffering/Product
- ResourceSpecification/Resource
- Composite/atomic
- ProductSpecification
- ProductOffering
- ProductOfferingPrice
- Product
- ServiceSpecification
- Role/entity
- Party/PartyRoles
- Customer
- Product
- Service
- Resource
- Business interaction
- BusinessInteraction/BusinessInteractionItems
- CustomerOrder
- Agreement
- ServiceOrder
- ResourceOrder
- TroubleTicket
- CharacteristicSpecification/Characteristic
- ProductSpecifications Characteristic
- ServiceSpecCharacteristics
- ResourceSpecCharacteristics
- EntitySpecification/Entity
- Getting Started with the SID
- Model files format
- SID UML Model- Rational Rose
- HTML
- XMI
- XSD
- UML editors
- Rational Rose
- Opensource editors
- Extending the Framework
- Principles
- Framework of Frameworks
- Extensions
- Existing business entities
- Adding attributes by sub-classing
- Adding attributes by composition
- New business entities
- Adding new business entities by aggregation
- Beware of sub-classing!
- Association naming guidelines
- Attribute naming guidelines
- Folder naming
- General modeling guidelines
- Existing business entities
- Model files format
- SID domains
- Framework Compliance/Conformance
- No Frameworx compliance criteria
- Only SID levels of compatibility…
- …and API tests
- eTOM conformance
- Main Uses for the Framework
- Common terminology
- Internally
- Externally
- Rationalize developments
- Standard interfaces
- Support RFP data specifications
- Common terminology
- Some Examples
- Course Wrap-up: Recap, Discussion, and Evaluations