PUMA

academical publication management
collect, organize, and share publications

( en | de )

 

Disambiguation of "Lindvall, Mikael"

Author of the publication

copydeleteadd this publication to your clipboard
What We Have Learned About Fighting Defects.

, , , , , , , , , and . IEEE METRICS, page 249-. IEEE Computer Society, (2002)

Please choose a person to relate this publication to

To differ between persons with the same name, the academic degree and the title of an important publication will be displayed. You can also use the button next to the name to display some publications already assigned to the person.

No persons found for author name Lindvall, Mikael
add a person with the name Lindvall, Mikael
 

Other publications of authors with the same name

An Extended Replication of an Experiment for Assessing Methods for Software Requirements Inspections., , , , , and . Empirical Software Engineering, 3 (4): 327-354 (1998)Avoiding Architectural Degeneration: An Evaluation Process for Software Architecture., , and . IEEE METRICS, page 77-86. IEEE Computer Society, (2002)Bridging the Gap between Business Strategy and Software Development., , , , , , , and . ICIS, page 25. Association for Information Systems, (2007)Detecting Security Vulnerabilities with Software Architecture Analysis Tools., , and . ICST Workshops, page 262-268. IEEE Computer Society, (2008)Does the Code Match the Design? A Process for Architecture Evaluation., , and . ICSM, page 393-. IEEE Computer Society, (2002)Lessons Learned about Structuring and Describing Experience for Three Experience Bases., , , and . LSO, volume 2176 of Lecture Notes in Computer Science, page 106-119. Springer, (2001)Good Change and Bad Change: An Analysis Perspective on Software Evolution., , , , and . Trans. Found. Mastering Chang., (2016)Combating architectural degeneration: a survey., and . Information & Software Technology, 47 (10): 643-656 (2005)Connecting research and practice: an experience report on research infusion with software architecture visualization and evaluation., , , , , , , , and . ISSE, 8 (4): 255-277 (2012)Understanding Change Requests to Predict Software Impact., and . SEW, page 66-75. IEEE Computer Society, (2006)