Title: Software Reuse Based on Business Processes and Requirements
Abstract:Software reuse is often just addressed at the level of code or low-level design. In contrast, this tutorial explains software reuse based on business processes and requirements. It presents and compar...Software reuse is often just addressed at the level of code or low-level design. In contrast, this tutorial explains software reuse based on business processes and requirements. It presents and compares three approaches co-developed by the presenter over more than a decade. The first of these approaches deals with requirements reuse in the context of product lines. It makes the relations among product line requirements explicit, so that single system requirements in this product line can be derived consistently. A key issue is commonality and variability across different products. This tutorial shows how requirements for a product line can be modeled, selected and reused to engineer the requirements for innovative new products. The second approach for software reuse involves case-based reasoning. Instead of explicit relations between requirements (or other artifacts), similarity metrics are employed for finding the most similar software case in a repository to a given set of requirements. This even works when a single envisioned usage scenario is specified yet, and it allows reusing also requirements from retrieved cases. The major point, however, is to facilitate reusing software design (including architecture) and code from similar software cases. The third approach (still under development) strives for (partly) automating software development for certain business applications through reusing business knowledge and software, where both are tightly connected. It involves automated reuse of business processes, and software executing them, based on ontological knowledge. A key point is closing the representational gap between procedurally represented business processes and declaratively represented concepts and their relations, taxonomies, partonomies, etc. So, this is an ontology-based approach for (partly) automated software development guided by business models.Read More
Publication Year: 2013
Publication Date: 2013-12-01
Language: en
Type: article
Indexed In: ['crossref']
Access and Citation
Cited By Count: 4
AI Researcher Chatbot
Get quick answers to your questions about the article from our AI researcher chatbot