29 research outputs found

    Aspect Oriented Programming Methodology to Support the Design of Specific Domain Framework

    Get PDF
    The aspect-oriented programming has valuable advantages over other programming paradigms, but in turn it presents difficulties when applying the concepts within the stages of analysis and development to reduce the drawbacks of this paradigm. This paper proposes a methodology to reduce the drawbacks of the paradigm, at the same time provides steps that involve elements of common analysis in the Requirements Engineering with Aspects (basic unit of paradigm) in order to create the framework for a specific domain. The proposed methodology brings together some benefits methodologies, but it emphasizes the treatment of the first disadvantages of the programming aspects and the location and identification of aspects and elements; in addition, this article provides a tool that supports some methodology steps by generating part of the framework code base. In the process of treatment issues, the analysis is oriented to the specification of aspects using AspectJ, with rules to locate and determine aspects within its four Cyclical stages. Finally, it includes a case study which evaluates the steps in this methodology.The aspect-oriented programming has valuable advantages over other programming paradigms, but in turn it presents difficulties when applying the concepts within the stages of analysis and development to reduce the drawbacks of this paradigm. This paper proposes a methodology to reduce the drawbacks of the paradigm, at the same time provides steps that involve elements of common analysis in the Requirements Engineering with Aspects (basic unit of paradigm) in order to create the framework for a specific domain. The proposed methodology brings together some benefits methodologies, but it emphasizes the treatment of the first disadvantages of the programming aspects and the location and identification of aspects and elements; in addition, this article provides a tool that supports some methodology steps by generating part of the framework code base. In the process of treatment issues, the analysis is oriented to the specification of aspects using AspectJ, with rules to locate and determine aspects within its four Cyclical stages. Finally, it includes a case study which evaluates the steps in this methodology

    Managed Evolution of Automotive Software Product Line Architectures: A Systematic Literature Study

    Get PDF
    The rapidly growing number of software-based features in the automotive domain as well as the special requirements in this domain ask for dedicated engineering approaches, models, and processes. Nowadays, software development in the automotive sector is generally developed as product line development, in which major parts of the software are kept adaptable in order to enable reusability of the software in different vehicle variants. In addition, reuse also plays an important role in the development of new vehicle generations in order to reduce development costs. Today, a high number of methods and techniques exist to support the product line driven development of software in the automotive sector. However, these approaches generally consider only partial aspects of development. In this paper, we present an in-depth literature study based on a conceptual model of artifacts and activities for the managed evolution of automotive software product line architectures. We are interested in the coverage of the particular aspects of the conceptual model and, thus, the fields covered in current research and research gaps, respectively. Furthermore, we aim to identify the methods and techniques used to implement automotive software product lines in general, and their usage scope in particular. As a result, this in-depth review reveals that none of the studies represent a holistic approach for the managed evolution of automotive software product lines. In addition, approaches from agile software development are of growing interest in this field

    Review of Requirement Engineering Approaches for Software Product Lines

    Full text link
    The Software Product Lines (SPL) paradigm is one of the most recent topics of interest for the software engineering community. On the one hand, the Software Product Lines is based on a reuse strategy with the aim to reduce the global time-to-market of the software product, to improve the software product quality, and to reduce the cost. On the other hand, traditional Requirement Engineering approaches could not be appropriated to deal with the new challenges that arises the SPL adoption. In the last years, several approaches have been proposed to cover this limitation. This technical report presents an analysis of specific approaches used in the development of SPL to provide solutions to model variability and to deal with the requirements engineering activities. The obtained results show that most of the research in this context is focused on the Domain Engineering, covering mainly the Feature Modeling and the Scenario Modeling. Among the studied approaches, only one of them supported the delta identification; this fact implies that new mechanisms to incorporate new deltas in the Domain specification are needed. Regarding the SPL adoption strategy, most of the approaches support a proactive strategy. However, this strategy is the most expensive and risk-prone. Finally, most of the approaches were based on modeling requirements with feature models giving less support to other important activities in the requirements engineering process such as elicitation, validation, or verification of requirements. The results of this study provide a wide view of the current state of research in requirements engineering for SPL and also highlight possible research gaps that may be of interest for researchers and practitioners.Blanes Domínguez, D.; Insfrán Pelozo, CE. (2011). Review of Requirement Engineering Approaches for Software Product Lines. http://hdl.handle.net/10251/1023

    A Proposed Method to Identify Requirements Significant to Mass Reduction

    Get PDF
    Reducing the mass of engineering products holds the potential for significant benefits by reducing material costs, environmental impact, transportation costs, and in the case of vehicles, reducing fuel consumption. While there are many approaches for reducing mass, analyzing requirements has the greatest potential since requirements definition is the earliest phase of product development, where the most design freedom exists. This thesis proposes a requirement analysis method that identifies requirements that impact significant amounts of mass. The research hypothesis is: Engineering requirements can be represented and processed in a systematic manner and linked to physical components and systems, thus enabling mass reduction in reverse engineering and product redesign. The approach proposed in this research follows. Engineering requirements are linked to mass through the creation of a standard requirement statement using pre-processing rules and syntax rules. These rules and guidelines are applicable to authoring new requirements and analyzing existing requirements documentation. The processed engineering requirements are linked to physical components and assemblies based on how the requirements affect the components. These relationships are captured in Design Structure Matrices (DSMs) and Domain Mapping Matrices (DMMs). These DMMs and DSMs are used to attain the amount of mass each requirement affects and the level of coupling of each requirement. Further, representations of the requirements, components, and associated relationships are represented using two software tools. First, a systems engineering tool is used to model the system. Second, this model is exported to a traditional spreadsheet application to perform basic mathematical and data filtering functions. Finally, the method is demonstrated on three subsystems of Family of Medium Tactical Vehicle (FMTV) truck

    Applying patterns in embedded systems design for managing quality attributes and their trade-offs

    Get PDF
    Embedded systems comprise one of the most important types of software-intensive systems, as they are pervasive and used in daily life more than any other type, e.g., in cars or in electrical appliances. When these systems operate under hard constraints, the violation of which can lead to catastrophic events, the system is classified as a critical embedded system (CES). The quality attributes related to these hard constraints are named critical quality attributes (CQAs). For example, the performance of the software for cruise-control or self-driving in a car are critical as they can potentially relate to harming human lives. Despite the growing body of knowledge on engineering CESs, there is still a lack of approaches that can support its design, while managing CQAs and their trade-offs with noncritical ones (e.g., maintainability and reusability). To address this gap, the state-of-research and practice on designing CES and managing quality trade-offs were explored, approaches to improve its design identified, and the merit of these approaches empirically investigated. When designing software, one common approach is to organize its components according to well-known structures, named design patterns. However, these patterns may be avoided in some classes of systems such as CES, as they are sometimes associated with the detriment of CQAs. In short, the findings reported in the thesis suggest that, when applicable, design patterns can promote CQAs while supporting the management of trade-offs. The thesis also reports on a phenomena, namely pattern grime, and factors that can influence the extent of the observed benefits

    Applying patterns in embedded systems design for managing quality attributes and their trade-offs

    Get PDF

    A Modelling Approach to Multi-Domain Traceability

    Get PDF
    Traceability is an important concern in projects that span different engineering domains. Traceability can also be mandated, exploited and man- aged across the engineering lifecycle, and may involve defining connections between heterogeneous models. As a result, traceability can be considered to be multi-domain. This thesis introduces the concept and challenges of multi-domain trace- ability and explains how it can be used to support typical traceability scenarios. It proposes a model-based approach to develop a traceability solution which effectively operates across multiple engineering domains. The approach introduced a collection of tasks and structures which address the identified challenges for a traceability solution in multi-domain projects. The proposed approach demonstrates that modelling principles and MDE techniques can help to address current challenges and consequently improve the effectiveness of a multi-domain traceability solution. A prototype of the required tooling to support the approach is implemented with EMF and atop Epsilon; it consists of an implementation of the proposed structures (models) and model management operations to sup- port traceability. Moreover, the approach is illustrated in the context of two safety-critical projects where multi-domain traceability is required to underpin certification arguments

    Technical change in US industry: A cross-industry analysis

    Get PDF
    The nature of the public policies which have influenced the pace and pattern of technical progress in a number of American industries is studied with the view of assessing the broad effects of these policies. The industries studied are agriculture, pharmaceuticals, semiconductors, computers, civil aircraft, automobiles and residential construction. The policies considered include research and development funding as well as government procurement, education, information dissemination, patent protection, licensing, regulations, and anti-trust policies

    Intern experience at Tech Tran Corporation, Naperville, Illinois: an internship report

    Get PDF
    "Submitted to the College of Engineering of Texas A&M University in partial fulfillment of the requirement for the degree of Doctor of Engineering"Includes reproduction of chapters 1-5 of a report prepared by Tech Tran Corporation for the U.S. Army Electronics Research and Development Command, March 1982, under the title: Preparation of Manufacturing Methods and Technology (MMT) procurement data packages (leaves 90-131)Includes copy of v. 1, no. 1 (March/April 1982) issue of: Manufacturing technology horizons. In addition to bearing leaf numbers 133-152, the pagination of the original publication is given ([1]-20)Includes vita (leaf 184)This report presents a survey of the author's internship experience with Tech Tran Corporation during the period September 1, 1981 through May 1, 1982. The eight month internship was spent as an associate engineer and associate editor assigned to the engineering branch. The intent of this report is to demonstrate that this experience fulfills the requirements of the Doctor of Engineering internship. The author's internship activities are presented to document the achievement of three major objectives: orientation to professional engineering consulting; development of management and interpersonal skills; and recognizable contributions to the internship firm. These objectives were attained through trips to various organizations, meetings, and conferences involved in manufacturing technology, assignments as an engineering consultant representing Tech Tran, and work preformed on three major Tech Tran contracts. The result of this internship experience was an appreciation for both the technical and non-technical aspects of operating an engineering consulting firm. The conclusion of the report is that the objectives were realized, and the internship requirements for the degree of Doctor of Engineering were satisfied
    corecore