A component-based product line architecture for workflow management systems

This paper presents a component-based product line for workflow management systems. The process followed to design the product line was based on the Catalysis method. Extensions were made to represent variability across the process. The domain of workflow management systems has been shown to be appropriate to the application of the product line approach as there are a standard architecture and models established by a regulatory board, the Workflow Management Coalition. In addition, there is a demand for similar workflow management systems but with some different features. The product line architecture was evaluated with Rapide simulation tools. The evaluation was based on selected scenarios, thus, avoiding implementation issues. The strategy that has been used to populate the architecture and experiment with the product line is shown. In particular, the design of the workflow execution manager component is described

Reusing three-phase power-flow object components for unbalanced harmonic analysis

In this paper, the harmonic penetration method is developed as a component-based application. The direct nodal voltage harmonic solution is developed as an independent software component and then integrated with existing three-phase power-flow software components. The harmonic solution reuses many facilities available in the fundamental frequency power-flow object components. The nonlinear devices such as six pulse converters are modeled as entity objects and inherited from the basic object-oriented power-system device model at fundamental frequency. Also, the linear solver also is reused form the power-flow component library. The application of object components shows that the development of complicated algorithms becomes easy due to the high code reusability

Flexible Framework For A Web Transactional Application

Software development project becomes difficult because of the complexity in the business requirements, rigid framework and unpredictable performance. These cause difficulties to deliver the software on time, to maintain it and to adapt to new requirements. This research proposes a Web-Based Transactional Application Architecture Framework (WTBF) to simplify the development of a complex software project by using template approach that contains assembled pieces of reusable software components. The framework provides a generalized component-based architectural template that can be reused by the users (software developer and an independent software vendor) to develop multi-tier transactional applications within a specific domain or for a new software project. One of its significant benefits is that users can concentrate on their business components development tasks instead of spending time on redeveloping basic software infrastructure from the scratch. The WTBF framework is developed by using the Java 2 Technology and the Model View Controller (MVC) is used for the architectural model

Overview of Requirements Engineering Process for Software Product Lines

Software Product Lines is an important strategy to minimize costs and time-to market, and maximize quality and productivity of the software development. It involves the management of variabilities and commonalities among several applications, which increases its complexity compared to traditional software development. In this context, a Requirements Engineering and management are central tasks, important to reduce the risks involved in a development of product line. System requirements must be properly identified, analysed and reviewed in order to provide adequate solution to manage variabilities and integrating them for making easy the products derivation. In this paper Requirements Engineering process and techniques used in some of the product line practices are reviewed and discussed. Also, Requirements Engineering techniques for traditional single product software development are analysed and their applicability in product line development is assessed. This work is licensed under a&nbsp;Creative Commons Attribution-NonCommercial 4.0 International License.</p

The Unified Software Development Process and Framework Development

Uygulama iskelet yapıları çok umut vaadeden bir yeniden kullanım yazılım teknolojisidir. Uygulama iskelet yapılarının geliştirilmesi karmaşık bir süreci gerektirir. Bu karmaşık süreci minimize etmek amacıyla birçok yöntem ve yaklaşım önerilmiştir. Birleşik Yazılım Geliştirme Süreci bugünkü yazılım uygulamalarındaki karmaşıklık engelini direkt olarak hedefleyen bir yöntemdir. Bu yazıda uygulama iskelet yapılarındaki karmaşıklığın yönetimi konusunda Birleşik Yazılım Geliştirme Süreci'nin rolü yaygın olarak kullanılan bir CASE (Bilgisayar Destekli Yazılım Mühendisliği) aracı olan "Rational Rose" ile birlikte araştırılmaya çalışılmıştır.Application frameworks are a very promising software reuse technology. The development of application frameworks is a complex process. Many methodologies and approaches have been proposed with the purpose of minimizing the complexities. The Unified Software Development Process directly addresses the complexity challenge of today's software applications. In this paper, we explore the role of the Unified Software Development Process together with a popular CASE tool: Rational Rose, in managing the complexity of developing application frameworks

The Unified Software Development Process and Framework Development

Uygulama iskelet yapıları çok umut vaadeden bir yeniden kullanım yazılım teknolojisidir. Uygulama iskelet yapılarının geliştirilmesi karmaşık bir süreci gerektirir. Bu karmaşık süreci minimize etmek amacıyla birçok yöntem ve yaklaşım önerilmiştir. Birleşik Yazılım Geliştirme Süreci bugünkü yazılım uygulamalarındaki karmaşıklık engelini direkt olarak hedefleyen bir yöntemdir. Bu yazıda uygulama iskelet yapılarındaki karmaşıklığın yönetimi konusunda Birleşik Yazılım Geliştirme Süreci'nin rolü yaygın olarak kullanılan bir CASE (Bilgisayar Destekli Yazılım Mühendisliği) aracı olan "Rational Rose" ile birlikte araştırılmaya çalışılmıştır.Application frameworks are a very promising software reuse technology. The development of application frameworks is a complex process. Many methodologies and approaches have been proposed with the purpose of minimizing the complexities. The Unified Software Development Process directly addresses the complexity challenge of today's software applications. In this paper, we explore the role of the Unified Software Development Process together with a popular CASE tool: Rational Rose, in managing the complexity of developing application frameworks

Spl needs an automatic holistic model for software reasoning with feature models

The number of features and their relations in a Software Product Line (SPL) may lead to have SPLs with a big number of potential products which may be difficult to manage. This number of potential products widely increases if, as well as functional features, extra–functional features are taken into account. There are several questions that a SPL engineer would like to ask to his SPL model such as: is it a valid model?, how many potential products a SPL has?, is there any product fulfilling the customer needs? and so forth. These types of questions are error prone to answer without an automatic support. The work reported in this position paper glipmses some misconceptions of previous related proposals: we uphold the need to have an holistic product line model were not distinction are made between functional and extra–functional features, we propose a model based on a formalism strong enough to support both type o features: contraint programming.Ministerio de Ciencia y Tecnología TIC2003-02737-C02-0

Knowledge Management Challenges in Renewal of R&D Processes in Software Business

A software company operates in a dynamic, knowledge intensive business. To stay competitive in such a business, the R&D processes and their development play a significant role. Knowledge management becomes a factor when organizing knowledge work. This paper is based on a qualitative case study conducted in a software company moving to component based production. In addition to theoretical insights, the paper describes the KM challenges involved in this process and suggests solutions to these. Also some managerial implications are proposed