Relevant bibliographies by topics / Agent Oriented Software Engineering

Academic literature on the topic 'Agent Oriented Software Engineering'

Author: Grafiati
Published: 4 June 2021
Last updated: 4 May 2024

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

Select a source type:

Contents

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Agent Oriented Software Engineering.'

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.

Journal articles on the topic "Agent Oriented Software Engineering"

1

BERNON, CAROLE, MASSIMO COSSENTINO, and JUAN PAVÓN. "Agent-oriented software engineering." Knowledge Engineering Review 20, no. 2 (June 2005): 99–116. http://dx.doi.org/10.1017/s0269888905000421.

Full text
Abstract:
Considering the great number of agent-oriented methodologies that can be found in the literature, and the fact that each one defines its own concepts and system structure, one of the main challenges in agent-oriented software engineering (AOSE) research is how to make these methodologies interoperable. By defining concepts used in a specific domain in a non-ambiguous way, meta-modelling may represent a step towards such interoperability. Consequently the main objective of the AOSE TFG (Technical Forum Group) is to establish a strategy for identifying a common meta-model that could be widely adopted by the AOSE community. This paper sums up the approach used by this TFG which consists of (i) studying and comparing the meta-models related to some existing methodologies (ADELFE, Gaia, INGENIAS, PASSI, RICA and Tropos) in order to find commonalities and (ii) giving a clear and basic definition for the core concepts used in multi-agent systems for relating and positioning them in a unified MAS meta-model. The first proposal, set up by the working group, for this unified meta-model then concludes this paper.
APA, Harvard, Vancouver, ISO, and other styles
2

Gómez-Sanz, Jorge J., and Rubén Fuentes-Fernández. "Understanding Agent-Oriented Software Engineering methodologies." Knowledge Engineering Review 30, no. 4 (September 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 of methodologies, looking for missing elements and future lines of improvement. The result is an account of how well the AOSE community is meeting the software lifecycle needs. It can be advanced that AOSE methodologies are far from providing all the answers industry requires and that effort has grounded mainly in requirements, design, and implementation phases.
APA, Harvard, Vancouver, ISO, and other styles
3

Mubarak, Hisham. "Developing Flexible Software Using Agent-Oriented Software Engineering." IEEE Software 25, no. 5 (September 2008): 12–15. http://dx.doi.org/10.1109/ms.2008.135.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Molesini, Ambra, Andrea Omicini, and Mirko Viroli. "Environment in agent-oriented software engineering methodologies." Multiagent and Grid Systems 5, no. 1 (March 31, 2009): 37–57. http://dx.doi.org/10.3233/mgs-2009-0118.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Mao, Xinjun. "Agent-Oriented Software Engineering: Status and Challenges." Journal of Computer Research and Development 43, no. 10 (2006): 1782. http://dx.doi.org/10.1360/crad20061016.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Gomez-Sanz, Jorge J., and Ruben Fuentes. "Agent oriented software engineering with web applications." International Journal of Web Engineering and Technology 1, no. 4 (2004): 471. http://dx.doi.org/10.1504/ijwet.2004.006271.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Cohen, Mark A., Frank E. Ritter, and Steven R. Haynes. "Applying Software Engineering to Agent Development." AI Magazine 31, no. 2 (July 28, 2010): 25. http://dx.doi.org/10.1609/aimag.v31i2.2214.

Full text
Abstract:
Developing intelligent agents and cognitive models is a complex software engineering activity. This article shows how all intelligent agent creation tools can be improved by taking advantage of established software engineering principles such as high-level languages, maintenance-oriented development environments, and software reuse. We describe how these principles have been realized in the Herbal integrated development environment, a collection of tools that allows agent developers to exploit modern software engineering principles.
APA, Harvard, Vancouver, ISO, and other styles
8

Wang, Chun Yan, Li Ge, and Wen Hong Liu. "Research on the Agent Oriented Software Design Engineering." Advanced Materials Research 926-930 (May 2014): 2402–5. http://dx.doi.org/10.4028/www.scientific.net/amr.926-930.2402.

Full text
Abstract:
Agent oriented software engineering is a novel software paradigm that is considered as an important approach to supporting the development of complex software systems based on agent technology. Many attentions had been paid by researchers in academic; literature and practitioners in industry literature. In the past ten years, great progresses of agent oriented software engineering has been made. However, there are still a great number of problems that should be solved before it moves to industry application and its potentials should be exploited extensively. After investigating the background and characteristics of agent oriented software engineering, the paper presented the state of agent oriented software design engineering
APA, Harvard, Vancouver, ISO, and other styles
9

Fischer, Klaus, Christian Hahn, and Cristian Madrigal Mora. "Agent-oriented software engineering: a model-driven approach." International Journal of Agent-Oriented Software Engineering 1, no. 3/4 (2007): 334. http://dx.doi.org/10.1504/ijaose.2007.016265.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Beydoun, Ghassan, and Graham Low. "Centering ontologies in agent oriented software engineering processes." Complex & Intelligent Systems 2, no. 3 (September 26, 2016): 235–42. http://dx.doi.org/10.1007/s40747-016-0025-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Agent Oriented Software Engineering"

1

Lin, Chia-En. "A Comparison of Agent-Oriented Software Engineering Frameworks and Methodologies." Thesis, University of North Texas, 2003. https://digital.library.unt.edu/ark:/67531/metadc4411/.

Full text
Abstract:
Agent-oriented software engineering (AOSE) covers issues on developing systems with software agents. There are many techniques, mostly agent-oriented and object-oriented, ready to be chosen as building blocks to create agent-based systems. There have been several AOSE methodologies proposed intending to show engineers guidelines on how these elements are constituted in having agents achieve the overall system goals. Although these solutions are promising, most of them are designed in ad-hoc manner without truly obeying software developing life-cycle fully, as well as lacking of examinations on agent-oriented features. To address these issues, we investigated state-of-the-art techniques and AOSE methodologies. By examining them in different respects, we commented on the strength and weakness of them. Toward a formal study, a comparison framework has been set up regarding four aspects, including concepts and properties, notations and modeling techniques, process, and pragmatics. Under these criteria, we conducted the comparison in both overview and detailed level. The comparison helped us with empirical and analytical study, to inspect the issues on how an ideal agent-based system will be formed.
APA, Harvard, Vancouver, ISO, and other styles
2

Hill, Richard. "A requirements elicitation framework for agent-oriented software engineering." Thesis, Sheffield Hallam University, 2006. http://shura.shu.ac.uk/19793/.

Full text
Abstract:
The hypothesis of this research is as follows: "Conceptual modelling is a useful activity for the early part of gathering requirements for agent-based systems." This thesis examines the difficulties of gathering and expressing requirements for agent based systems, and describes the development of a requirements elicitation framework. Conceptual modelling in the form of Conceptual Graphs is offered as a means of representing the constituent parts of an agent-based system. In particular, use of a specific graph, the Transaction Model, illustrates how complex agent concepts can be modelled and tested prior to detailed design specification, by utilising a design metaphor for an organisational activity. Using an exemplar in the healthcare domain, a preliminary design framework is developed showing how the Transaction Agent Modelling (TrAM) approach assisted the design of complex community healthcare payment models. Insight gained during the design process is used to enrich and refine the framework in order that detailed ontological specifications can be constructed, before validating with a mobile learning scenario. The ensuing discussion evaluates how useful the approach is, and demonstrates the following contributions: Use of the Transaction Model to impose a rigour upon the requirements elicitation process for agent-based systems; Use of Conceptual Graph type hierarchies for ontology construction; A means to check the transaction models using graphical inferencing with Peirce Logic; Provision of a method for the elicitation and decomposition of soft goals; The TrAM process for agent system requirements elicitation.
APA, Harvard, Vancouver, ISO, and other styles
3

Al-Azawi, Rula K. "Agent Oriented Software Engineering (AOSE) approach to game development methodology." Thesis, De Montfort University, 2015. http://hdl.handle.net/2086/11120.

Full text
Abstract:
This thesis investigates existing game development methodologies, through the process of researching game and system development models. The results indicate that these methodologies are engineered to solve specific problems, and most are suitable only for specific game genres. Different approaches to building games have been proposed in recent years. However, most of these methodologies focus on the design and implementation phase. This research aims to enhance game development methodologies by proposing a novel game development methodology, with the ability to function in generic game genres, thereby guiding game developers and designers from the start of the game development phase to the end of the implementation and testing phase. On a positive note, aligning development practice with universal standards makes it far easier to incorporate extra team members at short notice. This increased the confidence when working in the same environment as super developers. In the gaming industry, most game development proceeds directly from game design to the implementation phase, and the researcher observes that this is the only industry in which this occurs. It is a consequence of the game industry’s failure to integrate with modern development techniques. The ultimate aim of this research to apply a new game development methodology using most game elements to enhance success. This development model will align with different game genres, and resolve the gap between industry and research area, so that game developers can focus on the important business of creating games. The primary aim of Agent Oriented Agile Base (AOAB) game development methodology is to present game development techniques in sequential steps to facilitate game creation and close the gap in the existing game development methodologies. Agent technology is used in complex domains such as e-commerce, health, manufacturing, games, etc. In this thesis we are interested in the game domain, which comprises a unique set of characteristics such as automata, collaboration etc. Our AOAB will be based on a predictive approach after adaptation of MaSE methodology, and an adaptive approach using Agile methodology. To ensure proof of concept, AOAB game development methodology will be evaluated against industry principles, providing an industry case study to create a driving test game, which was the problem motivating this research. Furthermore, we conducted two workshops to introduce our methodology to both academic and industry participants. Finally, we prepared an academic experiment to use AOAB in the academic sector. We have analyzed the feedbacks and comments and concluded the strengths and weakness of the AOAB methodology. The research achievements are summarized and proposals for future work outlined.
APA, Harvard, Vancouver, ISO, and other styles
4

Oluyomi, Ayodele. "Patterns and protocols for agent oriented software development /." Connect to thesis, 2006. http://eprints.unimelb.edu.au/archive/00002780.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Dehlinger, Joshua Jon. "Incorporating product-line engineering techniques into agent-oriented software engineering for efficiently building safety-critical, multi-agent systems." [Ames, Iowa : Iowa State University], 2007.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Huang, Wei. "Agent-oriented software engineering : application to the management of community care provision." Thesis, University of Liverpool, 2006. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.428224.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Dam, Khanh Hoa, and s3007289@student rmit edu au. "Supporting Software Evolution in Agent Systems." RMIT University. Computer Science and Information Technology, 2009. http://adt.lib.rmit.edu.au/adt/public/adt-VIT20090319.143847.

Full text
Abstract:
Software maintenance and evolution is arguably a lengthy and expensive phase in the life cycle of a software system. A critical issue at this phase is change propagation: given a set of primary changes that have been made to software, what additional secondary changes are needed to maintain consistency between software artefacts? Although many approaches have been proposed, automated change propagation is still a significant technical challenge in software maintenance and evolution. Our objective is to provide tool support for assisting designers in propagating changes during the process of maintaining and evolving models. We propose a novel, agent-oriented, approach that works by repairing violations of desired consistency rules in a design model. Such consistency constraints are specified using the Object Constraint Language (OCL) and the Unified Modelling Language (UML) metamodel, which form the key inputs to our change propagation framework. The underlying change propagation mechanism of our framework is based on the well-known Belief-Desire-Intention (BDI) agent architecture. Our approach represents change options for repairing inconsistencies using event-triggered plans, as is done in BDI agent platforms. This naturally reflects the cascading nature of change propagation, where each change (primary or secondary) can require further changes to be made. We also propose a new method for generating repair plans from OCL consistency constraints. Furthermore, a given inconsistency will typically have a number of repair plans that could be used to restore consistency, and we propose a mechanism for semi-automatically selecting between alternative repair plans. This mechanism, which is based on a notion of cost, takes into account cascades (where fixing the violation of a constraint breaks another constraint), and synergies between constraints (where fixing the violation of a constraint also fixes another violated constraint). Finally, we report on an evaluation of the approach, covering both effectiveness and efficiency.
APA, Harvard, Vancouver, ISO, and other styles
8

Santi, Andrea <1985&gt. "Engineering Agent-Oriented Technologies and Programming Languages for Computer Programming and Software Development." Doctoral thesis, Alma Mater Studiorum - Università di Bologna, 2013. http://amsdottorato.unibo.it/5634/1/santi_andrea_tesi.pdf.

Full text
Abstract:
Mainstream hardware is becoming parallel, heterogeneous, and distributed on every desk, every home and in every pocket. As a consequence, in the last years software is having an epochal turn toward concurrency, distribution, interaction which is pushed by the evolution of hardware architectures and the growing of network availability. This calls for introducing further abstraction layers on top of those provided by classical mainstream programming paradigms, to tackle more effectively the new complexities that developers have to face in everyday programming. A convergence it is recognizable in the mainstream toward the adoption of the actor paradigm as a mean to unite object-oriented programming and concurrency. Nevertheless, we argue that the actor paradigm can only be considered a good starting point to provide a more comprehensive response to such a fundamental and radical change in software development. Accordingly, the main objective of this thesis is to propose Agent-Oriented Programming (AOP) as a high-level general purpose programming paradigm, natural evolution of actors and objects, introducing a further level of human-inspired concepts for programming software systems, meant to simplify the design and programming of concurrent, distributed, reactive/interactive programs. To this end, in the dissertation first we construct the required background by studying the state-of-the-art of both actor-oriented and agent-oriented programming, and then we focus on the engineering of integrated programming technologies for developing agent-based systems in their classical application domains: artificial intelligence and distributed artificial intelligence. Then, we shift the perspective moving from the development of intelligent software systems, toward general purpose software development. Using the expertise maturated during the phase of background construction, we introduce a general-purpose programming language named simpAL, which founds its roots on general principles and practices of software development, and at the same time provides an agent-oriented level of abstraction for the engineering of general purpose software systems.
APA, Harvard, Vancouver, ISO, and other styles
9

Santi, Andrea <1985&gt. "Engineering Agent-Oriented Technologies and Programming Languages for Computer Programming and Software Development." Doctoral thesis, Alma Mater Studiorum - Università di Bologna, 2013. http://amsdottorato.unibo.it/5634/.

Full text
Abstract:
Mainstream hardware is becoming parallel, heterogeneous, and distributed on every desk, every home and in every pocket. As a consequence, in the last years software is having an epochal turn toward concurrency, distribution, interaction which is pushed by the evolution of hardware architectures and the growing of network availability. This calls for introducing further abstraction layers on top of those provided by classical mainstream programming paradigms, to tackle more effectively the new complexities that developers have to face in everyday programming. A convergence it is recognizable in the mainstream toward the adoption of the actor paradigm as a mean to unite object-oriented programming and concurrency. Nevertheless, we argue that the actor paradigm can only be considered a good starting point to provide a more comprehensive response to such a fundamental and radical change in software development. Accordingly, the main objective of this thesis is to propose Agent-Oriented Programming (AOP) as a high-level general purpose programming paradigm, natural evolution of actors and objects, introducing a further level of human-inspired concepts for programming software systems, meant to simplify the design and programming of concurrent, distributed, reactive/interactive programs. To this end, in the dissertation first we construct the required background by studying the state-of-the-art of both actor-oriented and agent-oriented programming, and then we focus on the engineering of integrated programming technologies for developing agent-based systems in their classical application domains: artificial intelligence and distributed artificial intelligence. Then, we shift the perspective moving from the development of intelligent software systems, toward general purpose software development. Using the expertise maturated during the phase of background construction, we introduce a general-purpose programming language named simpAL, which founds its roots on general principles and practices of software development, and at the same time provides an agent-oriented level of abstraction for the engineering of general purpose software systems.
APA, Harvard, Vancouver, ISO, and other styles
10

Jayatilleke, Gaya Buddhinath, and buddhinath@gmail com. "A Model Driven Component Agent Framework for Domain Experts." RMIT University. Computer Science and Information Technology, 2007. http://adt.lib.rmit.edu.au/adt/public/adt-VIT20080222.162529.

Full text
Abstract:
Industrial software systems are becoming more complex with a large number of interacting parts distributed over networks. Due to the inherent complexity in the problem domains, most such systems are modified over time to incorporate emerging requirements, making incremental development a suitable approach for building complex systems. In domain specific systems it is the domain experts as end users who identify improvements that better suit their needs. Examples include meteorologists who use weather modeling software, engineers who use control systems and business analysts in business process modeling. Most domain experts are not fluent in systems programming and changes are realised through software engineers. This process hinders the evolution of the system, making it time consuming and costly. We hypothesise that if domain experts are empowered to make some of the system changes, it would greatly ease the evolutionary process, thereby making the systems more effective. Agent Oriented Software Engineering (AOSE) is seen as a natural fit for modeling and implementing distributed complex systems. With concepts such as goals and plans, agent systems support easy extension of functionality that facilitates incremental development. Further agents provide an intuitive metaphor that works at a higher level of abstraction compared to the object oriented model. However agent programming is not at a level accessible to domain experts to capitalise on its intuitiveness and appropriateness in building complex systems. We propose a model driven development approach for domain experts that uses visual modeling and automated code generation to simplify the development and evolution of agent systems. Our approach is called the Component Agent Framework for domain-Experts (CAFnE), which builds upon the concepts from Model Driven Development and the Prometheus agent software engineering methodology. CAFnE enables domain experts to work with a graphical representation of the system , which is easier to understand and work with than textual code. The model of the system, updated by domain experts, is then transformed to executable code using a transformation function. CAFnE is supported by a proof-of-concept toolkit that implements the visual modeling, model driven development and code generation. We used the CAFnE toolkit in a user study where five domain experts (weather forecasters) with no prior experience in agent programming were asked to make changes to an existing weather alerting system. Participants were able to rapidly become familiar with CAFnE concepts, comprehend the system's design, make design changes and implement them using the CAFnE toolkit.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Agent Oriented Software Engineering"

1

Shehory, Onn, and Arnon Sturm, eds. Agent-Oriented Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-642-54432-3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Ciancarini, Paolo, and Michael J. Wooldridge, eds. Agent-Oriented Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/3-540-44564-1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Müller, Jörg P., and Franco Zambonelli, eds. Agent-Oriented Software Engineering VI. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11752660.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Luck, Michael, and Lin Padgham, eds. Agent-Oriented Software Engineering VIII. Berlin, Heidelberg: Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-79488-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Giunchiglia, Fausto, James Odell, and Gerhard Weiß, eds. Agent-Oriented Software Engineering III. Berlin, Heidelberg: Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/3-540-36540-0.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Müller, Jörg P., and Massimo Cossentino, eds. Agent-Oriented Software Engineering XIII. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-39866-7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Weyns, Danny, and Marie-Pierre Gleizes, eds. Agent-Oriented Software Engineering XI. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-22636-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Wooldridge, Michael J., Gerhard Weiß, and Paolo Ciancarini, eds. Agent-Oriented Software Engineering II. Berlin, Heidelberg: Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-70657-7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Odell, James, Paolo Giorgini, and Jörg P. Müller, eds. Agent-Oriented Software Engineering V. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/b105022.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Luck, Michael, and Jorge J. Gomez-Sanz, eds. Agent-Oriented Software Engineering IX. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-01338-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Agent Oriented Software Engineering"

1

Bussmann, Stefan, Paolo Ciancarini, Keith Decker, Michael Huhns, and Michael Wooldridge. "Agent-Oriented Software Engineering." In Intelligent Agents VI. Agent Theories, Architectures, and Languages, 248–49. Berlin, Heidelberg: Springer Berlin Heidelberg, 2000. http://dx.doi.org/10.1007/10719619_18.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Jennings, Nicholas R. "Agent-Oriented Software Engineering." In Multi-Agent System Engineering, 1–7. Berlin, Heidelberg: Springer Berlin Heidelberg, 1999. http://dx.doi.org/10.1007/3-540-48437-x_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Jennings, Nicholas R. "Agent-Oriented Software Engineering." In Multiple Approaches to Intelligent Systems, 4–10. Berlin, Heidelberg: Springer Berlin Heidelberg, 1999. http://dx.doi.org/10.1007/978-3-540-48765-4_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Cuesta, Pedro, Alma Gómez, and Juan Carlos González. "Agent Oriented Software Engineering." In Issues in Multi-Agent Systems, 1–31. Basel: Birkhäuser Basel, 2007. http://dx.doi.org/10.1007/978-3-7643-8543-9_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Petrie, Charles. "Agent-Based Software Engineering." In Agent-Oriented Software Engineering, 59–75. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/3-540-44564-1_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Huget, Marc-Philippe. "Agent Communication." In Agent-Oriented Software Engineering, 101–33. Berlin, Heidelberg: Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-642-54432-3_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Kendall, Elizabeth A. "Agent Software Engineering with Role Modelling." In Agent-Oriented Software Engineering, 163–69. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/3-540-44564-1_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Lind, Jürgen. "Issues in Agent-Oriented Software Engineering." In Agent-Oriented Software Engineering, 45–58. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/3-540-44564-1_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Huhns, Michael N. "Interaction-Oriented Programming." In Agent-Oriented Software Engineering, 29–44. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/3-540-44564-1_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Miles, Simon, Mike Joy, and Michael Luck. "Designing Agent-Oriented Systems by Analysing Agent Interactions." In Agent-Oriented Software Engineering, 171–83. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/3-540-44564-1_11.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Agent Oriented Software Engineering"

1

Bezek, Andraz, and Matjaz Gams. "Agent-oriented software engineering." In the second international joint conference. New York, New York, USA: ACM Press, 2003. http://dx.doi.org/10.1145/860575.860730.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Cunha, Rafhael, Diana Adamatti, and Cléo Billa. "Agent oriented software engineering." In MEDES '15: The 7th International Conference on Management of computational and collective IntElligence in Digital EcoSystems. New York, NY, USA: ACM, 2015. http://dx.doi.org/10.1145/2857218.2857226.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Chan, K., L. Sterling, and S. Karunasekera. "Agent-oriented software analysis." In 2004 Australian Software Engineering Conference. Proceedings. IEEE, 2004. http://dx.doi.org/10.1109/aswec.2004.1290454.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Parandoosh, Faezeh. "Evaluating Agent-Oriented Software Engineering Methodologies." In 2007 2nd International Workshop on Soft Computing Applications. IEEE, 2007. http://dx.doi.org/10.1109/sofa.2007.4318323.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Ciancarini, Paolo, and Michael Wooldridge. "Agent-oriented software engineering (workshop session)." In the 22nd international conference. New York, New York, USA: ACM Press, 2000. http://dx.doi.org/10.1145/337180.337833.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

"Requirements Engineering with Agent-Oriented Models." In 8th International Conference on Evaluation of Novel Software Approaches to Software Engineering. SciTePress - Science and and Technology Publications, 2013. http://dx.doi.org/10.5220/0004569302540259.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Silva, Carla, Jaelson Castro, Patrícia Tedesco, and Ismênia Silva. "Describing Agent-Oriented Design Patterns in Tropos." In Simpósio Brasileiro de Engenharia de Software. Sociedade Brasileira de Computação, 2005. http://dx.doi.org/10.5753/sbes.2005.23808.

Full text
Abstract:
The increasing interest in software agents and multi-agent systems has recently led to the development of new methodologies based on agent concepts. The Tropos framework offers an approach to guide the development of agent-oriented systems by using concepts based on requirements engineering. In this paper, we concentrate on the detailed design and implementation phases of the Tropos approach. In particular, we outline a method for choosing and applying agent-oriented design patterns. Moreover, we discuss how agent-oriented design patterns could be properly described, and provide some means of implementing them in a particular agent environment JADE. The proposed pattern description includes a template as well as three UML extended diagrams to capture the behaviour, structure and collaboration of each pattern. By doing so, we hope to improve the understanding and usage of agent-oriented design patterns. We apply the proposal to an e-News example.
APA, Harvard, Vancouver, ISO, and other styles
8

Clarke, D. A. W. "Commercial Experience with Agent-Oriented Software Engineering." In 2006 IEEE/WIC/ACM International Conference on Intelligent Agent Technology. IEEE, 2006. http://dx.doi.org/10.1109/iat.2006.48.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Leong, P., Chunyan Miao, and Bu-Sung Lee. "Agent oriented software engineering for grid computing." In Sixth IEEE International Symposium on Cluster Computing and the Grid. IEEE, 2006. http://dx.doi.org/10.1109/ccgrid.2006.1630897.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Zhongzhi Shi, Haijun Zhang, Yong Cheng, Yuncheng Jiang, Qiujian Sheng, and Zhikung Zhao. "MAGE: an agent-oriented software engineering environment." In Proceedings of the Third IEEE International Conference on Cognitive Informatics, 2004. IEEE, 2004. http://dx.doi.org/10.1109/coginf.2004.1327482.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Agent Oriented Software Engineering"

1

Striuk, Andrii M., and Serhiy O. Semerikov. The Dawn of Software Engineering Education. [б. в.], February 2020. http://dx.doi.org/10.31812/123456789/3671.

Full text
Abstract:
Designing a mobile-oriented environment for professional and practical training requires determining the stable (fundamental) and mobile (technological) components of its content and determining the appropriate model for specialist training. In order to determine the ratio of fundamental and technological in the content of software engineers’ training, a retrospective analysis of the first model of training software engineers developed in the early 1970s was carried out and its compliance with the current state of software engineering development as a field of knowledge and a new the standard of higher education in Ukraine, specialty 121 “Software Engineering”. It is determined that the consistency and scalability inherent in the historically first training program are largely consistent with the ideas of evolutionary software design. An analysis of its content also provided an opportunity to identify the links between the training for software engineers and training for computer science, computer engineering, cybersecurity, information systems and technologies. It has been established that the fundamental core of software engineers’ training should ensure that students achieve such leading learning outcomes: to know and put into practice the fundamental concepts, paradigms and basic principles of the functioning of language, instrumental and computational tools for software engineering; know and apply the appropriate mathematical concepts, domain methods, system and object-oriented analysis and mathematical modeling for software development; put into practice the software tools for domain analysis, design, testing, visualization, measurement and documentation of software. It is shown that the formation of the relevant competencies of future software engineers must be carried out in the training of all disciplines of professional and practical training.
APA, Harvard, Vancouver, ISO, and other styles
2

Tkachuk, Viktoriia V., Vadym P. Shchokin, and Vitaliy V. Tron. The Model of Use of Mobile Information and Communication Technologies in Learning Computer Sciences to Future Professionals in Engineering Pedagogy. [б. в.], November 2018. http://dx.doi.org/10.31812/123456789/2668.

Full text
Abstract:
Research goal: the research is aimed at developing a model of use of mobile ICT in learning Computer Sciences to future professionals in Engineering Pedagogy. Object of research is the model of use of mobile ICT in learning Computer Sciences to future professionals in Engineering Pedagogy. Results of the research: the developed model of use of mobile ICT as tools of learning Computer Sciences to future professionals in Engineering Pedagogy is based on the competency-based, person-centered and systemic approaches considering principles of vocational education, general didactic principles, principles of Computer Science learning, and principles of mobile learning. It also takes into account current conditions and trends of mobile ICT development. The model comprises four blocks: the purpose-oriented block, the content-technological block, the diagnostic block and the result-oriented block. According to the model, the learning content of Computer Sciences consists of 5 main units: 1) Fundamentals of Computer Science; 2) Architecture of Modern Computers; 3) Fundamentals of Algorithmization and Programming; 4) Software of Computing Systems; 5) Computer Technologies in the Professional Activity of Engineer-pedagogues.
APA, Harvard, Vancouver, ISO, and other styles
3

Markova, Oksana M., Serhiy O. Semerikov, Andrii M. Striuk, Hanna M. Shalatska, Pavlo P. Nechypurenko, and Vitaliy V. Tron. Implementation of cloud service models in training of future information technology specialists. [б. в.], September 2019. http://dx.doi.org/10.31812/123456789/3270.

Full text
Abstract:
Leading research directions are defined on the basis of self-analysis of the study results on the use of cloud technologies in training by employees of joint research laboratory “Сloud technologies in education” of Kryvyi Rih National University and Institute of Information Technology and Learning Aids of the NAES of Ukraine in 2009-2018: cloud learning technologies, cloud technologies of blended learning, cloud-oriented learning environments, cloud-oriented methodological systems of training, the provision of cloud-based educational services. The ways of implementation SaaS, PaaS, IaaS cloud services models which are appropriate to use in the process of studying the academic disciplines of the cycles of mathematical, natural science and professional and practical training of future specialists in information technology are shown, based on the example of software engineering, computer science and computer engineering. The most significant advantages of using cloud technologies in training of future information technology specialists are definite, namely, the possibility of using modern parallel programming tools as the basis of cloud technologies. Conclusions are drawn; the direction of further research is indicated: designing a cloud-oriented learning environment for future specialists in computer engineering, identifying trends in the development of cloud technologies in the professional training and retraining of information technology specialists, developing a methodology for building the research competencies of future software engineering specialists by using cloud technologies.
APA, Harvard, Vancouver, ISO, and other styles
4

Raja, Rameez Ali, Vidushi Toshniwal, and Rodrigo Salgado. GIS-Based Geotechnical Database for Collaborative GIS. Purdue University, 2023. http://dx.doi.org/10.5703/1288284317637.

Full text
Abstract:
INDOT spends at least 8 million dollars annually on geotechnical site investigations, not including the amounts spent by contractors. The laborious and costly job of data collection in geotechnical practice requires the efficient storing and organizing of this valuable data to develop correlations and trends in spatially varying geotechnical data. INDOT currently uses gINT software for managing geotechnical data and ArcGIS for storing boring logs and geotechnical reports. The INDOT geotechnical office is pursuing means to improve the efficiency of their operations by developing a GIS-based geotechnical database for secure storage, easy retrieval, and flexible sharing of geotechnical data to enhance decision making. SPR-4616 is the first step towards the development of a geotechnical data management system in which important decisions on the components and structure of the database were made. The report presents a detailed conceptual layout for the development of a geotechnical database following an object-oriented programming approach. The report discusses in detail the geotechnical applications, the field, laboratory, and verification tests that will be included in the database. The geotechnical variables required to perform the engineering analysis in designing specific applications are logically linked with the geotechnical tests from which they are obtained. Lastly, a detailed layout of the proposed database structure and a user workflow example is provided in the report and can serve as a guide during the development of the database system.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Agent Oriented Software Engineering' for particular source types:
Journal articles Dissertations / Theses Books
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!

To the bibliography