Two marks will be entered into Ladok:
(a) one mark (U, G or VG) for the exam, (= 2 points)
(b) one mark (U or G) for the project reports (= 2 points).
The mark for the exam is returned in the normal way. G corresponds to obtaining 50% or more on the exam, while VG corresponds to obtaining 70% or more on the exam.
The mark for the project reports is the mark obtained by your project group. There is no individual mark which can be different for each group member. This means it is up to you to ensure that your colleagues do some work!
To obtain G as a final result on the project component, it is necessary to obtain at least G on *each* of the 4 reports. Any report which receives the grade U, must be rewritten and resubmitted, until the grade G is obtained.
(1) The coursebook this year will again be
Roger Pressman, "Software Engineering, A Practitioner's Approach" , McGraw Hill, 2000,
ISBN 0-07-709677-0.
The university bookshop has 17 copies in store!
Here is the web version of instructions for the MVK Practical Project Work 2004.
An excellent portal for online resources on project management and software engineering is gantthead.com
Software Dioxide is an internet portal for software engineering resources, including project management.
A question I am often asked is: "aren't there any lightweight lifecycle models?". Here is the ultimate lightweight model (RUP inspired) for a 1 man/week project.
The entire PSS 05 standard can be found online in ascii format here and in MS Word format here
Here are some links to example documents in a waterfall development model. Here is a very simple Software requirements specification (SRD)
A much larger example of and SRD (which follows the PSS 05 standard) can be found here
Finally, a good account of how object oriented methods can be used during the SRS phase can be found here
Here are some more links to relevant CERN web pages. Here is an article about relevant technologies (design languages and tools) for the ADD phase (also called the high-level design phase).
Here is a link to the detailed public report about the Arianne 5 flight 501 disaster. You can find out further information by typing "Arianne + 5" into your favourite search engine.
Here is some more info on CMM.
An interesting survey article on the CMM and the latest revised version, CMMI, can be found here.
This year's coursebook (2004) will be:
Roger S. Pressman, "Software Engineering, A Practitioner's Approach" , McGraw Hill, 2000,
ISBN 0-07-709677-0.
The book is very comprehensive, and covers most (but not all) of the topics we will consider.
For the project component we will still make extensive use of:
C. Mazza, J. Fairclough et al., "Software Engineering
Standards", Prentice Hall, 1994,
ISBN 0-13-106568-8.
This book provides a detailed description of the ESA engineering methodology standard PSS 05, which will be used for the course. Note, it is not necessary to buy this book.
Here is a link to Ian Sommerville's on-line software engineering resources. It contains a comprehensive list of links to sites relevant for the course.
Here is a link to more information on formal methods, which are covered in the course. It includes more information on FM tools, including SDT and the TRIO language.
Here is annotated set of templates for the PSS 05 documents URD, SRD and ADD online!
Up to Nada's home page.