Tarkvara kokkuvõte inglise keeles
names, no matter what type of object is in use at the moment.
2. COMPONENT TECHNOLOGY – THE PROBLEM
The Problem
•Today, anything and anyone must be net-enabled.
•Automated business processes, products, and software systems need to evolve in „e-Time“.
•Everything must be changeable, extensible, adaptable.
•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.