Pierre Flener, PhD, Docent
Pierre.Flener at it.uu.se
Shari Lawrence Pfleeger.
Software Engineering: Theory and Practice.
For the project management, we shall follow:Watts S. Humphrey.You must use/adapt its on-line supplements, such as the forms and the support tool.
TSPi - Introduction to the Team Software Process.
For the requirements process, we shall follow:Suzanne Robertson and James Robertson.You must use/adapt its Volere Requirements Specification Template.
Mastering the Requirements Process.
Upon appointment only, the instructor holds office hours for each team, in his office or elsewhere (the location is to be arranged by the team).
There are no lessons and no labs, all practice being achieved through the project.
Upon filled-out forms from each student, the instructor divides the class into teams (ideally of size 5, otherwise of size 6), and assign a precise role to each team member, early on in the course. The instructor is the coach for the teams, as well as their client and user. The same project is then launched by all teams.
Through appointments with the client/user, each team elaborates a requirements specification (version 1) for a software helping to solve the problem. Upon constructive feedback from the client/user and coach, each team eventually has to produce 2 more versions of their requirements specification, because of errors & inadequacies in earlier versions and/or because the client/user is changing his mind.
Each team also has to come up with a design specification (or module architecture) (version 1) corresponding to their requirements specification. Upon constructive feedback from the coach, each team eventually has to produce 1 more version of their design specification, because of errors & inadequacies in the earlier version and/or because of the occurring changes in the requirements specification!
Finally, without actually writing the software, each team has to produce a test plan according to which they would validate & verify the software, such that it would give them a reasonable degree of confidence in their software.
Within the first exam, each team will have a 2 hour oral project postmortem with the instructor, only over the final versions of their documents for the project, and maybe over some of the course material.
30% of the grade depend on the requirements specification
20% of the grade depend on the design specification
10% of the grade depend on the test-plan
20% of the grade depend on participation in the classroom and in meetings with the instructor
20% of the grade depend on participation in internal team meetings, according to anonymous peer-evaluation
The second exam will be a written exam over the course material. It is reserved for those who failed the first exam and thus actually participated in a project team, as the project is a mandatory part of the course and can only be taken while the course takes place.
Check here if you used one of my many abbreviations and notations when copying from the board, but cannot remember what it means...
Former students enjoying the project work!