A dependency constraint language to manage object‐oriented software architectures
The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.
Abstract
This paper presents a domain‐specific dependency constraint language that allows software architects to restrict the spectrum of structural dependencies, which can be established in object‐oriented systems. The ultimate goal is to provide architects with means to define acceptable and unacceptable dependencies according to the planned architecture of their systems. Once defined, such restrictions are statically enforced by a tool, thus avoiding silent erosions in the architecture. The paper also presents results from applying the proposed approach to different versions of a real‐world human resource management system. Copyright © 2009 John Wiley & Sons, Ltd.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Foundations for the study of software architecture
Perry, D. E., & Wolf, A. L. (1992) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/141874.141884 · Cited by 2,023
A classification and comparison framework for software architecture description languages
Medvidovic, N., & Taylor, R. N. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.825767 · Cited by 1,987 · cited 1×
“Architectural Description Languages (ADL): ADL represent another alternative to provide architectural conformance by construction [13].”
Background
Cited by
Controlling software architecture erosion: A survey
de Silva, L., & Balasubramaniam, D. (2012) · Journal of Systems and Software · doi:10.1016/j.jss.2011.07.036 · Cited by 184
Terra, R., Valente, M. T., Czarnecki, K., & Bigonha, R. S. (2015) · Software: Practice and Experience · doi:10.1002/spe.2228 · Cited by 37
“Third, because we have detected violations using DCL, we cannot claim that our approach provides equivalent coverage and precision when using other architecture conformance tools.”
BackgroundMethodResultInfluentialSelf-citationOn the Evolutionary Nature of Architectural Violations
Brunet, J., Bittencourt, R. A., Serey, D., & Figueiredo, J. (2012) · 2012 19th Working Conference on Reverse Engineering · doi:10.1109/wcre.2012.35 · Cited by 34
How Do Software Architects Specify and Validate Quality Requirements?
Caracciolo, A., Lungu, M. F., & Nierstrasz, O. (2014) · Lecture Notes in Computer Science · doi:10.1007/978-3-319-09970-5_32 · Cited by 32
Automated infrastructure as code program testing
Sokolowski, D., Spielmann, D., & Salvaneschi, G. (2024) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2024.3393070 · Cited by 20
“Terra and de Oliveira Valente [75] proposed specifying and statically enforcing dependencies in the software architectures to avoid erosion.”
BackgroundArchitectural Consistency Checking in Plugin-Based Software Systems
Greifenberg, T., Müller, K., & Rumpe, B. (2015) · Proceedings of the 2015 European Conference on Software Architecture Workshops · doi:10.1145/2797433.2797493 · Cited by 7
“Using DepCoL, it is possible to define constraints affecting groups of plugins, reducing the required specification effort, to formulate constraints for specific plugins only and to refine constraints.”
Metadata
- Authors
- Terra, R., & Valente, M. T.
- Venue
- Software: Practice and Experience
- Publisher
- Wiley
- Published
- 2009-06-08
- Volume
- 39
- Issue
- 12
- Pages
- 1073-1094
- ISSN
- 0038-0644 (ISSN-L)
- 1097-024X
- OpenAlex
- W4231342751
- Cited by
- 61
- References
- 2
- FWCI
- 3.61
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.