Our system is currently under heavy load due to increased usage. We're actively working on upgrades to improve performance. Thank you for your patience.
2009
DOI: 10.1007/978-3-642-04425-0_14
|View full text |Cite
|
Sign up to set email alerts
|

Evaluating the Impact of UML Modeling on Software Quality: An Industrial Case Study

Abstract: Abstract. The contribution of formal modeling approaches in software development has always been a subject of debates. The proponents of model-driven development argue that big upfront designs although require substantial investment will payoff later in the implementation phase in terms of increased productivity and quality. On the other hand, software engineers who are not very keen on modeling perceive the activity as simply a waste of time and money without any real contribution to the final software produc… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
21
0

Year Published

2011
2011
2017
2017

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 25 publications
(21 citation statements)
references
References 20 publications
(22 reference statements)
0
21
0
Order By: Relevance
“…In the context of MDD and MDA paradigms, where models are the basis of the whole development process, the quality of the models has a high impact on the final quality of software systems derived from them [121]. It means that a quality model (i.e.…”
Section: Software Qualitymentioning
confidence: 99%
“…In the context of MDD and MDA paradigms, where models are the basis of the whole development process, the quality of the models has a high impact on the final quality of software systems derived from them [121]. It means that a quality model (i.e.…”
Section: Software Qualitymentioning
confidence: 99%
“…The GQM template for goal definition [12,13] was used to define the goal of our experiment as follows: "Analyze the level of detail in UML models with the purpose of evaluating it with respect to the maintainability of source code from the point of view of researchers, in the context of Computer Science students at the University of Leiden. As in [3], we considered that the LoD in UML models should be defined as the amount of information that is used to represent a modeling element. LoD is a 'continuous' metric, but for the experiment we have taken two "extremes" -high and low LoD.…”
Section: Goalmentioning
confidence: 99%
“…The current increasing complexity of software projects [1] has led to the emergence of UML [2] as a tool with which to increase the understanding between customer and developer and to improve communication among team members [3]. Despite this, not all UML diagrams have the same complexity, layout, level of abstraction, etc.…”
Section: Introductionmentioning
confidence: 99%
“…It first appeared in 1997 and has now become one of the most widely-used modeling languages in industry. There is empirical evidence of its benefits during software development because it increases the understanding between customer and developer and improves communication among team members [6]. UML also improves the source code quality by reducing its defect density [7].…”
Section: Introductionmentioning
confidence: 99%