Module Title |
Software Process Quality
|
Module Code |
CA650
|
School |
School of Computing
|
Online Module Resources
|
Module Co-ordinator | Mr Renaat Verbruggen | Office Number | L2.43 |
Level |
1
|
Credit Rating |
7.5
|
Pre-requisite |
None
|
Co-requisite |
None
|
|
Module Aims
|
The goal of this module is to provide a systematic study of the software development process with an emphasis software quality, quality management, software process definition and software process improvement (SPI). This module will expose students to the principles of high quality software development processes and, identify the tasks that are essential for successful projects, discuss how tasks interact with each other, and discuss how an organization can develop and mature its software development process. It will also present the issues and approaches involved in software quality assurance both from the testing and the company practice points of view.The specific objectives of the module are:· Understand and define the scope of the software process· Understand the problems and concerns of software project managers · Define the stages of software projects · Measure the success of a project in meetings its goals· Understand SPI, its current models, methods and approaches.· Establish a process-focused software development organisation · Design and implement procedures for developing software quality · Understand the issues and approaches involved in software quality assurance at the company practice level· Understand the main approaches to software testing· Understand and be able to implement testing solutions at code level. · Benchmark organisations against industry standards for both software quality and software process models
|
Learning Outcomes
|
The student will have a sound understanding of the key issues surrounding the areas of software process and software quality. In particular, they will have a good understanding of management activities of software projects from a quality process perspective and will be able to actively participate in an SPI and quality management activities within an organisation context.After successfully completing this course students will: · be familiar with terminology used in discussing quality-orientated software development processes · have read and analyzed important historical and current literature addressing software processes (life cycle models, process models, etc.) and software quality assurance · understand the concepts embodied in the most prevalent software development process models, including knowledge of their advantages and disadvantages, and when it may be appropriate to use each approach· be able to construct and represent a quality-orientated software process for an organization or project · understand the factors that are important in building the capability or maturity of a software development organization, · be able to assess the maturity level of a software development organization, · understand factors that contribute to successful process change implementation, and · be able to plan and implement a software process improvement activity
|
Indicative Time Allowances
|
|
Hours
|
Lectures |
36
|
Tutorials |
|
Laboratories |
|
Seminars |
|
Independent Learning Time |
76.5
|
|
|
Total |
112.5
|
Placements |
|
Assignments |
|
|
NOTE
|
Assume that a 7.5 credit module load represents approximately 112.5 hours' work, which includes all teaching, in-course assignments, laboratory work or other specialised training and an estimated private learning time associated with the module.
|
Indicative Syllabus
|
· Software lifecycle· Software project management · Software Quality Management and Assurance· Software Process Management· Standards
|
Assessment | Continuous Assessment | 25% | Examination Weight | 75% |
|
Indicative Reading List
|
· Software Process Improvement, S.Zahran, Addison Wesley· Software Project Management , B.Hughes and M.Cotterell, McGraw Hill.Supplementary: · Software Project Management in Practice, Pankaj Jalote, Addison Wesley· Managing the Software Process, W.Humphrey, Addison Wesley· A Discipline for Software Engineering, W.Humphrey, Addison Wesley· T. Dyba, T. Diingsoyr and N. Brede-Moe SPI in Practice (A Handbook for IT Companies), Kluwer· T. Gilb and D. Graham. Software Inspection. Addison-Wesley· Quality Software Project Management, Robert T. Futrell, Donald F. Shafer, Linda I. Safer· Quality Software Project Management, Robert T. Futrell, Donald F. Shafer, Linda I. SaferThe course will be accompanied by a set of journal articles and other on-line resources to ensure that teaching materials are up to date with current technology and trends.
|
|
Programme or List of Programmes
|
BSSA | Study Abroad (DCU Business School) |
BSSAO | Study Abroad (DCU Business School) |
CAPD | PhD |
CAPM | MSc |
CAPT | PhD-track |
ECSA | Study Abroad (Engineering & Computing) |
ECSAO | Study Abroad (Engineering & Computing) |
EEPD | PhD |
EEPM | MEng |
EEPT | PhD-track |
GSE | Graduate Diploma in Software Engineering |
HMSA | Study Abroad (Humanities & Soc Science) |
HMSAO | Study Abroad (Humanities & Soc Science) |
MEPD | PhD |
MEPM | MEng |
MEPT | PhD-track |
MSE | MSc in Software Engineering |
NAVNMU | Non Award Visitors- UCD/DCU |
SHSA | Study Abroad (Science & Health) |
SHSAO | Study Abroad (Science & Health) |
Archives: | |