Auto saved by Logseq
This commit is contained in:
@@ -0,0 +1,336 @@
|
||||
file-path:: ../assets/Thesis_Proposal_Jose_Alvarez_1664999883485_0.pdf
|
||||
file:: [Thesis_Proposal_Jose_Alvarez_1664999883485_0.pdf](../assets/Thesis_Proposal_Jose_Alvarez_1664999883485_0.pdf)
|
||||
title:: hls__Thesis_Proposal_Jose_Alvarez_1664999883485_0
|
||||
|
||||
- cycle
|
||||
ls-type:: annotation
|
||||
hl-page:: 1
|
||||
id:: 633de438-5a79-4281-8e47-42f9d5b4b026
|
||||
- Iovino
|
||||
ls-type:: annotation
|
||||
hl-page:: 1
|
||||
id:: 633de43a-7805-4ee8-b552-9af94eda40e1
|
||||
- Mariani
|
||||
ls-type:: annotation
|
||||
hl-page:: 1
|
||||
id:: 633de43b-fe87-425f-80cc-3d514c06f310
|
||||
- Concepcion
|
||||
ls-type:: annotation
|
||||
hl-page:: 1
|
||||
id:: 633de43d-3912-4a6d-8ee1-d18606d20b39
|
||||
- A Reference Architecture (RA) is a generic architecture that provides guidelines and options for making decisions in developing more specific architectures and implementing solutions.
|
||||
ls-type:: annotation
|
||||
hl-page:: 2
|
||||
id:: 633de449-7ffd-440b-b117-b913e7cbc44d
|
||||
- Recommender Systems for Reference Architectures
|
||||
ls-type:: annotation
|
||||
hl-page:: 1
|
||||
id:: 633de45b-eca0-49c9-89d3-d9e26d078d51
|
||||
- Assistive modeling tools are software modules usually integrated with ML techniques to help the modeler compose models smartly
|
||||
ls-type:: annotation
|
||||
hl-page:: 2
|
||||
id:: 633de7fe-3dcf-431a-a497-98969f7d2099
|
||||
- multiple tasks might be subject to recommendations, and numerous tools have been presented as modeling assistants
|
||||
ls-type:: annotation
|
||||
hl-page:: 2
|
||||
id:: 633de80e-930a-4c44-a5ea-a38277fd3cc1
|
||||
- RS may assist in choosing suitable third-party programming libraries or recommend APIs, suggest refactoring of source code
|
||||
ls-type:: annotation
|
||||
hl-page:: 2
|
||||
id:: 633de82f-46df-4737-b8d3-2d8fe495cd7e
|
||||
- complete portions of a model or meta
|
||||
ls-type:: annotation
|
||||
hl-page:: 2
|
||||
id:: 633de84c-2804-4398-a71d-df220026c52b
|
||||
- We aim to build a project that delivers an innovative way of modeling RAs
|
||||
ls-type:: annotation
|
||||
hl-page:: 2
|
||||
id:: 633de8a3-e7c4-4a2e-a844-b2525e7832cf
|
||||
- develop an assistive tool that automates the architectural design proces
|
||||
ls-type:: annotation
|
||||
hl-page:: 2
|
||||
id:: 633de8ad-ef63-4826-afa3-5d5a24773388
|
||||
- ompliance checking
|
||||
ls-type:: annotation
|
||||
hl-page:: 2
|
||||
id:: 633de8c0-4496-4d33-b777-a62336d60482
|
||||
- Reference Architectures
|
||||
ls-type:: annotation
|
||||
hl-page:: 3
|
||||
id:: 633de8df-c888-4249-a74c-fd95ccbf7c24
|
||||
- Reference Architec
|
||||
ls-type:: annotation
|
||||
hl-page:: 3
|
||||
id:: 633de8e4-46ee-45a8-9acc-7c1261cb4977
|
||||
- reference models,
|
||||
ls-type:: annotation
|
||||
hl-page:: 4
|
||||
id:: 633de96f-4f0e-4249-b9ca-4ea154400854
|
||||
- eference architectures
|
||||
ls-type:: annotation
|
||||
hl-page:: 4
|
||||
id:: 633de972-be1d-4c81-b24e-6bdcad68e06e
|
||||
- concrete architectures
|
||||
ls-type:: annotation
|
||||
hl-page:: 4
|
||||
id:: 633de97a-01cc-4738-aee3-83795fc91f39
|
||||
- The main difference between them is that a reference architecture is an abstraction, a template that provides the guidelines and solutions for a problem
|
||||
ls-type:: annotation
|
||||
hl-page:: 5
|
||||
id:: 633df069-3dd8-4990-864d-d1379910471b
|
||||
- few attempts to automate the compliance checking of an architectural model w.r.t its RA
|
||||
ls-type:: annotation
|
||||
hl-page:: 5
|
||||
id:: 633df147-5c54-464c-9eec-d3708c04c2c4
|
||||
- when the architect needs to define his software architecture, it would be nice to suggest the minimal architecture structure to comply with the chosen RA.
|
||||
ls-type:: annotation
|
||||
hl-page:: 5
|
||||
id:: 633df160-52ba-4e3b-87b0-de325895edc1
|
||||
- hen the architect has already specified a partial architecture, and while selecting a RA, the result is not compliant, suggesting the modeling actions to reach minimal compliance would be effectiv
|
||||
ls-type:: annotation
|
||||
hl-page:: 5
|
||||
id:: 633df1a7-24c2-4676-83a2-8ef81620353c
|
||||
- when the software architects work with internal guidelines and regulations, they follow implicit RAs specifications
|
||||
ls-type:: annotation
|
||||
hl-page:: 5
|
||||
id:: 633df1b0-9671-499f-b4bc-192c1238fe68
|
||||
- In this thesis, we will address the problem of developing assistive tools for software architectural modeling that will consider the RA as a blueprint with the validation, compliance checking, and automation that will support the instantiation process
|
||||
ls-type:: annotation
|
||||
hl-page:: 6
|
||||
id:: 633df1f2-53ed-4105-abed-ad47cc527574
|
||||
- expensive in terms of effort, time-consuming and error-prone
|
||||
ls-type:: annotation
|
||||
hl-page:: 6
|
||||
id:: 633df223-a3e3-4fbd-84b6-a7e729b070ff
|
||||
- lack of datasets that relate a set of SA with its representative RA.
|
||||
ls-type:: annotation
|
||||
hl-page:: 6
|
||||
id:: 633df242-8b3d-4c2f-994b-68f7bef61b57
|
||||
- we plan to prepare a test suite to check the effectiveness and quality of the recommendation
|
||||
ls-type:: annotation
|
||||
hl-page:: 6
|
||||
id:: 633df5c4-3e3f-448f-877a-cb4320ad9747
|
||||
- Software architecture refers to the fundamental structures of a software system and the discipline of creating those structures and systems
|
||||
ls-type:: annotation
|
||||
hl-page:: 7
|
||||
id:: 633df73e-3485-45cb-bedf-338239a0a0a8
|
||||
- rchitecture of a software system is an abstraction representation analogous to the architecture of a building.
|
||||
ls-type:: annotation
|
||||
hl-page:: 7
|
||||
id:: 633df774-416a-4f73-a0f2-80f3b15e29c7
|
||||
- Reference Architecture is a generic architecture for a class of software systems used as a foundation for the design of concrete architectures from this class
|
||||
ls-type:: annotation
|
||||
hl-page:: 7
|
||||
id:: 633df79c-6dba-4a04-8f87-ed5e7c6e4d66
|
||||
- A reference architecture is used for the design of concrete architectures in multiple contexts, affecting different stakeholders in each context
|
||||
ls-type:: annotation
|
||||
hl-page:: 7
|
||||
id:: 633df83c-90b5-4f25-a7a8-b82ad61e607b
|
||||
- design
|
||||
ls-type:: annotation
|
||||
hl-page:: 7
|
||||
id:: 633df874-f095-444f-a73b-fa98ad781f18
|
||||
- A reference architecture is based on the functionalities and data flows defined in a reference model and applies architectural styles and patterns that help in addressing the main qualities expected from the architecture
|
||||
ls-type:: annotation
|
||||
hl-page:: 8
|
||||
id:: 633ed569-e995-4896-abea-4f39628d130b
|
||||
- usually RAs do not identify the internal mechanisms that drive the information processing among the components, like behavioural diagrams for instance
|
||||
ls-type:: annotation
|
||||
hl-page:: 8
|
||||
id:: 633ed831-b5ac-49c8-ab08-fdc8630ccdb9
|
||||
- serverless backen
|
||||
ls-type:: annotation
|
||||
hl-page:: 8
|
||||
id:: 633ed873-be0c-4cd2-b0d5-b6ddefb0e6f4
|
||||
- Those RA catalogs provided by these leading technology companies are crucial.
|
||||
ls-type:: annotation
|
||||
hl-page:: 8
|
||||
id:: 633ed910-d9a4-4d18-85be-ae74a2d5e706
|
||||
- t standardizes the development process and ensures the scalability of the implemented SA
|
||||
ls-type:: annotation
|
||||
hl-page:: 8
|
||||
id:: 633ed94b-3e4e-4e1d-b666-1d302617c8f6
|
||||
- information filtering system
|
||||
ls-type:: annotation
|
||||
hl-page:: 9
|
||||
id:: 633ed958-3fbc-4306-81d0-ad623f434a29
|
||||
- prioritised list of potentially interesting items
|
||||
ls-type:: annotation
|
||||
hl-page:: 10
|
||||
id:: 633ed960-c429-403d-9579-96893caa50b7
|
||||
- ollecting relevant user informa
|
||||
ls-type:: annotation
|
||||
hl-page:: 10
|
||||
id:: 633ed982-b861-4936-93b6-059c505df3a4
|
||||
- Learning from the collected information to build user profiles.
|
||||
ls-type:: annotation
|
||||
hl-page:: 10
|
||||
id:: 633ed989-2307-44ef-885f-b9afb5dff0e2
|
||||
- Applying a heuristic function or a previously built model to select and rank the items that the user is most likely to prefer.
|
||||
ls-type:: annotation
|
||||
hl-page:: 10
|
||||
id:: 633ed990-b577-46a9-904e-874227e48819
|
||||
- Explicit feedback refers to user preference statements about items they know, typically stored as numeric ratings or unary/binary values (e.g., likes and thumbs up/down). In contrast, implicit feedback is inferred by observing and mining user interactions within the system, such as previous search queries, product purchases, and mouse clicks. Other features that can be used to model users’ preferences include demographic data, personality traits, emotional states, and trust relationships [23].
|
||||
ls-type:: annotation
|
||||
hl-page:: 10
|
||||
id:: 633ed9bc-bbab-4f58-bb01-dc66a3cad84d
|
||||
- 30
|
||||
ls-type:: annotation
|
||||
hl-page:: 12
|
||||
id:: 633eda07-8ce3-41e0-87b5-72a892e280d9
|
||||
- . The authors defined the basic subsystems that characteriz
|
||||
ls-type:: annotation
|
||||
hl-page:: 12
|
||||
id:: 633eda20-1dd6-4253-9996-31ff7bd47495
|
||||
- Bellow
|
||||
ls-type:: annotation
|
||||
hl-page:: 12
|
||||
id:: 633eda39-5001-4044-9a8a-c3a6bcc0ce7c
|
||||
- Several frameworks have been developed to test the compliance between a particular domain-specific and generic reference architecture.
|
||||
ls-type:: annotation
|
||||
hl-page:: 13
|
||||
id:: 633edc46-ccc9-48a7-af72-8f8ff78beae6
|
||||
- ule-based architecture conformance checking approa
|
||||
ls-type:: annotation
|
||||
hl-page:: 13
|
||||
id:: 633edc64-c547-4b1a-bfb7-64ed0c7a0878
|
||||
- WA design before actually implementing it.
|
||||
ls-type:: annotation
|
||||
hl-page:: 14
|
||||
id:: 633edcd9-bc15-4c50-b1a9-1b40a0b574a5
|
||||
- automated compliance checkin
|
||||
ls-type:: annotation
|
||||
hl-page:: 14
|
||||
id:: 633edd00-5a84-450d-9878-7600c35bbb1e
|
||||
- he architect must always know perfectly the RA specification provided by senior architects or technology affiliates to compose the concrete architecture and check the compliance
|
||||
ls-type:: annotation
|
||||
hl-page:: 14
|
||||
id:: 633edd38-5b7c-490e-b770-9d806802076d
|
||||
- n order to reduce the burden of these essential tasks and further automate and support the architectural specification, a modeling assistant can propose modeling actions with the intent of composing not only a valid architectural model but a compliant one w.r.t. the chosen RA.
|
||||
ls-type:: annotation
|
||||
hl-page:: 15
|
||||
id:: 633edd99-6dde-41bf-b886-bebc00f77893
|
||||
- The authors employ a technique that relies on graph kernels to compute similarity values. Such a comparison can be time-consuming in the case of large graphs. Furthermore, some relationships might be missed due to the presented encoding mechanis
|
||||
ls-type:: annotation
|
||||
hl-page:: 16
|
||||
id:: 633ee4fa-9572-411e-ad0a-3cff904ef63d
|
||||
- Modelers can give feedback that can be used to update the model and improve the recommendation
|
||||
ls-type:: annotation
|
||||
hl-page:: 16
|
||||
id:: 633ee518-c325-4c14-86fb-492a67e7ed3a
|
||||
- modeling of software architectures and the use of modeling assistant to support it, ensuring conformance between the specific RA by suggesting modeling actions has to address issues related to
|
||||
ls-type:: annotation
|
||||
hl-page:: 18
|
||||
id:: 633ee5a7-5523-41d6-b28a-bbf864e0ab5b
|
||||
- nefficient support for the instantiation
|
||||
ls-type:: annotation
|
||||
hl-page:: 18
|
||||
id:: 633ee5b0-7ed8-4c3d-bd3c-39f71e577b47
|
||||
- absence of assistive modeling tools
|
||||
ls-type:: annotation
|
||||
hl-page:: 18
|
||||
id:: 633ee5b9-5428-4d80-a837-224a42f1f4fd
|
||||
- formal
|
||||
ls-type:: annotation
|
||||
hl-page:: 18
|
||||
id:: 633ee5e0-488c-4ebb-878e-167080c0bfc9
|
||||
- no
|
||||
ls-type:: annotation
|
||||
hl-page:: 18
|
||||
id:: 633ee5e2-d6b5-4986-8c5d-e76604a31e9d
|
||||
- repository
|
||||
ls-type:: annotation
|
||||
hl-page:: 18
|
||||
id:: 633ee5e4-037c-4317-be59-88a42bf32f4a
|
||||
- Too many ADLs have been developed over the past two decades
|
||||
ls-type:: annotation
|
||||
hl-page:: 18
|
||||
id:: 633ee62b-ca94-444b-919b-7ecf7cbc3fcc
|
||||
- system engineering, software engineering, and enterprise modeling
|
||||
ls-type:: annotation
|
||||
hl-page:: 18
|
||||
id:: 633ee645-a510-4cf4-8674-4b9e5b3ae9c2
|
||||
- or system engineering, ADL describes and represents the system architecture
|
||||
ls-type:: annotation
|
||||
hl-page:: 18
|
||||
id:: 633ee66d-95f0-48cf-92f6-aa83d575e271
|
||||
- For software engineering, ADL describes and represents the software architecture.
|
||||
ls-type:: annotation
|
||||
hl-page:: 18
|
||||
id:: 633ee67d-8aa1-4d31-8060-41a828eb5b24
|
||||
- For enterprise modeling and engineering, ADL describes and refers to the application architecture.
|
||||
ls-type:: annotation
|
||||
hl-page:: 18
|
||||
id:: 633ee683-c3d7-4a01-b9ed-4ece3ba72e75
|
||||
- a RA can be specified at a different level of abstraction with incremental fine-grained details and is left to architects who personally decide the abstraction level and details needed.
|
||||
ls-type:: annotation
|
||||
hl-page:: 19
|
||||
id:: 633ee77e-fa53-4178-8c63-7fb68f981715
|
||||
- ecommender systems that complete and repair models and suggest model transformations based on data sources represented as UML class diagram
|
||||
ls-type:: annotation
|
||||
hl-page:: 19
|
||||
id:: 633eef0e-c343-4d8d-805e-a4a4ed0dff3d
|
||||
- The main goal of our research is to develop a modeling assistant that helps the modeling process of software architectures to conform to its reference architecture
|
||||
ls-type:: annotation
|
||||
hl-page:: 19
|
||||
id:: 633eef2b-f0a1-4796-bc97-36efe446c972
|
||||
- In this case, it is a challenge to obtain repositories where there are already examples of software architectures that seniors have verified correctly. In case we can obtain enough repositories, they will undoubtedly be modeled with different ADLs. Another critical issue would be how to classify these architectural models based on clustering techniques and how to derive the reference architecture that represents those.
|
||||
ls-type:: annotation
|
||||
hl-page:: 19
|
||||
id:: 633eef63-1d3d-47ea-88c5-540ca879340d
|
||||
- different challenges that we have to face in the reference architecture context and the use of recommender systems to supports modellers with suggestion
|
||||
ls-type:: annotation
|
||||
hl-page:: 20
|
||||
id:: 633eefd6-3958-4f7e-8cfe-6181bf97e803
|
||||
- o consensus on how to represent RAs accurately
|
||||
ls-type:: annotation
|
||||
hl-page:: 20
|
||||
id:: 633ef00a-29d0-456c-a43e-a27a3e1424f8
|
||||
- However, as far as we know, there is a lack of repositories that relate RAs to specific SA
|
||||
ls-type:: annotation
|
||||
hl-page:: 20
|
||||
id:: 633ef07a-daba-48c8-b053-4470f63d0146
|
||||
- RQ1: How are reference architectures (RAs) modeled and represented in the literature?
|
||||
ls-type:: annotation
|
||||
hl-page:: 21
|
||||
id:: 633ef0ec-07e2-46c0-84da-3f3f38072dfd
|
||||
- RQ2: How can a correspondence between a set of software architectures (SA) and their general RA be defined?
|
||||
ls-type:: annotation
|
||||
hl-page:: 21
|
||||
id:: 633ef0f4-4d86-4bb1-8c75-f7e76aec4e9c
|
||||
- RQ3: What methodologies, tools and techniques are more suitable for building assistive architectural modeling tools?
|
||||
ls-type:: annotation
|
||||
hl-page:: 21
|
||||
id:: 633ef107-4896-4cd5-b57f-4ac019e1f119
|
||||
- RQ4: How much a developed architectural modeling assistant is effective in supporting the architectural composition?
|
||||
ls-type:: annotation
|
||||
hl-page:: 21
|
||||
id:: 633ef10c-a38b-4d0b-beb9-9e0a466af0cb
|
||||
- RQ5: How much a developed architectural modeling assistant is effective in supporting other architectural modeling task, e.g., architectural switch, refactoring, etc?
|
||||
ls-type:: annotation
|
||||
hl-page:: 21
|
||||
id:: 633ef111-0b6b-4ff9-a806-5689cd06c3b5
|
||||
- Alessio Bucaioni, Amleto Di Salle, Ludovico Iovino, Ivano Malavolta, and Patrizio Pelliccione. Reference architectures modelling and compliance checking. Software and Systems Modeling, pages 1–27, 2022.
|
||||
ls-type:: annotation
|
||||
hl-page:: 27
|
||||
id:: 633ff509-d420-48d0-b71f-55ff2dc6b2a2
|
||||
- RA modeling must be guided by a modeling assistant that provides interactive recommendations to support the instantiation, refinement, evolution, and migration of architectures with visualization and suggestions, continuously considering compliance with the RA
|
||||
ls-type:: annotation
|
||||
hl-page:: 22
|
||||
id:: 633ff52d-849e-4cc1-a962-79691797116e
|
||||
- cloud-based repository of software architectures and reference architectures
|
||||
ls-type:: annotation
|
||||
hl-page:: 22
|
||||
id:: 633ff537-1910-4761-b40c-c14e725a1346
|
||||
- this dataset can derive a hybrid implementation of the RS that could archive better results.
|
||||
ls-type:: annotation
|
||||
hl-page:: 22
|
||||
id:: 633ff53e-0fcd-4958-893c-d068da6e4914
|
||||
- pproaches for mapping and validating a specific model of SA with its respective RA
|
||||
ls-type:: annotation
|
||||
hl-page:: 24
|
||||
id:: 633ff580-3933-4b04-9f7f-eed4829abe4a
|
||||
- a model repository containing all the software architecture models and reference architectures we can use
|
||||
ls-type:: annotation
|
||||
hl-page:: 24
|
||||
id:: 633ff5a3-5955-415c-8cbe-68ae0d3121b1
|
||||
Reference in New Issue
Block a user