TMF Information Framework

Slides:



Advertisements
Similar presentations
Universal Fulfillment Organizer Leads CHT to NGOSS
Advertisements

Database Systems: Design, Implementation, and Management Tenth Edition
Chapter 4 Enterprise Modeling.
Overview of OASIS SOA Reference Architecture Foundation (SOA-RAF)
OASIS Reference Model for Service Oriented Architecture 1.0
Towards a harmonised Tispan Subscription model TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th - 15 th Source: Steve Orobec BT.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
Organizing Data & Information
The Use of Zachman Framework Primitives for Enterprise Modeling
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Introducing the Specifications of the MEF MEF 50: Carrier Ethernet Service Lifecycle Process Model.
TMF Information Framework
EA Modelling Guidelines
Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets.
Enterprise Architecture
_paper_c html#wp
Developing Enterprise Architecture
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Second RMSIG Workshop Methodology and Process Wolfram Höpken.
Phase 2: Systems Analysis
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
An Introduction to Software Architecture
Copyright © 2013 Curt Hill The Zachman Framework What is it all about?
Integrating Security Design Into The Software Development Process For E-Commerce Systems By: M.T. Chan, L.F. Kwok (City University of Hong Kong)
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 09. Review Introduction to architectural styles Distributed architectures – Client Server Architecture – Multi-tier.
Chapter 7 System models.
Slide 1 System models. Slide 2 Objectives l To explain why the context of a system should be modelled as part of the RE process l To describe behavioural.
System models l Abstract descriptions of systems whose requirements are being analysed.
Systems Analysis and Design in a Changing World, 3rd Edition
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Service Oriented Architecture CCT355H5 Professor Michael Jones Suezan Makkar.
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
OUTCOMES OBJECTIVES FUNCTIONS ACTIONS TERRITORIES LOCATIONS MARKET SEGMENTS TIME LINESCHALLENGE IMPACT RESOURCESACTIVITIESCHANNELS RELATIONS PARTNERS CUSTOMERS.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
© 2015 TM Forum | 1 Service Level Management for Smart City Ecosystems and Trusted IoT Nektarios Georgalas, BT.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Information ITIL Technology Infrastructure Library ITIL.
ONAP and MEF LSO External API Framework Functional Reference Architecture 12 July 2017 Andy Mayer, Ph.D. © 2016 AT&T Intellectual Property. All rights.
- The most common types of data models.
Interface Concepts Modeling Core Team
Understanding Enterprise Architecture
Business System Development
BIL 424 NETWORK ARCHITECTURE AND SERVICE PROVIDING.
Business System Development
Object Management Group Information Management Metamodel
TeleManagement Forum The voice of the OSS/BSS industry.
Overview of MDM Site Hub
Fundamentals & Ethics of Information Systems IS 201
ECOMP Information Model
ETOM Aryatama Wisnu Wardhana Vania Puspa Andari Febrianto Nugroho
Abstract descriptions of systems whose requirements are being analysed
The Object Oriented Approach to Design
TMF Information Framework
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Advanced Database Models
MANAGING DATA RESOURCES
EA Modelling Guidelines
Architectural Roadmap
Analysis models and design models
An Introduction to Software Architecture
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Chapter 2 Database Environment Pearson Education © 2014.
Chapter 5 Architectural Design.
SO-Architectural Roadmap
Presentation transcript:

TMF Information Framework Chip Srull

Integrated Models and Frameworks Frameworks provide containment and structure Different models, each developed for a domain/perspective Integrated within framework for alignment and containment Models for each viewpoint, perspective, domain, etc. Enterprise architecture & business process models Conceptual, logical and physical data models Application architecture and UML models Integrate domains and transform between perspectives Data and process and applications align Context, concept, logic and implementation views sync’d

Integrated Models with Frameworx Frameworx defines a comprehensive enterprise IT and process architecture that also embraces major IT industry standards such as ITIL and TOGAF. Business Process Framework (eTOM) is the industry's common process architecture for both business and functional processes Business and functional processes for telecommunication Full scope and interactions defined Information Framework (SID) provides a common reference model to describe management information: Common model: standardization and reduce complexity Consistent data use: service providers and business partners Conceptual Data Models UML class (domain) diagrams Application Framework (TAM) provides a common language to describe systems and their functions: Represents applications aligned to business functions Provides mapping between eTOM and SID Integration Framework provides a service oriented integration approach with standardized interfaces and support tools

TMF Frameworx Frameworx Is the industry’s most comprehensive business architecture Provides the flexibility of a vendor and technology-independent blueprint Allows Service Providers to realize ITIL-compliant implementations Is fully supported by a range of commercial products SOA compatible TM Forum’s Frameworx Integrated Business Architecture provides an industry agreed, service oriented approach for rationalizing operational IT, processes, and systems that enables Service Providers to significantly reduce their operational costs and improve business agility. Frameworx uses standard, reusable, generic blocks—Platforms and Business Services—that can be assembled in unique ways to gain the advantages of standardization while still allowing customization where necessary.

Information Framework (SID) Focuses on business entities and associated attribute definitions. Business Entity -- “a thing of interest to the business, such as customer, product, service, or network. Its attributes are facts that describe the entity.” (sound familiar?) Is fundamentally an Information Model. Information Model-- “a representation of business concepts, their characteristics and relationships, described in an implementation independent manner.” (sound familiar?) Entities and models are packaged in a series of documents and modeled in UML. Provides: an information/data reference model and a common information/data vocabulary, from a business entity perspective. the definition of the “things” that are to be affected by the business processes defined in the eTOM. the model that represents business concepts and their characteristics and relationships, described in an implementation-independent manner. Designed as a layered framework that partitions the shared information and data into eight high level domains.

Information Framework (SID) Uses the concepts of domains and ABEs (i.e. sub-domains) to categorize business entities Developed by the application of data affinity concepts to a telecom enterprise’s processes and data. High degree of cohesion between entities Loose coupling between different domains Top domains are broadly aligned with the eTOM

SAM – SID Mapping Accounting Activities and Events Contact Point Contracts Document Management Geography People and Organizations Physical Assets Roles

SID Common Categories Managed Entity ABE To ensure consistency, each ABE is aligned with a categorization pattern Management Entity ABE Interaction Configuration Performance Test Trouble Price Usage Managed Entity ABE Strategy and Plan Managed Entity Managed Entity Specification

What, Where, Why, When, Who GB922 Addendum 1P, V9.6, p. 6 GB922 Addendum 1L, V3.4, p. 22 GB922 Addendum 1T, V1.4, p. 15 GB922 Addendum 3, V9.5, p. 21

Conceptual Model - Entities Identity / Party (who) Individuals & Organizations Customer (actual or potential) Supplier User Time & Time Period (when) Calendar Places / Locations (where) Locations & Sites Addresses Motivation (why) Business Planning Work (how) Plan & Project Process Policy (how) The Business (what) Agreement & Contract Product Service Resource Event (when) Financials (what)

Information Framework Domain Addenda Number Deliverable Description GB922-1 Usage Usage Business Entities Uses the Usage abstract business entity to describe any resource-, service- or product-based usage that the external system can read, update and process. GB922-1A SID Agreement Provides the informational characteristics that are unique to an Agreement GB922-1BI SID Business Interaction Describes the relationship that business entities have with business interactions and how the business entities party role, resource role, and customer account, are involved in business interactions GB922-1BT SID Business Entity Base Types Covers base types that have been found to be useful during the documentation of the SID business models GB922-1J SID Project Provides a generic model, based on current industry best practice that can be used to link parts of the SID model together GB922-1L SID Location Provides a high level framework for the location (which is a complexe model with a number of subtleties), explains broad concepts and gives illustrative examples. GB922-1P SID Party Defines the information about companies and people. GB922-1Perform Performance Business Entities Describes the SID Service and Resource Performance Aggregate Business Entities (ABEs) GB922-1POL SID Policy Covers the business definition of the Policy model GB922-1R SID Root Business Entities Defines a set of common business entities that collectively serve as the foundation of the SID business view. GB922-1T SID Time Related Entities Covers the non base type entities that are time related GB922-2 SID Customer Provides the definitions of the customer business entities GB922-3 SID Product Provides detailed specification of products (ProductSpecifications), the way they are offered into the market (ProductOfferings) and in which they are maintained and perform while in use (Products) GB922-4SO SID Service Overview Provides the definition of services, differentiate between “customer facing” and “resource services GB922-4S-QoS SID Quality of Service Covers the business definition of QoS entities GB922-5LR SID Logical Resource Presents the LogicalResource Framework with an extensible set of classes and relationships that enable new lower-level LogicalResource concepts to be plugged into it GB922-5PR Information Framework Physical Resources Presents the management of network entities to better illustrate a complete worked example and to explain some of the more subtle parts of the model GB922-6 Information Framework Market / Sales Describes the Aggregate Business Entities (ABEs) that comprise the Market/Sales domain of the SID model GB922-7 SID Security Initial development of Enterprise domain Security ABEs including, Security Entity and associated Security Vulnerability, Security Event, Security Threat, Security Incident. GB922-7RA Information Framework: Enterprise Domain Revenue Assurance Business Entities Describes the Revenue Assurance area of the SID with controls, violations, key performance indicators, objectives, and rules. And includes revenue assurance actions/responses GB922-8 SID Supplier/Partner Initial development of Supplier/Partner domain, focused on Supplier/Partner and Supplier/Partner Agreement. GB922-X Information Framework XSD Schema Overview Provides an overview of the SID XML schema, including design considerations, an introduction to the schema, and an example of their use within an application integration framework

Information Framework (SID) The top layer (Layer 1) contains domains which are aligned with eTOM level 0 concepts Domain – collection of ABEs associated with a specific mgmt area. ABE – well-defined set of info and ops that characterize a highly cohesive, loosely coupled set of business entities.

SID – Level 2 Within each domain are multiple “Aggregate Business Entities” (ABEs) Service Domain

Example - ServiceSpecification

Example - ServiceSpecification

Architectural Patterns As with the Party entity, roles can be used to simplify the modeling of different types of Resources and to make the model inherently more extensible. [GB922 Addendum 5LR, v.9.5, p.38] Party and Party Role Resource and ResourceRole Service and ServiceRole Device and DeviceRole Other architectural patterns Specification Abstract Superclass (e.g. Party) Composite (assemble objects into trees; e.g. Party) Role Entity Temporal State Entity Self Relationship

High Level Conceptual Model