16-09-2016, 10:11 AM
[attachment=71064]
What is it about?
Based on Watts Humphrey’s Personal Software Process
Outlined in A Discipline for Software Engineering
You should have finished reading Chapters 1-4 already!
Six relatively easy programming assignments
On C
Focus on learning and understanding the process
Assignments map to Humphrey’s 1A-6A exercises
You’ll be submitting one assignment per week
Except on Thanksgiving and the midterm week
There’ll also be weekly reading assignments
The process will be increasingly elaborated as we go along…
Why are we doing this?
Hardly surprising facts:
1 – Most software projects go wrong
2 – Most software projects do not follow *any* development process
3 – Software projects that do follow some process have a much better chance of survival
It really can be almost any process
Extreme Programming and other Agile styles
Cleanroom
Capability Maturity Model (CMM)
How to get a good grade
Short story:
It’s very easy, really. Just follow the process thoroughly and you’ll do great.
Longer story:
Read ‘A Discipline for Software Engineering’ conscientiously.
Warning: Humphrey is not especially fun or concise
Stick to the process while doing the exercises
Use the forms appropriately
Extract insights from your own work, and report them
Reflections on your performance and on the process
Work on two levels
Quality of your code, quality of your process
Submit your assignments on time
What is it about?
Based on Watts Humphrey’s Personal Software Process
Outlined in A Discipline for Software Engineering
You should have finished reading Chapters 1-4 already!
Six relatively easy programming assignments
On C
Focus on learning and understanding the process
Assignments map to Humphrey’s 1A-6A exercises
You’ll be submitting one assignment per week
Except on Thanksgiving and the midterm week
There’ll also be weekly reading assignments
The process will be increasingly elaborated as we go along…
Why are we doing this?
Hardly surprising facts:
1 – Most software projects go wrong
2 – Most software projects do not follow *any* development process
3 – Software projects that do follow some process have a much better chance of survival
It really can be almost any process
Extreme Programming and other Agile styles
Cleanroom
Capability Maturity Model (CMM)
How to get a good grade
Short story:
It’s very easy, really. Just follow the process thoroughly and you’ll do great.
Longer story:
Read ‘A Discipline for Software Engineering’ conscientiously.
Warning: Humphrey is not especially fun or concise
Stick to the process while doing the exercises
Use the forms appropriately
Extract insights from your own work, and report them
Reflections on your performance and on the process
Work on two levels
Quality of your code, quality of your process
Submit your assignments on time