CS5635 INFORMATION 20/04/17
Software Quality Management
Course Number 4103021
Tuesday 10:15-11:30 and Thursday 10:15-11:30, 工學院 A 館 104
This course introduces principles of software quality management.
Nai-Wei Lin
EA 502, 272-0411 ext. 33110 naiwei@cs.ccu.edu.tw
1. Introduction to software engineering
2. Software process models
3. Software economics
4. Software quality management
5. Software quality concepts
6. Testing techniques for Software validation
7. Planning for software quality management
8. Measurement for software quality assurance
1.
D. Houston, Software Quality professional, ASQC, vol. 1, issue 2, 1999.
2.
IEEE Computer Society, Guide to the Software Engineering Body of Knowledge ,
2004.
3.
IEEE Std 730-2002, IEEE Standard for Software Quality Assurance Plans .
4.
IEEE Std 828-1998 IEEE Standard For Software Configuration Management Plans.
5.
IEEE Std 829-1998 IEEE Standard for Software Test documentation.
6.
IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements
Specifications.
7.
IEEE Std 1012-1998, IEEE Standard for Software Verification and Validation.
8.
IEEE Std 1028-1997 IEEE Standard for Software Reviews .
9.
IEEE Std 1042-1987, IEEE Guide to Software Configuration Management .
10.
IEEE Std 1058-1998 IEEE Standard for Software Project Management Plans .
11.
IEEE Std 1074-1997, IEEE Standard for Developing Software Life Cycle Processes .
12.
IEEE Std 1298-1992 (AS 3563.1-1991), IEEE Standard for Software Quality
Management System, Part 1: Requirements .
13.
IEEE/EIA 12207.0-1996, IEEE/EIA Standard—Industry Implementation of ISO/IEC
12207 : 1995.
14.
IEEE/EIA 12207.1-1997, IEEE/EIA Guide—Industry Implementation of ISO/IEC
12207 : 1995.
15.
IEEE/EIA 12207.2-1996, IEEE/EIA Guide—Industry Implementation of ISO/IEC
12207 : 1995.
1
CS5635 INFORMATION 20/04/17
16.
EIA/IEEE J-STD-016:1995 (IEEE Std 1498), Standard for Information
Technology—Software Life Cycle Processes—Software Development:
Acquirer-Supplier Agreement .
17.
ISO/IEC 12207: 1995, Information Technology—Software Life Cycle Processes .
18.
ISO/IEC 9126-1,2,3,4, Software Engineering Product Quality .
19.
S. H. Kan, Metrics and Models in Software Quality Engineering , Second Edition,
Addison Wesley, 2002.
20.
R. S. Pressman,
Software Engineering: A Practitioner’s Approach
, Sixth Edition,
2004.
21.
Software Engineering Institute, Capability Maturity Model Integration for Software
Engineering (CMMI) , 2002.
22.
I. Sommerville, Software Engineering , Seventh Edition, 2005.
50% Assignments
25% Midterm Exam (November 8)
25% Final Exam (January 10)
Without a prior arrangement, a missed examination results in a grade of zero. The grade for a late assignment is deducted by 10 for each day delayed. The grade for a late assignment is zero if it is delayed more than 3 days. A miss of an examination or an assignment results in a grade of zero for the semester. Assignments in this course require individual attention and effort to be of any benefit. Unless otherwise stated on the assignment sheet, all assignment work is expected to be that of each student alone, and not the product of team efforts or collaboration with other authors. Plagiarism or the incorporation of another student’s words or ideas constitutes theft of intellectual property; it will result in a grade of zero for the semester.
2