140 likes | 305 Views
Hiding middleware within a development environment. Middleware. By Arve Meisingset Telenor R&D. Scope framework. Telco operator organisation. Administrative layer. Q3+. TMN layer. Q3 -. Signalling network. Service provision. Customer. Communication network. Scope.
E N D
Hiding middleware within a development environment Middleware By Arve Meisingset Telenor R&D
Scope framework Telco operator organisation Administrative layer Q3+ TMN layer Q3 - Signalling network Service provision Customer Communication network
Scope Telco operator organisation Administrative layer Q3+ Focus TMN layer Q3 - Signalling network Service provision Customer Communication network TINA?
Data transformations Efficiency Flexibility Organisation History Natural language Arch Circuit Group SystemLayer Administrative layer Q3+ Channel TMN layer 1:N? trail link nld LinkConnection TMN Standards
End user application terminology Administrative layer # Interchange terminology Q3+ TMN layer # Terminology of other applications Observations
Lauesen S. Real-Life Object Oriented Systems. IEEE Software, March/April 1998. Lewandowski S M. Frameworks for Component-Based Client/Server Computing. ACM Computing Surveys, March 1998 vol 30 no 1. Literature
Communicationtwo or three tier Unbalanced Simple Balanced Complex
Data Schemata Data formats Layout Contents Terminology Distribution Storage transform Duality share process process process Q3, F: GDMO IDL SQL
Developer’s view Visible Layout Contents Terminology Distribution Storage Invisible process process process Platform middleware
Development functionality Developer’s view Repository Layout Contents Terminology Distribution Storage Overlapping views Selections, projections and unions from all layers No encapsulation of attributes or behaviour No inheritance, but relations and data types List language Not equality of data and behaviour, but behaviour subordinate to data i.e. not object oriented, but data oriented language
Systems plan p p Not-p p p p One distributed system Three (communicating) systems System boarder One system= a collection of data that is enforced as a consistent whole
Message based, not object based communication - most often Means of handling long transactions - most often Systems planning methods Middleware may be visible Between systems Systems plan
Different perspectives Usage perspective Data mappings process communication Middleware perspective platform
Middleware is great if it is made invisible to the application developer Conclusion