skip to content
Characteristics of higher-level languages for software architecture Preview this item
ClosePreview this item
Checking...

Characteristics of higher-level languages for software architecture

Author: Mary Shaw; David Garlan
Publisher: Pittsburgh, Pa. : School of Computer Science, Carnegie Mellon University, [1994]
Series: Research paper (Carnegie Mellon University. School of Computer Science), CMU-CS-94-210.
Edition/Format:   Book : English
Database:WorldCat
Summary:
Abstract: "As the size and complexity of software systems increases, the design and specification of overall system structure -- or software architecture -- emerges as a central concern. Architectural issues include the gross organization of the system, protocols for communication and data access, assignment of functionality to design elements, and selection among design alternatives. Currently system designers have  Read more...
Rating:

(not yet rated) 0 with reviews - Be the first.

Subjects
More like this

 

Find a copy in the library

&AllPage.SpinnerRetrieving; Finding libraries that hold this item...

Details

Document Type: Book
All Authors / Contributors: Mary Shaw; David Garlan
OCLC Number: 32155113
Notes: "Also appears as CMU Software Engineering Institute Technical Report CMU/SEI-94-TR-23 ESC-TR-94-023."
"December 1994."
Description: 15 pages ; 28 cm.
Series Title: Research paper (Carnegie Mellon University. School of Computer Science), CMU-CS-94-210.
Responsibility: Mary Shaw, David Garlan.

Abstract:

Abstract: "As the size and complexity of software systems increases, the design and specification of overall system structure -- or software architecture -- emerges as a central concern. Architectural issues include the gross organization of the system, protocols for communication and data access, assignment of functionality to design elements, and selection among design alternatives. Currently system designers have at their disposal two primary ways of defining software architecture: they can use the modularization facilities of existing programming languages and module interconnection languages; or they can describe their designs using informal diagrams and idiomatic phrases (such as 'client-server organization'). In this paper we explain why neither alternative is adequate. We consider the nature of architectural description as it is performed informally by systems designers. Then we show that regularities in these descriptions can form the basis for architectural description languages. Next we identify specific properties that such languages should have. Finally, we illustrate how current notations fail to satisfy those properties."

Reviews

User-contributed reviews
Retrieving GoodReads reviews...
Retrieving DOGObooks reviews...

Tags

Be the first.

Similar Items

Related Subjects:(1)

Confirm this request

You may have already requested this item. Please select Ok if you would like to proceed with this request anyway.

Linked Data


<http://www.worldcat.org/oclc/32155113>
library:oclcnum"32155113"
library:placeOfPublication
library:placeOfPublication
rdf:typeschema:Book
schema:about
schema:about
schema:contributor
schema:creator
schema:datePublished"1994"
schema:description"Abstract: "As the size and complexity of software systems increases, the design and specification of overall system structure -- or software architecture -- emerges as a central concern. Architectural issues include the gross organization of the system, protocols for communication and data access, assignment of functionality to design elements, and selection among design alternatives. Currently system designers have at their disposal two primary ways of defining software architecture: they can use the modularization facilities of existing programming languages and module interconnection languages; or they can describe their designs using informal diagrams and idiomatic phrases (such as 'client-server organization'). In this paper we explain why neither alternative is adequate. We consider the nature of architectural description as it is performed informally by systems designers. Then we show that regularities in these descriptions can form the basis for architectural description languages. Next we identify specific properties that such languages should have. Finally, we illustrate how current notations fail to satisfy those properties.""@en
schema:exampleOfWork<http://worldcat.org/entity/work/id/33762458>
schema:inLanguage"en"
schema:isPartOf
schema:name"Characteristics of higher-level languages for software architecture"@en
schema:publication
schema:publisher
wdrs:describedby

Content-negotiable representations

Close Window

Please sign in to WorldCat 

Don't have an account? You can easily create a free account.