Littérature scientifique sur le sujet « Software methodologies and engineering »

The size and complexity of industrial strength software systems are constantly increasing. This means that the task of managing a large software project is becoming even more challenging, especially in light of high turnover of experienced personnel. Software clustering approaches can help with the task of understanding large, complex software systems by automatically decomposing them into smaller, easier-to-manage subsystems. The main objective of this paper is to identify important research directions in the area of software clustering that require further attention in order to develop more effective and efficient clustering methodologies for software engineering. To that end, we first present the state of the art in software clustering research. We discuss the clustering methods that have received the most attention from the research community and outline their strengths and weaknesses. Our paper describes each phase of a clustering algorithm separately. We also present the most important approaches for evaluating the effectiveness of software clustering.

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.

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.

Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2019
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 157-158).
As the software industry evolves, various software development methodologies have become widely used in the industry. Most commonly used methodologies are Waterfall and Agile, along with less known alternatives, such as spiral and hybrid methodologies. When deciding on the methodologies, program managers tend to choose one based on the team preference or historical pattern. However, each software project is unique in its own way and has characteristics that are distinct from the previous projects the team has worked on. For each project, it is crucial to adopt a suitable methodology that help teams to produce the software that meets customer needs within schedule and budget constraints. Therefore, a practical question for every program manager is "How to find a suitable methodology for a specific project?" This thesis is aimed to help program managers answer this question.
We first explore how to evaluate each software development methodology based on the two-level decomposition of software development methodology, then analyze the project characteristics based on the situational inputs in three categories: scope, schedule and budget. Thereafter, the thesis proposes a framework to match software development methodology with a specific project. This thesis extends West's work in [1] by introducing a systems approach to assess a software project and a framework to determine the degree of compatibility between a methodology and a software project. The benefits of leveraging the systems approach are: ** The decomposition of methodologies highlights which elements in a methodology play key roles of providing the advantageous ilities over other methodologies. ** The decomposition of a project enables a program manager to evaluate the input elements of a project and gain a systems view on the project characteristics.
The framework allows program managers to compare several candidate methodologies and choose the most compatible one using the mismatch scores, weighted summations that indicate the incompatibilities between the candidate methodologies and the project based on the ilities ranking decided by the program managers. To demonstrate how to use this framework for a real world project, an example project is given. The detailed steps of calculating the mismatch scores between three methodologies and the project are shown. The proposed framework can be used as a guideline for program managers to find methodologies for different projects with the information gathered from project stakeholders. This framework has some limitations. A major one is that, since the framework is quantitative based, induvial experience is used to evaluate the elements of methodologies and factors of projects.
Further work can be done to improve the objectivity of the evaluation through the surveys of industrial experts and members of teams adopting this framework.
by Yuqing Ke.
S.M. in Engineering and Management
S.M.inEngineeringandManagement Massachusetts Institute of Technology, System Design and Management Program

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.

Mathematical models have been used to capture the behaviour of biological systems, from low-level biochemical reactions to multi-scale whole-organ models. Models are typically based on experimentally-derived data, attempting to reproduce the observed behaviour through mathematical constructs, e.g. using Ordinary Differential Equations (ODEs) for spatially-homogeneous systems. These models are developed and published as mathematical equations, yet are of such complexity that they necessitate computational simulation. This computational model development is often performed in an ad hoc fashion by modellers who lack extensive software engineering experience, resulting in brittle, inefficient model code that is hard to extend and reuse. Several Domain Specific Languages (DSLs) exist to aid capturing such biological models, including CellML and SBML; however these DSLs are designed to facilitate model curation rather than simplify model development. We present research into the application of techniques from software engineering to this domain; starting with the design, development and implementation of a DSL, termed Ode, to aid the creation of ODE-based biological models. This introduces features beneficial to model development, such as model verification and reproducible results. We compare and contrast model development to large-scale software development, focussing on extensibility and reuse. This work results in a module system that enables the independent construction and combination of model components. We further investigate the use of software engineering processes and patterns to develop complex modular cardiac models. Model simulation is increasingly computationally demanding, thus models are often created in complex low-level languages such as C/C++. We introduce a highly-efficient, optimising native-code compiler for Ode that generates custom, model-specific simulation code and allows use of our structured modelling features without degrading performance. Finally, in certain contexts the stochastic nature of biological systems becomes relevant. We introduce stochastic constructs to the Ode DSL that enable models to use Stochastic Differential Equations (SDEs), the Stochastic Simulation Algorithm (SSA), and hybrid methods. These use our native-code implementation and demonstrate highly-efficient stochastic simulation, beneficial as stochastic simulation is highly computationally intensive. We introduce a further DSL to model ion channels declaratively, demonstrating the benefits of DSLs in the biological domain. This thesis demonstrates the application of software engineering methodologies, and in particular DSLs, to facilitate the development of both deterministic and stochastic biological models. We demonstrate their benefits with several features that enable the construction of large-scale, reusable and extensible models. This is accomplished whilst providing efficient simulation, creating new opportunities for biological model development, investigation and experimentation.

The computer industry has a poor record of system development using the traditional life-cycle approach. The main cause of user dissatisfaction is the unacceptably large amount of time between specification and delivery of a system. In addition, users have limited opportunity to influence how the system will look when implemented once development has commenced. With the advent of 4GLs, system development using a prototyping approach has become a viable option. This has reduced the development tlme significantly and, together with the use of prototyping, has allowed users to become more involved in the development process. However, this change in the development process has meant that often the use of an accepted methodology/system life cycle has been ignored or altered. This has resulted in systems where the definition-of-requirements phase was often fast-tracked or omitted totally and the system documentation is insufficient for effective maintenance. Thus, this approach has not proved to be as successful as expected. However, the opportunities that prototyping offers should not be discarded because of the use of inappropriate software development methodologies, languages or tools. This study seeks to identify factors that may influence the success or failure of a prototyping project and to assess the importance of any developmentmethodologies being used. Information was gathered via interviews, questionnaires and, where deemed necessary, the reviewing of development procedures used. Conclusions have been drawn from data gathered from various organisations in Western Australia that have used prototyping for a number of projects, thus, suggesting a refinement of the development process. Two main areas appeared to affect the success of a software development project. The first is the lack of flexibility in the methodology used and inappropriateness of the development tools and languages. The second is insufficient requirements analysis. The results indicate that a methodology is required that provides a good framework, but is flexible enough to handle different types and sizes of project. It should specifically address prototyping and include guidelines as to how to select the most suitable prototyping approach for each project. It should contain examples of different deliverables and various development cycles appropriate for each type of prototyping. There should be automated tools available to handle documentation and code generation where possible. The development of a methodology with the above characteristics is required if the advantages of prototyping are to be maximised in the future.

Context: Over the recent years, ‘Lean Software Development’ (LSD) has been emerging as a significant practice in the Software Industry. The inherent nature of ‘Lean’ to efficiently handle frequently changing customer needs by minimizing ‘Waste’ is a major success factor in practicing it in the context of ‘Software Engineering’. In simple words, Lean Software Development is the true translation of Lean Manufacturing and Lean IT principles to Software Engineering. This work presents an in-depth analysis on the implication of lean methodologies from both ‘State of Art’ and ‘State of Practice’ in the context of Software Engineering. Objectives: The prime objective of the study is to investigate what methodologies were considered & adopted under lean philosophy and to present relevant evidence on the implication of lean methodologies in reference to what defines ‘lean’ in Software Engineering. An extensive literature review was aimed to find the existing challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were employed by various software organizations to appease their negative impact. Industrial interviews were conducted by interviewing lean experts, with a motive to find the current state of lean implementation in software industry. The outcomes from the systematic literature review (State of Art) and the industry (State of Practice) are comparatively analysed to explore the similarities and differences on the state of lean implication. Finally, a set of guidelines are recommended that would benefit an Industrial Practitioner/Stakeholder/Academic Researcher in practicing the appropriate lean methodology in the context of software engineering. Methods: We conducted a ‘Systematic literature review’ (SLR) by systematically analyzing relevant studies and then interviewed industrial experts to validate our findings. The systematic literature review was conducted according to the guidelines proposed by Dr. Barbara Kitchenham stated in ‘Guidelines for performing Systematic Literature Reviews’ article. The thorough review helped us in identifying various challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were practiced in the context of software engineering. The associated benefits of practicing the lean methodologies are also presented. The extensive review included peer reviewed articles from electronic databases such as IEEE Explore, Inspec, Scopus and ISI. In addition to this, we conducted snowball sampling on the references of the selected articles to avoid the potential risk of losing relevant and valuable information. Also, other potential sources of information such as books, theses/dissertations, white papers and website/blog articles are included as a part of Grey Literature. In this study, the articles related to the implication of lean methodologies in the context of software engineering were considered. The review included 72 primary studies published between 1993 and 2012. The primary studies were selected based on the following criteria: If they presented the challenging factors that negatively influenced the success of software projects. If they depicted the implication of lean mitigation methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) that appeased the negative impact of the identified challenging factors that hampered the success of software projects. If they depicted the implication of lean methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) in general or for a specific development/ Management/ Maintenance improvement activities that lead to the success of software projects in the context of software engineering. If they presented the benefits of practicing lean methodologies in the context of software engineering. The study quality assessment was done based on the quality criteria defined in the ‘Quality assessment criteria checklist’. The data such as Article ID, Article Title, Literature type (Peer- reviewed, Non-peer reviewed), Context of validation of the lean methodology (Industry/Academia), Subjects considered for the study (Researchers/students, Industrial practitioners), Type of article publication (Conference/ Journal/ Books/ Thesis Reports/ Doctoral dissertations/ Other), Research method used in the study (Case Study/ Experiment/ Experience Report/ Not stated/ Secondary Data Analysis/ Literature Review), Context of conducting the research (Industry/ Academia/ Not stated/ Both), Context of validation of the study (Strong/ Medium/ Weak), Publication date & year, Source of the publication, are extracted as a part of Quantitative analysis. The secondary data analysis for both ‘State of Art’ (Systematic literature review) and ‘State of Practice’ (Industry) was carried by performing a generic data analysis designed to answer our research questions. The more specific data such as the challenging factors that negatively influenced the success of software projects, the type of lean contribution presented i.e., the methodology being a Tool, Technique, Practice, Principal, Process or a Method, along with the benefits associated on their implication that helped us to answer our research questions are extracted as a part of qualitative analysis from the selected studies. The industrial interviews were conducted by interviewing potential lean experts who had decent experience in lean software development, to find the current state of lean implication in the software industry. In the end, a comparative analysis was performed to clearly understand the state of convergence and divergence between the results from extensive literature review and the industry with respect to the implication of lean methodologies in the context of software engineering. Results: A total of 72 primary articles were selected for data extraction. 56 articles were selected from the electronic databases that clearly depicted lean implementation in the context of software engineering. 9 articles were selected by conducting snowball sampling i.e. by scrutinizing the references of the selected primary studies and finally the grey literature resulted in 7 articles. Most of the articles discussed about lean implication in the context of software engineering. The depicted lean methodologies were validated in either Industry or Academia. A few articles depicted regarding lean principles and their benefits in the context of software engineering. Most of the selected articles in our study were peer- reviewed. Peer reviewing is a process of evaluating one’s work or performance by an expert in the same field in order to maintain or enhance the quality of work or performance in the particular field. This indicates that the articles considered for data extraction have been reviewed by potential experts in the research domain. Conclusions: This study provided a deeper insight into lean implication in the context of software engineering. The aim of the thesis is to find the challenging factors that negatively influenced the success of software projects. A total of 54 challenges were identified from the literature review. The 72 primary articles selected from various resources yielded 53 lean methodologies. The lean methodologies were grouped into Principles, practices, tools and methods. Mapping between the identified challenges and the mitigation lean methodologies is presented. Industrial interviews were conducted to find the current state of lean implication in software engineering. A total of 30 challenges were identified from the industry. A total of 40 lean methodologies were identified from the interviews. Comparative analysis was done to find the common challenges and mitigation lean methodologies between the State of art and State of practice. Based on the analysis a set of guidelines are presented at the end of the document. The guidelines benefit an industrial practitioner in practicing the appropriate lean methodology. Keywords: Lean Methodology, Lean software development, lean software management, lean software engineering, Systematic literature review, literature review.
Context: Over the recent years, ‘Lean Software Development’ (LSD) has been emerging as a significant practice in the Software Industry. The inherent nature of ‘Lean’ to efficiently handle frequently changing customer needs by minimizing ‘Waste’ is a major success factor in practicing it in the context of ‘Software Engineering’. In simple words, Lean Software Development is the true translation of Lean Manufacturing and Lean IT principles to Software Engineering. This work presents an in-depth analysis on the implication of lean methodologies from both ‘State of Art’ and ‘State of Practice’ in the context of Software Engineering. Objectives: The prime objective of the study is to investigate what methodologies were considered & adopted under lean philosophy and to present relevant evidence on the implication of lean methodologies in reference to what defines ‘lean’ in Software Engineering. An extensive literature review was aimed to find the existing challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were employed by various software organizations to appease their negative impact. Industrial interviews were conducted by interviewing lean experts, with a motive to find the current state of lean implementation in software industry. The outcomes from the systematic literature review (State of Art) and the industry (State of Practice) are comparatively analysed to explore the similarities and differences on the state of lean implication. Finally, a set of guidelines are recommended that would benefit an Industrial Practitioner/Stakeholder/Academic Researcher in practicing the appropriate lean methodology in the context of software engineering. Methods: We conducted a ‘Systematic literature review’ (SLR) by systematically analyzing relevant studies and then interviewed industrial experts to validate our findings. The systematic literature review was conducted according to the guidelines proposed by Dr. Barbara Kitchenham stated in ‘Guidelines for performing Systematic Literature Reviews’ article. The thorough review helped us in identifying various challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were practiced in the context of software engineering. The associated benefits of practicing the lean methodologies are also presented. The extensive review included peer reviewed articles from electronic databases such as IEEE Explore, Inspec, Scopus and ISI. In addition to this, we conducted snowball sampling on the references of the selected articles to avoid the potential risk of losing relevant and valuable information. Also, other potential sources of information such as books, theses/dissertations, white papers and website/blog articles are included as a part of Grey Literature. In this study, the articles related to the implication of lean methodologies in the context of software engineering were considered. The review included 72 primary studies published between 1993 and 2012. The primary studies were selected based on the following criteria: If they presented the challenging factors that negatively influenced the success of software projects. If they depicted the implication of lean mitigation methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) that appeased the negative impact of the identified challenging factors that hampered the success of software projects. If they depicted the implication of lean methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) in general or for a specific development/ Management/ Maintenance improvement activities that lead to the success of software projects in the context of software engineering. If they presented the benefits of practicing lean methodologies in the context of software engineering. The study quality assessment was done based on the quality criteria defined in the ‘Quality assessment criteria checklist’. The data such as Article ID, Article Title, Literature type (Peer- reviewed, Non-peer reviewed), Context of validation of the lean methodology (Industry/Academia), Subjects considered for the study (Researchers/students, Industrial practitioners), Type of article publication (Conference/ Journal/ Books/ Thesis Reports/ Doctoral dissertations/ Other), Research method used in the study (Case Study/ Experiment/ Experience Report/ Not stated/ Secondary Data Analysis/ Literature Review), Context of conducting the research (Industry/ Academia/ Not stated/ Both), Context of validation of the study (Strong/ Medium/ Weak), Publication date & year, Source of the publication, are extracted as a part of Quantitative analysis. The secondary data analysis for both ‘State of Art’ (Systematic literature review) and ‘State of Practice’ (Industry) was carried by performing a generic data analysis designed to answer our research questions. The more specific data such as the challenging factors that negatively influenced the success of software projects, the type of lean contribution presented i.e., the methodology being a Tool, Technique, Practice, Principal, Process or a Method, along with the benefits associated on their implication that helped us to answer our research questions are extracted as a part of qualitative analysis from the selected studies. The industrial interviews were conducted by interviewing potential lean experts who had decent experience in lean software development, to find the current state of lean implication in the software industry. In the end, a comparative analysis was performed to clearly understand the state of convergence and divergence between the results from extensive literature review and the industry with respect to the implication of lean methodologies in the context of software engineering. Results: A total of 72 primary articles were selected for data extraction. 56 articles were selected from the electronic databases that clearly depicted lean implementation in the context of software engineering. 9 articles were selected by conducting snowball sampling i.e. by scrutinizing the references of the selected primary studies and finally the grey literature resulted in 7 articles. Most of the articles discussed about lean implication in the context of software engineering. The depicted lean methodologies were validated in either Industry or Academia. A few articles depicted regarding lean principles and their benefits in the context of software engineering. Most of the selected articles in our study were peer- reviewed. Peer reviewing is a process of evaluating one’s work or performance by an expert in the same field in order to maintain or enhance the quality of work or performance in the particular field. This indicates that the articles considered for data extraction have been reviewed by potential experts in the research domain. Conclusions: This study provided a deeper insight into lean implication in the context of software engineering. The aim of the thesis is to find the challenging factors that negatively influenced the success of software projects. A total of 54 challenges were identified from the literature review. The 72 primary articles selected from various resources yielded 53 lean methodologies. The lean methodologies were grouped into Principles, practices, tools and methods. Mapping between the identified challenges and the mitigation lean methodologies is presented. Industrial interviews were conducted to find the current state of lean implication in software engineering. A total of 30 challenges were identified from the industry. A total of 40 lean methodologies were identified from the interviews. Comparative analysis was done to find the common challenges and mitigation lean methodologies between the State of art and State of practice. Based on the analysis a set of guidelines are presented at the end of the document. The guidelines benefit an industrial practitioner in practicing the appropriate lean methodology. Keywords: Lean Methodology, Lean software development, lean software management, lean software engineering, Systematic literature review, literature review.
0091-8375920473

Lean Software Development is a new approach to provide a quality philosophy in software development companies. Lean offers a set of principles that helps companies to identify inefficient processes and waste. Therefore, by applying these principles, we can reduce costs, by shorting development time, incrementing productivity.In this study a software company with seven employees is analyzed. The company develops software and wants to increase its maturity and the quality of its processes. Currently, it has few documented processes. Furthermore, the company want a common way of working for every project. The challenge relies in adapting the set of principles provided by Lean to this particular case of study.We seek to analyze the current situation of the company to find out about the problems and limitations of the current way of working. After that we will state recommendations about the use of Lean combined with Agile practices such as Scrum and XP.As a result we present a proposal for implementation adapted from these philosophies to the needs and characteristics of the company.We have found that there are several ways in which the company can benefit from the implementation of Lean practices in combination with Scrum and XP. The result is a new framework that can be applied for other small software development companies in a similar situation.

Model-Based Software Engineering (MBSE) a été proposé comme une méthodologie prometteuse de développement de logiciels pour surmonter les limites de la méthodologie traditionnelle basée sur la programmation pour faire face à la complexité des systèmes embarqués. MBSE favorise l’utilisation de langages de modélisation pour décrire les systèmes d’une manière abstraite et fournit des moyens pour générer automatiquement de différents artefacts de développement, p.ex. code et documentation, à partir de modèles. Le développement d’un système complexe implique souvent de multiples intervenants qui utilisent différents outils pour modifier les artefacts de développement, le modèle et le code en particulier dans cette thèse. Les modifications apportées aux artefacts évoquent le problème de cohérence qui nécessite un processus de synchronisation pour propager les modifications apportées dans l’un artefact aux autres artefacts. Dans cette étude, le problème de la synchronisation des modèles d’architecture basés sur les éléments UML composite structure (UML-CS) et UML state machine (UML-SM) du langage de l’Unified Modeling Language (UML), et le code orienté objet est présenté. UML-CSs sont utilisés pour décrire l’architecture du logiciel basée sur les composants et UML-SMs pour les comportements discrets liés aux événements des systèmes réactifs. Le premier défi est de permettre une collaboration entre les architectes de logiciels et les programmeurs produisant de modèle et de code, en utilisant différents outils. Il soulève le problème de synchronisation où il existe de modifications simultanées des artefacts. En fait, il existe un écart de perception entre les langages à base de diagramme (langages de modélisation) et les langages textuels (langages de programmation). D’une part, les programmeurs préfèrent souvent utiliser la combinaison familière d’un langage de programmation et d’un environnement de développement intégré. D’autre part, les architectes logiciels, travaillant à des niveaux d’abstraction plus élevés, favorisent l’utilisation des modèles et préfèrent donc les langages à base de diagramme pour décrire l’architecture du système. Le deuxième défi est qu’il existe un écart d’abstraction significatif entre les éléments du modèle et les éléments du code: les éléments UML-CS et UML-SM sont au niveau d’abstraction plus élevé que les éléments du code. L’écart rend la difficulté pour les approches de synchronisation actuelles car il n’y a pas de façon facile de réflecter les modifications du code au modèle. Cette thèse propose une approche automatisée de synchronisation composée de deux principales contributions corrélées. Pour aborder le premier défi, on propose un patron méthodologique générique de synchronisation entre modèle et code. Il consiste en des définitions des fonctionnalités nécessaires et plusieurs processus qui synchronisent le modèle et le code en fonction de plusieurs scénarios définis où les développeurs utilisent différents outils pour modifier le modèle et le code. Cette contribution est indépendante de UML-CSs et UML-SMs. La deuxième contribution traite du deuxième défi et est basée sur les résultats de la première contribution. Dans la deuxième contribution, un mapping bidirectionnel est présentée pour réduire l’écart d’abstraction entre le modèle et le code. Le mapping est un ensemble de correspondances entre les éléments de modèle et ceux de code. Il est utilisé comme entrée principale du patron méthodologique générique de synchronisation entre modèle et code. Plus important, l’utilisation du mapping fournit les fonctionnalités définies dans la première contribution et facilite la synchronisation des éléments de UML-CS et UML-SM et du code. L’approche est évaluée au moyen de multiples simulations et d’une étude de cas
Model-Based Software Engineering (MBSE) has been proposed as a promising software development methodology to overcome limitations of traditional programming-based methodology in dealing with the complexity of embedded systems. MBSE promotes the use of modeling languages for describing systems in an abstract way and provides means for automatically generating different development artifacts, e.g. code and documentation, from models. The development of a complex system often involves multiple stakeholders who use different tools to modify the development artifacts, model and code in particular in this thesis. Artifact modifications must be kept consistent: a synchronization process needs to propagate modifications made in one artifact to the other artifacts. In this study, the problem of synchronizing Unified Modeling Language (UML)-based architecture models, specified by UML composite structure (UML-CS) and UML state machine (UML-SM) elements, and object-oriented code is presented. UML-CSs are used for describing the component-based software architecture and UML-SMs for discrete event-driven behaviors of reactive systems. The first challenge is to enable a collaboration between software architects and programmers producing model and code by using different tools. This raises the synchronization problem of concurrent artifact modifications. In fact, there is a perception gap between diagram-based languages (modeling languages) and text-based languages (programming languages). On the one hand, programmers often prefer to use the more familiar combination of a programming language and an Integrated Development Environment. On the other hand, software architects, working at higher levels of abstraction, tend to favor the use of models, and therefore prefer diagram-based languages for describing the architecture of the system. The second challenge is that there is a significant abstraction gap between the model elements and the code elements: UML-CS andUML-SM elements are at higher level of abstraction than code elements. The gap makes current synchronization approaches hard to be applied since there is no easy way to reflect modifications in code back to model. This thesis proposes an automated synchronization approach that is composed of two main correlated contributions. To address the first challenge, a generic model-code synchronization methodological pattern is proposed. It consists of definitions of necessary functionalities and multiple processes that synchronize model and code based on several defined scenarios where the developers use different tools to modify model and code. This contribution is independent of UML-CSs and UML-SMs. The second contribution deals with the second challenge and is based on the results from the first contribution. In the second contribution, a bidirectional mapping is presented for reducing the abstraction gap between model and code. The mapping is a set of correspondences between model elements and code elements. It is used as main input of the generic model-code synchronization methodological pattern. More importantly, the usage of the mapping provides the functionalities defined in the first contribution and eases the synchronization of UML-CS and UML-SM elements and code. The approach is evaluated by means of multiple simulations and a case study

This thesis presents a procedural approach to evaluating software development methodologies. The evaluation procedure adopts a unique approach based on the fundamental assumption that the requirements govern the process by which software is constructed. To begin with, this research partitions desirable software characteristics into three categories, viz., objectives, principles and attributes. The thesis claims (claims are substantiated with literature references) that there exist definitive relationships (or linkages) among the software objectives, principles and attributes. These linkages form the foundation of the evaluation procedure. The procedure constitutes two processes, top-down process and bottom-up process. These processes are used to assess the software product and the employed software development methodology. The top-down process begins by identifying the objectives and travels down through principles and product attributes; thus, evaluating the adequacy of the methodology. The bottom-up process, on the other hand, starts at the attribute level and goes up through principles and objectives. The bottom-up process highlights the effectiveness of the methodology. Attributes are identified in the product via properties. This research establishes several properties (called factors in the report) for each attribute. A measurement approach is also presented to help assess the extent to which attributes are present. The feasibility and validity of the evaluation procedure are illustrated through the analysis of two real life methodologies.
M.S.