Knowledge (XXG)

Systems architecture

Source 📝

31: 330: 310:. A major purpose of the partitioning is to arrange the elements in the sub systems so that there is a minimum of interdependencies needed among them. In both software and hardware, a good sub system tends to be seen to be a meaningful "object". Moreover, a good architecture provides for an easy mapping to the user's requirements and the 273:
deals (more or less) exclusively with the computer program; and the systems engineer is responsible for seeing that the program is capable of properly running within the hardware device, and that the system composed of the two entities is capable of properly interacting with its external environment,
254:
is impotent; even as a software artifact, or program, is equally impotent unless it can be used to alter the sequential states of a suitable (hardware) machine. However, a hardware machine and its programming can be designed to perform an almost illimitable number of abstract and physical tasks.
255:
Within the computer and software engineering disciplines (and, often, other engineering disciplines, such as communications), then, the term system came to be defined as containing all of the elements necessary (which generally includes both hardware and software) to perform a useful function.
123:. If documented, it may include information such as a detailed inventory of current hardware, software and networking capabilities; a description of long-range plans and priorities for future purchases, and a plan for upgrading and/or replacing dated equipment and software. 136:
One can think of system architecture as a set of representations of an existing (or future) system. These representations initially describe a general, high-level functional organization, and are progressively refined to more detailed and concrete descriptions.
264:
is defined as one concerned with the complete device, both hardware and software and, more particularly, all of the interfaces of the device, including that between hardware and software, and especially between the complete device and its user (the CHI). The
115:
An architecture consists of the most important, pervasive, top-level, strategic inventions, decisions, and their associated rationales about the overall structure (i.e., essential elements and their relationships) and associated characteristics and
111:
An allocated arrangement of physical elements which provides the design solution for a consumer product or life-cycle process intended to satisfy the requirements of the functional architecture and the requirements
77:
and the sub-systems developed, that will work together to implement the overall system. There have been efforts to formalize languages to describe system architecture, collectively these are called
279:
A systems architecture makes use of elements of both software and hardware and is used to enable the design of such a composite system. A good architecture may be viewed as a 'partitioning
834:. Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering. Vol. 416. Cham: Springer International Publishing. pp. 708–720. 230:
Systems architecture depends heavily on practices and techniques which were developed over thousands of years in many other fields, perhaps the most important being civil architecture.
93:
The fundamental organization of a system, embodied in its components, their relationships to each other and to the environment, and the principles governing its design and evolution.
234:
Prior to the advent of digital computers, the electronics and other engineering disciplines used the term "system" as it is still commonly used today. However, with the arrival of
620: 148:
governing those relationships. The architectural components and set of relationships between these components that an architecture description may consist of hardware,
419: 409: 601: 242:
as a separate discipline, it was often necessary to distinguish among engineered hardware artifacts, software artifacts, and the combined artifacts. A
404: 955:
Markusheska, Nastasija; Srinivasan, Venkatachalam; Walther, Jan-Niclas; Gindorf, Alex; Biedermann, Jörn; Meller, Frank; Nagel, Björn (2022-07-01).
260:
Consequently, within these engineering disciplines, a system generally refers to a programmable hardware machine and its included program. And a
934: 892: 847: 802: 759: 539: 62:. An architecture description is a formal description and representation of a system, organized in a way that supports reasoning about the 505: 132:
The structure of components, their interrelationships, and the principles and guidelines governing their design and evolution over time.
380: 78: 414: 1003: 617: 1036: 1061: 307: 1051: 1056: 668: 156: 360:
Several types of systems architectures (underlain by the same fundamental principles) have been identified as follows:
311: 187: 495:." Proceedings of the 8th international workshop on software specification and design. IEEE Computer Society, 1996. 314:
of the user's requirements. Ideally, a mapping also exists from every least element to every requirement and test.
180: 597: 126:
A formal description of a system, or a detailed plan of the system at component level to guide its implementation.
877:
Fundamentals of Enterprise Architecture Management: Foundations for Steering the Enterprise-Wide Digital System
203: 172: 374: 303: 434: 429: 399: 369: 364: 198:
because a sequence of steps is prescribed to produce or to change the architecture of a system within a
105: 101: 478:
Hannu Jaakkoррмшлинla and Bernhard Thalheim. (2011) "Architecture-driven modelling methodologies." In:
266: 526:, Space Technology Library, vol. 41, Cham: Springer International Publishing, pp. 187–197, 439: 424: 280: 459: 986: 853: 827: 808: 765: 97: 723: 524:
Introduction to Satellite Ground Segment Systems Engineering: Principles and Operational Aspects
30: 978: 930: 888: 879:, The Enterprise Engineering Series, Cham: Springer International Publishing, pp. 23–60, 843: 798: 755: 727: 708: 535: 444: 270: 239: 235: 199: 171:. (In the specific case of computer systems, this latter, special, interface is known as the 190:(SAE) - the method and discipline for effectively implementing the architecture of a system: 1031: 968: 922: 880: 835: 790: 747: 696: 527: 449: 261: 251: 243: 168: 152:, documentation, facilities, manual procedures, or roles played by organizations or people. 43: 784: 741: 492: 167:, and on the interface(s) between the system and its external environment, especially the 957:"Implementing a system architecture model for automated aircraft cabin assembly processes" 672: 624: 605: 506:
A classification and comparison framework for software architecture description languages.
120: 454: 329: 129:
The composite of the design architectures for products and their life-cycle processes.
1045: 990: 857: 812: 769: 96:
A representation of a system, including a mapping of functionality onto hardware and
480:
Proceedings of the 2011 conference on Information Modelling and Knowledge Bases XXII
218: 89:
Various organizations can define systems architecture in different ways, including:
1026: 287:, which partitions all of the system's present and foreseeable requirements into a 17: 839: 531: 926: 884: 292: 141: 973: 519: 914: 872: 794: 751: 637: 299: 221:
as to the most effective way to design the system within a set of constraints.
160: 55: 982: 956: 919:
SAP Enterprise Architecture: A Blueprint for Executing Digital Transformation
665: 567: 295: 288: 284: 214: 63: 47: 145: 913:
Musukutwa, Sheunopa Chalmers (2022), Musukutwa, Sheunopa Chalmers (ed.),
247: 149: 67: 51: 144:
consisting of a system, the relationships among those elements, and the
298:
with nothing left over. That is, it is a partitioning scheme which is
164: 74: 59: 684: 649: 29: 661: 564: 560: 508:" Software Engineering, IEEE Transactions on 26.1 (2000): 70-93. 269:
deals (more or less) exclusively with the hardware device; the
324: 155:
A system architecture primarily concentrates on the internal
140:
System architecture conveys the informational content of the
1021: 695:
The Method Framework for Engineering System Architectures,
379:
Collaborative systems architectures (such as the Internet,
34:
Example of a high-level systems architecture for a computer
274:
especially the user, and performing its intended function.
828:"Software Architecture Evolution and Technology Research" 826:
Zeng, Ruiqi; Niu, Yiru; Zhao, Yue; Peng, Haiyang (2022).
584: 341: 638:
The National Center for Education Statistics glossary
580: 710:The fundamental principles of Systems Architecture 482:. Anneli Heimbürger et al. (eds). IOS Press. p. 98 504:Nenad Medvidovic and Richard N. Taylor (2000). " 493:A survey of architecture description languages 183:; formerly called the man-machine interface.) 119:A description of the design and contents of a 108:, and human interaction with these components. 8: 420:Enterprise information security architecture 410:Department of Defense Architecture Framework 186:One can contrast a system architecture with 73:A system architecture can consist of system 871:Ziemann, Jörg (2022), Ziemann, Jörg (ed.), 598:The Human Engineering Home Page's Glossary 1032:INCOSE Systems Architecture Working Group 1005:Choosing A Strategic Systems Architecture 972: 743:From Algorithms to Hardware Architectures 518:Nejad, Bobby (2023), Nejad, Bobby (ed.), 921:, Berkeley, CA: Apress, pp. 51–92, 405:Architectural pattern (computer science) 915:"Developing an Enterprise Architecture" 873:"Enterprise Architecture in a Nutshell" 618:OPEN Process Framework (OPF) Repository 471: 832:Advanced Hybrid Information Processing 7: 830:. In Liu, Shuai; Ma, Xuefei (eds.). 1027:What is Systems Architecture ? 386:Manufacturing systems architectures 381:intelligent transportation systems 79:architecture description languages 25: 1022:Principles of system architecture 722:The Art of Systems Architecture, 415:Enterprise architecture framework 786:Software Architecture by Example 383:, and joint air defense systems) 328: 1037:Journal of Systems Architecture 188:system architecture engineering 585:Software Engineering Institute 389:Strategic systems architecture 1: 179:human computer interface, or 840:10.1007/978-3-030-94551-0_54 532:10.1007/978-3-031-15900-8_13 27:Conceptual model of a system 927:10.1007/978-1-4842-8575-6_3 885:10.1007/978-3-030-96734-5_2 520:"The Physical Architecture" 1078: 974:10.1007/s13272-022-00582-6 581:Carnegie Mellon University 491:Paul C. Clements (1996) " 961:CEAS Aeronautical Journal 795:10.1007/978-1-4842-7990-8 752:10.1007/978-3-031-08693-9 173:computer human interface 783:Michaels, Paul (2022). 375:Enterprise architecture 238:and the development of 664:1220-1998 as found at 246:hardware artifact, or 35: 1062:Software architecture 740:Abbas, Karim (2023). 435:Software architecture 430:Requirements analysis 400:Arcadia (engineering) 370:Software architecture 365:Hardware architecture 106:hardware architecture 102:software architecture 33: 1052:Systems architecture 440:Software engineering 425:Process architecture 240:software engineering 1057:Systems engineering 460:Systems engineering 159:among the system's 100:, a mapping of the 98:software components 40:system architecture 18:System architecture 671:2006-05-17 at the 623:2006-03-05 at the 604:2015-02-13 at the 340:. You can help by 217:is used to inform 213:because a body of 36: 936:978-1-4842-8575-6 894:978-3-030-96734-5 849:978-3-030-94551-0 804:978-1-4842-7989-2 761:978-3-031-08692-2 728:Eberhardt Rechtin 713:, by Boris Golden 541:978-3-031-15900-8 445:Systems architect 358: 357: 271:software engineer 267:hardware engineer 250:, that lacks its 248:computing machine 236:digital computers 46:that defines the 16:(Redirected from 1069: 1009: 1001: 995: 994: 976: 952: 946: 945: 944: 943: 910: 904: 903: 902: 901: 868: 862: 861: 823: 817: 816: 780: 774: 773: 737: 731: 720: 714: 706: 700: 697:Donald Firesmith 693: 687: 682: 676: 658: 652: 647: 641: 634: 628: 614: 608: 594: 588: 577: 571: 557: 551: 550: 549: 548: 515: 509: 502: 496: 489: 483: 476: 450:Systems analysis 353: 350: 332: 325: 312:validation tests 262:systems engineer 252:computer program 44:conceptual model 21: 1077: 1076: 1072: 1071: 1070: 1068: 1067: 1066: 1042: 1041: 1018: 1013: 1012: 1002: 998: 954: 953: 949: 941: 939: 937: 912: 911: 907: 899: 897: 895: 870: 869: 865: 850: 825: 824: 820: 805: 782: 781: 777: 762: 739: 738: 734: 721: 717: 707: 703: 694: 690: 683: 679: 673:Wayback Machine 659: 655: 648: 644: 635: 631: 625:Wayback Machine 615: 611: 606:Wayback Machine 595: 591: 578: 574: 558: 554: 546: 544: 542: 517: 516: 512: 503: 499: 490: 486: 477: 473: 468: 396: 354: 348: 345: 338:needs expansion 323: 291:set of cleanly 228: 121:computer system 87: 70:of the system. 28: 23: 22: 15: 12: 11: 5: 1075: 1073: 1065: 1064: 1059: 1054: 1044: 1043: 1040: 1039: 1034: 1029: 1024: 1017: 1016:External links 1014: 1011: 1010: 996: 967:(3): 689–703. 947: 935: 905: 893: 863: 848: 818: 803: 775: 760: 732: 715: 701: 688: 677: 666:their glossary 653: 642: 629: 609: 589: 572: 552: 540: 510: 497: 484: 470: 469: 467: 464: 463: 462: 457: 455:Systems design 452: 447: 442: 437: 432: 427: 422: 417: 412: 407: 402: 395: 392: 391: 390: 387: 384: 377: 372: 367: 356: 355: 335: 333: 322: 319: 318: 317: 315: 277: 275: 258: 256: 227: 224: 223: 222: 207: 134: 133: 130: 127: 124: 117: 113: 109: 94: 86: 83: 26: 24: 14: 13: 10: 9: 6: 4: 3: 2: 1074: 1063: 1060: 1058: 1055: 1053: 1050: 1049: 1047: 1038: 1035: 1033: 1030: 1028: 1025: 1023: 1020: 1019: 1015: 1008:, by Brad Day 1007: 1006: 1000: 997: 992: 988: 984: 980: 975: 970: 966: 962: 958: 951: 948: 938: 932: 928: 924: 920: 916: 909: 906: 896: 890: 886: 882: 878: 874: 867: 864: 859: 855: 851: 845: 841: 837: 833: 829: 822: 819: 814: 810: 806: 800: 796: 792: 788: 787: 779: 776: 771: 767: 763: 757: 753: 749: 745: 744: 736: 733: 730:, 2nd ed 2002 729: 725: 719: 716: 712: 711: 705: 702: 698: 692: 689: 686: 681: 678: 674: 670: 667: 663: 657: 654: 651: 646: 643: 639: 633: 630: 626: 622: 619: 613: 610: 607: 603: 599: 593: 590: 586: 582: 576: 573: 569: 566: 562: 556: 553: 543: 537: 533: 529: 525: 521: 514: 511: 507: 501: 498: 494: 488: 485: 481: 475: 472: 465: 461: 458: 456: 453: 451: 448: 446: 443: 441: 438: 436: 433: 431: 428: 426: 423: 421: 418: 416: 413: 411: 408: 406: 403: 401: 398: 397: 393: 388: 385: 382: 378: 376: 373: 371: 368: 366: 363: 362: 361: 352: 343: 339: 336:This section 334: 331: 327: 326: 320: 316: 313: 309: 305: 301: 297: 294: 290: 286: 282: 278: 276: 272: 268: 263: 259: 257: 253: 249: 245: 241: 237: 233: 232: 231: 225: 220: 219:practitioners 216: 212: 208: 205: 201: 197: 193: 192: 191: 189: 184: 182: 178: 174: 170: 166: 162: 158: 153: 151: 147: 143: 138: 131: 128: 125: 122: 118: 114: 110: 107: 103: 99: 95: 92: 91: 90: 84: 82: 80: 76: 71: 69: 65: 61: 57: 53: 49: 45: 41: 32: 19: 1004: 999: 964: 960: 950: 940:, retrieved 918: 908: 898:, retrieved 876: 866: 831: 821: 785: 778: 742: 735: 718: 709: 704: 699:et al., 2008 691: 680: 656: 645: 632: 612: 592: 575: 555: 545:, retrieved 523: 513: 500: 487: 479: 474: 359: 346: 342:adding to it 337: 244:programmable 229: 210: 195: 185: 176: 154: 139: 135: 88: 72: 39: 37: 204:constraints 54:, and more 1046:Categories 942:2022-12-07 900:2022-12-07 724:Mark Maier 547:2022-12-07 466:References 308:exhaustive 296:subsystems 211:discipline 165:subsystems 161:components 157:interfaces 75:components 64:structures 991:248972956 983:1869-5590 858:246051702 813:248408249 770:251371033 579:From the 568:1471-2000 349:July 2012 304:inclusive 300:exclusive 285:algorithm 215:knowledge 209:SAE is a 194:SAE is a 116:behavior. 112:baseline. 104:onto the 68:behaviors 48:structure 669:Archived 621:Archived 602:Archived 394:See also 289:workable 150:software 142:elements 85:Overview 81:(ADLs). 52:behavior 293:bounded 226:History 42:is the 989:  981:  933:  891:  856:  846:  811:  801:  768:  758:  616:From 538:  306:, and 283:,' or 281:scheme 196:method 60:system 987:S2CID 854:S2CID 809:S2CID 766:S2CID 685:TOGAF 660:From 650:TOGAF 636:From 596:From 559:From 321:Types 146:rules 58:of a 56:views 979:ISSN 931:ISBN 889:ISBN 844:ISBN 799:ISBN 756:ISBN 726:and 662:IEEE 565:IEEE 561:ANSI 536:ISBN 169:user 66:and 969:doi 923:doi 881:doi 836:doi 791:doi 748:doi 583:'s 528:doi 344:. 202:of 200:set 181:HCI 177:AKA 163:or 1048:: 985:. 977:. 965:13 963:. 959:. 929:, 917:, 887:, 875:, 852:. 842:. 807:. 797:. 789:. 764:. 754:. 746:. 600:. 534:, 522:, 302:, 175:, 50:, 38:A 993:. 971:: 925:: 883:: 860:. 838:: 815:. 793:: 772:. 750:: 675:. 640:. 627:. 587:. 570:. 563:/ 530:: 351:) 347:( 206:. 20:)

Index

System architecture

conceptual model
structure
behavior
views
system
structures
behaviors
components
architecture description languages
software components
software architecture
hardware architecture
computer system
elements
rules
software
interfaces
components
subsystems
user
computer human interface
HCI
system architecture engineering
set
constraints
knowledge
practitioners
digital computers

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.