Database Reference
In-Depth Information
The Select Perspective uses the standard UML enriched with the extensions to support
component modeling. For the purpose of business modeling, it uses the notations of the
Computer Science Corporations (CSC) Catalyst methodology (CSC, 1995). This notation and
technique help to link the business processes, associated use cases and classes. The method
also uses Entity-Relationship Diagrams (ERD) for mapping between the UML class model and
the relational data model. Components in Select Perspective are executables offering services
through published interfaces. The services can, but not necessarily, be implemented using
object technologies. Though based on the UML, the method uses a streamlined set of UML
modeling techniques, without introducing new concepts that require UML extensions.
The component concept is seen as the concept of package, defi ned in UML as “a general
purpose mechanism for organizing elements into groups” (Booch et al., 1999). Two basic
stereotypes of the package are distinguished: a service package used in business-oriented
component modeling and a component package used in component and system implemen-
tation. A service package contains classes that have a high level of interdependency, and
serve a common purpose by delivering a consistent set of services. A component package
represents an executable component, i.e., the actual code. When a service package is placed
on a node of the network, it effectively becomes a component package. Special attention is
paid to component modeling of the legacy assets, i.e.,on how to use the component principles
to effi ciently wrap and further integrate legacy systems.
The latest version of Select Perspective includes support for Web Services, as well as
for Model-Driven Architecture and Agile Software Development, as promising paradigms
in software development. The Select Perspective software development life cycle is a set
of workfl ows that are based on an iterative and incremental development approach. The
method defi nes three basic workfl ows: Consume, Supply, and Manage. Consume workfl ow
delivers the solution that uses components and services from the component suppliers, then
maintains and supports that solution. Supply workfl ow delivers and maintains components
based on the request for services from particular component and service consumers. Manage
workfl ow is concerned with the activities of acquiring, certifying, classifying and locating
components to serve the needs of both component consumers and suppliers. Select Per-
spective provides a comprehensive development lifecycle for component-based solutions
that supports business-aligned parallel development in order to reduce time-to-market. The
method defi nes project management features such as iterative working, incremental working
and planning, parallel working and monitoring. The method is derived from best practices
proven on real projects.
Catalysis
Catalysis (D'Souza & Wills, 1999) is a component-oriented approach with its origins
in object-oriented analysis and design. Catalysis began in 1991 as a formalization of OMT
(Rumbaugh et al., 1991), and was developed over several years of applying, consulting, and
training. It extends second-generation OO-methods such as Fusion (Coleman et al., 1993)
and Syntropy (Cook & Daniels, 1994), including support for framework-based development
and defi ning methodical refi nements from abstract specifi cation to implementation. Catalysis
is well documented in the corresponding topic, technical papers, and by a dedicated website
(www.catalysis.org). Opportunities for training and consultancy are also provided. Catalysis
is effectively supported by the COOL family of tools such as COOL:Gen, COOL:Spex,
COOL:Joe, etc., originally developed by Sterling Software. After acquiring Select Software
