最新糖心Vlog

The objectives of this course are:

• To introduce students to the Software Engineering Institute's Personal Software Process, PSP, and
• To help students reflect on their own software development process.

At the end of the course students should be able to,

1. articulate a critical view of the Personal Software Process,
2. articulate a critical view of their own software development process,
3. write essays following the structure of a scientific paper and
4. apply the PSP to their work.

Textbook:
A Self-Improvement Process for Software Engineers, Watts S. Humphrey, Addison-Wesley, 2005, ISBN 0321305493.

Web page

• All course materials including lecture slides and assignment descriptions will be available on the course website.

Moodle

• We will be using the Computer Science Moodle forums.
• A link to the forums is available on the course website.
• All general questions relating to the course and its content must be posted to the forums.
• Any changes to the assessment requirements will be posted to the forums.

The background material is presented using lectures and is reinforced by the programming assignments and essays.

The key learning takes place by practicing the major components of the Personal Software Process through the programming assignments. Each programming assignment requires all previous assignments to have been completed correctly or the PSP cannot be practised appropriately.

Personal planning and time management are integral to the PSP and will be practised by the strict delivery of assignments on time and in the correct order.

The essays provide opportunities to research issues relevant to the practical application of the PSP and other software process improvement tools. They also require reflection on the significance of these tools and how the practical impact they can have.

The time commitment for a 3 unit course is 10 to 12 hours per week.

Lectures Topics

• Introduction to the PSP
• Process Measurement
• Planning
• The PROBE Technique
• Quality Issues
• Project Tracking
• Software Design
• PSP Review

Component 1: Programming Assignments - 20%

• Up to 10 programs - 2% each
• Programs 1 to 10 are due by 11.59pm on Friday of weeks 1 to 10 respectively.
• Hurdle requirement: 6 programs must be completed by 11.59pm on Friday of week 12.
• CBOK* areas: Abstraction, design, programming, systems development.

Component 2: Personal Process Review - 20%

• Due by 11.59pm on Friday of week 13.
  
• CBOK* areas: Professionalism, interpersonal communication, systems development.

Component 3: Essays - 60%

• Essay 1 - 10%
  Parts 1 and 2 are due by 11.59pm on Friday of week 3.
• Essay 2 - 20%
  Part 1 is due by 11.59pm on Friday of week 5.
  Part 2 is due by 11.59pm on Friday of week 6.
• Essay 3 - 30%
  Part 1 is due by 11.59pm on Friday of week 12.
  Part 2 is due by 11.59pm on Friday of week 13.
• Hurdle requirement: must score 40% of the available marks for Essay 3.
• CBOK* areas: Interpersonal communication, systems development.

The programming assignments, essay 1 and essay 2 are formative, essay 3 and the process review are summative.

*Details of the 最新糖心Vlogn Computer Society's Core Bode of Knowledge (CBOK) can be found in .

Completion of Programming Assignments
A programming assignment will not be considered to be complete until it has been assessed as acceptable by the course coordinator. A programming assignment will not be assessed as acceptable if there are any corrections required to be made or any previous programming assignments have not yet been accepted.

Hurdle Requirements
If one or more hurdle requirements are not achieved, the final mark for the course will be capped at 44 F.

Detailed descriptions of all assessments will be available on the course website.

Submission of Work for Assessment

• All assignments must be submitted using the Computer Science Web Submission System.
• The process review and essays will be submitted to turnitin.com for plagiarism detection.

Extensions for Assessment Tasks
Extensions will only be given in exceptional circumstances,

• evidence must be supplied,
• you must apply before the due date, and
• extensions can only be granted by the course coordinator.

Penalties for Late Submission of Programming Assignments
If a programming assignment is completed:

• on-time, it will score 2% of the overall mark for the course, or
• late but by 11.59pm on Friday of week 12, it will score 1% of the overall mark for the course.

When a programming assignment is completed late, the due date for the next programming assignment is 11.59pm on Friday of the next teaching week. The same number of weeks extension is then applied to all later programming assignments. Any programming assignment given a due date after week 12 will not be assessed and will be considered incomplete even if otherwise completed satisfactorily.

Penalties for Late Submission of Other Work

• The maximum mark that can be awarded will reduce by 25% for each day/part day late,
• Marks in excess of the maximum that can be awarded are discarded.
• Assignment work submitted 4 or more days late will receive 0 marks.

On-time Mark	1 Day Late	2 Days Late	3 Days Late	4+ Days Late
25%	25%	25%	25%	0
50%	50%	50%	25%	0
75%	75%	50%	25%	0
100%	75%	50%	25%	0

Provision of Feedback to Students
Marks will not be automatically awarded by the School of Computer Science Web Submission System. However, after each assignment marks and feedback will be posted to the Web Submission System.