Objectives and competences
The objective of this course is to give knowledge about quality management (organization process map, software development processes) and methods for process reingeneering and improvement.
Content (Syllabus outline)
• Quality management theory in software development: definition of process, components of a process, motivation for process management, content of the software development process, process areas in information systems development, examples of process areas: requirements management.
• Software quality metrics.
• Quality management and improvement models: activities of process management (definition of process content, implementation of process, assessment of the process efficiency, process improvement, process withdrawal), presentation of models for process improvement (Capability Maturity Model, ITIL, SPICE, ISO 25000) .
• Software quality: standards for software quality evaluation, process of quality evaluation.
• Technical debt measurement and management.
Learning and teaching methods
• lecturing, interactive work,
• development of examples,
• individual work with assistance of teaching assistant.
Intended learning outcomes - knowledge and understanding
On completion of this course the student will be able to
• map the organizational processes for quality management and classify them (supporting, development, administrative),
• manage the selected processes from software lifecycle,
• execute software quality metrics and interpret the results.
Intended learning outcomes - transferable/key skills and other attributes
• Communication skills: verbal (presentation of seminar work), written (exam, seminar work).
• Use of information technology: usage of supporting tools and methods for process management and modeling, tools for software quality evaluation.
• Organization skills: process management, software quality evaluation.
• Problem solving: software lifecycle exception management
• Working in a group: working in small groups
Readings
• I. Sommerville, Software Engineering, 9th Ed, Pearson, 2011
• Crispin, L., & Gregory, J. (2009). Agile testing: a practical guide for testers and agile teams (p. XLI, 533). Addison-Wesley.
• Martin, R. C., Feathers, M. C., Ottinger, T. R., Langr, J. J., Schuchert, B. L., Grenning, J. W., & Wampler, K. D. (2009). Clean code: a handbook of agile software craftsmanship (p. XXIX, 431). Prentice Hall.
• Galin, D. (2004). Software quality assurance: from theory to implementation (p. XXVI, 590). Pearson Education; Addison Wesley.
• Tian, J. (2005). Software quality engineering: testing, quality assurance, and quantifiable improvement (p. XXVI, 412). J. Wiley. http://www.loc.gov/catdir/toc/ecip051/2004022229.html
Prerequisits
Understanding the software lifecycle and methodologies is recommended.
Additional information on implementation and assessment Written exam may be replaced by a midterm exams.
