Using Design Patterns, Analysis Pattern, and Case-Based Reasoning to Improve Information Modeling and Method Engineering in Systems Development

Information modeling (IM) is the process of identifying information needs and models based onuser requirements and systems analysts’ perceptions during systems analysis and design. WhenIM is done correctly, it facilitates communication between the analysts and end-users about thefinal software product. In addition, successful IM provides a formal basis for both the analystsand the end-users about the tools and techniques that will be used in software development(SD), which, in turn, reduces costly overruns in time and money during systemsimplementation. Method engineering (ME) is the process of designing, constructing, andadapting information modeling methods for information systems development. As Siau (2003)and Kavakli (2005) point out that, while there has been a steady increase in IM and ME research(e.g. Kawalek & Wastell 2003, Kavakli 2005, Matulevicius 2005), most of the models reportedin recent literature are still primarily based on common sense approach, and, as a result, lack aslid theoretical foundation.This paper discusses the feasibility of combining design patterns (DPs), analysis patterns (APs) andcase-based reasoning (CBR) to improve information modeling and method engineering. Recentresearch in DP, AP, and CBR has proven that all those methods are effective in softwaredevelopment. In this paper, we propose a model that combines DP, AP and CBR as a tool toimprove IM and ME. We believe that the use of DP and AP, along with CBR will facilitate easiercommunication among systems analysts, end-users and software engineers thus improve on heefficiency in software development. In the paper, we also provide illustrative examples fromaccounting systems design to show the effectiveness of our proposed model. Finally, we provideevidence in this paper that the practical application of DPs, APs and CBR to systems developmentmakes it possible to identify and resolve critical issues and risks at earlier stages in IM and ME, andeventually lead to high quality end product

The evolution of tropos: Contexts, commitments and adaptivity

Software evolution is the main research focus of the Tropos group at University of Trento (UniTN): how do we build systems that are aware of their requirements, and are able to dynamically reconfigure themselves in response to changes in context (the environment within which they operate) and requirements. The purpose of this report is to offer an overview of ongoing work at UniTN. In particular, the report presents ideas and results of four lines of research: contextual requirements modeling and reasoning, commitments and goal models, developing self-reconfigurable systems, and requirements awareness

A Goal-based Framework for Contextual Requirements Modeling and Analysis

Requirements Engineering (RE) research often ignores, or presumes a uniform nature of the context in which the system operates. This assumption is no longer valid in emerging computing paradigms, such as ambient, pervasive and ubiquitous computing, where it is essential to monitor and adapt to an inherently varying context. Besides influencing the software, context may influence stakeholders' goals and their choices to meet them. In this paper, we propose a goal-oriented RE modeling and reasoning framework for systems operating in varying contexts. We introduce contextual goal models to relate goals and contexts; context analysis to refine contexts and identify ways to verify them; reasoning techniques to derive requirements reflecting the context and users priorities at runtime; and finally, design time reasoning techniques to derive requirements for a system to be developed at minimum cost and valid in all considered contexts. We illustrate and evaluate our approach through a case study about a museum-guide mobile information system

Requirements modelling and formal analysis using graph operations

The increasing complexity of enterprise systems requires a more advanced analysis of the representation of services expected than is currently possible. Consequently, the specification stage, which could be facilitated by formal verification, becomes very important to the system life-cycle. This paper presents a formal modelling approach, which may be used in order to better represent the reality of the system and to verify the awaited or existing system’s properties, taking into account the environmental characteristics. For that, we firstly propose a formalization process based upon properties specification, and secondly we use Conceptual Graphs operations to develop reasoning mechanisms of verifying requirements statements. The graphic visualization of these reasoning enables us to correctly capture the system specifications by making it easier to determine if desired properties hold. It is applied to the field of Enterprise modelling

Early aspects: aspect-oriented requirements engineering and architecture design

This paper reports on the third Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design Workshop, which has been held in Lancaster, UK, on March 21, 2004. The workshop included a presentation session and working sessions in which the particular topics on early aspects were discussed. The primary goal of the workshop was to focus on challenges to defining methodical software development processes for aspects from early on in the software life cycle and explore the potential of proposed methods and techniques to scale up to industrial applications

Knowledge formalization in experience feedback processes : an ontology-based approach

Because of the current trend of integration and interoperability of industrial systems, their size and complexity continue to grow making it more difficult to analyze, to understand and to solve the problems that happen in their organizations. Continuous improvement methodologies are powerful tools in order to understand and to solve problems, to control the effects of changes and finally to capitalize knowledge about changes and improvements. These tools involve suitably represent knowledge relating to the concerned system. Consequently, knowledge management (KM) is an increasingly important source of competitive advantage for organizations. Particularly, the capitalization and sharing of knowledge resulting from experience feedback are elements which play an essential role in the continuous improvement of industrial activities. In this paper, the contribution deals with semantic interoperability and relates to the structuring and the formalization of an experience feedback (EF) process aiming at transforming information or understanding gained by experience into explicit knowledge. The reuse of such knowledge has proved to have significant impact on achieving themissions of companies. However, the means of describing the knowledge objects of an experience generally remain informal. Based on an experience feedback process model and conceptual graphs, this paper takes domain ontology as a framework for the clarification of explicit knowledge and know-how, the aim of which is to get lessons learned descriptions that are significant, correct and applicable