The Object Management Group's (OMG) Model Driven Architecture (MDA) strategy envisages a world where models play a more direct role in software production, being amenable to manipulation and transformation by machine. Model Driven Engineering (MDE) is wider in scope than MDA. MDE combines process and analysis with architecture. This article sets out a framework for model driven engineering, which can be used as a point of reference for activity in this area. It proposes an organisation of the modelling 'space' and how to locate models in that space. It discusses different kinds of mappings between models. It explains why process and architecture are tightly connected. It discusses the importance and nature of tools. It identifies the need for defining families of languages and transformations, and for developing techniques for generating/configuring tools from such definitions. It concludes with a call to align metamodelling with formal language engineering techniques.

Model Driven Engineering

Emergence: From Chaos to Order by John H. Holland .

This book provides an in-depth description of event-based systems, covering topics ranging from local event matching and distributed event forwarding algorithms, through a practical discussion of software engineering issues raised by the event-based style, to state-of-the-art research in event-based systems like composite event detection and security. The authors offer a comprehensive overview, and show the power of event-based architectures in modern system design, encouraging professionals to exploit this technique in next generation large-scale distributed applications like information dissemination, network monitoring, enterprise application integration, or mobile systems.

/pdf/distributed-event-based-systems-33fttbtql7.pdf

Distributed event-based systems

Beginning a research project can be both daunting and exciting for all researchers, whether experienced or novice. This chapter highlights the crucial stage of creating a research project from a well-developed research question and appropriate methodology that best addresses the question. This beginning stage has a significant impact on the overall study, including the soundness of the results. This chapter explores strategies for conceiving of, and designing, a research project that can both be achievable and contribute to scholarship. This chapter draws on examples from two of the author’s own studies of interpreting in educational and legal settings, to more closely examine the many considerations required for an effective research project.

Designing a research project

Traceability--the ability to follow the life of software artifacts--is a topic of great interest to software developers in general, and to requirements engineers and model-driven developers in particular. This article aims to bring those stakeholders together by providing an overview of the current state of traceability research and practice in both areas. As part of an extensive literature survey, we identify commonalities and differences in these areas and uncover several unresolved challenges which affect both domains. A good common foundation for further advances regarding these challenges appears to be a combination of the formal basis and the automated recording opportunities of MDD on the one hand, and the more holistic view of traceability in the requirements engineering domain on the other hand.

https://link.springer.com/content/pdf/10.1007%2Fs10270-009-0145-0.pdf

A survey of traceability in requirements engineering and model-driven development

Requirements engineering is an important phase in a system’s life cycle. When poorly performed, various problems may occur, such as failures, cost overrun and delays. The increasing complexity of systems makes requirements engineering activities both more important and more difficult. Model-driven engineering, in which models are the main artifact during system development, is an emergent approach that tries to address system complexity by the intense use of models. This article proposes a model-driven approach to requirements engineering based on SysML Requirements and Use Case Diagrams. The main advantages are that user requirements are graphically modeled, their relationships are explicitly mapped, and system decomposition is considered in the early system development activities. In addition, requirements traceability is enhanced by using the SysML Requirements tables. The approach is illustrated by a list of user requirements for a road traffic management system.

Model-Driven User Requirements Specification using SysML

User requirements modeling and analysis of software-intensive systems

A modular Petri net to modeling and scenario analysis of a network of road traffic signals

Este artigo apresenta algumas vantagens das metodologias ageis para desenvolver software em relacao as metodologias tradicionais. Em particular sao apresentadas as principais caracteristicas e as praticas das metodologias ageis Extreme Programming e Scrum. Tambem sao feitas comparacoes com as metodologias tradicionais, procurando enfatizar que as metodologias ageis sao baseadas em pessoas e nao em processos e planejamentos. Finalmente sao apresentadas as principais vantagens e desvantagens da Extreme Programming e da Scrum. Tambem sao apresentados alguns resultados empiricos do uso de metodologias ageis.

/pdf/metodologias-ageis-extreme-programming-e-scrum-para-o-39aikwfqrn.pdf

Metodologias Ágeis Extreme Programming e Scrum para o Desenvolvimento de Software

Personality of software engineering professionals has been a continuous element of interest in academic research. Researchers have applied different models of personality analysis in various software engineering areas to identify improvement points, to promote job satisfaction and to better organize teams. This paper aims to conduct a study, by means of a systematic literature review (SLR), to evaluate personality models applied in software engineering and to understand how human personality influences professional’s work. Three main models, most frequently used, were identified (MBTI, BIG 5 and FFM) to evaluate software engineering professionals. There is evidence of the influence of personality on the activities performed. However, some results have suggested that the study of personality is not an easy task to be performed, because there are contradictions in findings that challenges the validity of studies.

Michel S. Soares

Papers

Model-Driven User Requirements Specification using SysML

User requirements modeling and analysis of software-intensive systems

A modular Petri net to modeling and scenario analysis of a network of road traffic signals

Metodologias Ágeis Extreme Programming e Scrum para o Desenvolvimento de Software

Influence of Human Personality in Software Engineering - A Systematic Literature Review.