Truth vs Knowledge: The Difference Between What a Component Does and What We Know It Does

Authors:
Mary Shaw
Affiliations:
School of Computer Science, Carnegie Mellon University, Pittsburgh PA
Venue:
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
Year:
1996

Citing 5
Cited 12

Foundations for the study of software architecture

ACM SIGSOFT Software Engineering Notes
Specification matching of software components

SIGSOFT '95 Proceedings of the 3rd ACM SIGSOFT symposium on Foundations of software engineering
Architectural mismatch or why it's hard to build systems out of existing parts

Proceedings of the 17th international conference on Software engineering
Software architecture: perspectives on an emerging discipline

Software architecture: perspectives on an emerging discipline
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach

IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development

Modeling execution architecture of software system using colored Petri nets

Proceedings of the 1st international workshop on Software and performance
A model-based approach to simulation composition

SSR '99 Proceedings of the 1999 symposium on Software reusability
Component-based software engineering and the issue of trust

Proceedings of the 22nd international conference on Software engineering
"Self-healing": softening precision to avoid brittleness: position paper for WOSS '02: workshop on self-healing systems

WOSS '02 Proceedings of the first workshop on Self-healing systems
An Approach to Preserving Sufficient Correctness in Open Resource Coalitions

IWSSD '00 Proceedings of the 10th International Workshop on Software Specification and Design
Enabling predictable assembly

Journal of Systems and Software - Special issue on: Component-based software engineering
Architectural issues in network-centric computing

ACM SIGSOFT Software Engineering Notes
A Data Model to Support End User Software Engineering

ICSE COMPANION '07 Companion to the proceedings of the 29th International Conference on Software Engineering
Toward a Calculus of Confidence

ESC '07 Proceedings of the First International Workshop on The Economics of Software and Computation
Integration of Extra-Functional Properties in Component Models

CBSE '09 Proceedings of the 12th International Symposium on Component-Based Software Engineering
QOS-Aware Composition of Enterprise System‘s Components: Constraint Logic Programming Approach

Informatica
Evaluating alternative COTS assemblies from imperfect component information

QoSA'06 Proceedings of the Second international conference on Quality of Software Architectures

Quantified Score

Hi-index	0.00

Visualization

Abstract

Conventional doctrine holds that specifications are sufficient, complete, static, and homogeneous. For system-level specifications, especially for software architectures, conventional doctrine often fails to hold. This can happen when properties other than functionality are critical, when not all properties of interest can be identified in advance, or when the specifications are expensive to create. That is, the conventional doctrine often fails for practical software components. Specifications for real software must be incremental, extensible, and heterogeneous. To support such specifications, our notations and tools must be able to extend and manipulate structured specifications. In the UniCon architecture description language, we introduce credentials, a property-list form of specification that supports evolving heterogeneous specifcations and their use with system-building and analysis tools.