View in EDS PDF Full Text

The Concept of Reference Architectures.

Saved in:
Bibliographic Details
Title: The Concept of Reference Architectures.
Authors: Cloutier, Robert1, Muller, Gerrit2, Verma, Dinesh1, Nilchiani, Roshanak1, Hole, Eirik1, Bone, Mary1
Source: Systems Engineering. Mar2010, Vol. 13 Issue 1, p14-27. 14p. 7 Diagrams.
Subjects: Complexity (Philosophy), Internetworking telecommunication software, Software engineering, Computer interfaces software, Architecture & technology
Abstract: The concept of Reference Architectures is novel in the business world. However, many architects active in the creation of complex systems frequently use the term Reference Architecture. Yet, these experienced architects do not collectively have a consistent notion of what constitutes a Reference Architecture, what is the value of maintaining the Reference Architecture, what is the best approach to visualizing a Reference Architecture, what is the most appropriate level of abstraction, and how should an architect make use of the Reference Architecture in their work? This paper examines current Reference Architectures and the driving forces behind development of them to come to a collective conclusion on what a Reference Architecture should truly be. It will be shown that a Reference Architecture captures the accumulated architectural knowledge of thousands man-years of work. This knowledge ranges from why (market segmentation, value chain, customer key drivers, application), what (systems, key performance parameters, system interfaces, functionality, variability), to how (design views and diagrams, essential design patterns, main concepts). The purpose of the Reference Architecture is to provide guidance for future developments. The Reference Architecture incorporates the vision and strategy for the future. The Reference Architecture is a reference for the hundreds of teams related to ongoing developments. By providing this reference all these teams have a shared baseline of why, what and how. It is the authors' goal that this paper will facilitate further research in the concepts and ideas presented herein. © 2009 Wiley Periodicals, Inc. Syst Eng [ABSTRACT FROM AUTHOR]
Copyright of Systems Engineering is the property of Wiley-Blackwell and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)
Database: Engineering Source
FullText Links:
  – Type: pdflink
Text:
  Availability: 0
Header DbId: egs
DbLabel: Engineering Source
An: 64937713
AccessLevel: 6
PubType: Academic Journal
PubTypeId: academicJournal
PreciseRelevancyScore: 0
IllustrationInfo
Items – Name: Title
  Label: Title
  Group: Ti
  Data: The Concept of Reference Architectures.
– Name: Author
  Label: Authors
  Group: Au
  Data: <searchLink fieldCode="AR" term="%22Cloutier%2C+Robert%22">Cloutier, Robert</searchLink><relatesTo>1</relatesTo><br /><searchLink fieldCode="AR" term="%22Muller%2C+Gerrit%22">Muller, Gerrit</searchLink><relatesTo>2</relatesTo><br /><searchLink fieldCode="AR" term="%22Verma%2C+Dinesh%22">Verma, Dinesh</searchLink><relatesTo>1</relatesTo><br /><searchLink fieldCode="AR" term="%22Nilchiani%2C+Roshanak%22">Nilchiani, Roshanak</searchLink><relatesTo>1</relatesTo><br /><searchLink fieldCode="AR" term="%22Hole%2C+Eirik%22">Hole, Eirik</searchLink><relatesTo>1</relatesTo><br /><searchLink fieldCode="AR" term="%22Bone%2C+Mary%22">Bone, Mary</searchLink><relatesTo>1</relatesTo>
– Name: TitleSource
  Label: Source
  Group: Src
  Data: <searchLink fieldCode="JN" term="%22Systems+Engineering%22">Systems Engineering</searchLink>. Mar2010, Vol. 13 Issue 1, p14-27. 14p. 7 Diagrams.
– Name: Subject
  Label: Subjects
  Group: Su
  Data: <searchLink fieldCode="DE" term="%22Complexity+%28Philosophy%29%22">Complexity (Philosophy)</searchLink><br /><searchLink fieldCode="DE" term="%22Internetworking+telecommunication+software%22">Internetworking telecommunication software</searchLink><br /><searchLink fieldCode="DE" term="%22Software+engineering%22">Software engineering</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+interfaces+software%22">Computer interfaces software</searchLink><br /><searchLink fieldCode="DE" term="%22Architecture+%26+technology%22">Architecture & technology</searchLink>
– Name: Abstract
  Label: Abstract
  Group: Ab
  Data: The concept of Reference Architectures is novel in the business world. However, many architects active in the creation of complex systems frequently use the term Reference Architecture. Yet, these experienced architects do not collectively have a consistent notion of what constitutes a Reference Architecture, what is the value of maintaining the Reference Architecture, what is the best approach to visualizing a Reference Architecture, what is the most appropriate level of abstraction, and how should an architect make use of the Reference Architecture in their work? This paper examines current Reference Architectures and the driving forces behind development of them to come to a collective conclusion on what a Reference Architecture should truly be. It will be shown that a Reference Architecture captures the accumulated architectural knowledge of thousands man-years of work. This knowledge ranges from why (market segmentation, value chain, customer key drivers, application), what (systems, key performance parameters, system interfaces, functionality, variability), to how (design views and diagrams, essential design patterns, main concepts). The purpose of the Reference Architecture is to provide guidance for future developments. The Reference Architecture incorporates the vision and strategy for the future. The Reference Architecture is a reference for the hundreds of teams related to ongoing developments. By providing this reference all these teams have a shared baseline of why, what and how. It is the authors' goal that this paper will facilitate further research in the concepts and ideas presented herein. © 2009 Wiley Periodicals, Inc. Syst Eng [ABSTRACT FROM AUTHOR]
– Name: AbstractSuppliedCopyright
  Label:
  Group: Ab
  Data: <i>Copyright of Systems Engineering is the property of Wiley-Blackwell and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract.</i> (Copyright applies to all Abstracts.)
PLink https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=64937713
RecordInfo BibRecord:
  BibEntity:
    Identifiers:
      – Type: doi
        Value: 10.1002/sys.20129
    Languages:
      – Code: eng
        Text: English
    PhysicalDescription:
      Pagination:
        PageCount: 14
        StartPage: 14
    Subjects:
      – SubjectFull: Complexity (Philosophy)
        Type: general
      – SubjectFull: Internetworking telecommunication software
        Type: general
      – SubjectFull: Software engineering
        Type: general
      – SubjectFull: Computer interfaces software
        Type: general
      – SubjectFull: Architecture & technology
        Type: general
    Titles:
      – TitleFull: The Concept of Reference Architectures.
        Type: main
  BibRelationships:
    HasContributorRelationships:
      – PersonEntity:
          Name:
            NameFull: Cloutier, Robert
      – PersonEntity:
          Name:
            NameFull: Muller, Gerrit
      – PersonEntity:
          Name:
            NameFull: Verma, Dinesh
      – PersonEntity:
          Name:
            NameFull: Nilchiani, Roshanak
      – PersonEntity:
          Name:
            NameFull: Hole, Eirik
      – PersonEntity:
          Name:
            NameFull: Bone, Mary
    IsPartOfRelationships:
      – BibEntity:
          Dates:
            – D: 01
              M: 03
              Text: Mar2010
              Type: published
              Y: 2010
          Identifiers:
            – Type: issn-print
              Value: 10981241
          Numbering:
            – Type: volume
              Value: 13
            – Type: issue
              Value: 1
          Titles:
            – TitleFull: Systems Engineering
              Type: main
ResultId 1