The purpose of the architecture of software systems in business organizations is to support those organizations in achieving business goals. In software development organizations the design of an architecture is a collective effort that involves various organizational stakeholders and designers, who identify, interpret, and reason about intents, and communicate, delegate, commit to, and implement intents and decisions. Current architectural design descriptions are by-and-large based on block-and-arrow notations representing "coarse-grained" solution elements of the system. They lack explicit representation for modeling and analyzing the decision-making of stakeholders and architectural designers who hold different organizational responsibilities, and pursue conflicting and/or synergistic business or system goals, while collectively pursuing organizational objectives. This thesis considers the proposition that a distributed intentionality perspective is applicable in the design of software system architectures. During architectural design, relationships between intentional actors define the context in which intentional actors pursue business and system goals and in which they negotiate architectural decision-making. The objective of this research is to investigate what an Intentional Architecture Language (IAL) could be like that utilizes intentional and organizational modeling and analysis concepts to support architectural decision-making efforts in organizational settings. Drawing from prior work on organizational modeling and analysis, this thesis first defines a core IAL, and then explores its use to model and analyze architectural decision-making both reported in the literature and empirically observed at a number of commercial projects in industry. Drawing from these explorations, this thesis proposes a number of extensions to the core IAL, discusses lessons learned, and points to the advantages and limitations in using an IAL to model and analyze architectural decision-making in an organizational setting.

The purpose of the architecture of software systems in business organizations is to support those organizations in achieving business goals. In software development organizations the design of an architecture is a collective effort that involves various organizational stakeholders and designers, who identify, interpret, and reason about intents, and communicate, delegate, commit to, and implement intents and decisions. Current architectural design descriptions are by-and-large based on block-and-arrow notations representing "coarse-grained" solution elements of the system. They lack explicit representation for modeling and analyzing the decision-making of stakeholders and architectural designers who hold different organizational responsibilities, and pursue conflicting and/or synergistic business or system goals, while collectively pursuing organizational objectives. This thesis considers the proposition that a distributed intentionality perspective is applicable in the design of software system architectures. During architectural design, relationships between intentional actors define the context in which intentional actors pursue business and system goals and in which they negotiate architectural decision-making. The objective of this research is to investigate what an Intentional Architecture Language (IAL) could be like that utilizes intentional and organizational modeling and analysis concepts to support architectural decision-making efforts in organizational settings. Drawing from prior work on organizational modeling and analysis, this thesis first defines a core IAL, and then explores its use to model and analyze architectural decision-making both reported in the literature and empirically observed at a number of commercial projects in industry. Drawing from these explorations, this thesis proposes a number of extensions to the core IAL, discusses lessons learned, and points to the advantages and limitations in using an IAL to model and analyze architectural decision-making in an organizational setting.

Modeliavimas aukštame abstrakcijos lygmenyje dažnai naudojamas išankstiniam kompromisų analizavimui vienlusčių sistemų projektavimo procese. Šiose magistro tezėse apžvelgiami du daugiausiai žadantys sisteminio lygmens specifikavimo metodai – vieninga modeliavimo kalba (UML) ir į aktorius orientuotas modeliavimas bei galimybės naudoti šiuos metodus kartu. Elgsenos projektavimo pavyzdžių abstrakcijos naudingos supaprastinant į duomenų perdavimą orientuotų sistemų projektavimą. Tradiciškai šie šablonai aprašomi naudojant UML diagramas, tačiau UML trūksta modelio vykdymą aprašančios sintaksės, dėl ko negalima atlikti UML šablonų modeliavimo kartu su šiuo metu vyraujančia vykdomųjų aprašymų technologija sisteminio lygmens projektavimui. Šiame dokumente pateikiamas metodas, kaip integruoti UML elgsenos šablonus kartu su vykdomaisiais sistemos modeliais. Šis metodas remiasi į aktorius orientuotu modeliavimu ir realizuotas kaip Ptolemy II papildymas. / Modeling at high levels of abstraction is often a need for early trade-off analysis within the Systems-on-Chip design flow. This master thesis overviews two the most promising approaches for system-level specification – Unified Modeling Language (UML) and actor oriented modeling. Also here is presented some possibilities of joint usage of those two approaches. Behavioral patterns are useful abstractions to simplify the design of the communication-centric systems. Such patterns are traditionally described using UML diagrams, but the lack of execution semantics in UML prevents the co-validation of the patterns together with simulation models and executable specifications which are the mainstream in today's system level design flows. In this paper there is described a method to validate UML-based behavioral patterns within executable system models. The method is based on actor orientation and was implemented as an extension of the Ptolemy II framework.