Библиография ГОСТ Р 57100-2016

[1] ANSI/IEEE Std 1471–2000, IEEE Recommended Practice for Architectural Description of Software–Intensive Systems

[2] Boucke, N., Composition and relations of architectural models supported by an architectural description language. Doctoral dissertation, Katholieke Universiteit Leuven, October, 2009

[3] Buschmann F., R. Meunier, H. Rohnert, P. Sommerlad and M. Stal, Pattern–Oriented Software Architecture: ASystem of Patterns, John Wiley & Sons, 1996

[4] Callo–Arias, Т. B., P. America, and P. Avgeriou, Defining execution viewpoints for a large and complex softwareintensive system, Proceedings of WICSA/ECSA2009

[5] Clements P., F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, and J. Stafford, Documenting Software Architectures: Views and Beyond, Boston: Addison–Wesley, 2002

[6] Darnton, G. and S. Giacoletto, Information in the Enterprise, Burlington, MA: Digital Press, 1992

[7] Dijkstra, E. W., Ontheroleofscientificthought. 1974. es.utexas. edu/users/EWD/transcriptions/EWD04xx/ EWD447.html

[8] Eeles P. and P. Cripps, The Process of Software Architecting. Addison Wesley, 2010

[9] Hilliard, R. «Viewpoint modelling», First ICSE Workshop on Describing Software Architecture with UML, May 2001 Hofmeister, C., R. Nord, and D. Soni, Applied Software Architecture, Reading, MA: Addison–Wesley, 1999 ISO/IEC 10746–1, Information technology – Open Distributed Processing – Reference model: Overview ISO/IEC 10746–2, Information technology – Open distributed processing – Reference model: Foundations ISO/IEC 10746–3, Information technology – Open distributed processing – Reference model: Architecture ISO/IEC 12207, Systems and software engineering – Software life cycle processes ISO/IEC 15288, Systems and software engineering – System life cycle processes ISO/IEC 15289, Systems and software engineering – Content of systems and software life cycle process information products (Documentation)

[17] ISO/IEC 15414:2006, Information technology – Open distributed processing – Reference model – Enterprise language

[18] ISO/IEC 15504–1:2004, Information technology – Process assessment – Part 1: Concepts and vocabulary

[19] IS0 15704, Industrial automation systems–Requirements for enterprise–reference architectures and methodologies

[20] ISO/IEC 19501:2005, Information technology – Open Distributed Processing – Unified Modeling Language (UML) Version 1.4.2

[21] ISO/IEC 19793:2008, Information technology – Open Distributed Processing – Use of UML for ODP system specifications

[22] ISO/IEC 25010, Systems and software engineering – Systems and software Quality Requirements and Evaluation (SQuaRE) – System and software quality models

[23] Kruchten, P.B., «The '4+1' View Model of Architecture», IEEE Software, 12(6), 45–50, 1995

[24] Kruchten, P.B., «An Ontology of Architectural Design Decisions in Software–Intensive Systems», Proceedings of the 2nd Groningen Workshop on Software Variability, 54–61, 2004

[25] Luckham, D.C., J.J. Kenney, LM. Augustin, J. Vera, D. Bryan and W. Mann, «Specification and analysis of system architecture using RAPIDE», IEEE Transactions on Software Engineering, 21(4), 336–355, April 1995

[26] Maier, M.W. and E. Rechtin, The art of systems architecting, CRC Press, 2nd edition, 2000

[27] Ministry of Defence Architecture Framework (MODAF), modaf.org.uk/

[28] Muskens, J., R.J. Bril and M.R.V. Chaudron, «Generalizing consistency checking between software views», Proceedings of the 5th Working IEEE/IFIP Conference on SoftwareArchitecture(WICSA'05), 169–180, Washington, DC: IEEE Computer Society, 2005

[29] Nuseibeh, B., J. Kramer and A. Finkelstein, «Аframework for expressing the relationships between multiple views in requirements specification», IEEE Transactions on Software Engineering, 20(10), 760–773, 1994

[30] Obbink, Н., Р.В. Kruchten, W. Kozaczynski, R. Hilliard, A. Ran, H. Postema, D. Lutz, R. Kazman, W. Tracz, and E. Kahane. Report on Software Architecture Review and Assessment (SARA), 2002. http://philippe.kruchten.com/ a rch itectu re/SARAv1 .pdf

[31] OMG formal/2008–11–01, Systems Modeling Language, version 1.1, November 2008

[32] Perry, D.E. and A.L Wolf, «Foundations forthe Study of Software Architecture», ACM SIGSOFT Software Engineering Notes, 17(4), 1992

[33] Proakis, J.G., Digital Communications. New York: McGraw–Hill, 1995

[34] Ran, A. «ARES Conceptual Framework for Software Architecture», M. Jazayeri, A. Ran, and F. van der Linden (eds.), Software Architecture for Product Families Principles and Practice. Boston: Addison–Wesley, 1–29, 2000

[35] Ross, D.T., «Structured Analysis (SA): a language for communicating ideas», IEEE Transactions on Software Engineering, SE–3(1), 16–34, 1977

[36] Rozansky, N. and E. Woods, Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives, Addison–Wesley, 2005

[37] Society of Automotive Engineers, Architecture Analysis & Design Language, http://www^OA.info/

[38] Shaw, M. «Prospects for an engineering discipline of software», IEEE Software, November 1990

[39] Smolander, K., «Four Metaphors of Architecture in Software Organizations: Finding out The Meaning of Architecture in Practice», Proceedings of the 2002 International Symposium on Empirical Software Engineering (ISESE'02)

[40] The Open Group, ArchiMate 1.0 Specification, February 2009, archimate.org/

[41] The Open Group Architecture Framework (TOGAF), opengroup.org/togaf/

[42] Viewpoints Repository for ISO/IEC 42010 iso–architecture.org/viewpoints/

[43] Wright ЯОА website, cs.cmu.edu/~able/wright/

[44] Zachman, J.A., «А Framework for Information Systems Architecture», IBM Systems Journal, 26(3), 1987

[45] Zimmermann O., Koehler J., Leymann F., Polley R., Schuster N., «Managing Architectural Decision Models with Dependency Relations, Integrity Constraints, and Production Rules», The Journal of Systems and Software and Services, Special Issue on Design Decisions and Rationale in Software Architecture Special Edition on Architectural Decisions, Elsevier, 2009

[из Библиография ГОСТ Р 57100-2016]