The Unified Modeling Language (UML) is now a standard means of expressing object-oriented analysis and design (OOAD) for the Object Management Group since 1997. The UML is called a modeling language, not a method. That is, the modeling language is the graphic notation that methods use to express design. However, the principles or guidelines for each UML notation modeling are lacking and those are crucial for the UML modeling. To address this important issue, this study utilizes research and development method to investigate the guidelines for each UML notation modeling. An example of war game is used to illustrate the guideline and application. With these guidelines, analysts can more easily use the UML notations to express OOAD and thereby improve the efficiency and effectiveness of UML modeling.

The system design document can provide maintenance workers a quick understanding of the system operation process and review detail which helps current increasingly complicated information quite a lot, especially the in the aspect of the comprehension of original design concept to system. In addition, the system design document of platform independent can even quickly switch the platform for system without designing system again. It largely increases the operation of information system across platform. Besides the source code, system design document is also one of the most important asset; for instance, when the source code is lost, the designer can quickly duplicate a set of system with the same function under a basis of system design document. Due to the constant revolution of the platform technology to the current software, as well as the prevalent of visualized rapid application development tool, there is no complete design document attached in a set of the developed information system, or the document has been missing. It is necessary to find a way for the source code of system to reversely generate system design document. The study is based on object-oriented technology and object-oriented model to address a concept that platform independent system design document can be reversely generated from the object-oriented source code and to generalize a set of the reverse modeling method from this study. Last, a implemented case would be carried out and verified by the method mentioned above. Through this method, the maintenance workers could therefore quickly transform codes to system design document and then increase the operation efficiency of system maintenance.

abstract: Computational models for relatively complex systems are subject to many difficulties, among which is the ability for the models to be discretely understandable and applicable to specific problem types and their solutions. This demands the specification of a dynamic system as a collection of models, including metamodels. In this context, new modeling approaches and tools can help provide a richer understanding and, therefore, the development of sophisticated behavior in system dynamics. From this vantage point, an activity specification is proposed as a modeling approach based on a time-based discrete event system abstraction. Such models are founded upon set-theoretic principles and methods for modeling and simulation with the intent of making them subject to specific and profound questions for user-defined experiments. Because developing models is becoming more time-consuming and expensive, some research has focused on the acquisition of concrete means targeted at the early stages of component-based system analysis and design. The model-driven architecture (MDA) framework provides some means for the behavioral modeling of discrete systems. The development of models can benefit from simplifications and elaborations enabled by the MDA meta-layers, which is essential for managing model complexity. Although metamodels pose difficulties, especially for developing complex behavior, as opposed to structure, they are advantageous and complementary to formal models and concrete implementations in programming languages. The developed approach is focused on action and control concepts across the MDA meta-layers and is proposed for the parallel Discrete Event System Specification (P-DEVS) formalism. The Unified Modeling Language (UML) activity meta-models are used with syntax and semantics that conform to the DEVS formalism and its execution protocol. The notions of the DEVS component and state are used together according to their underlying system-theoretic foundation. A prototype tool supporting activity modeling was developed to demonstrate the degree to which action-based behavior can be modeled using the MDA and DEVS. The parallel DEVS, as a formal approach, supports identifying the semantics of the UML activities. Another prototype was developed to create activity models and support their execution with the DEVS-Suite simulator, and a set of prototypical multiprocessor architecture model specifications were designed, simulated, and analyzed. / Dissertation/Thesis / Doctoral Dissertation Computer Science 2019

The need for a robust system architecture to support software development is well known. In enterprise software development, this must be realized in a multi-tier environment for deployment to a software framework. Many popular integrated development environment (IDE) tools for component-based frameworks push multi-tier partitioning by assisting developers with convenient code generation tools and software deployment tools which package the code. However, if components are not packaged wisely, modifying and adding components becomes difficult and expensive. To help manage change, vertical partitioning can be applied to compartmentalize components according to function and role, resulting in a grid partitioning. This thesis is to advocate a design methodology that enforces vertical partitioning on top of the horizontal multitier partitioning, and to provide guidelines that document the grid partitioning realization in enterprise software development processes as applied in the J2EE framework.

Submitted by Rosivalda Pereira (mrs.pereira@ufma.br) on 2017-08-11T20:35:45Z No. of bitstreams: 1 CleberPereira.pdf: 3089056 bytes, checksum: ab85b5af73443dbf91e821cbac7192ab (MD5) / Made available in DSpace on 2017-08-11T20:35:45Z (GMT). No. of bitstreams: 1 CleberPereira.pdf: 3089056 bytes, checksum: ab85b5af73443dbf91e821cbac7192ab (MD5) Previous issue date: 2010-08-09 / The proposed modeling system for assessing undergraduate degree courses, according to the parameters required by ENADE emerges from the need of the IES adjust its methodology and assessment procedures to the terms set by the exam. The proposed solution does not address a specific undergraduate course and may be applied for any knowledge area. The use of software agents is justified on the grounds of a classical computer application not being able to adapt to the reality of each student, delivering the second behavioral questions identified during the evaluation process.The statistics generated from this reasoning will serve both for students and for teachers in order to reevaluate the teaching and learning process. The modeling was performed according to the UML 2.0 TROPOS methodology was used for the modeling of agents and their implementation was done in JADE. / A proposta de modelagem de sistema de avaliação dos cursos superiores de graduação, segundo os parâmetros exigidos pelo ENADE, emerge da necessidade das IES adequarem sua metodologia e procedimentos de avaliação aos moldes estabelecidos pelo exame. A solução proposta não se dirige a um curso específico de graduação, podendo ser utilizada para qualquer área do conhecimento. O uso de agentes de software em seu desenvolvimento justifica-se em razão de uma aplicação computacional clássica não ser capaz de adaptar-se à realidade de cada aluno, entregando quesitos segundo o comportamento identificado durante o processo de avaliação. As estatísticas geradas a partir deste raciocínio servirão tanto para os alunos como para os docentes no sentido de reavaliar o processo de ensino aprendizagem. A modelagem foi efetuada segundo a UML 2.0, foi utilizada a metodologia TROPOS para a modelagem dos agentes e sua implementação foi realizada no JADE.

Conceptual modeling allows abstraction, communication and consensus building in system development. It is challenging to expand and improve the accuracy of models in an iterative process, producing models able to facilitate analysis. Modeling and analysis can be especially challenging in early Requirements Engineering (RE), where high-level system requirements are discovered. In this stage, hard-to-measure non-functional requirements are critical; understanding the interactions between systems and stakeholders is a key to system success. Goal models have been introduced as a means to ensure stakeholder needs are met in early RE. Because of the high-level, social nature of early RE models, it is important to provide procedures which prompt stakeholder involvement (interaction) and model improvement (iteration). Most current approaches to goal model analysis require quantitative or formal information that is hard to gather in early RE, or produce analysis results automatically over models. Approaches are needed which balance automated analysis over complex models with the need for interaction and iteration. This work develops a framework for iterative, interactive analysis for early RE using agent-goal models. We survey existing approaches for goal model analysis, providing guidelines using domain characteristics to advise on procedure selection. We define requirements for an agent-goal model framework specific to early RE analysis, using these requirements to evaluate the appropriateness of existing work and to motivate and evaluate the components of our analysis framework. We provide a detailed review of forward satisfaction procedures, exploring how different model interpretations affect analysis results. A survey of agent-goal variations in practice is used to create a formal definition of the i* modeling framework which supports sensible syntax variations. This definition is used to precisely define analysis procedures and concepts throughout the work. The framework consists of analysis procedures, implemented in the OpenOME requirements modeling tool, which allow users to ask “What if?” and “Is this goal achievable, and how?” questions. Visualization techniques are introduced to aid analysis understanding. Consistency checks are defined over the interactive portion of the framework. Implementation, performance and potential optimizations are described. Group and individual case studies help to validate framework effectiveness in practice. Contributions are summarized in light of the requirements for early RE analysis. Finally, limitations and future work are described.

Conceptual modeling allows abstraction, communication and consensus building in system development. It is challenging to expand and improve the accuracy of models in an iterative process, producing models able to facilitate analysis. Modeling and analysis can be especially challenging in early Requirements Engineering (RE), where high-level system requirements are discovered. In this stage, hard-to-measure non-functional requirements are critical; understanding the interactions between systems and stakeholders is a key to system success. Goal models have been introduced as a means to ensure stakeholder needs are met in early RE. Because of the high-level, social nature of early RE models, it is important to provide procedures which prompt stakeholder involvement (interaction) and model improvement (iteration). Most current approaches to goal model analysis require quantitative or formal information that is hard to gather in early RE, or produce analysis results automatically over models. Approaches are needed which balance automated analysis over complex models with the need for interaction and iteration. This work develops a framework for iterative, interactive analysis for early RE using agent-goal models. We survey existing approaches for goal model analysis, providing guidelines using domain characteristics to advise on procedure selection. We define requirements for an agent-goal model framework specific to early RE analysis, using these requirements to evaluate the appropriateness of existing work and to motivate and evaluate the components of our analysis framework. We provide a detailed review of forward satisfaction procedures, exploring how different model interpretations affect analysis results. A survey of agent-goal variations in practice is used to create a formal definition of the i* modeling framework which supports sensible syntax variations. This definition is used to precisely define analysis procedures and concepts throughout the work. The framework consists of analysis procedures, implemented in the OpenOME requirements modeling tool, which allow users to ask “What if?” and “Is this goal achievable, and how?” questions. Visualization techniques are introduced to aid analysis understanding. Consistency checks are defined over the interactive portion of the framework. Implementation, performance and potential optimizations are described. Group and individual case studies help to validate framework effectiveness in practice. Contributions are summarized in light of the requirements for early RE analysis. Finally, limitations and future work are described.

An evolutionary process currently taking place in engineering systems is the shift from hardware to software where the role of software engineering is becoming more central in developing large engineering systems. This shift represents a trend from a piece-meal vision of software development to a holistic, system-wide vision. The term "software crisis" of 1960's and 1970's was the observation that most software development projects end up with massive cost overruns and schedule delays. The growing complexity of software projects led to Waterfall, Spiral and other models to depict the software development lifecycle. These models are qualitative and study the product, process and project issues in isolation, and do not provide a quantitative framework to depict the various facets of development, testing, maintenance and reuse. In this thesis, a generic, unified lifecycle model (ULM) integrating the product, process and project view of software development based on re-entrant lines is proposed. A reentrant line is a multi-class queueing network that consists of several types of artifacts visiting a set of development teams more than once. An artifact is a general term for any object of information created, produced, changed or used by development teams and it includes items such as requirements specification documents, preliminary and detailed module designs and design documents, code, components, test plans and test suites. The artifacts visit the development teams several times before exiting the system, thus making the flow of artifacts non-acyclic. The main consequence of the re-entrant flow is that several artifacts at different stages of completion compete with each other for service by a development team. The ULM model output is obtained by using the criticality, complexity and usage of artifacts. The model is solved using linear programming and simulation methods. The software development process in a software organisation is represented by the proposed re-entrant line model. The model is used to predict project metrics such as the development time, cost and product quality for any new project to be taken up by the organization. The routing matrix of the artifacts in the ULM can be modified to derive different types of lifecycle models such as Waterfall, Prototyping, Spiral and Hybrid models. The ULM may be modified to include software reuse and component-based development. We investigate certain issues involved in software reuse. Reuse of components is modeled as an external arrival of artifacts at different stages in the ULM. Two distinct lifecycles in component based software development, namely, 'development for reuse' and 'development with reuse', are distinguished and the development time and cost for projects are estimated using LP bounds and simulation. The 'development for reuse' lifecycle involves reusable components development that is stored in a reuse library. As the number of components in the reuse library grows over time and with projects, the problem of effective and efficient retrieval of candidate components in order to facilitate systematic reuse becomes the bottleneck. A novel approach where components are stored in a case-base is proposed. The retrieval process is based on a reasoning approach that relies on similar cases (components) in the past to find solutions to the current problem (new software requirements in projects). The selection of candidate components for decisions pertaining to four levels of reuse {reuse as-is, reuse with minor code modifications, reuse of specifications, no reuse or develop afresh} in the current application is modeled using Rough and Fuzzy sets. These methodologies are illustrated with suitable case studies. Maintenance of legacy systems, representing a massive, long-term business investment, is an important but relatively new research area. The ULM is modified to depict the complex set of activities associated with software maintenance. Quantitative metrics such as release time of versions, cost, time and effort for maintenance are estimated using this model. Some of the specific contributions of this thesis are: 1. A unified quantitative lifecycle model (ULM) depicting the software development process is used to obtain project metrics such as development cost, development time and quality based on the product and process attributes for the Waterfall, Prototyping, Spiral and Hybrid lifecycle models. 2. Analytic hierarchy process (AHP) methodology is used to rank order the suitability of different lifecycle models for a new development project at hand, based on the metrics obtained from ULM. 3. The ULM is modified to depict component-based software development and to integrate reuse as an important basis for software development. Two distinct lifecycles for development for reuse and development with reuse are studied. The 'development for reuse' strategy generates reusable components that are organized and stored in a reuse library. The selection-decision regarding candidate components from this library for reuse in the current application is derived using a Rough and Fussy set methodology. 4. The ULM is adapted to represent the various activities associated with software maintenance. Estimates of maintenance metrics for different strategies of maintenance of legacy systems are obtained.

A Cyber-Physical System (CPS) has a tight integration of computation, networking and physicalprocess. It is a heterogeneous system that combines multi-domain consisting of both hardware andsoftware systems. Cyber subsystems in the CPS implement the control strategy that affects the physicalprocess. Therefore, software systems in the CPS are more complex. Visualization of a complex system provides a method of understanding complex systems byaccumulating, grouping, and displaying components of systems in such a manner that they may beunderstood more efficiently just by viewing the model rather than understanding the code. Graphicalrepresentation of complex systems provides an intuitive and comprehensive way to understand thesystem. OpenModelica is the open source development environment based on Modelica modeling andsimulation language that consists of several interconnected subsystems. OMEdit is one of the subsystemintegrated into OpenModelica. It is a graphical user interface for graphical modeling. It consists of toolsthat allow the user to create their own shapes and icons for the model. This thesis presents a methodology that provides an easy way of understanding the structure andexecution of programs written in the imperative language like C through graphical Modelica model.

Background: Software Engineering is a high-demand field constantly changing with new languages, tools, and frameworks. The use of software modeling in Software Engineering is essential for solving complex problems since it helps the developer understand abstraction and develop high-level code. For an overview of the current state of software modeling, this research attempts to present an overview of software modeling curricula and how students benefit from attending these courses. Method: First, to assess the survey’s clarity and eliminate any potential for bias, we conducted a pilot study with five teachers at M¨alardalen University. We surveyed 23 participants from 23 institutions and ten countries to get their responses to Research Questions 2, 3, and 4. We have collected data for programs from 10 different countries with their top 5 universities to address Research Question 1. Results: To maintain meaning in the Software Engineering domain, we used our findings to seek the usage of knowledge gained from the academic environment in the industry when the students shift from academia to industry. Through this thesis, we present the current view of software modeling curricula and their contribution to preparing students for the industry. The following significant findings were reached: (i) software modeling aids in better understanding of abstraction concepts and the development of high-level applications; (ii) UML is one of the most popular languages; and (iii) some limitations of software modeling tools include license type, outdated tools, or poorly documented tools.