UML PROFILE FOR SAVECCM - Research

Component – based software engineering
naming scheme to ensure this demand (CORBA, EJB, and Microsoft
DCOM).
• Modularity and encapsulation. Each component encapsulates a set of
closely related elements and implements appropriate logic to perform a
specific task.
• Independent delivery. Software component must be delivered as
independent part which can be integrated into the system and can be
replaced under certain conditions. Each component must play an
independent role in a system.
• Contract – based interface. A software component has its interface which
determines a contract between the client of an interface and a provider of
an implementation for the interface. A contract specifies what is expected
from the client in order to use the interface to access a component
service function. It also defines what kind of services and
implementations have to be provided to meet the service contract. This
implicates that a component delivers its provided services only if its
clients access the provided component interface in a right way.
• Reusability. Reusability of software components is the fundamental
notion of CBSE. Unlike a conventional software module which usually
has a very limited reuse scope, a software component provides multiplelevel
granularities for reuse on a large scope. The reusable elements of a
software component include its analysis specification, component design
and design patterns, source code, and executables. In addition,
component deployment mechanisms and test support information (such
as test cases and test scripts) are also a reusable items.
Properties listed above, evince that a software component merges two distinct
perspectives: component as an implementation and component as an architectural
abstraction; components are therefore architectural implementations. Viewed as
implementations, components can be deployed, and assembled into larger
(sub)systems. Viewed as architectural abstractions, components express design
rules that impose a standard coordination model on all components. These design
rules take the form of a component model, or a set of standards and conventions
to which components must conform.
The most important feature of a component is the separation of its interfaces
from its implementation. What distinguishes the concepts in CBSE from concepts
in many other programming languages are requirements of integration of a
component into an application. Component integration and deployment should be
independent of the component development life cycle and there should be no
need to recompile the application when updating with a new component.
7