| 1. |
|
|
| 2. |
- Aurum, Aybüke, et al.
(author)
-
Aligning Requirements with Business Objectives : A Framework for Requirements Engineering Decisions
- 2005
-
Conference paper (peer-reviewed)abstract
- As software development continues to increase in complexity, involving far-reaching consequences, there is a need for decision support to improve the decision making process in requirements engineering (RE) activities. This research begins with a detailed investigation of the complexity of decision making during RE activities on organizational, product and project levels. Secondly, it presents a conceptual model which describes the RE decision making environment in terms of stakeholders, information requirements, decision types and business objectives. The purpose of this model is to facilitate the development of decision support systems in RE and to help further structure and analyse the decision making process in RE.
|
|
| 3. |
|
|
| 4. |
|
|
| 5. |
- Aurum, Aybüke, et al.
(author)
-
Increasing the Understanding of Effectiveness in Software Inspections Using Published Data Sets
- 2005
-
In: Journal of Research and Practice in Information Technology. - 1443-458X. ; 37:3, s. 51-64
-
Journal article (peer-reviewed)abstract
- Since its inception into software engineering software inspection has been viewed as a cost-effective way of increasing software quality. Despite this many questions remain unanswered regarding, for example, ideal team size or cost effectiveness. This paper addresses some of these questions by performing an analysis using 30 published data sets from empirical experiments of software inspections. The main question is concerned with determining a suitable team size for software inspections. The effectiveness of different team sizes is also studied. Furthermore, the differences in mean effectiveness between different team sizes are investigated based on the inspection environmental context, document types and reading technique. It is concluded that it is possible to choose a suitable team size based on the effectiveness of inspections. This can be used as a tool to assist in the planning of inspections. A particularly interesting result is that variation in the effectiveness between different teams is considerably higher for certain types of documents than for others. Our findings contain important information for anyone planning, controlling or managing software inspections.
|
|
| 6. |
|
|
| 7. |
- Aurum, Aybüke, et al.
(author)
-
The Fundamental Nature of Requirements Engineering Activities as a Decision-Making Process
- 2003
-
In: Information and Software Technology. - : Elsevier. - 0950-5849 .- 1873-6025. ; 45:14, s. 945-954
-
Journal article (peer-reviewed)abstract
- The requirements engineering (RE) process is a decision-rich complex problem solving activity. This paper examines the elements of organization-oriented macro decisions as well as process-oriented micro decisions in the RE process and illustrates how to integrate classical decision-making models with RE process models. This integration helps in formulating a common vocabulary and model to improve the manageability of the RE process, and contributes towards the learning process by validating and verifying the consistency of decision-making in RE activities.
|
|
| 8. |
- Barney, Sebastian, et al.
(author)
-
A product management challenge : Creating software product value through requirements selection
- 2008
-
In: Journal of Systems Architecture. - Cavtat, CROATIA : ELSEVIER SCIENCE BV. - 1383-7621 .- 1873-6165.
-
Conference paper (peer-reviewed)abstract
- It is important for a software company to maximize value creation for a given investment. The purpose of requirements engineering activities is to add business value that is accounted for in terms of return on investment of a software product. This paper provides insight into the release planning processes used in the software industry to create software product value, by presenting three case studies. It examines how IT professionals perceive value creation through requirements engineering and how the release planning process is conducted to create software product value. It also presents to what degree the major stakeholders' perspectives are represented in the decision-making process. Our findings show that the client and market base of the software product represents the most influential group in the decision to implement specific requirements. This is reflected both in terms of deciding the processes followed and the decision-making criteria applied when selecting requirements for the product. Furthermore, the management of software product value is dependant on the context in which the product exists. Factors, such as the maturity of the product, the marketplace in which it exists, and the development tools and methods available, influence the criteria that decide whether a requirement is included in a specific project or release. (C) 2007 Elsevier B.V. All rights reserved.
|
|
| 9. |
- Barney, Sebastian, et al.
(author)
-
Balancing Software Product Investments
- 2009
-
In: [Host publication title missing]. - Orlando, Florida : IEEE. - 1938-6451. - 9781424448425 ; , s. 257-268
-
Conference paper (peer-reviewed)abstract
- The long-term sustainability of a software product depends on more than developing features. Priorities are placed on aspects that support the development of software, like software product quality (eg. ISO 9126), project constraints -- time and cost, and even the development of intellectual capital (IC). A greater focus on any one aspect takes priority from another, but as each aspects delivers a different type of value managers have trouble comparing and balancing these aspects. This paper presents a method to help determine the balance between key priorities in the software development process. The method is applied to a new case study, that also combines with results from previous studies. The results show it is possible to compare features, quality, time, cost and IC in a comprehensive way, with the case study showing that participants perceive a change from a shorter-term product perspective to a longer-term organisation beneficial to the business.
|
|
| 10. |
- Barney, Sebastian, et al.
(author)
-
Creating Software Product Value in China
- 2009
-
In: IEEE Software. - : IEEE Computer Society. - 0740-7459. ; 26:4
-
Journal article (peer-reviewed)abstract
- China has become a formidable player and continues to grow strongly in what has become a dynamic global market for software development. In this highly competitive environment it has never been more difficult or important to maximize the creation of software product value. But each key stakeholder group – purchasers, users, software managers and developers – has a different notion of value when looking at a software product. As the value of a software product is largely derived through the requirements it fulfils, we looked at the criteria used to select and prioritise requirements for a release of software, and the perspectives that motivate them. The value of a software product is largely derived through the requirements it fulfils. To help understand how value is created we looked at the criteria used to select and prioritise requirements for a release of software, and the perspectives that motivate them. We studied three groups of software development companies operating in China – Chinese companies with a domestic market, Chinese companies with an international market, and western companies operating in China. The results were similar for all three groups, except After-sales Support was a significantly greater concern for Chinese companies with an international market.
|
|
