Log in

Relevant bibliographies by topics / Software architecture – Evaluation / Journal articles

Journal articles on the topic 'Software architecture – Evaluation'

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

Author: Grafiati

Published: 4 June 2021

Last updated: 19 February 2022

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 – Evaluation.'

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

Sobhy, Dalia, Rami Bahsoon, Leandro Minku, and Rick Kazman. "Evaluation of Software Architectures under Uncertainty." ACM Transactions on Software Engineering and Methodology 30, no. 4 (July 2021): 1–50. http://dx.doi.org/10.1145/3464305.

Full text

Abstract:

Context: Evaluating software architectures in uncertain environments raises new challenges, which require continuous approaches. We define continuous evaluation as multiple evaluations of the software architecture that begins at the early stages of the development and is periodically and repeatedly performed throughout the lifetime of the software system. Numerous approaches have been developed for continuous evaluation; to handle dynamics and uncertainties at run-time, over the past years, these approaches are still very few, limited, and lack maturity. Objective: This review surveys efforts on architecture evaluation and provides a unified terminology and perspective on the subject. Method: We conducted a systematic literature review to identify and analyse architecture evaluation approaches for uncertainty including continuous and non-continuous, covering work published between 1990–2020. We examined each approach and provided a classification framework for this field. We present an analysis of the results and provide insights regarding open challenges. Major results and conclusions: The survey reveals that most of the existing architecture evaluation approaches typically lack an explicit linkage between design-time and run-time. Additionally, there is a general lack of systematic approaches on how continuous architecture evaluation can be realised or conducted. To remedy this lack, we present a set of necessary requirements for continuous evaluation and describe some examples.

APA, Harvard, Vancouver, ISO, and other styles

2

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

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 (February 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 opposed to qualitative assessments. In addition, this paper presents an empirical case study of applying the metrics. The approach and the metrics data provide insights into software architecture sensitivity analysis on system qualities and trade-off analysis among a set of design alternatives to support product evolution.

APA, Harvard, Vancouver, ISO, and other styles

4

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 (June 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 algorithms applied to architecture reconstruction problems with high dimensionality in terms of objectives. These problems have been selected as representative of the typical challenges faced by software architects dealing with legacy systems and the results inform the ongoing development of a software tool that supports the analysis of trade-offs between different reconstructed architectures.

APA, Harvard, Vancouver, ISO, and other styles

5

Tarvainen, Pentti. "Adaptability Evaluation at Software Architecture Level." Open Software Engineering Journal 2, no. 1 (September 25, 2008): 1–30. http://dx.doi.org/10.2174/1874107x00802010001.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Vishnyakov, Andrei, and Sergey Orlov. "Software Architecture and Detailed Design Evaluation." Procedia Computer Science 43 (2015): 41–52. http://dx.doi.org/10.1016/j.procs.2014.12.007.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Tsai, Jeffrey J. P., Bing Li, and Eric Y. T. Juan. "Parallel evaluation of software architecture specifications." Communications of the ACM 40, no. 1 (January 1997): 83–86. http://dx.doi.org/10.1145/242857.242881.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Shanmugapriya, P., and R. M. Suresh. "Software Architecture Evaluation Methods A Survey." International Journal of Computer Applications 49, no. 16 (July 28, 2012): 19–26. http://dx.doi.org/10.5120/7711-1107.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Wang, Alf Inge, and Bian Wu. "Using Game Development to Teach Software Architecture." International Journal of Computer Games Technology 2011 (2011): 1–12. http://dx.doi.org/10.1155/2011/920873.

Full text

Abstract:

This paper describes a case study of how a game project using the XNA Game Studio from Microsoft was implemented in a software architecture course. In this project, university students have to construct and design a type of software architecture, evaluate the architecture, implement an application based on the architecture, and test this implementation. In previous years, the domain of the software architecture project has been a robot controller for navigating a maze.Robot controllerwas chosen as the domain for the project, as there exist several papers and descriptions on reference architectures for managing mobile robots. This paper describes the changes we had to make to introduce an XNA game development project to the software architecture course, and our experiences from running a software architecture project focusing on game development and XNA. The experiences described in this paper are based on feedback from the course staff, the project reports of the students, and a mandatory course evaluation. The evaluation shows among other things that the majority of the students preferred the game project to the robot project, that XNA was considered to be suitable platform for a software architecture project, that the students found it useful to learn XNA and C#, and that some students were carried away when developing the game in the software architecture project.

APA, Harvard, Vancouver, ISO, and other styles

10

Venkitachalam, Hariharan, Christian Granrath, Balachandar Gopalakrishnan, and Johannes Richenhagen. "Metric-based Evaluation of Powertrain Software Architecture." SAE International Journal of Passenger Cars - Electronic and Electrical Systems 10, no. 1 (March 28, 2017): 194–208. http://dx.doi.org/10.4271/2017-01-1615.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Kalmar, Ralf, Thorsten Keuler, Jens Knodel, and Matthias Naab. "Effective Quality Assurance with Software Architecture Evaluation." ATZelektronik worldwide 6, no. 5 (October 2011): 22–25. http://dx.doi.org/10.1365/s38314-011-0048-z.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Koh, Hyon-Hee, Sang-Hwan Kung, and Jae-Nyon Park. "Evaluation Method to Choose Architectural Approaches in the Software Architecture Design Phase." KIPS Transactions:PartD 12D, no. 4 (August 1, 2005): 617–26. http://dx.doi.org/10.3745/kipstd.2005.12d.4.617.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Nugroho, Herry Prasetyo, Muhammad Irfan, and Amrul Faruq. "Software Defined Networks: a Comparative Study and Quality of Services Evaluation." Scientific Journal of Informatics 6, no. 2 (December 1, 2019): 181–92. http://dx.doi.org/10.15294/sji.v6i2.20585.

Full text

Abstract:

Software-Defined Network (SDN) as architecture network that separates the control and forwarding functions, so that network operators and administrators can configure the networks in a simple and centrally between thousands of devices. This study is designed and evaluate the Quality of Services (QoS) performances between the two networks employed SDN-based architecture and without SDN-based. MinNet as a software emulator used as a data plane in the network Software Define Network. In this study, comparison of the value of the QoS on the network based on Software Defined Network and traditional network during the test run from the source node is investigated. Network testing by using traffic loads. Traffic loads are used starting from 20Mbps-100Mbps. The result is verified that the QoS analysis of the Software-Defined Network architecture performed better than conventional network architectures. The value of the latency delay on the Software Define Network range between 0,019-0,084ms, and with 0% packet loss when addressed the network traffics of 10-100Mbps.

APA, Harvard, Vancouver, ISO, and other styles

14

Athar, Ali, Rao Muzamal Liaqat, and Farooque Azam. "A Comparative Analysis of Software Architecture Evaluation Methods." Journal of Software 11, no. 9 (September 2016): 934–42. http://dx.doi.org/10.17706/jsw.11.9.934-942.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Anouncia, Dr S. Margret, Merin Cherian, Anubhuti Parija, Dulcy R. Sylvia., and D. Jayaprasanna. "A Framework for Software Architecture Visualization and Evaluation." International Journal of Computer Applications 1, no. 8 (February 25, 2010): 65–72. http://dx.doi.org/10.5120/180-315.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

majidi, Fatemeh, and Ali Harounabadi. "Performance Evaluation using Blackboard Technique in Software Architecture." International Journal of Computer Applications Technology and Research 4, no. 2 (February 20, 2015): 142–48. http://dx.doi.org/10.7753/ijcatr0402.1011.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Liu, Xia. "Review of Software Architecture Analysis and Evaluation Methods." Journal of Computer Research and Development 42, no. 7 (2005): 1247. http://dx.doi.org/10.1360/crad20050724.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Kumar, B. Sathis. "EVALUATION OF CAPTURING ARCHITECTURALLY SIGNIFICANT REQUIREMENTS." Asian Journal of Pharmaceutical and Clinical Research 10, no. 13 (April 1, 2017): 122. http://dx.doi.org/10.22159/ajpcr.2017.v10s1.19589.

Full text

Abstract:

Every software development organization strives for customer satisfaction. It is universally accepted that the success of software development lies in the clear understanding of the client requirements. During requirement elicitation and analysis stage, the system analyst identifies the functional and non-functional requirements from the customer. Security, usability, reliability, performance, scalability and supportability are the significant quality attributes of a software system. These quality attributes are also referred as non-functional requirements. Only a few functional and quality attributes requirement help to identify and shape the software architecture. A software system’s architecture is the set of prime design decisions made about the system. If the requirement influences the architectural design decision then, it is referred as Architecturally Significant Requirement (ASR). Identifying and specifying all the possible ASR are important tasks in the requirement elicitation and analysis stage.In this research, general problems that are faced while capturing and specifying ASR in requirement elicitation and analysis is studied. Among the different requirement elicitation techniques, use case diagram has been identified and enhanced to solve the problem of capturing and specifying ASR during the requirement elicitation and analysis phase

APA, Harvard, Vancouver, ISO, and other styles

19

Magableh, Basel, and Stephen Barrett. "Productivity Evaluation of Self-Adaptive Software Model Driven Architecture." International Journal of Information Technology and Web Engineering 6, no. 4 (October 2011): 1–19. http://dx.doi.org/10.4018/jitwe.2011100101.

Full text

Abstract:

Anticipating context changes using a model-based approach requires a formal procedure for analysing and modelling context-dependent functionality and stable description of the architecture which supports dynamic decision-making and architecture evolution. This article demonstrates the capabilities of the context-oriented component-based application-model-driven architecture (COCA-MDA) to support the development of self-adaptive applications; the authors describe a state-of-the-art case study and evaluate the development effort involved in adopting the COCA-MDA in constructing the application. An intensive analysis of the application requirements simplified the process of modelling the application’s behavioural model; therefore, instead of modelling several variation models, the developers modelled an extra-functionality model. COCA-MDA reduces the development effort because it maintains a clear separation of concerns and employs a decomposition mechanism to produce a context-oriented component model which decouples the applications’ core functionality from the context-dependent functionality. Estimating the MDA approach’s productivity can help the software developers select the best MDA-based methodology from the available solutions. Thus, counting the source line of code is not adequate for evaluating the development effort of the MDA-based methodology. Quantifying the maintenance adjustment factor of the new, adapted, and reused code is a better estimate of the development effort of the MDA approaches.

APA, Harvard, Vancouver, ISO, and other styles

20

Del Rosso, Christian. "Continuous evolution through software architecture evaluation: a case study." Journal of Software Maintenance and Evolution: Research and Practice 18, no. 5 (2006): 351–83. http://dx.doi.org/10.1002/smr.337.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Gallagher, K., A. Hatch, and M. Munro. "Software Architecture Visualization: An Evaluation Framework and Its Application." IEEE Transactions on Software Engineering 34, no. 2 (March 2008): 260–70. http://dx.doi.org/10.1109/tse.2007.70757.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Abroshan, Vahid, Ali Harounabadi, and Seyed Javad Mirabedini. "Evaluation of software architecture using fuzzy colored Petri nets." Management Science Letters 3, no. 2 (February 1, 2013): 665–82. http://dx.doi.org/10.5267/j.msl.2012.12.001.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Dehkordi, Zohreh Shiriyan, Ali Harounabadi, and Saeed Parsa. "Evaluation of software architecture using fuzzy color Petri net." Management Science Letters 3, no. 2 (February 1, 2013): 555–62. http://dx.doi.org/10.5267/j.msl.2012.12.016.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

Mao, Song, and Tapas Kanungo. "Software architecture of PSET: a page segmentation evaluation toolkit." International Journal on Document Analysis and Recognition 4, no. 3 (March 1, 2002): 205–17. http://dx.doi.org/10.1007/s100320200070.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Ghayyur, Shahbaz Ahmed Khan, Daud Awan, and Malik Sikander Hayat Khiyal. "A Case of Engineering Quality for Mobile Healthcare Applications Using Augmented Personal Software Process Improvement." Mobile Information Systems 2016 (2016): 1–14. http://dx.doi.org/10.1155/2016/3091280.

Full text

Abstract:

Mobile healthcare systems are currently considered as key research areas in the domain of software engineering. The adoption of modern technologies, for mobile healthcare systems, is a quick option for industry professionals. Software architecture is a key feature that contributes towards a software product, solution, or services. Software architecture helps in better communication, documentation of design decisions, risks identification, basis for reusability, scalability, scheduling, and reduced maintenance cost and lastly it helps to avoid software failures. Hence, in order to solve the abovementioned issues in mobile healthcare, the software architecture is integrated with personal software process. Personal software process has been applied successfully but it is unable to address the issues related to architectural design and evaluation capabilities. Hence, a new technique architecture augmented personal process is presented in order to enhance the quality of the mobile healthcare systems through the use of architectural design with integration of personal software process. The proposed process was validated by case studies. It was found that the proposed process helped in reducing the overall costs and effort. Moreover, an improved architectural design helped in development of high quality mobile healthcare system.

APA, Harvard, Vancouver, ISO, and other styles

26

Burn, G. L. "Implementing the evaluation transformer model of reduction on parallel machines." Journal of Functional Programming 1, no. 3 (July 1991): 329–66. http://dx.doi.org/10.1017/s0956796800000137.

Full text

Abstract:

AbstractThe evaluation transformer model of reduction generalizes lazy evaluation in two ways: it can start the evaluation of expressions before their first use, and it can evaluate expressions further than weak head normal form. Moreover, the amount of evaluation required of an argument to a function may depend on the amount of evaluation required of the function application. It is a suitable candidate model for implementing lazy functional languages on parallel machines.In this paper we explore the implementation of lazy functional languages on parallel machines, both shared and distributed memory architectures, using the evaluation transformer model of reduction. We will see that the same code can be produced for both styles of architecture, and the definition of the instruction set is virtually the same for each style. The essential difference is that a distributed memory architecture has one extra node type for non-local pointers, and instructions which involve the value of such nodes need their definitions extended to cover this new type of node.To make our presentation accessible, we base our description on a variant of the well-known G-machine, an abstract machine for executing lazy functional programs.

APA, Harvard, Vancouver, ISO, and other styles

27

Belyavtsev, Ivan, and Sergey Starkov. "Reactivity margin evaluation software for WWR-c reactor." Nuclear Energy and Technology 4, no. 3 (December 7, 2018): 197–201. http://dx.doi.org/10.3897/nucet.4.31862.

Full text

Abstract:

The WWR-c reactor reactivity margin can be calculated using a precision reactor model. The precision model based on the Monte Carlo method (Kolesov et al. 2011) is not well suited for operational calculations. The article describes the work on creating a software package for preliminary evaluations of the WWR-c reactor reactivity margin. The research has confirmed the possibility of using an artificial neural network to approximate the reactivity margin based on the reactor core condition. Computational experiments were conducted on training the artificial neural network using the precision model data and real reactor measured data. According to the results of the computational experiments, the maximum relative approximation error ∆k/k for fuel burnup was 3.13 and 3.56%, respectively. The mean computation time was 100 ms. The computational experiments showed it possible to construct the artificial neural network architecture. This architecture became the basis for building a software package for evaluating the WWR-c reactor reactivity margin – REST API based web-application – which has a convenient user interface for entering the core configuration. It is also possible to replenish the training sample with new measurements and train the artificial neuron network once again. The reactivity margin evaluation software is ready to be tested by the WWR-c reactor personnel and to be used as a component of the automated reactor refueling system. With minor modifications, the software package can be used for reactors of other types.

APA, Harvard, Vancouver, ISO, and other styles

28

Ali Babar, Muhammad. "A framework for groupware-supported software architecture evaluation process in global software development." Journal of Software: Evolution and Process 24, no. 2 (June 8, 2010): 207–29. http://dx.doi.org/10.1002/smr.478.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Cordova, Rodrygo T., Paulo R. L. Gondim, Jaime Lloret, and Jose M. Jimenez. "Experimental Evaluation of a SDN-DMM Architecture." Network Protocols and Algorithms 10, no. 2 (June 28, 2018): 52. http://dx.doi.org/10.5296/npa.v10i2.13193.

Full text

Abstract:

Mobility management has become a great challenge due to the exponential growth in the number of devices that can connect to home or visited networks, and the need for providing seamless mobility in future generation networks. SDN-DMM (Software Defined Network Architecture for Distributed Mobility Management) architecture has been proposed [11], allowing to separate control and data planes, for the distributed mobility management through bidirectional IP flows. This article reports on aspects related to the implementation of SDN-DMM, conducted with metrics as packet loss, throughput and handover latency, considered in a comparison involving traditional routing and SDN-DMM. The results show the SDN approach not only provides the intrinsic benefits of SDN in comparison with traditional architectures, but also deals with the distributed mode of mobility management in heterogeneous access networks in a simplified and efficient way.

APA, Harvard, Vancouver, ISO, and other styles

30

Hudaib, Amjad, Fawaz Fawaz Al-Zaghoul, Maha Saadeh, and Huda Saadeh. "ADTEM-Architecture Design Testability Evaluation Model to Assess Software Architecture Based on Testability Metrics." Journal of Software Engineering and Applications 08, no. 04 (2015): 201–10. http://dx.doi.org/10.4236/jsea.2015.84021.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Kim, Jungho, Sungwon Kang, Jongsun Ahn, and Seonah Lee. "EMSA: Extensibility Metric for Software Architecture." International Journal of Software Engineering and Knowledge Engineering 28, no. 03 (March 2018): 371–405. http://dx.doi.org/10.1142/s0218194018500134.

Full text

Abstract:

Software extensibility, the capability of adding new functions to a software system, is established based on software architecture. Therefore, developers need to evaluate the capability when designing software architecture. To support the evaluation, researchers have proposed metrics based on quality models or scenarios. However, those metrics are vague or subjective, depending on specific systems and evaluators. We propose the extensibility metric for software architecture (EMSA), which represents the degree of extensibility of a software system based on its architecture. To reduce the subjectivity of the metric, we first identify a typical task of adding new functions to a software system. Second, we define the metrics based on the characteristics of software architecture and its changes and finally combine them into a single metric. The originality of EMSA comes from defining metrics based on software architecture and extensibility tasks and integrating them into one. Furthermore, we made an effort to translate the degree into effort estimation expressed as person-hours. To evaluate EMSA, we conducted two types of user studies, obtaining measurements in both a laboratory and a real-world project. The results show that the EMSA estimation is reasonably accurate [6.6% MMRE and 100% PRED(25%)], even in a real-world project (93.2% accuracy and 8.5% standard deviation).

APA, Harvard, Vancouver, ISO, and other styles

32

Fuggetta, Alfonso. "Open source software––an evaluation." Journal of Systems and Software 66, no. 1 (April 2003): 77–90. http://dx.doi.org/10.1016/s0164-1212(02)00065-1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Peng Ye, Youcong Ni, Linlin Zhang, Kai Zhao, and Ming Hu. "Adaptability Evaluation of Aspect-Oriented Software Architecture Using Quantitative Metrics." International Journal of Advancements in Computing Technology 5, no. 4 (February 28, 2013): 216–23. http://dx.doi.org/10.4156/ijact.vol5.issue4.27.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Kim, Jin-Sik, and In-Oh Jeon. "Maintainability Testing Evaluation Method for Service Oriented Architecture based Software." Journal of the Korea Contents Association 9, no. 3 (March 28, 2009): 81–90. http://dx.doi.org/10.5392/jkca.2009.9.3.081.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

NabiOmidvar, Mohammad, and Reza Vaziri. "Provide a Method for Evaluation of Software Architecture using Ontology." International Journal of Computer Applications 64, no. 16 (February 15, 2013): 1–7. http://dx.doi.org/10.5120/10715-1307.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Upadhyay, Nitin. "SDMF: Systematic Decision-making Framework for Evaluation of Software Architecture." Procedia Computer Science 91 (2016): 599–608. http://dx.doi.org/10.1016/j.procs.2016.07.151.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Eshragh, Faeze, and Mehdi Kargahi. "Analytical architecture-based performability evaluation of real-time software systems." Journal of Systems and Software 86, no. 1 (January 2013): 233–46. http://dx.doi.org/10.1016/j.jss.2012.08.014.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Bass, Len, Robert Nord, William Wood, David Zubrow, and Ipek Ozkaya. "Analysis of architecture evaluation data." Journal of Systems and Software 81, no. 9 (September 2008): 1443–55. http://dx.doi.org/10.1016/j.jss.2008.02.021.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Mitsuyuki, Taiga, Kazuo Hiekata, Takuya Goto, and Bryan Moser. "Evaluation of Project Architecture in Software Development Mixing Waterfall and Agile by Using Process Simulation." Journal of Industrial Integration and Management 02, no. 02 (June 2017): 1750007. http://dx.doi.org/10.1142/s2424862217500075.

Full text

Abstract:

For software development, especially massive software systems, a waterfall process is used traditionally. A waterfall process can be highly effective on the condition that a master plan is fixed and the possibility of changes and uncertain rework is low. However, in software development projects, many kinds of reworks occur corresponding to uncertain requirement changes and program bugs. In addition, with the advent of cloud-based software platforms and continuous development operations, it is possible to develop a software system while operating the system. To respond to this situation, software development projects often adopt an agile process. Agility may allow conditional response to uncertain rework, yet at the same time it may be difficult to control the achievement of known project targets. Recently, many cases of adopting mixed processes including waterfall and agile have been reported in the massive software development projects. In this paper, we argue that the mixed process architecture should be designed, considering the scale of the targeted software project, the culture of organization, the probability of uncertain requirement changes, and so on. This paper proposes a methodology of evaluating the impact of waterfall, agile, and mixed project architectures by using process simulation. A project architectural approach is evaluated with a simulator which includes a software reliability growth model and uncertain rework driven by requirement change and error propagation. The proposed methodology was applied to a development project for a simple shopping website. The results showed that the proposed methodology allows exploration of partial agile adoption depending on the nature of the system development project, including its scale and chances of change. For example, in this paper, if the scale of the project is small, the positive effect of increasing agility by adopting agile processes is low. On the other hand, if the scale of the project is large, the effect of increasing agility by adopting agile process can increase. Furthermore, it became clear that it is important to not apply an agile process blindly, but instead to design a mixed project architecture considering the number of errors and development schedule targets across the project scope.

APA, Harvard, Vancouver, ISO, and other styles

40

Paulson, Eberechukwu Numan, Kamaludin Mohamad Yusof, Muhammad Nadzir Bin Marsono, Umar Suleiman Dauda, and Fapohunda Kofoworola. "Quality of Service Evaluation of Software Defined Internet of Things Network." ELEKTRIKA- Journal of Electrical Engineering 20, no. 1 (April 30, 2021): 65–75. http://dx.doi.org/10.11113/elektrika.v20n1.223.

Full text

Abstract:

With the exponential growth of the Internet of Things (IoT) devices connected to the internet, resource provisioning for such the heterogeneous network is a challenging task for the traditional network architecture. In this context, the Software-Defined Networking (SDN) introduces many opportunities and provides the potential to overcome challenges associated with traditional network architecture. This work presents a Software-Defined IoT (SDIoT) architecture. The main focus of this research is to design a control plane (CP) for the SDIoT. The scope of this work is limited to the introduction of an overlay SDN CP in the traditional IoT network architecture. The proposed architecture focuses on resource provisioning while ensuring the quality of service (QoS) satisfaction for the network. A comparative analysis between the traditional and the SDN network approach was done in terms of Jitter, Latency and Throughput. From the latency, delay and throughput performance results, the SDN-based IoT network improves network efficiency by reducing network overheads generated from frequent communication between the nodes and the controllers. Precisely, the average latency and average jitter percentile improvement from the traditional IoT network to the SDIoT for all the nodes is 574% and 600% respectively. Also, an overall throughput improvement is recorded for the SDIoT when compared to traditional IoT network for all the nodes.

APA, Harvard, Vancouver, ISO, and other styles

41

Chondamrongkul, Nacha, Jing Sun, Ian Warren, and Scott Uk-Jin Lee. "Integrated Formal Tools for Software Architecture Smell Detection." International Journal of Software Engineering and Knowledge Engineering 30, no. 06 (June 2020): 723–63. http://dx.doi.org/10.1142/s0218194020400057.

Full text

Abstract:

The architecture smells are the poor design practices applied to the software architecture design. The smells in software architecture design can be cascaded to cause the issues in the system implementation and significantly affect the maintainability and reliability attribute of the software system. The prevention of architecture smells at the design phase can therefore improve the overall quality of the software system. This paper presents a framework that supports the detection of architecture smells based on the formalization of architecture design. Our modeling specification supports representing both structural and behavioral aspect of software architecture design; it allows the smells to be analyzed and detected with the provided tools. Our framework has been applied to seven architecture smells that violate different design principles. The evaluation has been conducted and the result shows that our detection approach gives accurate results and performs well on different size of models. With the proposed framework, other architecture smells can be defined and detected using the process and tools presented in this paper.

APA, Harvard, Vancouver, ISO, and other styles

42

Dowdeswell, Barry, Roopak Sinha, and Stephen G. MacDonell. "Architecting an Agent-Based Fault Diagnosis Engine for IEC 61499 Industrial Cyber-Physical Systems." Future Internet 13, no. 8 (July 23, 2021): 190. http://dx.doi.org/10.3390/fi13080190.

Full text

Abstract:

IEC 61499 is a reference architecture for constructing Industrial Cyber-Physical Systems (ICPS). However, current function block development environments only provide limited fault-finding capabilities. There is a need for comprehensive diagnostic tools that help engineers identify faults, both during development and after deployment. This article presents the software architecture for an agent-based fault diagnostic engine that equips agents with domain-knowledge of IEC 61499. The engine encourages a Model-Driven Development with Diagnostics methodology where agents work alongside engineers during iterative cycles of design, development, diagnosis and refinement. Attribute-Driven Design (ADD) was used to propose the architecture to capture fault telemetry directly from the ICPS. A Views and Beyond Software Architecture Document presents the architecture. The Architecturally-Significant Requirement (ASRs) were used to design the views while an Architectural Trade-off Analysis Method (ATAM) evaluated critical parts of the architecture. The agents locate faults during both early-stage development and later provide long-term fault management. The architecture introduces dynamic, low-latency software-in-loop Diagnostic Points (DPs) that operate under the control of an agent to capture fault telemetry. Using sound architectural design approaches and documentation methods, coupled with rigorous evaluation and prototyping, the article demonstrates how quality attributes, risks and architectural trade-offs were identified and mitigated early before the construction of the engine commenced.

APA, Harvard, Vancouver, ISO, and other styles

43

Maheshwari, Piyush, and Albert Teoh. "Supporting ATAM with a collaborative Web-based software architecture evaluation tool." Science of Computer Programming 57, no. 1 (July 2005): 109–28. http://dx.doi.org/10.1016/j.scico.2004.10.008.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

Chang, Wen-Kui, and Shuen-Lin Jeng. "Impartial evaluation in software reliability practice." Journal of Systems and Software 76, no. 2 (May 2005): 99–110. http://dx.doi.org/10.1016/j.jss.2004.03.029.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

Czajkowski, Michael F., Cheryl V. Foster, Thomas T. Hewett, Joseph A. Casacio, William C. Regli, and Heike A. Sperber. "A student project in software evaluation." ACM SIGCSE Bulletin 33, no. 3 (September 2001): 13–16. http://dx.doi.org/10.1145/507758.377446.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Curtis, Bill, Sylvia B. Sheppard, Elizabeth Kruesi-Bailey, John Bailey, and Deborah A. Boehm-Davis. "Experimental evaluation of software documentation formats." Journal of Systems and Software 9, no. 2 (February 1989): 167–207. http://dx.doi.org/10.1016/0164-1212(89)90019-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Bousias, K., L. Guang, C. R. Jesshope, and M. Lankamp. "Implementation and evaluation of a microthread architecture." Journal of Systems Architecture 55, no. 3 (March 2009): 149–61. http://dx.doi.org/10.1016/j.sysarc.2008.07.001.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Venkitachalam, Hariharan, Dirk von Wissel, and Johannes Richenhagen. "Metric-based Evaluation of Software Architecture for an Engine Management System." SAE International Journal of Engines 9, no. 3 (April 5, 2016): 1377–85. http://dx.doi.org/10.4271/2016-01-0037.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Meiappane, A., B. Chitra, and Prasanna Venkataesan. "Evaluation of Software Architecture Quality Attribute for an Internet Banking System." International Journal of Computer Applications 62, no. 19 (January 18, 2013): 21–24. http://dx.doi.org/10.5120/10189-5062.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Ebeiyamba, Oluchukwu. "Evaluation of the software architecture of the supply chain management system." African Journal of Business Management 6, no. 51 (December 26, 2012): 12086–94. http://dx.doi.org/10.5897/ajbm10.1264.

Full text

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!