Keywords: Scope Management, Technical Product Management, Software Product Management, Requirements Engineering, Distributed Development, Quality Assurance, Process Assessment, Process Improvement, Innovation, Empirical, Market-driven Product Development of Software Intensive Products, Software and Technology Product Management, Factor Analysis, Value-based Software Engineering (VBSE), product lines, agile / streamline / lean product development.

General about research

I am industry applied, focusing on engineering and application first. My main criteria for success is if my research results are actually used in industry, that is, if I can provide proof of usability and usefulness (efficiency and effectiveness) of the solutions I provide as a response to the challenges identified.

I also believe that engineering researchers (especially in Software Engineering) have to flexible, and adapt to the needs and challenges identified. I started with computer science, evolved towards requirements engineering, but work in several fields such as product management, verification and validation, statistical factor analysis, and agile and lean development. A common theme overall is process assessment and improvement and technology and knowledge transfer. I like being able to tackle problems outside of my comfort zone, and an engineer adapts to solve problems.

Current research projects

-> Software Value Analysis (Telenor)(start 2013-ongoing)

The implementation of “agile” methodologies promises waste reduction and improved time-to-market as well as customer satisfaction. However, there is a danger of sub optimization as waste on a project level might not be waste on product level. In addition, maximizing value as customer satisfaction goes beyond short term feature selection. This AGILE/LEAN project is under startup, but involves scaling AGILE and LEAN methodologies up to be able to handle large organizations with complex product development with distributed engineering. As an example we are looking at finding a balance between agility and long-term maintainability, but the project handles the entire product development cycle.

--> Software Value Analysis (Ericsson)(start 2009-ongoing)

Re-defining how software is valued. This involved the creation of the Software Value Map, value patterns and themes to support product development at Ericsson. [download poster]

Keywords: Value based software engineering, product management, requirements engineering, decision support, measurement, reuse.

--> Global Engineering (Daimler AG)(start 2009-ongoing)

Daimler AG faces many challenges and a complex product development environment spread over global partners. Excellence in handling and optimizing distributed development includes GSE practices, models, but also statistical factor analysis to measure feature coherence.

Keywords: Global Software Engineering, Automotive, Factor Analysis, Reuse, Refactoring.

--> Value and Innovation BESQ+ (IBM, Ericsson, Qtema)(start 2011-ongoing)

In the value context, companies need to estimate total cost of ownership and total value of ownership for a software product or a feature, which enables a cost basis for determining the economic value of that product or feature. This requires estimating total direct capital investment in hardware and software plus indirect costs of installation, training, maintenance, downtime, technical support, and upgrading. These estimations will help in making decisions that are better for value creation. This calls for a radical reinvention of the value term to include all perspectives of software value, ranging from what implication a decision today has on the architecture, sustainability, innovation and quality, to user perspectives like usability and user experience.

Keywords: Value based software engineering, product management, requirements engineering, decision support, measurement, innovation.

--> Verification and Requirements Engineering EASE  (Axis)(start 2011-ongoing)

Adaptive Framework for Streamlined Requirements and Test Co-optimization involves the utilization of natural overlap between requirements and test to achieve a minimal overlap and waste by using variation selection aspects. Variations depend on e.g. domain, criticality, time-to-market etc, making it possible to choose what type of requirements engineering and tests to perform in relation to the needs and goals of the organization. Variation selection aspects can be used on company, product or even feature level to adapt what is done to assure good-enough for purpose.

Keywords: Verification and Validation, Requirements Engineering, Taxonomy, Co-optimization.

--> Lean Software Development (Volvo PV)(start 2008-ongoing)

Introduce lean software product development focusing on complex automotive projects. This project has thus far mapped challenges in the boundary between product development, software development, and production to an extremely detailed extent. The continuation is to add automotive lean to software development, and enhance the lean standard, enabling effective and efficient collaboration in product development.

Keywords: Lean / Streamline / Agile, Automotive, Process Assessment and Improvement, Project Management, Automotive Software.

General about research (Product Management and Requirements Engineering)

As requirements are direct products of the requirements engineering (RE) process inadequacies herein can have severe consequences. These consequences are mainly due to the fact that problems in requirements filter down to design and implementation, and several sources indicate that inadequate requirements are the leading source for project failure. If RE is studied in the context of a market-driven incremental product development situation, which is becoming increasingly commonplace in software industry, requirements engineering is also a prerequisite for release planning activities, i.e. the decision about which customers get what features and quality at what point in time, which in itself is a major determinant of the success of a product. The importance of having an adequate RE process in place that produces good enough requirements can be considered as crucial to the successful development of products, whether it be in a bespoke or market-driven development effort. There are however clear indications that requirements engineering is lacking in industry since inadequacies in requirements is a major determinant in project failure.

The research is centered on developing processes and models adapted to help enterprises to fulfill their potential with regards to catching, analyzing, prioritizing and managing requirements. This is accomplished through the development of processes/methods/models for a number of important activities:

oAssessment of the Product Management and RE process, i.e. what is the situation today and what are the needs for the future (what to improve and why).

oPlanning support, i.e. what should be improved first and how will these decisions impact the process as a whole (what and how).

A result of the above mentioned activities several needs were identified in industry. To address these needs the Requirements Abstraction Model (RAM) was developed. It was designed to handle requirements coming in from multiple stakeholders on multiple levels of abstraction in a continuous market-driven product development situation. It supports primarily product management with the work-up (abstraction and break-down) of requirements in a structured way, offering abstract requirements comparable to product strategies, as well as refined testable requirements as input to development. The idea behind this model is to offer tangible and everyday support to engineers working with requirements, and enable them to produce good enough requirements for product and project planning, as well as establishing what to develop.

In addition to this the technology of Implementation Proposals has also been developed to ensure that distributed development environments are efficient and effective and correspond to the quality and engineering goals set by an advanced Technical Product and Requirements Management process.

A major consideration taken during the research was that the results should be applicable and practically usable in industry. The close cooperation with industry partners, as well as validation of the results in industry was designed to help ensure this. The impact of the research is twofold, first, the development and validation of tools/methods to help small and medium sized enterprises to perform assessments and perform improvement planning activities. A major consideration in this case was that the research results produce affordable and practical processes/models enabling and motivating the initiation of improvement. Second, the development and validation of the Requirements Abstraction Model was a result of several needs identified in industry. The model can be used by organizations to catch, analyze and manage requirements, and offers structure and repeatability to the RE process. It is also important to realize that the model was developed to be adaptable to almost any organization and product.

The development of Implementation Proposals was also based in industry needs as the development environments become more and more complex as they often are spread over geographical and cultural boundaries. This demanded an controlled and controllable technical handshaking process be created that could ensure the successful planning, design and overall development of products.

Industry impact

Several technologies (models, processes, techniques, and frameworks) have been validated in industry with very good results. Due to confidentiality reasons no actual ROI numbers can be published in dollars and cents. However, the figures below are all published in scientific publications (see publications). There you can download more information about the technologies.

The Requirements Abstraction Model (RAM)©

Improvement in requirements quality by over 30% efficiency improved by 30%, defect decrease by more than 25%.

Implementation Proposals with Handshaking©

Effort estimation accuracy increase by between 50-70%, defect decrease by about 40%.

See: http://list.bth.se/pipermail/pressreleaser/2006-October/000014.html

The Market-driven Requirements Engineering Model (REPM)©

A light-weight process assessment and improvement model for companies working in a market-driven context.

See: http://www.bth.se/mdrepm

General items of interest in relation to research








current research projects