An architecture-centric approach for systems design

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

The most critical requirements for the lifetime value of a system are its nonfunctional requirements such as reliability, security, maintainability, changeability, etc. These are collectively known as the 'ilities' and are typically addressed in system design once the functional architecture has been developed. In this paper we propose the use of architecturecentric design that modifies this standard workflow so that those non-functional requirements, which actually reflect the true business needs, are addressed first. This ensures that the final system better reflects and embodies those architecturally-significant requirements rather than having them addressed secondarily. This is an important change since the 'ilities' are systemic properties (properties of the system as a whole) rather than systematic properties (properties of individual components or sub-systems) and are therefore difficult to address once the functional architecture has been determined and the separation of concerns is already somewhat completed. We provide an example of the approach based around a simplified case study of an online, on-board health monitoring system for shipboard gas turbine electricity generators that collects, filters, analyzes, transmits, and mines sensor data from the generators subsystems.

Original languageEnglish (US)
Title of host publication19th Annual International Symposium of the International Council on Systems Engineering (INCOSE 2009) in conjunction with the 3rd Asia-Pacific Conference on Systems Engineering APCOSE 2009
PublisherINCOSE-International Council on Systems Engineering
Pages299-310
Number of pages12
ISBN (Print)9781615674398
StatePublished - Jan 1 2009
Event19th Annual International Symposium of the International Council on Systems Engineering, INCOSE 2009 - , Singapore
Duration: Jul 20 2009Jul 23 2009

Publication series

Name19th Annual International Symposium of the International Council on Systems Engineering, INCOSE 2009
Volume1

Other

Other19th Annual International Symposium of the International Council on Systems Engineering, INCOSE 2009
CountrySingapore
Period7/20/097/23/09

Fingerprint

Maintainability
Gas turbines
Electricity
Systems analysis
Health
Monitoring
Sensors
Industry

All Science Journal Classification (ASJC) codes

  • Hardware and Architecture
  • Information Systems
  • Control and Systems Engineering

Cite this

Neill, C., Sangwan, R. S., & Paulish, D. J. (2009). An architecture-centric approach for systems design. In 19th Annual International Symposium of the International Council on Systems Engineering (INCOSE 2009) in conjunction with the 3rd Asia-Pacific Conference on Systems Engineering APCOSE 2009 (pp. 299-310). (19th Annual International Symposium of the International Council on Systems Engineering, INCOSE 2009; Vol. 1). INCOSE-International Council on Systems Engineering.
Neill, Colin ; Sangwan, Raghvinder S. ; Paulish, Daniel J. / An architecture-centric approach for systems design. 19th Annual International Symposium of the International Council on Systems Engineering (INCOSE 2009) in conjunction with the 3rd Asia-Pacific Conference on Systems Engineering APCOSE 2009. INCOSE-International Council on Systems Engineering, 2009. pp. 299-310 (19th Annual International Symposium of the International Council on Systems Engineering, INCOSE 2009).
@inproceedings{ec73ce3007474eebb9051a98cd39de28,
title = "An architecture-centric approach for systems design",
abstract = "The most critical requirements for the lifetime value of a system are its nonfunctional requirements such as reliability, security, maintainability, changeability, etc. These are collectively known as the 'ilities' and are typically addressed in system design once the functional architecture has been developed. In this paper we propose the use of architecturecentric design that modifies this standard workflow so that those non-functional requirements, which actually reflect the true business needs, are addressed first. This ensures that the final system better reflects and embodies those architecturally-significant requirements rather than having them addressed secondarily. This is an important change since the 'ilities' are systemic properties (properties of the system as a whole) rather than systematic properties (properties of individual components or sub-systems) and are therefore difficult to address once the functional architecture has been determined and the separation of concerns is already somewhat completed. We provide an example of the approach based around a simplified case study of an online, on-board health monitoring system for shipboard gas turbine electricity generators that collects, filters, analyzes, transmits, and mines sensor data from the generators subsystems.",
author = "Colin Neill and Sangwan, {Raghvinder S.} and Paulish, {Daniel J.}",
year = "2009",
month = "1",
day = "1",
language = "English (US)",
isbn = "9781615674398",
series = "19th Annual International Symposium of the International Council on Systems Engineering, INCOSE 2009",
publisher = "INCOSE-International Council on Systems Engineering",
pages = "299--310",
booktitle = "19th Annual International Symposium of the International Council on Systems Engineering (INCOSE 2009) in conjunction with the 3rd Asia-Pacific Conference on Systems Engineering APCOSE 2009",

}

Neill, C, Sangwan, RS & Paulish, DJ 2009, An architecture-centric approach for systems design. in 19th Annual International Symposium of the International Council on Systems Engineering (INCOSE 2009) in conjunction with the 3rd Asia-Pacific Conference on Systems Engineering APCOSE 2009. 19th Annual International Symposium of the International Council on Systems Engineering, INCOSE 2009, vol. 1, INCOSE-International Council on Systems Engineering, pp. 299-310, 19th Annual International Symposium of the International Council on Systems Engineering, INCOSE 2009, Singapore, 7/20/09.

An architecture-centric approach for systems design. / Neill, Colin; Sangwan, Raghvinder S.; Paulish, Daniel J.

19th Annual International Symposium of the International Council on Systems Engineering (INCOSE 2009) in conjunction with the 3rd Asia-Pacific Conference on Systems Engineering APCOSE 2009. INCOSE-International Council on Systems Engineering, 2009. p. 299-310 (19th Annual International Symposium of the International Council on Systems Engineering, INCOSE 2009; Vol. 1).

Research output: Chapter in Book/Report/Conference proceedingConference contribution

TY - GEN

T1 - An architecture-centric approach for systems design

AU - Neill, Colin

AU - Sangwan, Raghvinder S.

AU - Paulish, Daniel J.

PY - 2009/1/1

Y1 - 2009/1/1

N2 - The most critical requirements for the lifetime value of a system are its nonfunctional requirements such as reliability, security, maintainability, changeability, etc. These are collectively known as the 'ilities' and are typically addressed in system design once the functional architecture has been developed. In this paper we propose the use of architecturecentric design that modifies this standard workflow so that those non-functional requirements, which actually reflect the true business needs, are addressed first. This ensures that the final system better reflects and embodies those architecturally-significant requirements rather than having them addressed secondarily. This is an important change since the 'ilities' are systemic properties (properties of the system as a whole) rather than systematic properties (properties of individual components or sub-systems) and are therefore difficult to address once the functional architecture has been determined and the separation of concerns is already somewhat completed. We provide an example of the approach based around a simplified case study of an online, on-board health monitoring system for shipboard gas turbine electricity generators that collects, filters, analyzes, transmits, and mines sensor data from the generators subsystems.

AB - The most critical requirements for the lifetime value of a system are its nonfunctional requirements such as reliability, security, maintainability, changeability, etc. These are collectively known as the 'ilities' and are typically addressed in system design once the functional architecture has been developed. In this paper we propose the use of architecturecentric design that modifies this standard workflow so that those non-functional requirements, which actually reflect the true business needs, are addressed first. This ensures that the final system better reflects and embodies those architecturally-significant requirements rather than having them addressed secondarily. This is an important change since the 'ilities' are systemic properties (properties of the system as a whole) rather than systematic properties (properties of individual components or sub-systems) and are therefore difficult to address once the functional architecture has been determined and the separation of concerns is already somewhat completed. We provide an example of the approach based around a simplified case study of an online, on-board health monitoring system for shipboard gas turbine electricity generators that collects, filters, analyzes, transmits, and mines sensor data from the generators subsystems.

UR - http://www.scopus.com/inward/record.url?scp=84878073353&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84878073353&partnerID=8YFLogxK

M3 - Conference contribution

AN - SCOPUS:84878073353

SN - 9781615674398

T3 - 19th Annual International Symposium of the International Council on Systems Engineering, INCOSE 2009

SP - 299

EP - 310

BT - 19th Annual International Symposium of the International Council on Systems Engineering (INCOSE 2009) in conjunction with the 3rd Asia-Pacific Conference on Systems Engineering APCOSE 2009

PB - INCOSE-International Council on Systems Engineering

ER -

Neill C, Sangwan RS, Paulish DJ. An architecture-centric approach for systems design. In 19th Annual International Symposium of the International Council on Systems Engineering (INCOSE 2009) in conjunction with the 3rd Asia-Pacific Conference on Systems Engineering APCOSE 2009. INCOSE-International Council on Systems Engineering. 2009. p. 299-310. (19th Annual International Symposium of the International Council on Systems Engineering, INCOSE 2009).