2,843 research outputs found

    Framework for Product Lifecycle Management integration in Small and Medium Enterprises networks

    Get PDF
    In order to improve the performance of extended enterprises, Small and Medium Enterprises (SMEs) must be integrated into the extended networks. This integration must be carried out on several levels which are mastered by the Product Lifecycle Management (PLM). But, PLM is underdeveloped in SMEs mainly because of the difficulties in implementing information systems. This paper aims to propose a modeling framework to facilitate the implementation of PLM systems in SMEs. Our approach proposes a generic model for the creation of processes and data models. These models are explained, based on the scope and framework of the modeling, in order to highlight the improvements provided

    Metamodel-based model conformance and multiview consistency checking

    Get PDF
    Model-driven development, using languages such as UML and BON, often makes use of multiple diagrams (e.g., class and sequence diagrams) when modeling systems. These diagrams, presenting different views of a system of interest, may be inconsistent. A metamodel provides a unifying framework in which to ensure and check consistency, while at the same time providing the means to distinguish between valid and invalid models, that is, conformance. Two formal specifications of the metamodel for an object-oriented modeling language are presented, and it is shown how to use these specifications for model conformance and multiview consistency checking. Comparisons are made in terms of completeness and the level of automation each provide for checking multiview consistency and model conformance. The lessons learned from applying formal techniques to the problems of metamodeling, model conformance, and multiview consistency checking are summarized

    A taxonomy of asymmetric requirements aspects

    Get PDF
    The early aspects community has received increasing attention among researchers and practitioners, and has grown a set of meaningful terminology and concepts in recent years, including the notion of requirements aspects. Aspects at the requirements level present stakeholder concerns that crosscut the problem domain, with the potential for a broad impact on questions of scoping, prioritization, and architectural design. Although many existing requirements engineering approaches advocate and advertise an integral support of early aspects analysis, one challenge is that the notion of a requirements aspect is not yet well established to efficaciously serve the community. Instead of defining the term once and for all in a normally arduous and unproductive conceptual unification stage, we present a preliminary taxonomy based on the literature survey to show the different features of an asymmetric requirements aspect. Existing approaches that handle requirements aspects are compared and classified according to the proposed taxonomy. In addition,we study crosscutting security requirements to exemplify the taxonomy's use, substantiate its value, and explore its future directions

    An information-centric approach to enterprise modelling for product recovery

    Get PDF
    Recovery of used products and materials is becoming a field of rapidly growing importance. The scope and scale of product recovery have expanded tremendously over the past decade. Recent changes in government legislation in various countries and increasing customer awareness towards greener products have forced the manufacturers to rethink their business strategies. This has also resulted in new business opportunities in the area of remanufacturing and a large number of small and medium enterprises (SMEs) have appeared in the recovery industry. These SMEs include reprocessing and recycling companies as well as freight forwarders and warehousing companies. Recovery firms have to deal with customer demands and returns that are largely dependant on the state of the art in technology. They change without any warnings and unfortunately a third party recovery firm has little control over them as compared to an original equipment manufacturer (OEM). In such situations, these companies must not only quickly adapt to the changes but also continuously evolve to survive in the market. They have to be versatile, changeable and able to quickly redesign and modify their own facilities and processes to cope with the changing situations. This paper presents an information–centred formal model for product recovery enterprises to aid the designers with modelling and evaluation tools to enable progressive design of the enterprise. The modelling exercise in this work involves description of the different views of the enterprise, namely strategic view, physical view, functional view and performance view. The analysis of the system (as part of the performance view) has been carried out using simulation

    MaDe4IC: an abstract method for managing model dependencies in inter-organizational cooperations

    Get PDF
    Inter-organizational cooperations are complex in terms of coordination, agreements, and value creation for involved partners. When managing complex cooperations, it is vital to maintain models describing them. Changing one model to regain consistency with the running system might result in new inconsistencies. As a consequence, this maintenance phase grows in complexity with increasing number of models. In this context, challenges are to ensure consistency at design time and to monitor the system at runtime, i.e., at design time, consistency between different models describing the cooperation needs to be ensured. At runtime, behavior of the software system needs to be compared with its underlying models. In this paper, we propose a structured and model-independent method that supports ensuring and maintaining consistency between running system and underlying models for inter-organizational cooperations

    Second ECOOP Workshop on Precise Behavioral Semantics (with an Emphasis on OO Business Specifications)

    Full text link
    Business specifications are essential to describe and understand businesses (and, in particular, business rules) independently of any computing systems used for their possible automation. They have to express this understanding in a clear, precise, and explicit way, in order to act as a common ground between business domain experts and software developers. They also provide the basis for reuse of concepts and constructs ("patterns") common to all - from finance to telecommunications -, or a large number of, businesses, and in doing so save intellectual effort, time and money. Moreover, these patterns substantially ease the elicitation and validation of business specifications during walkthroughs with business customers, and support separation of concerns using viewpoints.Comment: 21 pages, 0 figure

    Managing Evolutionary Method Engineering by Method Rationale

    Get PDF
    This paper explores how to integrate formal meta-models with an informal method rationale to support evolutionary (continuous) method development. While the former provides an exact and computer-executable specification of a method, the latter enables concurrent learning, expansion, and refinement of method use (instances of meta-models) and meta-models (evolution of method specifications). We explain the need for method rationale by observing the criticality of evolving method knowledge in helping software organizations to learn, as well as by the recurrent failure to introduce rigid and stable methods. Like a design rationale, a method rationale establishes a systematic and organized trace of method evolution. Method rationale is located at two levels of type-instance hierarchy depending on its type of use and the scope of the changes traced. A method construction rationale garners a history of method knowledge evolution as part of the method engineering process, which designs and adapts the method to a given organizational context. A method use rationale maintains knowledge of concrete use contexts and their history and justifies further method deployment in alternative contexts, reveals limitations in its past use, and enables sharing of method use experience. The paper suggests how a method rationale helps share knowledge of methods between method users and engineers, explores how method engineers coordinate the evolution of the existing method base through it, and suggests ways to improve learning through method rationale

    A Framework for Constraint-Programming based Configuration

    Get PDF

    Software Product Line

    Get PDF
    The Software Product Line (SPL) is an emerging methodology for developing software products. Currently, there are two hot issues in the SPL: modelling and the analysis of the SPL. Variability modelling techniques have been developed to assist engineers in dealing with the complications of variability management. The principal goal of modelling variability techniques is to configure a successful software product by managing variability in domain-engineering. In other words, a good method for modelling variability is a prerequisite for a successful SPL. On the other hand, analysis of the SPL aids the extraction of useful information from the SPL and provides a control and planning strategy mechanism for engineers or experts. In addition, the analysis of the SPL provides a clear view for users. Moreover, it ensures the accuracy of the SPL. This book presents new techniques for modelling and new methods for SPL analysis
    • 

    corecore