Proceedings of the First International Symposium on Environments and Tools for Ada 1991
DOI: 10.1145/112629.112632
|View full text |Cite
|
Sign up to set email alerts
|

Descriptive and predictive aspects of the 3Cs model

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

1
3
0

Year Published

2004
2004
2019
2019

Publication Types

Select...
3
3
1

Relationship

0
7

Authors

Journals

citations
Cited by 10 publications
(4 citation statements)
references
References 7 publications
1
3
0
Order By: Relevance
“…The previous work most similar in character to ours is the "3Cs" model [4, 7,211. Like ours, this is a conceptual model designed to foster better articulation and t o promote deeper insight about reuse and reusability.…”
Section: Introductionsupporting
confidence: 60%
“…The previous work most similar in character to ours is the "3Cs" model [4, 7,211. Like ours, this is a conceptual model designed to foster better articulation and t o promote deeper insight about reuse and reusability.…”
Section: Introductionsupporting
confidence: 60%
“…Subsequent elaboration by the members of the group at the Workshop on Methods and Tools for Reuse in June 1990 (Latour et al, 1990;Edwards, 1990;Tracz, 1990b) has given the "3C reference model" the potential to become the accepted basis for discourse on reusable software components among members of the reuse community. We adopt the model here in order to support this trend toward a much-needed common intellectual and terminological framework.…”
Section: 1a Model Of Software Structurementioning
confidence: 99%
“…The leader of the American delegation to that conference was Alan Perlis, another pioneer of software reuse who in 1987 coedited with Ted Biggerstaff the two‐volume Software Reusability, which effectively consecrated reuse as a formal discipline . Shortly after the publication of Software Reusability, a reference model for reuse known as the “3C model” was elaborated by a working group . It obtained its first broad exposure in a publication in 1991, where it was stated that “...the 3C reference model has the potential to become the accepted basis for discourse on reusable software components among members of the reuse community.”…”
Section: Introductionmentioning
confidence: 99%
“…The 3C model described in Figure defines and distinguishes three ideas: concept, content, and context. In the simplest terms, concept is a reusable component's specification, “what it is.” This has led to formal component specifications and much more. Early on the key idea emerged of separating the specification from the implementation, the Content “how it works.” The iconic example is a stack implemented variously as an array, a linked list, and so forth. Finally, the context indicates “how it is used.” The explosion of the Ariane 5 rocket back in the 1990s was a famous case of a software component from the Ariane 4 being reused in the wrong Context …”
Section: Introductionmentioning
confidence: 99%