1 / 21

Accounting Management in a TINA-Based Service and Network Environment

Patrick Hellemans, Cliff Redmond, Koen Daenen, Dave Lewis. IS&N 99 - Barcelona. Accounting Management in a TINA-Based Service and Network Environment. FlowThru Project. ACTS Project: March 1998 - February 2000 Focal Point of Research = Integrated Management Solutions

keithbsmith
Download Presentation

Accounting Management in a TINA-Based Service and Network Environment

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. Patrick Hellemans, Cliff Redmond, Koen Daenen, Dave Lewis IS&N 99 - Barcelona Accounting Management in a TINA-Based Service and Network Environment

  2. FlowThru Project • ACTS Project: March 1998 - February 2000 • Focal Point of Research = Integrated Management Solutions • Reuse, Customisation and Integration of Components • Across organisational domains • Across technological domains • Approach • Define guidelines for system analysis and design • Apply guidelines to the realisation of FlowThru system demonstrator

  3. Standard Organizations Frameworks & interfaces Component Vendors Business Needs Business Needs Requirements Frameworks & interfaces System Developers Components & Frameworks Development Requirements Requirements Integrated Systems Operation Service Providers Network Providers Management Systems Market Context

  4. Guidelines for Analysis and Design • Top-down approach • Management Business Process Modeling (TMF, TINA-C) • Business Actors, Roles, Business Scenarios • System Design • Components, Interactions, Information Flows • Component Facades • Component Boundaries, External Actors, Interfaces • Bottom-up Approach • Identification and analysis of reusable software components • Adaptation and re-engineering requirements

  5. Guidelines for Analysis and Design • UML Notations Used At All Levels • Profiling according to abstraction level • Paradigm Plus and Rationale ROSE Session 3B Modeling Management Components for Reuse Using UML Dave Lewis

  6. FlowThru System Demonstrator - Business Scenarios • Accounting Scenario - subject of this paper • Fulfilment system • pre-service phase • Network planning, configuration and provisioning • ATM connectivity services • Assurance system • in-service phase • Problem handling • Adherence to Service Level Agreements • Trouble Ticketing Service

  7. Fulfilment Assurance Accounting Sales Order Handling Problem Handling Customer QoS Mgt Invoicing/ Collection Customer Care Processes Service Planning/ Developmt Service Configu- ration Service Problem Resolution Service Quality Mgt Rating & Discounting Service/Product Development and Maintenance Processes Network Planning/ Developmt Network Provisioning Network Inventory Mgt Network Maintenance & Planning Network Data Mgt Networks and Systems Management Processes Physical Network and Information Technology TM Forum Business Process Model

  8. Network Data Management Decomposed Into Service and Network Data Management Rating/Discounting Broker Rating/Discounting Consumer Rating/Discounting Retailer Data Management Data Management 3Pty Service Provider Data Management Connectivity Provider Mapping Onto TINA Business Model Invoicing/Collection

  9. Access Session Comp Access Session Comp Service Subscription Component Service Session Comp Service Session Comp Service Accounting Component Retailer Consumer Connection Management Component Connection Management Component ATM Accounting Component Connectivity Provider FlowThru Accounting System Components Collect Usage Data at Network (ATM) Level, Generate Network-Level Charges and Forward These to Service Accounting Component Newly Defined and Developped for FlowThru Management of Subscription Contracts Implemented According to TINA Specifications Newly Developped for FlowThru Manage Secure Relationship Between Consumer and Retailer: service access, service subscription, … Implemented According to TINA Specifications Originate from VITAL Project Connection Management on Top of ATM Network Implemented According to TINA Specifications Originate from VITAL and ReTINA Projects Usage and Operation of Specific Service: - Digital Library - Multimedia Conference Implemented According to TINA Specifications Originate from VITAL Project Collecting and Collating Service-Level Usage Data, Generate Charges and Correlate with Network-Level Charges, Generate Consumer Bill Implemented According to TINA Specifications Originates from PROSPECT

  10. Accounting-Specific Use Cases • getBill • Consumer Requests Bill for Certain Billing Period • getSessionCharges • Consumer Requests Charges During Service Session • generateAccountableEvents • Generate Accountable Events Towards Service and/or ATM Accounting Component • listAccountingSessions • Request a List of Currently Active Management Accounting Sessions

  11. Access Session Comp Access Session Comp Service Subscription Component Service Session Comp Service Session Comp Service Accounting Component Retailer Consumer Connection Management Component Connection Management Component ATM Accounting Component Connectivity Provider FlowThru Accounting System Components - Boundary Objects Access Session Component Provider Agent: termination point of access session procedures in Consumer domain

  12. Access Session Comp Access Session Comp Service Subscription Component Service Session Comp Service Session Comp Service Accounting Component Retailer Consumer Connection Management Component Connection Management Component ATM Accounting Component Connectivity Provider FlowThru Accounting System Components - Boundary Objects Access Session Component User Agent: termination point of access session procedures in Retailer domain for one specific Consumer

  13. Access Session Comp Access Session Comp Service Subscription Component Service Session Comp Service Session Comp Service Accounting Component Retailer Consumer Connection Management Component Connection Management Component ATM Accounting Component Connectivity Provider FlowThru Accounting System Components - Boundary Objects Service Session Component Service Session User Application: termination point of service session procedures in Consumer domain for a specific service

  14. Access Session Comp Access Session Comp Service Subscription Component Service Session Comp Service Session Comp Service Accounting Component Retailer Consumer Connection Management Component Connection Management Component ATM Accounting Component Connectivity Provider FlowThru Accounting System Components - Boundary Objects Service Session Component Service Session Manager: Implements core logic of a specific service Generates accountable events towards Service Accounting Component

  15. Access Session Comp Access Session Comp Service Subscription Component Service Session Comp Service Session Comp Service Accounting Component Retailer Consumer Connection Management Component Connection Management Component ATM Accounting Component Connectivity Provider FlowThru Accounting System Components - Boundary Objects Subscription Component Subscription Agent: contact point within Subscription component for a specific Consumer Subscription Manager: manages subscription contracts

  16. Access Session Comp Access Session Comp Service Subscription Component Service Session Comp Service Session Comp Service Accounting Component Retailer Consumer Connection Management Component Connection Management Component ATM Accounting Component Connectivity Provider FlowThru Accounting System Components - Boundary Objects Service Accounting Component Account Manager: manages accounts for individual Consumers Usage Metering Data: receives, collects and collates accountable events at service-level Charge Control: calculates charges for a specific service session Bill Control: calculates Consumer bills Billing Aggregation: receives and correlates charges collected at network level

  17. Access Session Comp Access Session Comp Service Subscription Component Service Session Comp Service Session Comp Service Accounting Component Retailer Consumer Connection Management Component Connection Management Component ATM Accounting Component Connectivity Provider FlowThru Accounting System Components - Boundary Objects Connection Management Component Terminal Layer Adapter: termination point within Consumer domain of technology-specific connectivity management procedures

  18. Access Session Comp Access Session Comp Service Subscription Component Service Session Comp Service Session Comp Service Accounting Component Retailer Consumer Connection Management Component Connection Management Component ATM Accounting Component Connectivity Provider FlowThru Accounting System Components - Boundary Objects Connection Management Component Communication Session Manager: provides technology-independent connectivity service interface towards service level Layer Network Coordinator: coordinates technology-specific connectivity management procedures within a single administrative domain

  19. Access Session Comp Access Session Comp Service Subscription Component Service Session Comp Service Session Comp Service Accounting Component Retailer Consumer Connection Management Component Connection Management Component ATM Accounting Component Connectivity Provider FlowThru Accounting System Components - Boundary Objects ATM Accounting Component Metering Manager: receives, collects and collates accountable events at network (ATM) level Charge Manager: calculates charges collected at network (ATM) level

  20. Accounting System Realization - Status • Component and system analysis finalised • Component adaptation requirements identified • Component implementation adaptation on-going • System integration planned june-july

  21. Conclusions • FlowThru Guidelines Promote Reuse At Both Design and Implementation Level • Use of One Single Standard Notation (UML) At Different Abstraction Levels Eases Information Exchange, but More In-Depth Profiling of UML Notations Required • Component Facades Descriptions Ease Process of Building Management Systems by Reusing Existing Software Components • Fitting components together to realize business scenarios • Identifying required adaptations to reused components • TINA Specifications Sufficiently Detailed To Allow Component Integration Originated By Different Projects • FlowThru Guidelines and Demonstrator Results Will Be Presented to Teams of Experts During FlowThru Trial Phase (November 99)

More Related