| 1. |
|
|
| 2. |
- Aurum, A, et al.
(författare)
-
State-of-the-art: software inspections after 25 years
- 2002
-
Ingår i: Software Testing, Verification & Reliability. - : Wiley. - 0960-0833 .- 1099-1689. ; 12:3, s. 133-154
-
Tidskriftsartikel (refereegranskat)abstract
- Software inspections, which were originally developed by Michael Fagan in 1976, are an important means to verify and achieve sufficient quality in many software projects today. Since Fagan's initial work, the importance of software inspections has been long recognized by software developers and many organizations. Various proposals have been made by researchers in the hope of improving Fagan's inspection method. The proposals include structural changes to the process and several types of support for the inspection process. Most of the proposals have been empirically investigated in different studies. This is a review paper focusing on the software inspection process in the light of Fagan's inspection method and it summarizes and reviews other types of software inspection processes that have emerged in the last 25 years. This paper also addresses important issues related to the inspection process and examines experimental studies and their findings that are of interest with the purpose of identifying future avenues of research in software inspection.
|
|
| 3. |
- Aurum, Aybüke, et al.
(författare)
-
The Fundamental Nature of Requirements Engineering Activities as a Decision-Making Process
- 2003
-
Ingår i: Information and Software Technology. - : Elsevier. - 0950-5849 .- 1873-6025. ; 45:14, s. 945-954
-
Tidskriftsartikel (refereegranskat)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.
|
|
| 4. |
- Berander, Patrik, et al.
(författare)
-
Differences in Views between Development Roles in Software Process Improvement : A Quantitative Comparison
- 2004
-
Konferensbidrag (refereegranskat)abstract
- This paper presents a quantitative study that evaluates how different roles in a software development organization view different issues in software process improvement. The study is conducted in a large Swedish telecommunication organization with the traditional roles of software development. The respondents of the study got five different questions related to process improvement. The result was that the different roles disagreed in three of the questions while they agreed in two of the questions. The disagreement was related to issues about importance of improvement, urgency of problems, and threat against successful process management, while the questions where the roles agreed focused on communication of the processes (documentation and teaching). It is concluded that it is important to be aware and take into account the different needs of different roles and that looking into other areas (e.g. marketing) could be beneficial when conducting process improvements.
|
|
| 5. |
- Berander, Patrik, et al.
(författare)
-
Identification of Key Factors in Software Process Management : A Case Study
- 2003
-
Konferensbidrag (refereegranskat)abstract
- When conducting process related work within an organization, it is important to be aware of which factors that are most important to consider. This paper presents an empirical study that was performed in order to find the key success factors in process management. One factor, namely synchronization of processes, was considered as much more important within the studied organization than within the studied literature. This shows that more research might be needed in this area. The study further shows that it is important to relate process improvement work to the properties of the affected organization and that the key factors identified are highly interrelated.
|
|
| 6. |
- Bratthall, Lars, et al.
(författare)
-
Is it Possible to Decorate Graphical Software Design and Architecture Models with Qualitative Information? : An Experiment
- 2002
-
Ingår i: IEEE Transactions on Software Engineering. - : IEEE. - 0098-5589 .- 1939-3520. ; 28:12, s. 1181-1193
-
Tidskriftsartikel (refereegranskat)abstract
- Software systems evolve over time and it is often difficult to maintain them. One reason for this is often that it is hard to understand the previous release. Further, even if architecture and design models are available and up to date, they primarily represent the functional behaviour of the system. To evaluate whether it is possible to also represent some non-functional aspects, an experiment has been conducted. The objective of the experiment is to evaluate the cognitive suitability of some visual representations that can be used to represent a control relation, software component size and component external and internal complexity. Ten different representations are evaluated in a controlled environment using 35 subjects. The results from the experiment show that it representations with low cognitive accessibility weight can be found. In an example, these representations are used to illustrate some qualities in an SDL block diagram. It is concluded that the incorporation of these representations in architecture and design descriptions is both easy and probably worthwhile. The incorporation of the representations should enhance the understanding of previous releases and hence help software developers in evolving and maintaining complex software systems.
|
|
| 7. |
|
|
| 8. |
- Damm, Lars-Ola, et al.
(författare)
-
Determining the Improvement Potential of a Software Development Organization through Fault Analysis : A Method and a Case Study
- 2004
-
Konferensbidrag (refereegranskat)abstract
- Successful software process improvement depends on the ability to analyze past projects and determine which parts of the process that could become more efficient. One typical data source is the faults that are reported during product development. From an industrial need, this paper provides a solution based on a measure called faults-slip-through, i.e. the measure tells which faults that should have been found in earlier phases. From the measure, the improvement potential of different parts of the development process is estimated by calculating the cost of the faults that slipped through the phase where they should have been found. The usefulness of the method was demonstrated by applying it on two completed development projects at Ericsson AB. The results show that the implementation phase had the largest improvement potential since it caused the largest faults-slip-through cost to later phases, i.e. 81 and 84 percent of the total improvement potential in the two studied projects.
|
|
| 9. |
- Gorschek, Tony, et al.
(författare)
-
Identification of Improvement Issues Using a Lightweight Triangulation Approach
- 2003
-
Konferensbidrag (refereegranskat)abstract
- One of the challenges in requirements engineering is the ability to improve the process and establish one that is “good-enough”. The objective of this paper is to present a lightweight approach to identify process improvement issues. The approach is developed to capture both the views of different stakeholders and different sources of information. An industrial investigation from a small company is presented. In the investigation both projects and the line organization have been interviewed and documentation from them has been studied to capture key issues for improvement. The issues identified from one source are checked against other sources. The dependencies between the issues have been studied. In total nine issues for improvement of the requirements engineering work at the company were identified. It is concluded that the approach is effective in capturing issues, and that the approach helps different stakeholders to get their view represented in the process improvement work.
|
|
| 10. |
- Gorschek, Tony, et al.
(författare)
-
Packaging Software Process Improvement Issues : a Method and a Case Study
- 2004
-
Ingår i: Software, practice & experience. - : John Wiley and Sons Ltd. - 0038-0644 .- 1097-024X. ; 34:14, s. 1311-1344
-
Tidskriftsartikel (refereegranskat)abstract
- Software process improvement is a challenge in general and in particular for small- and medium-sized companies. Assessment is one important step in improvement. However, given that a list of improvement issues has been derived, it is often very important to be able to prioritize the improvement proposals and also look at the potential dependencies between them. This paper comes from an industrial need to enable prioritization of improvement proposals and to identify their dependencies. The need was identified in a small- and medium-sized software development company. Based on the need, a method for prioritization and identification of dependencies of improvement proposals was developed. The prioritization part of the method is based on a multi-decision criteria method and the dependencies are identified using a dependency graph. The developed method has been successfully applied in the company, where people with different roles applied the method. The paper presents both the method as such and the successful application of it. It is concluded that the method worked as a means for prioritization and identification of dependencies. Moreover, the method also allowed the employees to discuss and reason about the improvement actions to be taken in a structured and systematic way.
|
|
