Docstoc

Software Process Improvement

Document Sample
Software Process Improvement Powered By Docstoc
					    Software Process Improvement



By:
Parham Darbandi Tehrani - 6719902
Padamati Shekar Reddy - 6693377
      Software Process Improvement
                              History

State-of-the-art software practices in 1984, for large software
systems [Jones, 1995]:

  • More than half were late in excess of 12 months
  • Average cost was more than twice the initial budget
  • Cancellation rate exceeded 15%
  • Quality and reliability was poor, for both small and large projects
  • Software personnel were increasing by more than 10% per year
  • Software was the largest known business expense that could not
    be managed
   Software Process Improvement
                     Means


“understanding existing processes and changing
these processes to increase product quality and/or
reduce costs and development time.”
   Software Process Improvement
                        approach 1


The process maturity approach:
  • improving process
  • project management
  • introducing good software engineering practice into an
    organization


The primary goals
  • Improved product quality
  • Process predictability.
    Software Process Improvement
                        approach 2


The agile approach
  • Iterative development
  • reduction of overheads in the software process


The primary characteristics
  • Rapid delivery of functionality
  • Responsiveness to changing customer requirements
Process attributes
        Software Process Improvement
           The process improvement cycle

                                    Attributes of the current process
                                    Forms a baseline




Changes to the process that have   The current process is assessed and
been identified during the         bottlenecks and weaknesses are
analysis are introduced.           identified.
     Software Process Improvement
       Frameworks and Methodologies


Models and certifications that help assess the state of the
organization’s process and serve as a framework for improving
that process.
CMM, ISO 9000 : frameworks

There are also methodologies that an organization can adopt that
describe the complete set of activities, roles, and work products
needed to build software.
RUP, XP : methodologies
Software Process Improvement
           CMMI
Software Process Improvement
           SPICE
   Software Process Improvement
                     Strengths


Based on best practices
Provides a vision
Management tool for improvement
Changes are prescribed
Explicit priority to quality
    Software Process Improvement
                  Weaknesses

Product quality not         Continuation difficult
addressed                    Dependency on individual
Lack of measurement         managers
No cost/benefit analysis    Phasing not logical
included                     Improvement takes long
Too generic                 Risk for bureaucracy
No project level support:
(for large organisations)
   Software Process Improvement
                    Conclusion

no best model, none is complete
people are key (managers, quality managers,
developers)
bottom-up vs top-down (cost, infrastructure)


reasons:
business requirement (certification)
productivity (better, cheaper, faster)
Software Process Improvement
               Software Process Improvement
                                                     References

1. Sommerville, Ian. "Process Improvement." Software Engineering. 9Th ed. Boston: Pearson, 2011. 705-30. Print.
2. U.S. General Accounting Office. “DoD Information Technology: Software and Systems Process Improvement Programs Vary in Use of Best
Practices.” GAO-01-116. Washington, D.C.: GAO, Mar. 2001
3. McFeeley, R., 1996. IDEAL: A Users Guide for Software Process Improvement (Technical Report CMU/SEI-96-HB-001 ). Pittsburgh: Software
Engineering Insitute, Carnegie Mellon University. http://www.sei.cmu.edu/library/abstracts/reports /96hb001.cfm
4. Austin, R., Paulish, D., A Survey of Commonly Applied Methods for Software Process Improvement, TECHNICAL REPORT CMU/SEI-93-TR-
027, Software Process Measurement, 1993. Print
5. Khokhar, M.N.; Zeshan, K.; Aamir, J.; , "Literature review on the software process improvement factors in the small organizations," New
Trends in Information Science and Service Science (NISS), 2010 4th International Conference on , vol., no., pp.592-598, 11-13 May 2010
6. Harter, D.E.; Kemerer, C.F.; Slaughter, S.A.; , "Does Software Process Improvement Reduce the Severity of Defects? A Longitudinal Field
Study," Software Engineering, IEEE Transactions on , vol.38, no.4, pp.810-827, July-Aug. 2012
7. Jos Trienekens, Rob Kusters, and Rini Van Solingen. 2001. Product Focused Software Process Improvement: Concepts and Experiences
from Industry. Software Quality Control 9, 4 (December 2001), 269-281.
8. Francisco J. Pino, Félix García , and Mario Piattini. 2008. Software process improvement in small and medium software enterprises: a
systematic review. Software Quality Control. 16, 2 (June 2008), 237-261.
9. Layman, B. Implementing an organizational software process improvement program. IEEE Software Engineering, 2, 279-288, 2005 .
10. Wiegers, “Software Process Improvement: Ten Traps to Avoid,” Software Development, May 1996, pp. 51–58.

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:4/2/2013
language:Unknown
pages:16