Academic literature on the topic 'Aspect-oriented software development (AOSD)'

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

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources 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.

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

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
More sources

Dissertations / Theses on the topic "Aspect-oriented software development (AOSD)"

1

Rodrigues, Antonielly Garcia. "Desenvolvimento de software orientado a temas: um estudo de caso." Universidade de São Paulo, 2006. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-06042010-110211/.

Full text
Abstract:
O Paradigma Orientado a Objetos tem sido atualmente a abordagem dominante de desenvolvimento de software. Contudo, ela sofre da Tirania da Decomposição Dominante, pois não permite uma modularização adequada da implementação relativa a interesses estruturais. Como consequência, a implementação relativa a cada interesse estrutural fica espalhada pelos módulos do programa e entrelaçada com a implementação relativa a outros interesses estruturais. Outras abordagens de desenvolvimento de software, como o Desenvolvimento de Software Orientado a Aspectos com AspectJ e a Separação Multidimensional de
APA, Harvard, Vancouver, ISO, and other styles
2

FIGUEIREDO, EDUARDO MAGNO LAGES. "A QUANTITATIVE APPROACH TO ASPECT ORIENTED SOFTWARE DEVELOPMENT." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2006. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=8625@1.

Full text
Abstract:
COORDENAÇÃO DE APERFEIÇOAMENTO DO PESSOAL DE ENSINO SUPERIOR<br>FUNDAÇÃO PADRE LEONEL FRANCA<br>O desenvolvimento de software orientado a aspectos é um paradigma recente que introduz novas abstrações e mecanismos com o objetivo de melhorar a modularidade de interesses que se espalham pelo sistema. Entretanto, a satisfação de atributos de qualidade em sistemas orientados a aspectos não é tarefa simples e a utilização equivocada destas novas abstrações pode resultar em efeitos colaterais relacionados a princípios importantes da Engenharia de Software, tais como elevado acoplamento, baixa c
APA, Harvard, Vancouver, ISO, and other styles
3

Rodrigues, António Pedro Lopes Borba. "Aspect-oriented domain analysis." Master's thesis, FCT - UNL, 2008. http://hdl.handle.net/10362/1777.

Full text
Abstract:
Dissertação de Mestrado em Engenharia Informática<br>Domain analysis (DA) consists of analyzing properties, concepts and solutions for a given domain of application. Based on that information, decisions are made concerning the software development for future application within that domain. In DA, feature modeling is used to describe common and variable requirements for software systems. Nevertheless, they show a limited view of the domain. In the mean time, requirement approaches can be integrated to specify the domain requirements. Among them, we have viewpoint oriented approaches that stand
APA, Harvard, Vancouver, ISO, and other styles
4

Piveta, Eduardo Kessler. "Improving the search for refactoring opportunities on object-oriented and aspect-oriented software." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2009. http://hdl.handle.net/10183/15651.

Full text
Abstract:
Refatoração é o processo de melhorar o projeto de sistemas de software sem modificar seu comportamento externamente observável. O processo de refatoração pode auxiliar a incrementalmente melhorar a qualidade de software de um sistema através da aplicação de transformações que preservam comportamento chamadas de padrões de refatoração. O principal objetivo da pesquisa que esta tese descreve é prover um processo detalhado para refatoração, incluindo mecanismos para (i) seleção e criação de modelos de qualidade, padrões de refatoração e funções heurísticas, (ii) a busca e priorização de oportunid
APA, Harvard, Vancouver, ISO, and other styles
5

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
APA, Harvard, Vancouver, ISO, and other styles
6

Vaira, Žilvinas. "Investigation, Improvement and Development of Aspect-Oriented Design Patterns." Doctoral thesis, Lithuanian Academic Libraries Network (LABT), 2012. http://vddb.laba.lt/obj/LT-eLABa-0001:E.02~2012~D_20120426_160722-02556.

Full text
Abstract:
Software systems are permanently changed in order to meet new requirements and to adapt them to permanently changing technology. Design modularity decouples design concerns that probably can be changed and in this way facilitates further system changes. Unfortunately, some design concerns, called crosscutting concerns, cannot be modularized using traditional modularization methods and techniques. Modularization of crosscutting concerns is the research subject of the new emerging software engineering paradigm, aspect-oriented analysis and design. However, this paradigm is still not enough matur
APA, Harvard, Vancouver, ISO, and other styles
7

Breu, Silvia. "Mining and tracking in evolving software." Thesis, University of Cambridge, 2013. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.607860.

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

Basch, Mark Alan. "Incorporating Aspects into the Software Development Process in Context of Aspect-Oriented Programming." UNF Digital Commons, 2002. http://digitalcommons.unf.edu/etd/112.

Full text
Abstract:
Aspect-oriented programming is a relatively new approach to programming that is design to resolve issues of separation of concerns. Rather than focusing on commonality of objects, as in object-oriented programming, aspect –oriented programming focuses on commonality of concerns, or more precisely as described by experts in the field, of "cross-cutting concerns." These are aspects that cut across different modules of a program, such as security and authentication issues. While much research in the area has focused on developing programming languages, little attention has been given to dealing w
APA, Harvard, Vancouver, ISO, and other styles
9

Bodin, Joakim. "Verifikation av verktyget aspect analyzer." Thesis, Linköping University, Department of Computer and Information Science, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-1985.

Full text
Abstract:
<p>Rising complexity in the development of real-time systems has made it crucial to have reusable components and a more flexible way of configuring these components into a coherent system. Aspect-oriented system development (AOSD) is a technique that allows one to put a system’s crosscutting concerns into"modules"that are called aspects. Applying AOSD in real-time and embedded system development one can expect reductions in the complexity of the system design and development. </p><p>A problem with AOSD in its current form is that it does not support predictability in the time domain. Hence, in
APA, Harvard, Vancouver, ISO, and other styles
10

Uhlin, Pernilla. "Aspect Analyzer: Ett verktyg för automatiserad exekveringstidsanalys av komponenter och aspekter." Thesis, Linköping University, Department of Computer and Information Science, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-1914.

Full text
Abstract:
<p>The increasing complexity in the development of a configurable real-time system has emerged new principles of software techniques, such as aspect-oriented software development and component-based software development. These techniques allow encapsulation of the system's crosscutting concerns and increase the modularity of the software. The properties of a component that influences the systems performance or semantics are specified separately in entities called aspects, while basic functionality of the property still remains in the component. </p><p>When building a real-time system, differen
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Aspect-oriented software development (AOSD)"

1

Netherlands) International Conference on Aspect-Oriented Software Development (1st 2002 Enschede. AOSD 2002: 1st International Conference on Aspect-Oriented Software Development : Enschede, the Netherlands, April 22-26, 2002 : conference proceedings. ACM Press, 2002.

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

E, Filman Robert, ed. Aspect oriented software development. Addison-Wesley, 2005.

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

Mehmet, Akşit, ed. Transactions on aspect-oriented software development. Springer-Verlag, 2007.

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

Mehmet, Akşit, ed. Transactions on aspect-oriented software development. Springer-Verlag, 2007.

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

Leavens, Gary T. Transactions on Aspect-Oriented Software Development IX. Springer Berlin Heidelberg, 2012.

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

Katz, Shmuel, Mira Mezini, Christine Schwanninger, and Wouter Joosen, eds. Transactions on Aspect-Oriented Software Development VIII. Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-22031-9.

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

Rashid, Awais, and Mehmet Aksit, eds. Transactions on Aspect-Oriented Software Development IV. Springer Berlin Heidelberg, 2007. http://dx.doi.org/10.1007/978-3-540-77042-8.

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

Katz, Shmuel, Mira Mezini, and Jörg Kienzle, eds. Transactions on Aspect-Oriented Software Development VII. Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-16086-8.

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

Chiba, Shigeru, Éric Tanter, Erik Ernst, and Robert Hirschfeld, eds. Transactions on Aspect-Oriented Software Development XII. Springer Berlin Heidelberg, 2015. http://dx.doi.org/10.1007/978-3-662-46734-3.

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

Leavens, Gary T., Shigeru Chiba, and Éric Tanter, eds. Transactions on Aspect-Oriented Software Development X. Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-36964-3.

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

Book chapters on the topic "Aspect-oriented software development (AOSD)"

1

Van Landuyt, Dimitri, Steven Op de beeck, Eddy Truyen, and Pierre Verbaeten. "Building a Digital Publishing Platform Using AOSD." In Transactions on Aspect-Oriented Software Development VIII. Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-22031-9_6.

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

Sutton, Stanley M. "Aspect-Oriented Software Development and Software Process." In Unifying the Software Process Spectrum. Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11608035_17.

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

Kienzle, Jörg, Wisam Al Abed, Franck Fleurey, Jean-Marc Jézéquel, and Jacques Klein. "Aspect-Oriented Design with Reusable Aspect Models." In Transactions on Aspect-Oriented Software Development VII. Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-16086-8_8.

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

Rashid, Awais, Alessandro Garcia, and Ana Moreira. "Aspect-Oriented Software Development Beyond Programming." In Lecture Notes in Computer Science. Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11763864_46.

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

McNeile, Ashley, and Ella Roubtsova. "Aspect-Oriented Development Using Protocol Modeling." In Transactions on Aspect-Oriented Software Development VII. Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-16086-8_4.

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

Lee, Seung-Hyung, and Young-Jae Song. "Aspect Oriented Software Development Using Requirement Engineering." In Lecture Notes in Electrical Engineering. Springer Netherlands, 2011. http://dx.doi.org/10.1007/978-94-007-2911-7_19.

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

Ciraci, Selim, Wilke Havinga, Mehmet Aksit, Christoph Bockisch, and Pim van den Broek. "A Graph-Based Aspect Interference Detection Approach for UML-Based Aspect-Oriented Models." In Transactions on Aspect-Oriented Software Development VII. Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-16086-8_9.

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

Garg, Rachit Mohan, and Deepak Dahiya. "An Aspect Oriented Component Based Model Driven Development." In Software Engineering and Computer Systems. Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-22203-0_44.

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

Holzer, Adrian, Lukasz Ziarek, K. R. Jayaram, and Patrick Eugster. "Abstracting Context in Event-Based Software." In Transactions on Aspect-Oriented Software Development IX. Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-35551-6_4.

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

Katz, Shmuel. "Aspect Categories and Classes of Temporal Properties." In Transactions on Aspect-Oriented Software Development I. Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11687061_4.

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

Conference papers on the topic "Aspect-oriented software development (AOSD)"

1

Haupt, Michael. "Session details: Modularity in systems software." In AOSD '12: Aspect-oriented Software Development. ACM, 2012. http://dx.doi.org/10.1145/3256435.

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

Gabriel, Richard P. "Session details: Keynote address 1." In AOSD '12: Aspect-oriented Software Development. ACM, 2012. http://dx.doi.org/10.1145/3256438.

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

Sullivan, Kevin. "Session details: Keynote address 3." In AOSD '12: Aspect-oriented Software Development. ACM, 2012. http://dx.doi.org/10.1145/3256439.

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

Tanter, Éric. "Session details: Keynote address 5." In AOSD '12: Aspect-oriented Software Development. ACM, 2012. http://dx.doi.org/10.1145/3256441.

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

Haupt, Michael. "Session details: Keynote address 4." In AOSD '12: Aspect-oriented Software Development. ACM, 2012. http://dx.doi.org/10.1145/3256440.

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

Haupt, Michael. "Session details: Invited talk." In AOSD '12: Aspect-oriented Software Development. ACM, 2012. http://dx.doi.org/10.1145/3256406.

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

Lohmann, Daniel. "Session details: From silicon to the ground." In AOSD '12: Aspect-oriented Software Development. ACM, 2012. http://dx.doi.org/10.1145/3256407.

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

Borchert, Christoph. "Session details: From the ground to heaven." In AOSD '12: Aspect-oriented Software Development. ACM, 2012. http://dx.doi.org/10.1145/3256408.

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

Masuhara, Hidehiko. "Session details: Interference." In AOSD '12: Aspect-oriented Software Development. ACM, 2012. http://dx.doi.org/10.1145/3256433.

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

Joosen, Wouter. "Session details: Debugging." In AOSD '12: Aspect-oriented Software Development. ACM, 2012. http://dx.doi.org/10.1145/3256431.

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

Reports on the topic "Aspect-oriented software development (AOSD)"

1

Gurieiev, Viktor, Yulii Kutsan, Anna Iatsyshyn, et al. Simulating Systems for Advanced Training and Professional Development of Energy Specialists in Power Sector. [б. в.], 2020. http://dx.doi.org/10.31812/123456789/4456.

Full text
Abstract:
The crisis of the system of professional development and personnel training in the energy sector exists not only in Ukraine but also all over the world. The article describes the concept of development and functioning of the industry system of personnel training in the energy sector of Ukraine. The importance of using modern web-oriented technologies to improve the skills of operational and dispatching personnel in the energy sector of Ukraine is substantiated. The meth- ods of distributed power system operating modes modelling are presented. De- velopment and software tools for the constructi
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!