Integration of non-functional requirements in model-driven architecture

Enterprises today face many challenges related to lack of interoperability. Enterprise applications and software systems need to be interoperable in order to achieve seamless business across organisational boundaries and thus achieve virtual networked organisations. IEEE defines interoperability as “the ability of two or more systems or components to exchange information and to use the information that has been exchanged”. MDA is the OMG instantiation of an approach to software development kown as Model Driven Engineering (MDE) or Model Driven Development (MDD). MDD focuses on Models as the primary artefacts in the development process, with Transformations as the primary operation on models, used to map information from one model to another. There is presently an important paradigm shift in the field of software engineering that may have important consequences on the way information systems are built and maintained. Model-driven development (MDD), and in particular OMG's Model-Driven Architecture ® (MDA®), is emerging as the state of practice for developing modern enterprise applications and software systems. The MDD paradigm improves the way of addressing and solving interoperability issues compared to earlier non-modelling approaches. However, developing correct and useful models is not an easy task. We believe that there is a need for an interoperability framework that provides guidance on how MDD should be applied to address interoperability. A key to the success of MDD is the development of ontologies supporting the mapping from one model to another, either at the same level of abstraction or at different levels. Various approaches have been proposed and tested, starting from common ontologies, shared by all the models, to local ontologies, specific to each software. We propose here to discuss the applicability of MDD to the urban civil engineering (UCE) field. This should help to establish the requirements for ontologies to be applied for interoperability of systems commonly used in this domain. In the first section of this paper, we briefly introduce some key principles of the MDA approach and the role of ontologies in model transformation approaches. The following section describes the Model Driven Development (MDD) interoperability framework. The last part presents a way of applying the MDA techniques to urban civil engineering projects, with the objective of testing the feasibility and relevancy of the approach to this domain.

This paper presents a method to compose architectural description (AD) that is suitable for translative model-driven development (MDD). In it, we map the translative MDD artifacts to the AD which complies with the IEEE Standard 1471-2000. The method comprises viewpoints which address separately platform-independent requirements specification (PIRS) and platform requirements specification (PRS). Functional and non-functional requirements concerns are also accommodated within this method. Our proposed method applies object-oriented analysis and recursive design (OOA/RD) concepts to build the architectural models. Within our method, the OOA/RD concepts are adjusted in order to accommodate non-functional requirements specifications. In terms of separation of concerns, our method offers clearer decomposition compared with the specified viewpoints in model-driven architecture (MDA).

One of the primary responsibilities of requirement engineer is the elicitation of non-functional and functional requirements. Functional requirements sketch out the functionality, the system has to be performed while non-functional requirements compel the restrictions on this functionality. Software industry is raising its demand for not only the required functionality but the necessity of non-functional requirements too such as performance, security, usability, security, privacy etc. The current practice in the industry is to deal with functional requirements as first class requirements while non-functional requirements are only catered at design and implementation level. This approach leaves a serious flaw in the system design towards user satisfaction and often results in the failure of projects such as the classic example of London Ambulance System[1]. The chances of software success can be maximized when dealing with NFR at the requirements level. This literature survey is a first effort of its kind to seek key NFR challenges and issues while elicitation level of requirement engineering. It also find-outs the approaches and methods that are suggested in literature to deal with these issues.

Manufacturing companies today face an increasingly dynamic environment. Development of production planning systems requires approaches that offer flexibility in development of solutions. Applying the UML (Unified Modeling Language) and MDA (Model Driven Architecture) paradigm can ensure compatibility between applications developed on different platforms. The MDA approach to software development becomes an obvious choice. In this approach, the models drive the process of software development. These models are defined at different levels of abstraction to represent various aspects of the system. The transformation of models from one level of abstraction to another, or the transformation of models to executable code is performed by using automated transformation tools. The strength of MDA lies in the fact that it is based on widely used industry standards for visualizing, storing and exchanging software designs and models. The models in MDA are abstracted at three different levels – the Computation Independent Model (CIM), the Platform Independent Model (PIM) and the Platform Specific Model (PSM). The key to the success of MDA lies in automated or semi-automated model-to-model and model-to-code transformations. In this paper, we examine how a platform-independent model of an MRP-based production planning system can be created using MDA approach, from which several platform-specific systems can be achieved, as required.

This chapter on “Software Design” emphasizes the role of modeling, prototyping, and simulation in software design. The chapter introduces the principles of software design, issues and challenges. Modeling techniques used in procedural and object oriented methodologies is presented along with the Unified Modeling Language (UML). The suitability of prototyping, as a design artifact and a simulation method is briefly discussed. Software processes such as Rapid Application Development (RAD), Rational Unified Process (RUP) and Agile methodologies which influence the design process have been discussed and recommended. The chapter then deals with Design Metrics for Quality Analysis, Software Risk Analysis and Threat Modeling for design of secure software. Finally, some of the recent research topics such as Model Driven Architecture (MDA), Model Driven Development (MDD), Meta Object Facility (MOF), and Model Driven Testing (MDT) have been covered.

Research and/or Engineering Questions/Objective The evaluation of vehicle characteristics at an early phase of functional development is a key task in the definition of a viable system and function architecture. Today this is complicated by the fact that full vehicle characteristics, in particular those of modern hybrid and electric vehicles, are dependent on a broad range of electrical, mechanical, thermal and control-related partial aspects. In addition to the current driving status and information on the environment, modern energy management systems (e.g. control systems, range, charging and thermal management) also require predictive information on the driving route to be expected. This includes, for example, uphill road grades, curve radii, speed limits, number of lanes, urban and residential areas, intersections and traffic lights. All together, the intelligent fusion of this information provides for increased safety and energy efficiency. Methodology These additional functions however result in additional complexity in the development process, which must be controlled. Nevertheless many questions already arise in a very early phase of development, in particular in the interaction with the actual utilization profile, such as route, driver and environment characteristics in the various target regions of the future vehicle. This article shows new ways and methods of how the functions and total vehicle characteristics can be evaluated in virtual driving tests in the early phase of development. The method provides a major support for the development and evaluation of energy management systems in the complete vehicle environment with corresponding system interactions: The evaluation of energy states, losses and fuel consumptions in realistic utilization profiles, such as route, driver and environment characteristics in the various target regions of the future vehicle. Results In addition to the evaluation of the individual target functions in a broad range of different scenarios, the correct designs of the individual system components in the complete vehicle can also be verified. The performance and robustness of the operating strategy, as well as the corresponding fuel consumption or CO2 emission values in the range of worldwide conditions of use can also be predicted with the different choice of route and driver types and the amount of traffic typical for the region. Limitations of this study Furthermore, positive fuel consumption effects are identified in the virtual driving test which cannot be recognized due to the insufficient repetitive accuracy in actual traffic. During this, the method can be consistently and uniformly used in the x-in-the-loop development process. As soon as hardware components like the engine, drive train or battery are available, these actual components can already be tested in the virtual driving test in combination with the virtual vehicle in accordance with the principles described. Conclusion As a result, the system and functional architecture can already be comprehensively evaluated in a very early development phase and the degree of integration maturity in the later, actual integration levels can be raised to a considerably higher standard, minimizing time-consuming, expensive development loops.

새로운 패러다임의 시스템 개발 접근 방법은 OMG(Object Management Group)에서 MDA(Model Driven Architecture)로 표준화하고 있다. MDA의 핵심 기술은 모델 중심의 시스템 구현을 위한 기술 구조를 정의하는 것으로 시스템의 설계 및 명세에 대한 구현 기술을 플랫폼 독립적 모델(PIM : Platform Independent Model)로 설계한 후, 구현 환경에 적합한 플랫폼 종속적 모델(PSM : Platform Specific Model)로 설계하여 구현환경에 맞는 언어로 변환하는 기술이다. MDA의 핵심인 MOF(Meta-Object Facility), UML, XMI(XML Metadata Interchange), CWM(Common Warehouse Metamodel) 표준 등이 포함된다. MDA 지원 자동화 툴들은 위의 정보들을 갖고 변환 작업을 수행한 후 실행 가능한 시스템으로 생산해 내는 것이다.[1] 본 논문에서는 MDA기반 접근 방법을 적용하여 학사관리 시스템을 설계 및 구현하고, MDA기반 접근 방법에 대한 모델링의 중요성을 강조하였다. 또한 소프트웨어를 효율적으로 개발하는 방법을 제시하여 플랫폼 독립적 모델(PIM)로 작성하고, 플랫폼 종속적 모델(PSM)을 J2EE 플랫폼 기반의 EJB(Enterprise Java Beans)로 변환하는 과정 등을 제시하였다. MDA를 지원하는 자동화 툴 및 편집기(Together Architect 2006 for Eclipse, Edit plus 2)와 데이터베이스 모델링 툴(ER/WIN 4.1)을 사용하여 시스템 설계 및 구현을 하였으며, 전통적 개발 프로세스와 MDA 기반 개발 프로세스에 대한 유효성 분석 결과를 제시하였다. The system development approach method of the new paradigm, as being standardizing MDA(Model Driven Architecture) in OMG(Object Management Group), the core technique of MDA definite technique structure for system materialization focusing on Model, is to build the design and the statement for system in PIM(Platform Independent Model), Materialization technique, and to build PSM(Platform Specific Model) adapt to materialization environment, and then to be the technique transforming into language Platform suitable to materialization environment. It includes MOF(Meta-Object Facility), UML, XMI(XML Metadata Interchange), CWM(Common Warehouse Metamodel), the core of MDA. Though these operations MDA support automatic tools product the practicable system after carrying out transform operation with the above information. In this thesis, it will be approached how to design and materialize the Bachelor management system based on MDA and the importance of modeling should be emphasized by applying to the approach method based on MDA. It should be suggested how to develop software efficiently, written it out in PIM, and suggested the process transforming PSM into EJB by J2EE Platform. The system is designed and implemented using automatic tool, edit machine(Together Architect 2006 for Eclipse, Edit plus2) supporting MDA and Database Modeling tool(ER/WIN 4.1). In conclusion, it should be suggested the efficiency analysis result for development process of traditional and based on MDA.

Data Warehouses (DW) manage crucial enterprise information used for the decision making process which has to be protected from unauthorized accesses. However, security constraints are not properly integrated in the complete DWs' development process, being traditionally considered in the last stages. Furthermore, legacy systems need a reverse engineering process in order to accomplish re-documentation for detecting new security requirements as well as system's design recovery to enable migration and reuse. Thus, we have proposed a model driven architecture (MDA) for secure DWs which takes into account security issues from the early stages of development and provides automatic transformations between models. This paper fulfills this architecture providing an architecture-driven modernization (ADM) process focused on obtaining conceptual security models from legacy OLAP systems.

Welcome to the DATE 08 Conference Proceedings. DATE combines the world's favourite electronic systems design conference and Europe's leading international exhibition for electronic design, automation and test, from system level hardware and software implementation right down to integrated circuit design. The DATE 08 event features a technical program with 77 sessions covering the latest developments in system design and embedded software, IC design/test methodologies and EDA tools, together with an exhibition with the leading EDA, silicon and IP providers showing their new products and services. Challenges that you all face or soon will face in your daily practice are the increasing design complexity of highly integrated systems, the introduction of reconfigurability and embedded software, and the control of power and variability in nanometer IC designs. All these issues will be addressed in this year's DATE event. For the 11th successive year DATE has prepared an exciting technical programme, with the help of the more than 400 members of the Technical Programme Committee, who dedicated their time to thoroughly review the 839 submissions in 37 topics, ranging from system level down to circuit design and covering all the most relevant application domains. The submissions are organised in 4 major areas: D --- Design Methods, Tools, Algorithms and Languages A --- Application Design T --- Test Methods, Tools and Innovative Experiences E --- Embedded Software After a thorough review and selection process (with an average of 5 reviews per paper), finally 198 regular papers were selected for presentation at the conference. Additionally, there are 46 Interactive Presentations that are organised in 5 IP sessions. Together with the invited special sessions (panels, embedded tutorials and hot topic sessions), this has resulted in a high-quality technical program. The technical program provides a wide but high-quality coverage of design, design automation and test topics, from the system level to the integrated circuit level. Compared with previous years, submissions in the Embedded Software track has increased by 50%, showing a clear trend towards a comprehensive system design focus with integrated hardware and software solutions. DATE has established itself firmly as a true Electronic System Design Conference. This year the conference is held in Germany, at the ICM in Munich and spans an entire working week from Monday March 10 to Friday March 14. On Monday, eleven pre-conference tutorials will be given. The three-full day tutorials cover topics of great interest for system design. The first tutorial deals with techniques to automatically realising embedded system from high-level functional models. The second tutorial addresses the different issues related to communication based design and architectures in automotive electronic systems. The third tutorial discusses several key concepts on system-level design and application mapping for wireless and multimedia MPSoC architectures. Furthermore, eight half-day tutorials are also given, which cover a wide spectrum of topics on specification, modelling, design and test. The main conference opens on Tuesday March 11, with two very interesting and complementary keynote speeches. Dominique Vernay, Chief Technical Officer for Thales, will talk about the challenges of embedded systems design, and Giovanni de Micheli, Professor at EPFL, will present his views on designing micro/nano systems for a safer and healthier tomorrow. On the same day, the Executive Track offers a series of business panels with executives discussing hot topics in design: the perils of 45 nanometers, the changes in EDA strategies from IDM, to fablite to fabless, and embedded systems level design strategies. DATE 08 will again offer two specific days related to special themes. On Wednesday March 12, a special full-day track is devoted to Automotive Electronics---Software and Architecture. This special-day track will focus on the challenges faced by the automotive supply chain with particular attention to system and software architecture design. It provides a comprehensive analysis of the evolution of automotive architectures, including ECUs, sensors and communication standards and discusses how new methods, tools and standards for interoperability and component-based design can deal with the increasing complexity of software systems and their need for reliability and guaranteed timely behaviour. In addition, it addresses to what degree existing standards, including AUTOSAR and FLEXRAY and model-based development, can support the development of safety and time-critical software. On Thursday March 13, a second special full-day track focuses on Dependable Embedded Systems. This track will address both conceptual and applied issues for design, analysis and validation of dependable embedded systems. The utility of embedded systems and services is based, in large part, on our depending on their sustained functionality in spite of the encountered operational or malicious disruptions. As the number of transient and also permanent disruptions (given the decreasing device geometries, higher device density, lower voltage latching, faster clocks etc) is expected to increase substantially, this will not only be a key issue for the hardware community but also the systems community in general. Solutions using a combination of hardware and software might be more effective than hardware-only or software-only solutions. This track focuses on both conceptual and applied issues for design, analysis and validation of dependable embedded systems. Besides these special tracks, the main conference is organized in six parallel tracks of sessions, three devoted to design methods, tools, algorithms and languages, one to application design, one to test methods, tools and innovative experiences, and finally one to embedded software. The presentations of the selected regular papers in these parallel tracks are complemented by nine Special Sessions and two Invited Industrial Sessions. The special sessions are organized in the form of panels, hot topics, and embedded tutorials. The topics to be covered include quantitative evaluation for embedded systems design, design and manufacturing at 32 and 22nm, software for wireless networked embedded systems, test challenges for low power devices, quantitative productivity measurement in IC design, and 3D Integration. The two invited industrial sessions deal with industrial system designs in transportation and information technologies. To emphasise that DATE is the major event for the designers, DATE 08 features also invited sessions where Europe's famous consumer industry presents their best designs and design practices. Friday March 14 is the day for the DATE workshops. DATE 08 offers workshops on current and emerging important issues in design, test, EDA and software to complement the regular conference. They provide a unique opportunity for the various research and design communities to spend a day discussing the latest and the best, sharing their experiences and visions. This year's workshop program includes eight workshop themes. Four workshops are related to software engineering, ranging from dependable software to modelling, analysis and development tools. Four other workshop themes cover a variety of topics such as the impact of process variations on design and test, the merging world of Nano-Electro-Mechanical Systems, new directions in high level synthesis, and heterogeneous reconfigurable hardware. Each workshop features presentations, invited or submitted, from highly distinguished academic and industrial researchers. Finally, throughout the conference days, DATE offers a comprehensive overview of commercial design and verification tools in its large exhibition hall. Exhibitors include EDA vendors, silicon, FPGA and IP providers showing their new products and services. In addition, there is an Exhibition Theatre featuring talks from engineering managers of the leading electronic manufacturers on first-hand design experiences of commercial EDA tools. New this year is the European projects village where different European and large government funded projects will be able to show their ongoing research and results to the design community and have the opportunity for internal meetings and discussions. The DATE week will be also an opportunity for students and universities to show their research work, through the PhD Forum on Monday evening and the University Booth where hardware and software demonstrations will be shown by different universities on a rotation schedule. The DATE 08 event's program will be particularly attractive to industrial designers, at analog, IC, FPGA and embedded system level, as well as software designers, to researchers and academics as well as to design managers, and an increasing attendance is expected. We therefore invite you to take full advantage of the many opportunities offered to you by DATE 08, to extend your knowledge and/or business in electronic system's design and to exploit the abundant networking possibilities offered to socialise with colleagues, including fringe meetings and a memorable social party with bands and dancing. We hope that you will all enjoy the DATE 08 Conference and Exhibition.

Requirements engineering is the first phase in software development life cycle and it also plays one of the most important and critical roles. Requirement document mainly contains both functional requirements and non-functional requirements. Non-functional requirements are significant to describe the properties and constraints of the system. Early identification of Non-functional requirement has direct impact on the system architecture and initial design decision. Practically, non-functional requirements are extracted manually from the document. This makes it tedious, time-consuming task and prone to various errors. In this paper, we propose an automatic approach to identify and classify non-functional requirements using semantic and syntactic analysis with machine learning approaches from unconstrained documents. We used A dataset of public requirements documents (PURE) that consists of 79 unconstrained requirements documents in different forms. In our approach, features were extracted from the requirement sentences using four different natural language processing methods including statistical and state-ofthe-art semantic analysis presented by Google word2vec and bidirectional encoder representations from transformers models. The adopted approach can efficiently classify non-functional requirements with an accuracy between 84% and 87% using statistical vectorization method and 88% to 92% using word embedding semantic methods. Furthermore, by fusing different models trained on different features, the accuracy improves by 2.4% compared with the best individual classifier. INDEX TERMS Software requirement, Machine learning, Natural language processing.

This book will help readers gain a solid understanding of non-functional requirements inherent in systems design endeavors. It contains essential information for those who design, use, and maintain complex engineered systems, including experienced designers, teachers of design, system stakeholders, and practicing engineers. Coverage approaches non-functional requirements in a novel way by presenting a framework of four systems concerns into which the 27 major non-functional requirements fall: sustainment, design, adaptation, and viability. Within this model, the text proceeds to define each non-functional requirement, to specify how each is treated as an element of the system design process, and to develop an associated metric for their evaluation. Systems are designed to meet specific functional needs. Because non-functional requirements are not directly related to tasks that satisfy these proposed needs, designers and stakeholders often fail to recognize the importance of such attributes as availability, survivability, and robustness. This book gives readers the tools and knowledge they need to both recognize the importance of these non-functional requirements and incorporate them in the design process

The management of software development for single and dual processor system designs is making progress towards becoming a mature discipline. A good part of the progress can be attributed to the development and use of standard system and software engineering methods and design principles.However, new computer system designs (networking, distributed systems, embedded systems, multi- and coprocessors, fault tolerant systems, etc.) will create new challenges for managers of software development. The reason for this effect on management is that some of the system and software engineering methods and design principles developed for single and dual processor system designs are not valid for these newer designs.Some of the issues that software development project managers will need to cope with are:1. Life cycle model adjustments2. Rapid prototyping activities3. Different hardware and software phasing4. Increased tool development5. New trade-offs and hybrid developments of off-the-shelf software and newly developed software6. Development of concurrent design principles7. New software design principles to support fault tolerance and the use of new memory technologiesThe above items are just now being recognized as problems, and solutions for them either do not exist, or are not widely known.These problems create a series of new challenges that managers must deal with for software development based on the new architectures and requirements. The purposes of this paper are to discuss these issues and to identify some solutions that can serve in the interim as the technology changes to meet these new challenges.

System models are constructed to design, study, and understand complex systems. According to the systems modeling language (SysML) that is a standard for model-based system engineering, all engineering activities should be performed using a common model. To validate complex system models defined in SysML, simulation is usually employed. There are numerous efforts to simulate SysML models using different simulation methods and tools. However, the efficient support of automated generation of executable simulation code is still an issue tangled by the research community. This paper introduces DEVSys, an integrated framework for utilizing existing SysML models and automatically producing executable discrete event simulation code, according to model driven architecture (MDA) concepts. Although this approach is not simulation-specific, discrete event system specification (DEVS) was employed, due to the similarities between SysML and DEVS, mainly in system structure description, and the mature, yet ongoing research on expressing executable DEVS models in a simulator-neutral manner. DEVSys framework elements include (a) a SysML profile for DEVS, enabling integration of simulation capabilities into SysML models, (b) a meta-model for DEVS, allowing the utilization of MDA concepts and tools, (c) a transformation of SysML models to DEVS models, using a standard model transformation language as query/view/transform (QVT), and (d) the generation of DEVS executable code for a DEVS simulation environment with an extensible markup language (XML) interface. The definition and implementation of DEVSys elements, as well as the process for its application are demonstrated and discussed, with the aid of a simple working example.

Predicting the outcomes of software projects using data available in early development phases allows developers and managers more time to re-plan or re-design systems as needed to increase success. This research investigates early lifecycle predictive models of software faults and effort using information available no later than the system design phase. Static analysis of system designs characterizes intra- and inter-component control flow structure to calculate objective system design metrics. The model building process composes these design metrics into a set of relative factors that calibrate the relationships between the metrics and software faults and effort. These component-based predictive models provide a powerful approach to capture and analyze the designs of complex systems. These models facilitate the identification of essential system characteristics in terms of component structures and interactions, and they enable comprehensive analysis by being scalable to large systems. The research approach applies static analysis tools to the designs of 23 large-scale NASA systems containing over 5000 software components in order to automatically generate state- and interaction-based models of their designs. The static analysis tools derive the number of internal states for a component from its internal control flow design structure using cyclomatic complexity, and they calculate the number of interactions between components from the passing of control flow or data abstractions between components. The research approach evaluates the models by characterizing their relationships to favorable or unfavorable aspects of the system designs, in terms of component development faults and effort. The data analysis focuses on describing the characteristics of the state- and interaction-based models and identifying system design factors revealed by the models that relate to low or high faults, fault correction effort, and development effort. The results include the following, with comparative data being statistically significant at α < 0.05: ♦ The static analysis tools successfully generated state- and interaction-based models of the 23 system designs comprised of 5469 components. The numbers of states per component were exponentially distributed with an average of 14.3 and a median of 7.0. The numbers of interactions per component were exponentially distributed with an average of 8.8 and a median of 4.0. During system development, the components had 0.60 faults on average. ♦ Components with the most states (top 20%) had 7.8 times more faults than did those with the fewest states (bottom 20%). Components with the most states also had 22.5 times more fault correction effort and 5.4 times more development effort than did those with the fewest states. ♦ Components with the most interactions (top 20%) had 2.9 times more faults than did those with the fewest interactions (bottom 20%). Components with the most interactions also had 3.9 times more fault correction effort and 2.7 times more development effort than did those with the fewest interactions. In conclusion, we outline future research directions that build on these system modeling ideas and strategies.

The most important element of industrial software development is the creation of a common vocabulary of terms for exchanging information between software and industrial engineers. Based on this cooperation, technical domain knowledge is converted into data structures, algorithms and rules. Currently, when people are used to receiving short and quick messages, the most efficient way of knowledge extraction is work on examples or mockups to facilitate better understanding of the problem. Shorter rounds in the presentation of mockups allows continuous work on live object models rather than specifications which make experts more open for sharing their knowledge and provides quicker and more reliable feedback on the data structure and the completeness of the model. Latest research and progress in the area of Model Driven Architecture (MDA) resulted in advanced tools for the creation of models, automatic source code generation as well as whole frameworks for creating application skeletons based on these models. In this paper a collaborative process which uses MDA approach (model, tools and frameworks) for extracting knowledge from domain experts is presented. During presented process, a cooperation of a software engineer and a domain expert via phone calls and one live workshop resulted in a complete model of machine and drive including specific machine features and diagnostic processes. Finally, a working diagnostics application was verified by the domain expert proving that MDA resulted in the expected results. The diagnostics application was verified on real data collected on the winding machine for more than one month, collected diagnostics data included more than 150 signals and 20Gb of raw analog data to dig into before getting condensed diagnostics results. Additionally to the process itself, the article presents identified risks, benefits from applying the MDA approach and lessons learned from applying this new innovative process. For further work, the possibilities of extending and dynamically extending existing models should be studied. In previous works we have focused on an ontology based approach, which does not meet all expectations when it comes to application in real world environment. As simpler and more mature technology, MDA was shown to be more productive and easier to adapt for building industrial applications.