his.sePublications
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Important building blocks of an Architectural Description Language
University of Skövde, Department of Computer Science.
2002 (English)Independent thesis Basic level (degree of Bachelor)Student thesis
Abstract [en]

Software Architectures is an area that started to develop in the beginning of the 1990's. Through Software Architectures, software engineering developers have new improved opportunities for reusing, understanding, communication, analysis etc. To describe Software Architectures, Architecture Description Languages (ADLs) were proposed in the middle of the 1990's. There is not yet any common well-accepted definition of what an ADL really is. There are two tracks however; the first consider that an ADL's primary role is to provide formal syntax and a lower level of semantics; the second approach means that communication and understanding is the most important part for an ADL to play.

Because of the lack of a common definition, numerous ADLs have been developed, each with their own strengths and weaknesses and all reflecting their developers' view on what an ADL is. The problem with these ADLs is that they work in a standalone fashion and can not use the facilities of the other ADLs. ACME has been developed to solve this problem. ACME is an Architecture Description Interchange Language, which means that it can serve as a bridge between different ADLs, i.e. that one ADL can use the features of another ADL.

There are some software engineering researchers that consider ACME not to be an ADL, since ACME is the least common denominator of the present ADLs and is according to the researchers therefore not an ADL in itself. Therefore, in this report we will first compare ACME with other ADLs, and then present what features ACME needs to add to its environment to become an ADL.

Place, publisher, year, edition, pages
Skövde: Institutionen för datavetenskap , 2002. , 50 p.
Keyword [en]
ADL, criterions comparison, ACME
Identifiers
URN: urn:nbn:se:his:diva-636OAI: oai:DiVA.org:his-636DiVA: diva2:3028
Presentation
(English)
Uppsok

Supervisors
Available from: 2008-01-30 Created: 2008-01-30 Last updated: 2009-05-04Bibliographically approved

Open Access in DiVA

fulltext(1510 kB)191 downloads
File information
File name FULLTEXT01.psFile size 1510 kBChecksum SHA-1
8da8ecec22f74375c9ddedbdf652c3cdb242cbc76fa5258742a2c2854110f599e55d9a61
Type fulltextMimetype application/postscript
fulltext(1510 kB)191 downloads
File information
File name FULLTEXT02.pdfFile size 1510 kBChecksum SHA-512
4ecbc27b0d1ce303556457975800d6c4f67c23d1b3919a0f128b365dc16135b1a81fb1048df83468ba1eac27f2b01e5d2747e18e31c39452f42b2e17b55bf3f8
Type fulltextMimetype application/pdf

By organisation
Department of Computer Science

Search outside of DiVA

GoogleGoogle Scholar
Total: 382 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

Total: 202 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf