Log in

Relevant bibliographies by topics / Aspect-oriented software development (AOSD) / Journal articles

To see the other types of publications on this topic, follow the link: Aspect-oriented software development (AOSD).

Journal articles on the topic 'Aspect-oriented software development (AOSD)'

Author: Grafiati

Published: 4 June 2025

Last updated: 1 August 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 'Aspect-oriented software development (AOSD).'

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

ORTIN, FRANCISCO, LUIS VINUESA, and JOSE M. FELIX. "THE DSAW ASPECT-ORIENTED SOFTWARE DEVELOPMENT PLATFORM." International Journal of Software Engineering and Knowledge Engineering 21, no. 07 (2011): 891–929. http://dx.doi.org/10.1142/s0218194011005554.

Full text

Abstract:

Aspect-Oriented Software Development (AOSD) provides systematic means to modularize crosscutting concerns in software development. Common AOSD benefits are a higher level of abstraction, concern reuse, better legibility, and software maintainability improvement. In AOSD, static weaving implementations commonly obtain better runtime performance, whereas dynamic weaving provides runtime application adaptiveness and a valuable aid in software development. Since both approaches provide benefits, we have developed a Dynamic and Static Aspect Weaving (DSAW) platform that supports both kinds of weave

APA, Harvard, Vancouver, ISO, and other styles

2

Vidal Silva, Cristian, Rodrigo Saens, Carolina Del Río, and C. Villarroel. "OOAspectZ and aspect-oriented UML class diagrams for Aspect-oriented software modelling (AOSM)." Ingeniería e Investigación 33, no. 3 (2013): 66–71. http://dx.doi.org/10.15446/ing.investig.v33n3.41048.

Full text

Abstract:

Regarding modularised software development, Aspect-oriented programming (AOP) identifies and represents individually crosscutting concerns during the software development cycle's programming stage. This article proposes and applies OOAspectZ to formal Aspect-oriented requirement specifications for prior stages of the software development cycle. It particularly concerns requirement specification and the structural design of data and behaviour, along with describing and applying Aspect-oriented UML class diagrams to designing classes, aspects and associations among classes and aspects during Asp

APA, Harvard, Vancouver, ISO, and other styles

3

Vidal-Silva, C. L., E. Madariaga, T. Pham, F. Johnson, L. A. Urzua, and L. Carter. "JPIAspectZ: A Formal Requirement Specification Language for Joint Point Interface AOP Applications." Engineering, Technology & Applied Science Research 9, no. 4 (2019): 4338–41. http://dx.doi.org/10.48084/etasr.2774.

Full text

Abstract:

Aspect-oriented software development (AOSD) solves a few issues of the object-oriented software development (OOSD) approach and adds a few more concerning modules and their relationships. Join point interface (JPI) is an AOSD methodology that by the definition of the interface between advised artifacts and aspects solves associated AOSD issues to get software with a high modularity level. Looking for a JPI software development approach, this article proposes and exemplifies the use of JPIAspectZ, an extension of the formal aspect-oriented language AspectZ for the software JPI requirement speci

APA, Harvard, Vancouver, ISO, and other styles

4

Vidal-Silva, Cristian, Erika Madariaga, Trung Pham, Franklin Johnson, Luis Alberto Urzua, and Luis Carter. "JPIAspectZ: A Formal Requirement Specification Language for Joint Point Interface AOP Applications." Engineering, Technology & Applied Science Research 9, no. 4 (2019): 4338–41. https://doi.org/10.5281/zenodo.3370535.

Full text

Abstract:

Aspect-oriented software development (AOSD) solves a few issues of the object-oriented software development (OOSD) approach and adds a few more concerning modules and their relationships. Join point interface (JPI) is an AOSD methodology that by the definition of the interface between advised artifacts and aspects solves associated AOSD issues to get software with a high modularity level. Looking for a JPI software development approach, this article proposes and exemplifies the use of JPIAspectZ, an extension of the formal aspect-oriented language AspectZ for the software JPI requirement speci

APA, Harvard, Vancouver, ISO, and other styles

5

Pérez, Jennifer, Isidro Ramos, Jose Carsí, and Cristóbal Costa-Soria. "Model-Driven Development of Aspect-Oriented Software Architectures." JUCS - Journal of Universal Computer Science 19, no. (10) (2013): 1433–73. https://doi.org/10.3217/jucs-019-10-1433.

Full text

Abstract:

The Model-Driven Development (MDD) paradigm has become widely spread in the last few years due to being based on models instead of source code, and using automatic generation techniques to obtain the final software product. Until now, the most mature methodologies that have been proposed to develop software following MDD are mainly based on functional requirements by following the Object-Oriented Paradigm. Therefore, mature MDD methodologies are required for supporting the code generation from models that specify non-functional requirements. The Aspect-Oriented Software Development (AOSD) appr

APA, Harvard, Vancouver, ISO, and other styles

6

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

7

Rashid, Awais, Thomas Cottenier, Phil Greenwood, et al. "Aspect-Oriented Software Development in Practice: Tales from AOSD-Europe." Computer 43, no. 2 (2010): 19–26. http://dx.doi.org/10.1109/mc.2010.30.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

HAN, IKJOO, and DOO-HWAN BAE. "COMPOSITION OF ASPECTS BASED ON A RELATION MODEL: SYNERGY OF MULTIPLE PARADIGMS." International Journal of Software Engineering and Knowledge Engineering 16, no. 03 (2006): 379–402. http://dx.doi.org/10.1142/s0218194006002847.

Full text

Abstract:

Software composition for timely and affordable software development and evolution is one of the oldest pursuits of software engineering. In current software composition techniques, Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD) have attracted academic and industrial attention. Black box composition used in CBSD provides simple and safe modularization for its strong information hiding, which is, however, the main obstacle for a black box composite to evolve later. This implies that an application developed through black box composition cannot take ad

APA, Harvard, Vancouver, ISO, and other styles

9

Sandeep, Dalal, Hooda Susheela, and Solanki Kamna. "Comparative Analysis of Various Testing Techniques Used for Aspect-Oriented Software System." Indonesian Journal of Electrical Engineering and Computer Science 12, no. 1 (2018): 51–60. https://doi.org/10.11591/ijeecs.v12.i1.pp51-60.

Full text

Abstract:

Nowadays, Aspect-Oriented Programming (AOP) paradigm is getting more popularity in the field of software development. But testing an AspectOriented Software System (AOSS) is not well matured. Therefore, many researchers have been focusing on testing an AOSS. Moreover, the literature indicates that very few papers have devoted to literature survey but still there is need to study in depth of various testing techniques used for AOSS. Therefore, in this paper, a comprehensive study of existing various testing techniques for AOSS have been conducted and present a comparative analysis result of var

APA, Harvard, Vancouver, ISO, and other styles

10

Gal-Chis, Calin Eugen Nicolae. "Modeling Concern Spaces Using Multi Dimensional Separation of Concerns." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 11, no. 2 (2013): 2302–13. http://dx.doi.org/10.24297/ijct.v11i2.1181.

Full text

Abstract:

For software products, the specifications, the requirements even the variables, the code or the software modules are subject to be labelled with key-terms, or described using attributes or specific values. The purpose of these notations is linked to the semantic of the object labelled, and is used as an indexing form for that specific category. A separation of concerns meta model is proposed here to provide the support of using a unitary type of notation in labelling various kind of resources used in the process of developing software, from requirements and specifications all the way to variab

APA, Harvard, Vancouver, ISO, and other styles

11

Dalal, Sandeep, and Susheela Hooda. "Comparative Analysis of Various Testing Techniques used for Aspect-Oriented Software System." Indonesian Journal of Electrical Engineering and Computer Science 12, no. 1 (2018): 51. http://dx.doi.org/10.11591/ijeecs.v12.i1.pp51-60.

Full text

Abstract:

<p>Nowadays, Aspect-Oriented Programming (AOP) paradigm is getting more popularity in the field of software development. But testing an Aspect-oriented software system (AOSS) is not well matured. Therefore, many researchers have been focusing on testing an AOSS. Moreover, the literature indicates that very few papers have devoted to literature survey but still there is need to study in depth of various testing techniques used for AOSS. Therefore, in this paper, a comprehensive study of existing various testing techniques for AOSS have been conducted and present a comparative analysis res

APA, Harvard, Vancouver, ISO, and other styles

12

Gómez-Sanz, Jorge J., and Rubén Fuentes-Fernández. "Understanding Agent-Oriented Software Engineering methodologies." Knowledge Engineering Review 30, no. 4 (2015): 375–93. http://dx.doi.org/10.1017/s0269888915000053.

Full text

Abstract:

AbstractFor many years, the progress in agent-oriented development has focused on tools and methods for particular development phases. This has not been enough for the industry to accept agent technology as we expected. Our hypothesis is that the Agent-Oriented Software Engineering (AOSE) community has not recognized the kind of development methods that industry actually demands. We propose to analyze this hypothesis starting with a more precise definition of what an AOSE methodology should be. This definition is the first step for a review of the current progress of an illustrative selection

APA, Harvard, Vancouver, ISO, and other styles

13

Abdalla, Reem, and Alok Mishra. "Agent-Oriented Software Engineering Methodologies: Analysis and Future Directions." Complexity 2021 (December 29, 2021): 1–21. http://dx.doi.org/10.1155/2021/1629419.

Full text

Abstract:

The Internet of Things (IoT) facilitates in building cyber-physical systems, which are significant for Industry 4.0. Agent-based computing represents effective modeling, programming, and simulation paradigm to develop IoT systems. Agent concepts, techniques, methods, and tools are being used in evolving IoT systems. Over the last years, in particular, there has been an increasing number of agent approaches proposed along with an ever-growing interest in their various implementations. Yet a comprehensive and full-fledged agent approach for developing related projects is still lacking despite th

APA, Harvard, Vancouver, ISO, and other styles

14

WEIß, GERHARD. "Agent orientation in software engineering." Knowledge Engineering Review 16, no. 4 (2001): 349–73. http://dx.doi.org/10.1017/s026988890100025x.

Full text

Abstract:

Agent-Oriented Software Engineering (AOSE) is rapidly emerging in response to urgent needs in both software engineering and agent-based computing. While these two disciplines coexisted without remarkable interaction until some years ago, today there is rich and fruitful interaction among them and various approaches are available that bring together techniques, concepts and ideas from both sides. This article offers a guide to the broad body of literature on AOSE. The guide, which is intended to be of value to both researchers and practitioners, is structured according to key issues and key top

APA, Harvard, Vancouver, ISO, and other styles

15

Atkinson, C., and T. Kuhne. "Aspect-oriented development with stratified frameworks." IEEE Software 20, no. 1 (2003): 81–89. http://dx.doi.org/10.1109/ms.2003.1159035.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Losavio, Francisca, Alfredo Matteo, and Patricia Morantes. "UML Extensions for Aspect Oriented Software Development." Journal of Object Technology 8, no. 5 (2009): 105. http://dx.doi.org/10.5381/jot.2009.8.5.a1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Han, Hyuck, Hyungsoo Jung, and Heon Y. Yeom. "Aspect-oriented development of cluster computing software." Cluster Computing 14, no. 4 (2011): 357–75. http://dx.doi.org/10.1007/s10586-011-0166-7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Eichberg, Michael. "Component-Based Software Development with Aspect-Oriented Programming." Journal of Object Technology 4, no. 3 (2005): 21. http://dx.doi.org/10.5381/jot.2005.4.3.a3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Brichau, Johan, Ruzanna Chitchyan, Alessandro Garcia, et al. "A Model Curriculum for Aspect-Oriented Software Development." IEEE Software 23, no. 6 (2006): 53–61. http://dx.doi.org/10.1109/ms.2006.146.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Mohan Garg, Rachit, and Deepak Dahiya. "An Aspect Oriented Component Based Archetype Driven Development." Journal of Information Technology Research 4, no. 3 (2011): 29–49. http://dx.doi.org/10.4018/jitr.2011070103.

Full text

Abstract:

This paper incorporates the concepts of aspects and software reuse in archetype driven architecture. The proposed work develops the software by partitioning the whole system into different independent components and aspects to facilitate component reuse. The authors illustrate the ease of modeling the components separately and emphasize concerns that the OOP paradigm has failed to address. This paper places emphasis on designing and modeling the software rather than coding. Identification of reusable components is carried out using the hybrid methodology and aspects are identified by domain ex

APA, Harvard, Vancouver, ISO, and other styles

21

Ghareb, Mazen Ismaeel, and Gary Allen. "IMPROVING THE DESIGN AND IMPLEMENTATION OF SOFTWARE SYSTEMS USES ASPECT ORIENTED PROGRAMMING." Journal of University of Human Development 1, no. 3 (2015): 362. http://dx.doi.org/10.21928/juhd.v1n3y2015.pp362-368.

Full text

Abstract:

Aspect Oriented Programming (AOP) is a technique used to enhance the separation of concern in software design and implementation. To implement AOP developers most commonly use AspectJ, an extension of the Java language. In order to represent the separation of concerns a new design technique is needed for modeling of aspects. Aspect Oriented Design language (ASDL) is a design notation could build on the existing design language UML. It is capable of supporting many aspects-oriented languages. This research aims to investigate where developers can use aspect-oriented programming in the software

APA, Harvard, Vancouver, ISO, and other styles

22

Ghanem, Kinan, Haysam Al-Radwan, and Ahmad Ahmad. "The Effect of Overlapping Area on Ping-Pong Handover in LTE Networks." Journal of University of Human Development 1, no. 3 (2015): 369. http://dx.doi.org/10.21928/juhd.v1n3y2015.pp369-375.

Full text

Abstract:

Aspect Oriented Programming (AOP) is a technique used to enhance the separation of concern in software design and implementation. To implement AOP developers most commonly use AspectJ, an extension of the Java language. In order to represent the separation of concerns a new design technique is needed for modeling of aspects. Aspect Oriented Design language (ASDL) is a design notation could build on the existing design language UML. It is capable of supporting many aspects-oriented languages. This research aims to investigate where developers can use aspect-oriented programming in the software

APA, Harvard, Vancouver, ISO, and other styles

23

Tekinerdogan, Bedir. "Reflection on Turkish aspect-oriented software development workshop series." ACM SIGSOFT Software Engineering Notes 37, no. 2 (2012): 30–33. http://dx.doi.org/10.1145/2108144.2108165.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

SINGH, Pradeep Kumar, Om Prakash SANGWAN, Amrendra PRATAP, and Amar Pal SINGH. "An Analysis on Software Reusability in Context of Object Oriented and Aspect Oriented Software Development." International Journal of Information Security and Cybercrime 3, no. 2 (2014): 19–28. http://dx.doi.org/10.19107/ijisc.2014.02.02.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

AGOSTINHO, SÉRGIO, ANA MOREIRA, ANDRÉ MARQUES, et al. "ASPECT-ORIENTED SPECIFICATION: A CASE STUDY IN SPACE DOMAIN." International Journal of Software Engineering and Knowledge Engineering 20, no. 06 (2010): 783–808. http://dx.doi.org/10.1142/s0218194010004943.

Full text

Abstract:

Aspect-oriented software development claims to improve several software engineering principles, such as modularization, abstraction and composition. The Aspect for the Space Domain project (ASSD) developed a metadata-driven approach for aspect-oriented requirements analysis. The main objectives of the ASSD project, funded by the European Space Agency , were to study the applicability and usefulness of aspect-orientation for the space domain (ground segment software projects in particular), focusing on the early stages of the software development life cycle. Therefore, this paper describes a ri

APA, Harvard, Vancouver, ISO, and other styles

26

Costa-Soria, Cristóbal, and Jennifer Pérez. "Teaching software architectures and aspect-oriented software development using open-source projects." ACM SIGCSE Bulletin 41, no. 3 (2009): 385. http://dx.doi.org/10.1145/1595496.1563027.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Mguni, Kagiso, and Yirsaw Ayalew. "An Assessment of Maintainability of an Aspect-Oriented System." ISRN Software Engineering 2013 (February 10, 2013): 1–11. http://dx.doi.org/10.1155/2013/121692.

Full text

Abstract:

Software maintenance is an important activity in software development. Some development methodologies such as the object-oriented have contributed in improving maintainability of software. However, crosscutting concerns are still challenges that affect the maintainability of OO software. In this paper, we discuss our case study to assess the extent of maintainability improvement that can be achieved by employing aspect-oriented programming. Aspect-oriented programming (AOP) is a relatively new approach that emphasizes dealing with crosscutting concerns. To demonstrate the maintainability impro

APA, Harvard, Vancouver, ISO, and other styles

28

Babu, Chitra, and R. Vijayalakshmi. "Metrics-based design selection tool for aspect oriented software development." ACM SIGSOFT Software Engineering Notes 33, no. 5 (2008): 1–10. http://dx.doi.org/10.1145/1402521.1402522.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Harrison, W., H. Ossher, S. Sutton, and P. Tarr. "Supporting aspect-oriented software development with the Concern Manipulation Environment." IBM Systems Journal 44, no. 2 (2005): 309–18. http://dx.doi.org/10.1147/sj.442.0309.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Pérez-Toledano, Miguel, Amparo Navasa, Juan-Manuel Murillo-Rodríguez, and Carlos Canal. "A Safe Dynamic Adaptation Framework for Aspect-Oriented Software Development." JUCS - Journal of Universal Computer Science 14, no. (13) (2008): 2212–38. https://doi.org/10.3217/jucs-014-13-2212.

Full text

Abstract:

One focus of current software development is the re-use of components in the construction of systems. Software Adaptation facilitates the consequent need to adapt these components to the new environment by employing adaptors which are obtained automatically and hence with a certain guarantee of suitability, from formal descriptions of the interface behaviour. One appropriate technique for Software Adaptation is Aspect-Oriented Programming (AOP) which makes use of aspects to facilitate the dynamic adaptation of components transparently and non-intrusively. However, owing to the way that aspects

APA, Harvard, Vancouver, ISO, and other styles

31

Chu, Yan Hua, and Jin Ling Yu. "Aspect-Oriented Programming and Modeling Based on UML." Advanced Materials Research 756-759 (September 2013): 2610–14. http://dx.doi.org/10.4028/www.scientific.net/amr.756-759.2610.

Full text

Abstract:

Traditional software development method will bring code tangling, code scattered and many other issues. Aspect-oriented programming came into being under this circumstance. AOP is a new programming paradigm which is independent of all the other programming languages. The scale and complexity of software systems increase continually. Efficiently control the complexity of software systems has already become a vitally important issue which needs to be addressed. In the modular design and implementation of software, cross cut always arise between primary functional modules and non-functional modul

APA, Harvard, Vancouver, ISO, and other styles

32

Idate, Sonali R., T. Srinivasa Rao, and Dipak J. Mali. "Context-Based Aspect-Oriented Requirement Engineering Model." Engineering, Technology & Applied Science Research 13, no. 2 (2023): 10460–65. http://dx.doi.org/10.48084/etasr.5699.

Full text

Abstract:

Mobile applications are context-oriented systems that involve the use of context information while operating. Mobile applications demand tackling context information in the early phase of software engineering. A context-aware system demands a different approach to handling the influence of the context on a system's requirements. Aspect-oriented Requirement Engineering separates concerns throughout requirements, called crosscutting concerns, in the early phase of software development to improve the modularity of complex applications. Capturing requirements embedded within context is a challengi

APA, Harvard, Vancouver, ISO, and other styles

33

Vranic, Valentino, and Milan Laslop. "Aspects and roles in software modeling: A composition based comparison." Computer Science and Information Systems 13, no. 1 (2016): 199–216. http://dx.doi.org/10.2298/csis151207065v.

Full text

Abstract:

It?s intriguing how the work on inherent aspect-oriented modeling almost completely ignores the similarity between aspect-oriented and role based decomposition and composition. Ever since the notion of aspect entered the software development arena, it has been compared to the notion of role. Findings range from identifying greater similarities to more cautious observations that albeit aspects and roles are similar, they appear to be more as complimentary with a significant effort needed to really bring them together in programming. Even a cursory comparison of Theme/UML, which represents a des

APA, Harvard, Vancouver, ISO, and other styles

34

Ionescu, Tudor B., Andreas Piater, Walter Scheuermann, and Eckart Laurien. "An Aspect-Oriented Approach for the Development of Complex Simulation Software." Journal of Object Technology 9, no. 1 (2010): 161. http://dx.doi.org/10.5381/jot.2010.9.1.a4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Gulia, Preeti, Manju Khari, and Shrikant Patel. "Metrics Analysis in Object Oriented and Aspect Oriented Programming." Recent Patents on Engineering 13, no. 2 (2019): 117–22. http://dx.doi.org/10.2174/1872212112666180831115458.

Full text

Abstract:

Background: Object oriented programming (OOP) is a programming paradigm that has been used for several years by the software engineering community. The best practice of OOP was gathered and they are known as Design Patterns. They provide guidelines for developing flexible software applications. Recent studies claim that some patterns have limitations and their implementations could be improved. Researchers claim that Aspect Oriented Programming (AOP) is a paradigm that provides features to overcome the limitations of OOP and patterns. However, even with the good results achieved using AOP, it

APA, Harvard, Vancouver, ISO, and other styles

36

Fuentes, Lidia, Mónica Pinto, and Pablo Sánchez. "Generating CAM aspect-oriented architectures using Model-Driven Development." Information and Software Technology 50, no. 12 (2008): 1248–65. http://dx.doi.org/10.1016/j.infsof.2007.10.020.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Permana, Diky Oktiadi, and Muhammad Fachrie. "A Mobile-Based Used Vehicle Buying System Implementation." International Journal Software Engineering and Computer Science (IJSECS) 3, no. 3 (2023): 246–51. http://dx.doi.org/10.35870/ijsecs.v3i3.1717.

Full text

Abstract:

Aspect-oriented software is characterized by enhanced reusability and maintainability compared to object-oriented software. In aspect-oriented software development, concerns scattered across objects are separated and modularized into aspects. This research is motivated by the buyer's mistrust in used vehicle transactions due to concerns over potential fraud. To address this, the study proposes designing an e-commerce application that facilitates interactions between prospective vehicle sellers and buyers, alleviating transactional apprehensions. The analysis and design phases of the software d

APA, Harvard, Vancouver, ISO, and other styles

38

Chaudhary, Ritika, and Ram Chatterjee. "Predilection of Reusability over Maintainability in Aspect-Oriented Systems." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 6, no. 3 (2013): 423–35. http://dx.doi.org/10.24297/ijct.v6i3.4482.

Full text

Abstract:

Maintenance is the important phase in software development lifecycle which initiates after the software has been deployedÂ for use. Reusability is an important area of concern which depicts the extent to which a module can be used again inÂ different applications with slight or no modification. Maintainability is one of the contributing factors for assessingÂ Reusability. So, assessment of Reusability is preferred over Maintainability.Â This paper has been split into Introduction, Role of Maintainability, Role of reusability and conclusion. In the introduction section the concept that how the

APA, Harvard, Vancouver, ISO, and other styles

39

SoleimanianGharehchopogh, Farhad, Esmail Amini, and Behnam Zebardast. "Aspect-Oriented Software Development based Solution for Intervention Concerns Problems: Case Study." International Journal of Computer Applications 63, no. 4 (2013): 16–25. http://dx.doi.org/10.5120/10453-5157.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Murphy, G. C., R. J. Walker, and E. L. A. Banlassad. "Evaluating emerging software development technologies: lessons learned from assessing aspect-oriented programming." IEEE Transactions on Software Engineering 25, no. 4 (1999): 438–55. http://dx.doi.org/10.1109/32.799936.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Xiao, Kun. "Aspect-Oriented Dynamic Weaving Testing Based on Sequence Diagrams." Applied Mechanics and Materials 336-338 (July 2013): 1957–63. http://dx.doi.org/10.4028/www.scientific.net/amm.336-338.1957.

Full text

Abstract:

Now, the aspect-oriented software development is placed in the initial phase. For the nature of dynamic weaving, it is difficult to test the aspect-oriented dynamic weavings. The methods of the object-oriented testing and the procedure-oriented testing can not be applied in the dynamic weaving testing. In this paper, it analyzes the properties of the dynamic weaving, and induces the constraints in the dynamic weaving. Then, it regards the dynamic weavings as the processes piling the crosscutting concerns up the core concerns, and gives the formation concepts of the dynamic weaving. Following,

APA, Harvard, Vancouver, ISO, and other styles

42

CUI, ZHANQI, LINZHANG WANG, XI LIU, LEI BU, JIANHUA ZHAO, and XUANDONG LI. "VERIFYING ASPECT-ORIENTED MODELS AGAINST CROSSCUTTING PROPERTIES." International Journal of Software Engineering and Knowledge Engineering 23, no. 05 (2013): 655–76. http://dx.doi.org/10.1142/s0218194013400123.

Full text

Abstract:

Dealing with crosscutting concerns has been a critical problem in software development processes. To facilitate handling crosscutting concerns at design phases, we proposed an aspect-oriented modeling and integration approach with UML activity diagrams. The primary concerns are depicted with UML activity diagrams as primary models, whereas crosscutting concerns are described with aspectual extended activity diagrams as aspect models. Aspect models can be integrated into primary models automatically. The AOM approach can reduce the complexity of design models. However, potential faults that vio

APA, Harvard, Vancouver, ISO, and other styles

43

STEIN, DOMINIK, STEFAN HANENBERG, and RAINER UNLAND. "JOIN POINT DESIGNATION DIAGRAMS: A GRAPHICAL REPRESENTATION OF JOIN POINT SELECTIONS." International Journal of Software Engineering and Knowledge Engineering 16, no. 03 (2006): 317–46. http://dx.doi.org/10.1142/s0218194006002811.

Full text

Abstract:

The specification of join point selections (also known as "pointcuts") is a major design issue in Aspect-Oriented Software Development. Aspect-oriented systems generally provide specific language constructs (subsumed by the term "pointcut language") for specifying such a join point selection. Pointcut languages differ widely with respect to their syntax and semantics. Consequently, developers familiar with one specific language can hardly benefit from this knowledge when designing and implementing pointcuts in another language. This implies that developers working with different aspect-oriente

APA, Harvard, Vancouver, ISO, and other styles

44

RANJAN, PRABHAT, and A. K. MISRA. "A NOVEL APPROACH OF REQUIREMENT GATHERING AND ANALYSIS FOR AGENT ORIENTED SOFTWARE ENGINEERING (AOSE)." International Journal of Software Engineering and Knowledge Engineering 19, no. 01 (2009): 79–111. http://dx.doi.org/10.1142/s0218194009004064.

Full text

Abstract:

In this paper, an agent-based open and adaptive system development process has been proposed which continuously change and evolve to meet new requirements. The proposed methodology is based on a model-based technique that provides a specific model for the type of information to be gathered and uses this model to drive the domain specific analysis process. The focus is on a clear separtion between the requirement gathering and analysis phases. The analysis methodology further splits the analysis phase into the user_centric analysis and the system_centric analysis phases. Optimization of the sys

APA, Harvard, Vancouver, ISO, and other styles

45

Kardas, Geylani. "Model-driven development of multiagent systems: a survey and evaluation." Knowledge Engineering Review 28, no. 4 (2013): 479–503. http://dx.doi.org/10.1017/s0269888913000088.

Full text

Abstract:

AbstractTo work in a higher abstraction level is of critical importance for the development of multiagent systems (MAS) since it is almost impossible to observe code-level details of such systems due to their internal complexity, distributedness and openness. As one of the promising software development approaches, model-driven development (MDD) aims to change the focus of software development from code to models. This paradigm shift, introduced by the MDD, may also provide the desired abstraction level during the development of MASs. For this reason, MDD of autonomous agents and MASs has been

APA, Harvard, Vancouver, ISO, and other styles

46

Ghareb, Mazen Ismaeel, and Garry Allen. "An empirical evaluation of metrics on aspect-oriented programs." UHD Journal of Science and Technology 3, no. 2 (2019): 74. http://dx.doi.org/10.21928/uhdjst.v3n2y2019.pp74-86.

Full text

Abstract:

 The quality evaluation of software metrics measurement is considered as the primary indicator of imperfection prediction and software maintenance in various empirical studies of software products. However, there is no agreement on which metrics are compelling quality pointers for new software development approaches such as aspect-oriented programming (AOP) techniques. AOP intends to enhance programming quality by providing fundamentally different parts of the systems, for example, pointcuts, advice, and intertype relationships. Hence, it is not evident if quality characteristics for AOP

APA, Harvard, Vancouver, ISO, and other styles

47

Rusdiana, Cahyani, Kaspul Kaspul, and Nurul Hidayati Utami. "USING FLIPBOOK MAKER TO CREATE SCIENCE PROCESS ORIENTED ELECTRONIC HANDOUT." JURNAL ATRIUM PENDIDIKAN BIOLOGI 7, no. 2 (2022): 154. http://dx.doi.org/10.24036/apb.v7i2.12763.

Full text

Abstract:

E-handout is teaching material that are displayed electronically. One of the software used for e-handout development is Flipbook Maker. Mentioning the development of information technology, plus the proliferation of distance education, then the development of e-handout is one of the most appropriate choices. Moreover, its development is accompanied by Science Process Skills, so this development is carried out. This development research consists of 4 stages; define, design, develop and disseminate. This article contains research results in the form of values and descriptions of practicality tes

APA, Harvard, Vancouver, ISO, and other styles

48

SINGH, Pradeep Kumar, Om Prakash SANGWAN, Amrendra PRATAP, and Amar Pal SINGH. "An Analysis on Software Testability and Security in Context of Object and Aspect Oriented Software Development." International Journal of Information Security and Cybercrime 3, no. 1 (2014): 17–28. http://dx.doi.org/10.19107/ijisc.2014.01.02.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Syed-Mohamad, Sharifah Mashita, Amir Ngah, Al-Fahim Mubarak Ali, and Pantea Keikhosrokiani. "Measuring Software Maintainability: An Exploration of Metrics and Continuous Practices." Journal of Advanced Research in Applied Sciences and Engineering Technology 63, no. 2 (2025): 181–95. https://doi.org/10.37934/araset.63.2.181195.

Full text

Abstract:

Maintainability is a critical aspect of modern software projects, referring to the ease with which a system can be modified, repaired, or adapted to changing requirements. In today's agile environment, maintainability is becoming increasingly important, yet there is not much literature that reports whether the metrics established since several decades ago are still used in modern projects. Are there different measures of software maintainability in Agile and DevOps, in particular? This paper reviews the evolution of software maintainability metrics from traditional function-oriented to contemp

APA, Harvard, Vancouver, ISO, and other styles

50

Stein, Dominik, and Stefan Hanenberg. "Why Aspect-Oriented Software Development And Model-Driven Development Are Not The Same – A Position Paper –." Electronic Notes in Theoretical Computer Science 163, no. 1 (2006): 71–82. http://dx.doi.org/10.1016/j.entcs.2006.07.004.

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!