UML Components: A Simple Process for Specifying Component-Based Software

By J. Cheesman, J. Daniels. 2000

575 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

A Classification Framework for Software Component Models (2011, background): “lifecycle, a component has different forms [16]: Initially, a”
Applications of Ontologies in Software Engineering (2006, background): “Usually, this search for reusable components takes place after the analysis phase, when the functional requirements are settled [ 12 ].”
Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools (2004, background): “Component-based development (CBD) arose in the late nineties [15, 6].”
The Palladio component model for model-driven performance prediction (2009, methodology): “Although the concept of reusable software components has been discussed since the famous 1968 NATO conference on software engineering [42], CBSE has gained wide-spread attention only since the 1990s due to the failure of object-oriented programming to effectively support reuse [13,27,60].”
Performance evaluation of component-based software systems: A survey (2010, background): “To clarify the notion of component life-cycle, Figure 2 shows four stages of the idealised component life-cycle by Cheesman and Daniels [14].”
Software Component Models (2006, methodology): “A.1 Category 1: Design without Repository A.1.1 UML2.0 In UML2.0 [25], [ 26 ], a component is a modular unit of a system with well-defined interfaces that is replaceable within its environment.”