Tarkvara kokkuvõte inglise keeles
•Quality is an important issue.
Architectural consequences of these requirements:
•Software should not be designed as monolithic unit but partitioned into composableservices that can be
spontaneously connected and orchestrated by business/technical processes (component-based software).
•„Software entropy“should be maximized: loosely coupling between peers,decentralized information access,
reflective approaches (Just-in-Time Integration).
•Software must be e-enabled.
Application Partioning
•Solutions consist of collections of components.
•Components are divided into multiple packages.
•Packages can work with each other across a network through ObjectRequestBroker(ORB).
•This application partitioning is transparent to the component developer.
3. COM Principles:
Rigorous Encapsulation: - no leakage of implementation details; – All object manipulation through strict
interfaces.
Polymorphism: – via multiple interfaces per class; – “Discoverable”: Query Interface
annaabi.ee 
