Software development: A paradigm for the future

A new paradigm for software development that treats software development as an experimental activity is presented. It provides built-in mechanisms for learning how to develop software better and reusing previous experience in the forms of knowledge, processes, and products. It uses models and measures to aid in the tasks of characterization, evaluation and motivation. An organization scheme is proposed for separating the project-specific focus from the organization's learning and reuse focuses of software development. The implications of this approach for corporations, research and education are discussed and some research activities currently underway at the University of Maryland that support this approach are presented

Goals/questions/metrics method and SAP implementation projects

During the last years some researchers have studied the critical success factors (CSFs) in ERP implementations. However, until now, no one has studied how these CSFs should be put in practice to help organizations achieve success in ERP implementations. This technical research report attempts to define the usage of Goals/Questions/Metrics (GQM) approach in the definition of a measurement system for ERP implementation projects. GQM approach is a mechanism for defining and interpreting operational, measurable goals. Lately, because of its intuitive nature the approach has gained widespread appeal. We present a metrics overview and a description of GQM approach. Then we provide an example of GQM application for monitoring sustained management support in ERP implementations. Sustained management support is the most cited critical success factor in ERP implementation projects.Postprint (published version

Integrating automated support for a software management cycle into the TAME system

Software managers are interested in the quantitative management of software quality, cost and progress. An integrated software management methodology, which can be applied throughout the software life cycle for any number purposes, is required. The TAME (Tailoring A Measurement Environment) methodology is based on the improvement paradigm and the goal/question/metric (GQM) paradigm. This methodology helps generate a software engineering process and measurement environment based on the project characteristics. The SQMAR (software quality measurement and assurance technology) is a software quality metric system and methodology applied to the development processes. It is based on the feed forward control principle. Quality target setting is carried out before the plan-do-check-action activities are performed. These methodologies are integrated to realize goal oriented measurement, process control and visual management. A metric setting procedure based on the GQM paradigm, a management system called the software management cycle (SMC), and its application to a case study based on NASA/SEL data are discussed. The expected effects of SMC are quality improvement, managerial cost reduction, accumulation and reuse of experience, and a highly visual management reporting system

Modelling the Strategic Alignment of Software Requirements using Goal Graphs

This paper builds on existing Goal Oriented Requirements Engineering (GORE) research by presenting a methodology with a supporting tool for analysing and demonstrating the alignment between software requirements and business objectives. Current GORE methodologies can be used to relate business goals to software goals through goal abstraction in goal graphs. However, we argue that unless the extent of goal-goal contribution is quantified with verifiable metrics and confidence levels, goal graphs are not sufficient for demonstrating the strategic alignment of software requirements. We introduce our methodology using an example software project from Rolls-Royce. We conclude that our methodology can improve requirements by making the relationships to business problems explicit, thereby disambiguating a requirement's underlying purpose and value.Comment: v2 minor updates: 1) bitmap images replaced with vector, 2) reworded related work ref[6] for clarit

Towards Automated Context-aware Software Quality Management

To consistently improve software quality management, greater automation and tighter integration of quality tools and measurements in the software engineering environment is essential. However, automation of software quality management faces numerous challenges such as project uniqueness, project dynamics, efficiency, and limited time and quality expenditures. In this paper, an approach is proposed that extends the Goal-Question-Metric technique and automates the monitoring of quality goals via a multi-agent system by using competitive bidding agent behavior for proactive vs. cooperative voting for reactive measures. The preliminary results show promise for systematically harmonizing (conflicting) quality attributes, goals, metrics, and countermeasures and for automating aspects of software quality management

Systematic evaluation of software product line architectures

The architecture of a software product line is one of its most important artifacts as it represents an abstraction of the products that can be generated. It is crucial to evaluate the quality attributes of a product line architecture in order to: increase the productivity of the product line process and the quality of the products; provide a means to understand the potential behavior of the products and, consequently, decrease their time to market; and, improve the handling of the product line variability. The evaluation of product line architecture can serve as a basis to analyze the managerial and economical values of a product line for software managers and architects. Most of the current research on the evaluation of product line architecture does not take into account metrics directly obtained from UML models and their variabilities; the metrics used instead are difficult to be applied in general and to be used for quantitative analysis. This paper presents a Systematic Evaluation Method for UML-based Software Product Line Architecture, the SystEM-PLA. SystEM-PLA differs from current research as it provides stakeholders with a means to: (i) estimate and analyze potential products; (ii) use predefined basic UML-based metrics to compose quality attribute metrics; (iii) perform feasibility and trade-off analysis of a product line architecture with respect to its quality attributes; and, (iv) make the evaluation of product line architecture more flexible. An example using the SEI’s Arcade Game Maker (AGM) product line is presented as a proof of concept, illustrating SystEM-PLA activities. Metrics for complexity and extensibility quality attributes are defined and used to perform a trade-off analysis

Tools Integration for Supporting Software Measurement: A Systematic Literature Review

Software measurement (SM) is a key area to support process quality improvement and project management. Due to the nature of the measurement activities, tool support is essential. Tools can be combined to support the SM process and provide necessary information for decision making. However, tools are usually developed without concern for integration. As a result, organizations have to deal with integration issues to enable communication between tools. Aiming at investigating studies in the literature that report initiatives involving tool integration for supporting SM, we performed a systematic literature review. Twelve initiatives were found. This paper presents the results of the systematic review and discusses the main findings