General Information:

The information here corresponds to Semester 1 of the session 2009-2010.

See the G52LSS Module Specification.

Timetable for Semester 1 in 2009-2010:
-- Friday 13:00-14:00 in LT3-EXCHGE
-- Friday 16:00-17:00 in LT2-EXCHGE

See the Module Reading List.

Topics

Lecture 1 -- Introduction, Reading 1 (pdf 4 up, pdf 6 up)

Lecture 2 -- Large Systems Development (pdf 4 up, pdf 6 up)

Lecture 3(x2) -- Rapid and Agile Development, Reading 2 (pdf 4 up, pdf 6 up)

Lecture 4 -- Project Initiation, Reading 3, Reading 4 (pdf 4 up, pdf 6 up)

Lecture 5 -- Project Management, (pdf 4 up, pdf 6 up)

Lecture 6 -- Project Scheduling with PERT (pdf 4 up, pdf 6 up)

Lecture 7 -- Critical Path Method (pdf 4 up, pdf 6 up)

Lecture 8 -- GANTT Charts and CPM (pdf 4 up, pdf 6 up)

Lecture 9 -- Project Re-scheduling (pdf 4 up, pdf 6 up)

Lecture 10 -- Requirements Analysis, (pdf 4 up, pdf 6 up) Reading 5, Reading 6

Lecture 11 -- Information Gathering Methods (pdf 4 up, pdf 6 up)

Lecture 12 -- Defining System Requirements (pdf 4 up, pdf 6 up)

Lecture 13 -- Use Case Analysis (pdf 4 up, pdf 6 up)

Lecture 14 -- Process Modelling with DFDs (pdf 4 up, pdf 6 up)

Lecture 15 -- Constructing DFDs (pdf 4 up, pdf 6 up)

Lecture 16 -- Validating DFDs (pdf 4 up, pdf 6 up)

Lecture 17 -- Process Specification (pdf 4 up, pdf 6 up)

Lecture 18 -- The Design Phase (pdf 4 up, pdf 6 up)

Lecture 19 -- Implementation and Maintenance (pdf 4 up, pdf 6 up)

Lecture 20 -- Summary and Revision(pdf 4 up, pdf 6 up)

Assessment:

Coursework (40%)

The coursework for this module is a group assignment and it involves an exercise on Project Planning and Analysis.

The submission date for the whole coursework is Tuesday 08-December 2009 at 16:00 hrs (4pm). Please contact Ondrej (oxr@cs.nott.ac.uk) if you have any questions about the coursework.

In this coursework you will approach several of the steps in Systems Development Life Cycle for a given scenario. The requirements and conditions for each step are described in the CourseWork specification. It is very important that the groups maintain constant communication and work steadily in order to complete the assignment and achieve good results.

STEP 1 - Forming Groups

The class will been organised in groups of 4 (or 3) students. Please contact Ondrej (oxr@cs.nott.ac.uk) by Friday 6th November if you wish to propose yuor group members (see email). Please make sure that you establish communication with every member of your group. The group must select a representative who will act as the spokesperson to report progress and group issues to the lecturer. Please note that being the group representative does not imply that the person has more or less responsibility, it is just to establish a clear point of contact between the lecturer and each group. Those students who do not get in touch with their group soon after allocation, might be moved from their original group to another group so that those groups that are well-formed can start their coursework. Also, please note that when reporting the work for the assignment, only students who contributed to the work should be included in the submission, i.e. the group is not forced to include everyone when submitting the coursework. Doing otherwise is unethical and the group as a whole is responsible for this. Moreover, together with the final submission on 8-December 2009, each member of the group will be asked to assess the overall contribution of each person to the group work and this will be used to fine-tune individual marks. The groups for this session will be published here. If you are not in that list please let me know now!

STEP 2 - The Coursework
use the first pages of the coursework specification as the cover page for the submission of your coursework. The cover page should include only the names of those team members who actually contributed to the coursework.

The coursework specification is now available. The whole coursework must be submitted electronically and in printed form as indicated in the cover page.

STEP 3 - Peer Assessment of Contribution (mandatory)

Please assess the contribution of every member of your team on the completion of the Coursework (including yourself). Rate the individual contribution using one of the following numbers:

• 1 means 'Poor' contribution
• 2 means 'adequate' contribution
• 3 means 'substantial' contribution

Please note that:

• Each student's contribution gets anonymously rated by the other members of the team.
• The mark is adjusted only for those that participated in the coursework, that is, those listed in the coursework cover sheet.
• The formula to adjust the marks will not be revealed to avoid team members negotiating a target mark.
• If everyone rates each other the same, marks are not adjusted for anyone in the team and everyone gets the same mark which already reflects the overall quality of the work.
• You MUST submit the peer assessment as soon as possible but no later than Friday 12-December-2008 by 17:00 HRS.
• Not sending the peer assessment will provoke that your mark is penalised.

What to do next? Please use this text file to enter your assessment and submit through the CS submission system. You can establish a remote connection to your CS server, so there should be no problem to submit your peer assessment even if you left Nottingham already.

There will be some feedback available here on the module assessment.

Examination (60%)

The exam exam is a multiple choice style and because of this format, past exam papers are not available. In the Summary and Revision Lecture, sample questions will be shown and guidelines on how to prepare for the examination will also be provided.

Resit Examination: weighting is 100%, i.e. coursework is not taken into account for resits marks.