CS Store Search
Displaying 1-6 out of 6 total
Achieving and Maintaining CMMI Maturity Level 5 in a Small Organization
By Davide Falessi,Michele Shaw,Kathleen Mullen
Issue Date:September 2014
CMMI (Capability Maturity Model Integration) models are collections of best practices that help organizations improve their processes. This article reports on the authors' experience in achieving and maintaining CMMI Maturity Level 5 in a small organizatio...
Investigating Automatic Static Analysis Results to Identify Quality Problems: An Inductive Study
2012 35th Annual IEEE Software Engineering Workshop (SEW)
By Antonio Vetro,Nico Zazworka,Forrest Shull,Carolyn Seaman,Michele A. Shaw
Issue Date:October 2012
Background: Automatic static analysis (ASA) tools examine source code to discover "issues", i.e. code patterns that are symptoms of bad programming practices and that can lead to defective behavior. Studies in the literature have shown that these...
Decision Support with EMPEROR
Empirical Software Engineering and Measurement, International Symposium on
By Michele A. Shaw, Raimund L. Feldmann, Forrest Shull
Issue Date:September 2007
Selecting the right practice or technology for a given task should be based on the project goals and context. The selection process should be supported by empirical evidence and experiences with the practice in similar contexts . Practitioners, however,...
Software Process Improvement in Small Organizations: A Case Study
By Kathleen Coleman Dangle, Patricia Larsen, Michele Shaw, Marvin V. Zelkowitz
Issue Date:November 2005
A case study of a five-year-old startup company looks at the role of process improvement in the context of a small organization. It explores why the company realized that process improvement was necessary for continued growth. The company is implementing m...
Investigating the impact of design debt on software quality
Found in: Proceeding of the 2nd working on Managing technical debt (MTD '11)
By Carolyn Seaman, Forrest Shull, Michele A. Shaw, Nico Zazworka
Issue Date:May 2011
Technical debt is a metaphor describing situations where developers accept sacrifices in one dimension of development (e.g. software quality) in order to optimize another dimension (e.g. implementing necessary features before a deadline). Approaches, such ...
Building empirical support for automated code smell detection
Found in: Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM '10)
By Carolyn Seaman, Forrest Shull, Jan Schumacher, Michele Shaw, Nico Zazworka
Issue Date:September 2010
Identifying refactoring opportunities in software systems is an important activity in today's agile development environments. The concept of code smells has been proposed to characterize different types of design shortcomings in code. Additionally, metric-...
Original Search Engine
Need a Web Account?
Become a Member
This site and all contents (unless otherwise noted) are Copyright ©2008, IEEE, Inc. All rights reserved.