Experiences from introducing UML-based development in a large safety-critical project

Anda, Bente; Hansen, Kai T.; Gullesen, Ingolf; Thorsen, Hanne Kristin

doi:10.1007/s10664-006-9020-6

Cited by 68 publications

(43 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The first study [4], investigated the effects of adopting UML-based development on the company's development process. The results showed that the UML-based method led to improved traceability of requirements to code, improved communication within the development teams (and to some extent in the reviews), improved design of the code, quicker development of test cases and better coverage of these, and a product that was better documented than were previous products.…”

Section: Earlier Studiesmentioning

confidence: 99%

“…Several benefits have previously been reported related to improved documentation, design and testing in the company. However, challenges have also been noted, particularly those that are caused by the company's large base of legacy code [3,4,27]. The study reported in this paper focuses on the use case modelling part of the UML-based development.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

An investigation of use case quality in a large safety-critical software development project

Anda

Hansen

Sand

2009

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

Section: Earlier Studiesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

An investigation of use case quality in a large safety-critical software development project

Anda

Hansen

Sand

2009

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

“…but since larger development projects typically are broken down into smaller parts, and individual parts are often modelled by different teams (Anda et al, 2004), the task of the experiment may be representative for small tasks in industrial development projects. The class diagrams created by the subjects of the experiments contained between four and thirteen classes.…”

Section: The Role Of Use Cases In the Construction Of Class Diagramsmentioning

confidence: 99%

“…This task may influence the results. In particular, the results may be different on a larger system, and if development is based on existing systems (Anda et al, 2004).…”

Section: Experimental Materialsmentioning

confidence: 99%

Investigating the Role of Use Cases in the Construction of Class Diagrams

Anda

Sjøberg

2005

Empir Software Eng

Self Cite

View full text Add to dashboard Cite

Several approaches have been proposed for the transition from functional requirements to objectoriented design. In a use case-driven development process, the use cases are important input for the identification of classes and their methods. There is, however, no established, empirically validated technique for the transition from use cases to class diagrams. One recommended technique is to derive classes by analyzing the use cases. It has, nevertheless, been reported that this technique leads to problems, such as the developers missing requirements and mistaking requirements for design. An alternative technique is to identify classes from a textual requirements specification and subsequently apply the use case model to validate the resulting class diagram. This paper describes two controlled experiments conducted to investigate these two approaches to applying use case models in an object-oriented design process. The first experiment was conducted with 53 students as subjects. Half of the subjects used a professional modelling tool; the other half used pen and paper. The second experiment was conducted with 22 professional software developers as subjects, all of whom used one of several modelling tools. The first experiment showed that applying use cases to validate class diagrams constructed from textual requirements led to more complete class diagrams than did the derivation of classes from a use case model. In the second experiment, however, we found no such difference between the two techniques. In both experiments, deriving class diagrams from the use cases led to a better structure of the class diagrams. The results of the experiments therefore show that the technique chosen for the transition from use cases to class diagrams affects the quality of the class diagrams, but also that the effects of the techniques depend on the categories of developer applying it and on the tool with which the technique is applied.

show abstract

“…Use cases have gradually become a widely accepted requirement specification technique both in research domain [2,10,13,32,33,74,103,151] as well as, to some extent, in industrial practice [8,9,39,59,109]. Nevertheless, their inherent utilization of natural language and a behavior of requirement documentation in a semi-conventional way, mean that they are affected by issues such as ambiguity, redundancy, inconsistency, and incompleteness [2,32,146].…”

Section: Introductionmentioning

confidence: 99%