A programming language view to model-driven engineering

MDE provides an appealing framework for supporting engineering activities, from early design phases to acceptance tests; going through refinement, architectural and functional design down to code generation and V&V efforts. Yet, separation of concerns between system engineers, architects and embedded domain experts may badly interact. by lack of a exchange mechanisms at both syntactic and semantic levels. Pivot meta-models also demonstrated their limits. In this talk, I'll illustrate on various projects how the use of a text-based modeling notation, combined with a strong semantics inherited from typical object-oriented languages, can support seamless integration of most concerns of a traditional V cycle, thus solving many issues in MDE approaches. I'll base my presentation on present current discussions part of the AADL standardization committee to enrich Architecture Description Language with a Constraint language. The objective is to increase the coupling between modeling and verification. By making the verification part of extended semantics rules of an ADL, we control the patterns used to describe the system, ensuring designers respect requirements, but also integrate V&V as part of the modeling effort

Sistem Informasi Monitoring Pembayaran Piutang Penjualan Berbasis Web

Progress and development of information technology occur quickly. This encourages business entities or companies to use information technology to support the development of employee performance to make it easier and more efficient. The application of information systems in various fields is now also widely used, one of which is in the field of accounting. However, not all companies have implemented a web-based information system, one example at PT. Sarana Anugerah Perdana. Problems that occur at PT. Sarana Anugerah Perdana is a credit payment monitoring system that still uses semi-computerization so that A.R staff have difficulty distinguishing which customer receivables are due or are due. Based on the background of the problem, the authors want to create a web-based monitoring system at PT. Sarana Anugerah Perdana. This research was conducted using the SWOT analysis method, system requirements elicitation and system design using UML (Unified Modeling Language) to visualize. In addition, the programming language used is PHP (Hypertext Preprocessor), database server with MySQL, sublime text 2, CodeIgniter framework and web server with XAMPP. With the existence of a system of monitoring the payment of accounts receivable, it can facilitate AR staff (Account Receivable) in monitoring customer receivables and also facilitate in making and producing payment reports and accurate accounts receivable

Requirements analysis for decision-support system design: evidence from the automotive industry

The purpose of this paper is to outline the requirements analysis that was carried out to support the development of a system that allows engineers to view real-time data integrated from multiple silos such as Product Lifecycle Management (PLM) and Warranty systems, in a single and visual environment. The outcome of this study provides a clear understanding of how engineers working in different phases of the product-lifecycle could utilise such information to improve the decision making process and as a result design better products. This study uses data collected via in-depth semi-structured interviews and workshops that includes people working in various roles within the automotive sector. In order to demonstrate the applicability this approach, SysML diagrams are also provided

Miki: a wiki for synchronous modeling of software requirements

Eliciting a high quality requirements model that can be traced down to implementations is a challenge. Keeping models updated for evolving software systems is a further challenge. Formal modelling methods are one approach - but one that is too rigid and costly for many small software engineering companies [1]. We propose a light-weight alternative, using a wiki as the synchronous bridge between requirements capture and more formal modeling features of the IDE such as Eclipse

User-centred design of flexible hypermedia for a mobile guide: Reflections on the hyperaudio experience

A user-centred design approach involves end-users from the very beginning. Considering users at the early stages compels designers to think in terms of utility and usability and helps develop the system on what is actually needed. This paper discusses the case of HyperAudio, a context-sensitive adaptive and mobile guide to museums developed in the late 90s. User requirements were collected via a survey to understand visitors’ profiles and visit styles in Natural Science museums. The knowledge acquired supported the specification of system requirements, helping defining user model, data structure and adaptive behaviour of the system. User requirements guided the design decisions on what could be implemented by using simple adaptable triggers and what instead needed more sophisticated adaptive techniques, a fundamental choice when all the computation must be done on a PDA. Graphical and interactive environments for developing and testing complex adaptive systems are discussed as a further step towards an iterative design that considers the user interaction a central point. The paper discusses how such an environment allows designers and developers to experiment with different system’s behaviours and to widely test it under realistic conditions by simulation of the actual context evolving over time. The understanding gained in HyperAudio is then considered in the perspective of the developments that followed that first experience: our findings seem still valid despite the passed time

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