Log in

Relevant bibliographies by topics / Software architecture / Journal articles

To see the other types of publications on this topic, follow the link: Software architecture.

Journal articles on the topic 'Software architecture'

Author: Grafiati

Published: 4 June 2021

Last updated: 25 July 2025

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the top 50 journal articles for your research on the topic 'Software architecture.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

1

WOODSIDE, C. M. "SOFTWARE RESOURCE ARCHITECTURE." International Journal of Software Engineering and Knowledge Engineering 11, no. 04 (2001): 407–29. http://dx.doi.org/10.1142/s0218194001000608.

Full text

Abstract:

Performance is determined by a system's resources and its workload. Some of the resources are software resources which are an aspect of the software architecture; some of them are even created by the software behaviour. This paper describes software resources and resource architecture, and shows how resource architecture can be determined from software architecture and behaviour. The resource architecture is distinct from views of software architecture which describe software components, but it is related to the so-called "execution view" of architecture. The paper considers how resource archi

APA, Harvard, Vancouver, ISO, and other styles

2

Abuseta, Yousef. "Towards a Generic Software Architecture for IoT Systems." International Journal of Software Engineering & Applications 15, no. 6 (2024): 01–16. https://doi.org/10.5121/ijsea.2024.15601.

Full text

Abstract:

The complexity of IoT, owing to the inherent distributed and dynamic nature of such systems, brings more challenges to the software development process. A vast number of devices with different communication protocols and data formats is involved and needs to be connected and exchange data with each other in a seamless manner. Traditional software architectures fall short of addressing the requirements of IoT systems and, therefore, a new approach to software architecture is required. This paper presents an attempt to lay out the foundation for a quality attribute driven software architecture f

APA, Harvard, Vancouver, ISO, and other styles

3

Medvidovic, Nenad, Eric M. Dashofy, and Richard N. Taylor. "The Role of Middleware in Architecture-Based Software Development." International Journal of Software Engineering and Knowledge Engineering 13, no. 04 (2003): 367–93. http://dx.doi.org/10.1142/s0218194003001330.

Full text

Abstract:

Software architectures promote development focused on modular functional building blocks (components), their interconnections (configurations), and their interactions (connectors). Since architecture-level components often contain complex functionality, it is reasonable to expect that their interactions will be complex as well. Middleware technologies such as CORBA, COM, and RMI provide a set of predefined services for enabling component composition and interaction. However, the potential role of such services in the implementations of software architectures is not well understood. In practice

APA, Harvard, Vancouver, ISO, and other styles

4

Siedashev, Oleh. "DETERMINATION OF SOFTWARE ARCHITECTURE (SOA) AND MICROSERVICE ARCHITECTURE (MSA) USAGE CRITERIA." Computer Science and Cybersecurity, no. 2 (December 30, 2024): 41–50. https://doi.org/10.26565/2519-2310-2024-2-04.

Full text

Abstract:

In modern software development, one of the key tasks is to choose the appropriate architecture for the system in the early stages of its design. This article examines two popular software architecture approaches: service-oriented architecture (SOA) and microservice architecture (MSA). Based on the analysis of architectural features, advantages and disadvantages of these approaches, the criteria that influence the choice of an architectural model depending on the specifics of the system are investigated. Microservice architecture, due to its independence and the possibility of rapid scaling, is

APA, Harvard, Vancouver, ISO, and other styles

5

Ulichev, Oleksandr, Oleksandr Dorenskyi, and Victor Kulahin. "Innovative Solutions and Benefits of Microservice Architecture for Software Products." Central Ukrainian Scientific Bulletin. Technical Sciences 1, no. 10(41) (2024): 16–29. https://doi.org/10.32515/2664-262x.2024.10(41).16-29.

Full text

Abstract:

The rapid advancement of technology and increasing market competition compel businesses to adapt swiftly by implementing new features and services to meet user demands. Traditional monolithic software architectures often hinder this agility due to challenges in scalability and maintenance. This article aims to analyze microservice architecture to solve these challenges, exploring its historical development, current trends, practical implementation aspects, and comparison with alternative architectural styles such as modulith architecture. The study examines the limitations of monolithic archit

APA, Harvard, Vancouver, ISO, and other styles

6

McGregor, John D. "Software Architecture." Journal of Object Technology 3, no. 5 (2004): 65. http://dx.doi.org/10.5381/jot.2004.3.5.c7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Anderson, Bruce, Mary Shaw, Larry Best, and Kent Beck. "Software architecture." ACM SIGPLAN Notices 28, no. 10 (1993): 356–59. http://dx.doi.org/10.1145/167962.165922.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Ponnala Gangadhar Adepu, Ramesh. "Modeling Software Architecture with UML." International Journal of Science and Research (IJSR) 1, no. 3 (2012): 21–26. http://dx.doi.org/10.21275/ijsr12120316.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Roško, Zdravko. "Business Applications Architecture Model Based on Software Product Line Approach." Research Papers Faculty of Materials Science and Technology Slovak University of Technology 21, Special-Issue (2013): 90–97. http://dx.doi.org/10.2478/rput-2013-0015.

Full text

Abstract:

Abstract Software product line architecture is one of the most important artifacts defined at the early stage of a product line development process. Since the rest of the products are developed based on the initial product line architecture, it is of high importance to ensure the architecture stability by enabling the software’s evolution possibilities. Industrial evidence shows that companies spend more resources on maintaining and evolving their architecture and products than on the initial development of them. Hence, there is a need for flexible software architecture that stays stable as th

APA, Harvard, Vancouver, ISO, and other styles

10

Sarma, U. V. R., Neelakantam Pavani Pavani, and P. Premchand. "Building Software Architecture using Architectural Design Patterns." International Journal of Science and Engineering Applications 2, no. 4 (2013): 71–77. http://dx.doi.org/10.7753/ijsea0204.1004.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Donins, Uldis, and Janis Osis. "Reconciling software requirements and architectures within MDA." Scientific Journal of Riga Technical University. Computer Sciences 38, no. 38 (2009): 84–95. http://dx.doi.org/10.2478/v10143-009-0007-9.

Full text

Abstract:

Reconciling software requirements and architectures within MDAIn the software development world little guidance and few methods are available for reconciling software requirements and architecture which satisfies those requirements. In fact none of these methods use formal basis for the reconciling process. The main goal of this paper is to define an approach by which it is possible to reconcile software requirements and architectures within model driven architecture. Model driven architecture considers system from three viewpoints. Each viewpoint has its own model by which the viewpoint is mo

APA, Harvard, Vancouver, ISO, and other styles

12

Rocha, Fábio Gomes, Sanjay Misra, and Michel S. Soares. "Guidelines for Future Agile Methodologies and Architecture Reconciliation for Software-Intensive Systems." Electronics 12, no. 7 (2023): 1582. http://dx.doi.org/10.3390/electronics12071582.

Full text

Abstract:

Background: Several methodologies have been proposed since the first days of software development, from what is now named traditional/heavy methodologies, and later their counterpart, the agile methodologies. The whole idea behind agile methodologies is to produce software at a faster pace than what was considered with plan-based methodologies, which had a greater focus on documenting all tasks and activities before starting the proper software development. Problem: One issue here is that strict agilists are often against fully documenting the software architecture in the first phases of a sof

APA, Harvard, Vancouver, ISO, and other styles

13

Xu, Hongzhen, Wenlin Song, and Zhiqiang Liu. "A Specification and Detection Approach for Parallel Evolution Conflicts of Software Architectures." International Journal of Software Engineering and Knowledge Engineering 27, no. 03 (2017): 373–98. http://dx.doi.org/10.1142/s0218194017500139.

Full text

Abstract:

Software evolution has been a necessary part of the software development, while software architecture evolution is an important issue of software evolution. Software architecture evolution is generally realized through some evolution operations such as adding components or connectors, removing components or connectors. However, when some evolution operations are applied to the same software architecture in parallel, they sometimes make conflicting modifications, which will hinder the correctness of software architecture evolution. Although different approaches have been proposed to describe an

APA, Harvard, Vancouver, ISO, and other styles

14

Sahlabadi, Mahdi, Ravie Chandren Muniyandi, Zarina Shukur, and Faizan Qamar. "Lightweight Software Architecture Evaluation for Industry: A Comprehensive Review." Sensors 22, no. 3 (2022): 1252. http://dx.doi.org/10.3390/s22031252.

Full text

Abstract:

Processes for evaluating software architecture (SA) help to investigate problems and potential risks in SA. It is derived from many studies that proposed a plethora of systematic SA evaluation methods, while industrial practitioners currently refrain from applying them since they are heavyweight. Nowadays, heterogeneous software architectures are organized based on the new infrastructure. Hardware and associated software allow different systems, such as embedded, sensor-based, modern AI, and cloud-based systems, to cooperate efficiently. It brings more complexities to SA evaluation. Alternativ

APA, Harvard, Vancouver, ISO, and other styles

15

Sarma, A. D. N. "A Generic Functional Architecture for Operational BI System." International Journal of Business Intelligence Research 9, no. 1 (2018): 64–77. http://dx.doi.org/10.4018/ijbir.2018010105.

Full text

Abstract:

In recent years, Operational Business Intelligence has emerged as an important trend in the Business Intelligence (BI) market. Majority of BI application architectures are bespoke in nature which have several architectural limitations like tightly coupled, static, historic, subjective, no performance measurement of business processes, limited user access, limited analytical processing, querying and reporting features. In this article, a generic functional architecture for Operational BI systems based on software architecture principles is presented. All functional modules of the system are der

APA, Harvard, Vancouver, ISO, and other styles

16

Ruiz Nepomuceno, Aldair, Eduardo López Domínguez, Saúl Domínguez Isidro, María Auxilio Medina Nieto, Amilcar Meneses-Viveros, and Jorge de la Calleja. "Software Architectures for Adaptive Mobile Learning Systems: A Systematic Literature Review." Applied Sciences 14, no. 11 (2024): 4540. http://dx.doi.org/10.3390/app14114540.

Full text

Abstract:

Adaptive Mobile Learning Systems (AMLSs) are technological tools that incorporate adaptive learning to generate an individual teaching–learning process for each student. Despite the proliferation of AMLS, their development is often hindered by a lack of standardization and the poor quality of existing software architectures in terms of requirements correctness and coverage. This paper presents a systematic literature review (SLR) of software architectures oriented to developing AMLS reported in the state of the art. For this SLR, we searched the ACM Digital Library, IEEE Xplore, Science Direct

APA, Harvard, Vancouver, ISO, and other styles

17

ZHANG, Li. "Software Architecture Evaluation." Journal of Software 19, no. 6 (2008): 1328–39. http://dx.doi.org/10.3724/sp.j.1001.2008.01328.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Anderson, Bruce, Mary Shaw, Larry Best, and Kent Beck. "Software architecture (panel)." ACM SIGPLAN OOPS Messenger 5, no. 2 (1994): 63–66. http://dx.doi.org/10.1145/260304.260321.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Garlan, David. "Software architecture (panel)." ACM SIGSOFT Software Engineering Notes 20, no. 4 (1995): 5. http://dx.doi.org/10.1145/222132.222134.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Barber, K. S., and J. Holt. "Software architecture correctness." IEEE Software 18, no. 6 (2001): 64–65. http://dx.doi.org/10.1109/52.965805.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Del Ra, William. "Software systems architecture." ACM SIGSOFT Software Engineering Notes 37, no. 2 (2012): 36. http://dx.doi.org/10.1145/2108144.2108171.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Miyachi, Christine. "Agile software architecture." ACM SIGSOFT Software Engineering Notes 36, no. 2 (2011): 1–3. http://dx.doi.org/10.1145/1943371.1943388.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Leigh, Andrew. "Software Architecture Insights." ITNOW 66, no. 3 (2024): 60–61. http://dx.doi.org/10.1093/itnow/bwae102.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

Innocente, V., L. Silvestris, and D. Stickland. "CMS software architecture." Computer Physics Communications 140, no. 1-2 (2001): 31–44. http://dx.doi.org/10.1016/s0010-4655(01)00253-3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Davis, Margaret J., and Roger B. Williams. "Software architecture characterization." ACM SIGSOFT Software Engineering Notes 22, no. 3 (1997): 30–38. http://dx.doi.org/10.1145/258368.258380.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Yashyna, O., and O. Kravchuk. "RESEARCH OF MICROSERVICE ARCHITECTURE, REST ARCHITECTURAL STYLE AND THEIR MODERN IMPLEMENTATION ON JAVA." Herald of Khmelnytskyi National University. Technical sciences 289, no. 5 (2020): 106–14. https://doi.org/10.31891/2307-5732-2020-289-5-106-114.

Full text

Abstract:

Software architecture is a set of important decisions about the organization of the software system. The success and speed of the project development, the complexity of its support and understanding of the program structure depends on the correct choice of software architecture. For this reason, developers often use new architectural solutions to build software, trying to find the best solutions to a problem. The common practice of program development was the development on the principle of monolithic architecture, which envisages the project as a single program, which is responsible for all n

APA, Harvard, Vancouver, ISO, and other styles

27

BROWN, ALAN W., and JOHN A. McDERMID. "THE ART AND SCIENCE OF SOFTWARE ARCHITECTURE." International Journal of Cooperative Information Systems 16, no. 03n04 (2007): 439–66. http://dx.doi.org/10.1142/s0218843007001718.

Full text

Abstract:

Experience in all aspects of software engineering has confirmed the pivotal role of focusing on architectural concerns in the development of complex software-intensive systems. Consequently, the past 20 years has seen significant investments in the theory and practice of software architecture. However, architectural deficiencies are frequently cited as a key factor in the shortcomings and failures that lead to unpredictable delivery of complex operational systems. Here, we consider the art and science of software architecture: we explore the current state of software architecture, identify key

APA, Harvard, Vancouver, ISO, and other styles

28

Goel, Amit. "The Philosophy of Software Architecture." International Journal of Web Portals 2, no. 4 (2010): 28–39. http://dx.doi.org/10.4018/jwp.2010100103.

Full text

Abstract:

Computer Software Intensive systems have become ingrained in our daily life. Apart from obvious scientific and business applications, various embedded devices are empowered with computer software. Such a diverse application of Computer Software has led to inherent complexity in building such systems. As civilizations moved forward, the concept of architectural thinking and practice was introduced to grapple with the complexity and other challenges of creating buildings, skyscrapers, townships, and cities. The Practice of Software Architecture is an attempt to understand and handle similar chal

APA, Harvard, Vancouver, ISO, and other styles

29

Ananthavijayan, Ramesh, Prabhakar Karthikeyan Shanmugam, Sanjeevikumar Padmanaban, Jens Holm-Nielsen, Frede Blaabjerg, and Viliam Fedak. "Software Architectures for Smart Grid System—A Bibliographical Survey." Energies 12, no. 6 (2019): 1183. http://dx.doi.org/10.3390/en12061183.

Full text

Abstract:

Smart grid software interconnects multiple Engineering disciplines (power systems, communication, software and hardware technology, instrumentation, big data, etc.). The software architecture is an evolving concept in smart grid systems, in which system architecture development is a challenging process. The architecture has to realize the complex legacy power grid systems and cope with current Information and Communication Technologies (ICT). The distributed generation in a smart grid environment expects the software architecture to be distributed and to enable local control. Smart grid archit

APA, Harvard, Vancouver, ISO, and other styles

30

Papapostolu, A., and D. Birov. "Architecture Evolution through Dynamic Reconfiguration in jADL." Information Technologies and Control 15, no. 1 (2017): 23–32. http://dx.doi.org/10.1515/itc-2017-0019.

Full text

Abstract:

Abstract In software architecture the dynamic structure of a software system can be described in terms of components and connectors and expressed through the use of Architectural Description Languages (ADLs). We present jADL, a new ADL, designed for the creation and validation of dynamic and mobile architectures. It, also, aims to help towards the process of “unifying” the definition and implementation of an architecture in a way that the final result is consistent with the architecture in terms of both functional requirements and quality attributes. In this paper, we examine into details the

APA, Harvard, Vancouver, ISO, and other styles

31

Kyaruzi, John J., and Jan van Katwijk. "CONCERNS ON ARCHITECTURE-CENTERED SOFTWARE DEVELOPMENT: A SURVEY." Journal of Integrated Design and Process Science: Transactions of the SDPS, Official Journal of the Society for Design and Process Science 4, no. 3 (2000): 13–35. http://dx.doi.org/10.3233/jid-2000-4302.

Full text

Abstract:

We propose a framework for practical realization of architecture-centered software development that consolidates two major view-points in the domain of software architecture: (1) an architecture-based systems development view which requires development processes and products to respect good architecting principles and (2) a system-based architecture technology development view which requires software architecture methods and technologies to respect evolution, reuse and componentization as, inherently, basic properties of software systems. We survey and discuss the use of software architecture

APA, Harvard, Vancouver, ISO, and other styles

32

Bahrami, Mehdi, and Mohammad Bahrami. "A Review of Software Architecture for Collaborative Software’s." Advanced Materials Research 433-440 (January 2012): 2372–76. http://dx.doi.org/10.4028/www.scientific.net/amr.433-440.2372.

Full text

Abstract:

Software architecture has emerged as an important sub-discipline of software engineering; particularly in the realm of large system development. Collaboration software applications are inherently cooperative, requiring many software applications to coordinate their efforts to produce a software system application. Integral to this effort is developing shared understanding surrounding multiple artifacts, each artifact embodying its own model, over the entire development process. This focus on model collaboration embedded within a larger process is what distinguishes collaboration research in so

APA, Harvard, Vancouver, ISO, and other styles

33

Tsybulnyk, Serhii, Viktoriia Nakoryk, and Diana Pivtorak. "DESIGN OF THE ARCHITECTURE OF THE AUTOMATED SYSTEM FOR CREATING THE ACCOMPANYING DOCUMENTATION OF THE EDUCATIONAL PROCESS." Bulletin of Kyiv Polytechnic Institute. Series Instrument Making, no. 67(1) (June 30, 2024): 77–83. http://dx.doi.org/10.20535/1970.67(1).2024.306737.

Full text

Abstract:

Background. The architecture of the automated system is the main source of quality of software and software-hardware systems. It determines how quickly and efficiently a developer is able to analyze, understand, test, extend, and maintain an automated system. Changes in the system architecture have a high cost due to its complexity and the possibility of destruction during expansion. At present, most of the knowledge and information about the design decisions on which the architecture is based are implicitly embedded in it, which leads to problems during the development process, in particular,

APA, Harvard, Vancouver, ISO, and other styles

34

Hexmoor, Henry, and David Kortenkamp. "Issues on building software for hardware agents." Knowledge Engineering Review 10, no. 3 (1995): 301–4. http://dx.doi.org/10.1017/s0269888900007499.

Full text

Abstract:

James Albus states that “an architecture is a description of how a system is constructed from basic components and how those components fit together to form the whole” (Albus, 1995). A software architecture for physical agents reflects the organising principles that its designers have learned from many prior experiences in building such agents. Architectures that have been proposed for physical agents have differed greatly—from subsumption (Brooks, 1986) to Soar (Laird et al., 1987). However, a surprising consensus about architectures is beginning to emerge within the small community of resear

APA, Harvard, Vancouver, ISO, and other styles

35

Gite, Kundan. "Monolithic vs. Microservices Architecture: A Comparative Study of Software Development Paradigms." International Scientific Journal of Engineering and Management 04, no. 06 (2025): 1–9. https://doi.org/10.55041/isjem04468.

Full text

Abstract:

Abstract: Software architecture is the backbone of any application, shaping its scalability, maintainability, and overall performance. Among the most widely adopted architectural patterns are Monolithic and Microservices architectures, each offering distinct benefits and trade-offs. A monolithic approach keeps all components tightly integrated into a single system, simplifying development and deployment but limiting flexibility as applications grow. In contrast, microservices break down applications into smaller, independently deployable services, improving scalability and fault isolation whil

APA, Harvard, Vancouver, ISO, and other styles

36

Bilokon, O. S. "Software Architecture of Navigation Systems for Control Modules of Robotics." Èlektronnoe modelirovanie 45, no. 5 (2023): 103–12. http://dx.doi.org/10.15407/emodel.45.05.103.

Full text

Abstract:

The peculiarities of the software architecture of navigation systems of robotic control modules are considered. Particular attention is focused on the reproduced classifications of the characteristics of architectural solutions. The three-functional architecture of the Shakey robot, the architecture of R. Brooks (Subsumption), and Boltzmann's intellectual model were studied in detail. Three-level architectural system LAAS, multi-level architecture CLARAty, intelligent real-time control system CIRCA are also considered.

APA, Harvard, Vancouver, ISO, and other styles

37

Nivethitha, V., and P. M Abhinaya. "Combinatorics based problem specific software architecture formulation using multi-objective genetic algorithm." International Journal of Engineering & Technology 7, no. 1.7 (2018): 79. http://dx.doi.org/10.14419/ijet.v7i1.7.9579.

Full text

Abstract:

In Software Development Process, the design of complex systems is an important phase where software architects have to deal with abstract artefacts, procedures and ideas to discover the most suitable underlying architecture. Due to uncontrolled modifications of the design and frequent change of requirements, many of the working systems do not have a proper architecture. Most of the approaches recover the architectural blocks at the end of the development process which are not appropriate to the system considered. In order to structure these systems software components compositions and interact

APA, Harvard, Vancouver, ISO, and other styles

38

LUNG, CHUNG-HORNG, and KALAI KALAICHELVAN. "AN APPROACH TO QUANTITATIVE SOFTWARE ARCHITECTURE SENSITIVITY ANALYSIS." International Journal of Software Engineering and Knowledge Engineering 10, no. 01 (2000): 97–114. http://dx.doi.org/10.1142/s0218194000000079.

Full text

Abstract:

Software architectures are often claimed to be robust. However, there is no explicit and concrete definition of software architecture robustness. This paper gives a definition of software architecture robustness and presents a set of architecture metrics that were applied to real-time telecommunications software for the evaluation of robustness. The purpose of this study is to provide a structured method to support software architecture evaluations and downstream software implementations. The study also expands the software architecture research to quantitative and measurable evaluations as op

APA, Harvard, Vancouver, ISO, and other styles

39

Schmidt, Heinz, Iman Poernomo, and Ralf Reussner. "TRUST-BY-CONTRACT: MODELLING, ANALYSING AND PREDICTING BEHAVIOUR OF SOFTWARE ARCHITECTURES." Journal of Integrated Design and Process Science: Transactions of the SDPS, Official Journal of the Society for Design and Process Science 5, no. 3 (2001): 25–51. http://dx.doi.org/10.3233/jid-2001-5304.

Full text

Abstract:

Architecture description languages (ADLs) are used to specify high-level, compositional views of a software application. ADL research focuses on software composed of prefabricated parts, so-called software components. ADLs usually come equipped with rigorous state-transition style semantics, facilitating verification and analysis of specifications. Consequently, ADLs are well suited to configuring distributed and event-based systems. However, additional expressive power is required for the description of enterprise software architectures in particular, those built upon newer middleware, such a

APA, Harvard, Vancouver, ISO, and other styles

40

Dong, Xia, Shou Quan Wang, Xin Zhang, and Xiao Jia Ji. "Software Radar Hardware Architecture Based on General Computer." Advanced Materials Research 846-847 (November 2013): 207–10. http://dx.doi.org/10.4028/www.scientific.net/amr.846-847.207.

Full text

Abstract:

For software radar, different functions are realized by software running on standard hardware platform, which brings to great predominance over traditional radar. In this paper, realizable structure of software radar was analyzed, and hardware platform based on computer was studied. Two hardware architectures, one-computer architecture as well as computer cluster architecture were raised based on computer. The one-computer architecture is available to radars that cubage is restricted, while computer cluster architecture is applied in huge radar with complex computation.

APA, Harvard, Vancouver, ISO, and other styles

41

Pinto, Mónica, and Lidia Fuentes. "Modeling Quality Attributes with Aspect-Oriented Architectural Templates." JUCS - Journal of Universal Computer Science 17, no. (5) (2011): 639–69. https://doi.org/10.3217/jucs-017-05-0639.

Full text

Abstract:

The quality attributes of a software system are, to a large extent, determined by the decisions taken early in the development process. Best practices in software engineering recommend the identification of important quality attributes during the requirements elicitation process, and the specification of software architectures to satisfy these requirements. Over the years the software engineering community has studied the relationship between quality attributes and the use of particular architectural styles and patterns. In this paper we study the relationship between quality attributes and As

APA, Harvard, Vancouver, ISO, and other styles

42

Niepostyn, Stanislaw Jerzy, and Wiktor Bohdan Daszczuk. "Entropy as a Measure of Consistency in Software Architecture." Entropy 25, no. 2 (2023): 328. http://dx.doi.org/10.3390/e25020328.

Full text

Abstract:

In building software architectures, the relations between elements in different diagrams are often overlooked. The first stage of building IT systems is the use of ontology terminology, not software terminology, in the requirements engineering process. Then, when constructing software architecture, IT architects more or less consciously however introduce elements that represent the same classifier on different diagrams with similar names. These connections are called consistency rules and are usually not attached in any way in a modeling tool, and only a significant number of them in the model

APA, Harvard, Vancouver, ISO, and other styles

43

Abd Elkareem, Noha, Mazen Selim, and Ahmed Shalaby. "Software-Defined Metaverse (SDM) Architecture." Journal of Metaverse 4, no. 2 (2024): 146–56. http://dx.doi.org/10.57019/jmv.1541821.

Full text

Abstract:

The metaverse, a vast virtual shared space that integrates enhanced physical reality with persistent virtual environments, has the potential to revolutionize digital interaction by providing deeply immersive and interactive experiences. Leveraging cutting-edge technologies such as virtual reality (VR), augmented reality (AR), blockchain, artificial intelligence (AI), and cloud computing, the metaverse aims to harmonize the physical and digital worlds. However, existing metaverse architectures face significant challenges related to scalability, security, and efficiency. This paper introduces a

APA, Harvard, Vancouver, ISO, and other styles

44

GRUNDY, JOHN, and JOHN HOSKING. "SOFTARCH: TOOL SUPPORT FOR INTEGRATED SOFTWARE ARCHITECTURE DEVELOPMENT." International Journal of Software Engineering and Knowledge Engineering 13, no. 02 (2003): 125–51. http://dx.doi.org/10.1142/s0218194003001238.

Full text

Abstract:

A good software architecture design is crucial in successfully realising an object-oriented analysis (OOA) specification with an object-oriented design (OOD) model that meets the specification's functional and non-functional requirements. Most CASE tools and software architecture design notations do not adequately support software architecture modelling and analysis, integration with OOA and OOD methods and tools, and high-level, dynamic architectural visualisations of running systems. We describe SoftArch, an environment that provides flexible software architecture modelling using a concept o

APA, Harvard, Vancouver, ISO, and other styles

45

Schmidt, Frederick, Stephen MacDonell, and Andy M. Connor. "Multi-Objective Reconstruction of Software Architecture." International Journal of Software Engineering and Knowledge Engineering 28, no. 06 (2018): 869–92. http://dx.doi.org/10.1142/s0218194018500262.

Full text

Abstract:

Design erosion is a persistent problem within the software engineering discipline. Software designs tend to deteriorate over time and there is a need for tools and techniques that support software architects when dealing with legacy systems. This paper presents an evaluation of a search-based software engineering (SBSE) approach intended to recover high-level architecture designs of software systems by structuring low-level artifacts into high-level architecture artifact configurations. In particular, this paper describes the performance evaluation of a number of metaheuristic search algorithm

APA, Harvard, Vancouver, ISO, and other styles

46

Yang, Shuo, Xinjun Mao, Sen Yang, and Zhe Liu. "Towards a hybrid software architecture and multi-agent approach for autonomous robot software." International Journal of Advanced Robotic Systems 14, no. 4 (2017): 172988141771608. http://dx.doi.org/10.1177/1729881417716088.

Full text

Abstract:

To support robust plan execution of autonomous robots in dynamic environments, autonomous robot software should include adaptive and reactive capabilities to cope with the dynamics and uncertainties of the evolving states of real-world environments. However, conventional software architectures such as sense-model-plan-act and behaviour-based paradigms are inadequate for meeting the requirements. A lack of sensing during acting in the sense-model-plan-act paradigm makes the software slow to react to run-time contingencies, whereas the behaviour-based architectures typically fall short in planni

APA, Harvard, Vancouver, ISO, and other styles

47

Li, Qiuying, and Fuping Zeng. "Enhancing Software Architecture Adaptability: A Comprehensive Evaluation Method." Symmetry 16, no. 7 (2024): 894. http://dx.doi.org/10.3390/sym16070894.

Full text

Abstract:

The field of self-adaptive software is becoming increasingly crucial because software has to adapt its behavior at runtime to keep up with dynamic and constantly evolving environments. The ability of software to modify and adjust itself is known as adaptability, which has been acknowledged as an important quality attribute. As software architecture development represents the initial stage of the design process, architectural design has emerged as a critical development activity. The degree to which the architecture can adapt to changes will be the key factor in determining the adaptability of

APA, Harvard, Vancouver, ISO, and other styles

48

Tsai, W. T., Raymond A. Paul, Chun Fan, and Xiao Wei. "DYNAMIC ARCHITECTURES FOR SOA-BASED APPLICATIONS." Journal of Integrated Design and Process Science: Transactions of the SDPS, Official Journal of the Society for Design and Process Science 11, no. 4 (2007): 65–105. http://dx.doi.org/10.3233/jid-2007-11404.

Full text

Abstract:

The architecture of SOA-based applications is different from traditional software architecture where the architecture is mainly static. The architecture of an SOA-based application is dynamic, i.e., the application may be composed at runtime using existing services. Thus SOA has provided a new direction for software architecture study, where the architecture is determined at runtime and the architecture can be dynamically changed at runtime to meet the new software requirements. This paper proposes an architecture classification scheme for SOA-based applications. Using this classification, sev

APA, Harvard, Vancouver, ISO, and other styles

49

Xiang, Liang, Yang Hua, Jia Si Wang, Zhong Wei Chen, and Song Yang Du. "Software Information Management-Oriented Software Architecture Analysis." Applied Mechanics and Materials 263-266 (December 2012): 1745–49. http://dx.doi.org/10.4028/www.scientific.net/amm.263-266.1745.

Full text

Abstract:

This paper is to study the common architecture of the software development and compare the software system architecture-selection criteria. Meanwhile, this paper offers appropriate software architecture solution according to the features of data information management of the software testing organization.

APA, Harvard, Vancouver, ISO, and other styles

50

Tummers, J., A. Kassahun, and B. Tekinerdogan. "Reference architecture design for farm management information systems: a multi-case study approach." Precision Agriculture 22, no. 1 (2020): 22–50. http://dx.doi.org/10.1007/s11119-020-09728-0.

Full text

Abstract:

AbstractOne of the key elements of precision agriculture is the farm management information system (FMIS) that is responsible for data management, analytics and subsequent decision support. Various FMISs have been developed to support the management of farm businesses. A key artefact in the development of FMISs is the software architecture that defines the gross level structure of the system. The software architecture is important for understanding the system, analysing the design decisions and guiding the further development of the system based on the architecture. To assist in the design of

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!