Compliance Level |
Meaning |
Business Benefits |
Issues |
| Concept Compliance |
Systems that are organized according to top level TINA reference models (such as the retailer model). |
Organized to perform one or more distinct TINA business roles.
Industry shared recognition of problems with a solid context for dealing with them. |
The need to have a simplified model of TINA business roles as related to functional decoupling of interfaces needs to be made explicit to be followed. |
|
Layering / Partitioning Compliance
|
Systems that are functionally decomposed in accordance with TINA.
Interfaces are used to decouple layers and functions in the implementation as defined by TINA. but the underlying object model may be different.
|
Ability to perform a TINA business role in the telecommunications services business
Ability to reuse TINA architecture as the basis for managing development and maintenance.
Ability to find human resources on market who have technical familiarity with your product's baseline architecture.
Simplifies development of functional specifications.
Potential bridging of functionality to other TINA systems
A step towards TINA conformance.
Ability to be flexible in defining, deploying, or leveraging telecommunications services.
|
Clarity and completeness of TINA model at this level is required.
High level layering and partitioning requirements for reference points will need to be made.
How reference points are simplified to this level needs to be made explicit.
|
|
Information Model Compliance
|
Object classes defined according to TINA.
Operations defined with semantic equivalence to TINA operations.
|
Enables object-level bridges between other TINA Compliant third party implementations.
Greater reuse of objects within developer's organization, less new development to manage.
|
Externalized information model is linked with internal model. Not typically able to unlink internal and external views.
|
|
Technical Conformance
|
Systems that can inter-operate over some useful portion of a reference point's interfaces.
|
Functionally adequate with assured interworking.
Ability to purchase and deploy third party software solutions and integrate them directly with other TINA systems.
|
Facets need to correspond to complete enough sets of functionality to be useful.
To define effective objective test criteria added reference point info. is needed.
|
| Operational Conformance
|
Systems that both technically conform to TINA and can inter-operate at a guaranteed service level in terms of responsiveness, availability and other service level guarantees.
|
Plug and play - Ready to inter-operate with any other business with similar TINA compliant systems.
Assured performance under production conditions.
|
The concept of operations and service levels for TINA services themselves is yet to be dealt with.
CORBA does not yet include this level.
|
