Course: COMP1632 Systems Development

Project

Contribution: 50% of
course

60: Systems Development Project - CW1 Individual Coursework - Released Term 1 - MAC

PDF file required

Greenwich Course Leader: Mrs Keeran Jamil

Due date: April 2017 TBC

This coursework should take an average student who is up-to-date with tutorial work
approximately 100 hours
Learning Outcomes:
A, B, C

Plagiarism is presenting somebody elses work as your own. It includes:

copying information directly from the Web or books without referencing
the material; submitting joint coursework as an individual effort; copying
another students coursework; stealing or buying coursework from
someone else and submitting it as your own work. Suspected
plagiarism will be investigated and if found to have occurred will be dealt
with according to the procedures set down by the University.
All material copied or amended from any source (e.g. internet,
books) must be referenced correctly according to the reference
style you are using.
Your work will be submitted for electronic plagiarism checking.
Any attempt to bypass our plagiarism detection systems will be
treated as a severe Assessment Offence.
Coursework Submission Requirements

An electronic copy of your work for this coursework should be fully uploaded by
midnight (local time) on the Deadline Date.
The last version you upload will be the one that is marked.
For this coursework you must submit a single Acrobat PDF document. In
general, any text in the document must not be an image (i.e. must not be
scanned) and would normally be generated from other documents (e.g. MS
Office using "Save As .. PDF").
There are limits on the file size. The current limits are displayed on the
coursework submission page on the Intranet
Make sure that any files you upload are virus-free and not protected by a
password or corrupted otherwise they will be treated as null submissions.
Comments on your work will be available from the Coursework page on the
Intranet. The grade will be made available in the portal.
You must NOT submit a paper copy of this coursework.
All coursework must be submitted as above

The University website has details of the current Coursework Regulations, including details
of penalties for late submission, procedures for Extenuating Circumstances, and penalties
for Assessment Offences. See http://www2.gre.ac.uk/current-students/regs for details.

Specification
The Case Study
Student attendance register (SAR) system for the CIS Department
The Department of Computing and Information Systems (CIS) at the University of
Greenwich (UoG) operates an intranet to support its core academic operations. Various
subsystems on the CIS Intranet have read-only access to parts of the main UoG
Academic Information System (AIS) which deals centrally with student registration,
finances and progression
You have been asked to develop a system to record student attendance to teaching
sessions. A teaching session can be a Lecture, a Tutorial session or a Lab session. Each
session is associated with a lead member of staff and a room, lecture theatre or lab
section. Courses run over periods of 13 or 26 weeks, following a set pattern.
The system should allow a course coordinator to maintain lists of students associated
with the course, assign them into one of multiple lecture occurrences and into smaller
tutorial/lab groups associated to tutors and rooms/labs.
The list of students comes from the central AIS system that records all students
registered on a course. Each student is uniquely identified by their Student ID (SID).
The course coordinator can add other students to the register list. These are students
who are attending the course but they have not yet registered officially to the course.
These must be centrally registered UoG students to a valid programme for CIS and
they are identified by their SID or their unique computer systems user ID, also
maintained centrally within the AIS. These students will be attached to the course as
temporary registrations. Once the student registers officially to the course, their
inclusion into the register lists for the course will automatically become permanent.
Tutors on the course can print blank registers for the current week for their own
sessions. Students sign next to their name on the list during the teaching session.
Following this the tutor will enter the student attendance onto the system by entering
a tick next to each attending students name for that session.
During some lecture sessions, a lecturer can pass around the class a customised PDA
with an integral barcode reader. Attending students will scan their student card
barcode using the reader to record their attendance at the session. Following this, the
lecturer will dock the PDA at a cradle at the school office that will record all
attendances onto the register system.
The system also provides individual attendance records and attendance statistics to
tutors, managers and admin staff within the school. Students can only see their own
attendance record by logging onto the system. Finally, the system should provide a
hyperlinked version of a register with links to other information on each system
coming from the central AIS system, such as registration status, holds, student
photograph, programme name and a list of courses the student is officially registered
on.

You are part of a system development team to do the analysis, design and
development of their new hybrid system. They have a tight deadline of 4 months for
the system to go live, staff should be trained within 2 weeks and the analysis, design
and development of the new system should be within the budget of 40,000 pounds as
decided by the Vice Chancellor.
You are required (individually) to model the current business system and propose a
new, integrated software SAR system that will include all current functionality and
enhancements needed.
Your job is to elicit the exact requirements from the client (your tutors). This can be
done in Q and A sessions during class and on the MOODLE discussion forum. However,
you will (as good software engineers) confirm in writing any assumptions and
conclusions you make from these discussions. For example, assumptions and
conclusion can also be made about the different stakeholders and any conflict of
interest they may face.
THIS SHOULD BE DONE VIA the discussion forum. In this way everyone will have
access to all the assumptions, and you will have a confirmation from the teaching
team.

Deliverables
You are required to INDIVIDUALLY produce a report documenting details on your
project management approach, as well as the initial requirements analysis of
the new system. The report should be brief and to the point.
The report should be around 3000 words and must include the
following:
a) A Rich Picture serving as an initial exploration of the primary issues and

b)
c)
d)

e)

f)

stakeholders; Include any assumptions you had to make throughout this

process.
A root definition (and CATWOE) to be used as a starting point for the
proposed design;
A list of functional and non-functional requirements;
A conceptual analysis containing:
Detailed use case diagram accompanied by two narratives (which you
deem to be the main functionality) of the scenario.
Students here should create a detailed use case diagram, with
<<includes>> and <<extends>>. The idea is for them to focus on how
the staff will use the system.
As part of your project plan identify the SMART objectives as well as the
key stakeholders relevant to your project. Assumptions should be stated
clearly.
Attach the Gantt chart for your project plan. You should make sure the
Gantt chart is printed in an appropriate scale and only includes the work
packages and activities (the individual tasks should not be included in the
Gantt chart). You should make sure the individual activities are clearly
identified, and that any dependencies and parallel activities are made
clear.

Other relevant information for your report:

Please include a table of contents
Please make sure to provide a screenshot of your MS Project files in your
report. You can submit the MS Project files separately as well, as a zip file in
the relevant Coursework Submission area by the indicated deadline.
Please remember that large diagrams are best reproduced on a separate
page. You must ensure that the diagrams are readable! Remember that this
coursework is an opportunity to show what you have learned throughout this
first semester of this course.
Please make sure that any assumptions made, need to be stated
clearly in the report.

Grading Criteria
Your work will be assessed for the quality of the individual report you will
produce. In particular, marks will be awarded for:
1) Clear understanding and demonstration of project management tools and
techniques.
2) Correct use of the first three stages of the Soft systems methodology.
3) Correct use of UML notation.
4) Suitability and consistency between the UML models (This includes selecting
suitable aspects to model for each of the diagram types).
5) Coherence between the proposed system, as expressed in the root definition,
with the UML diagrams.
6) Sophistication and novelty of the extra functionalities students will propose.
7) Demonstration of independent thinking.
8) Presentation, structure and coherence of the report.

Assessment Criteria
Typically marks will be awarded as follows:
70+ Excellent
mark A thorough understanding of the subject.
Excellent knowledge of project management tools and
s
techniques.
Mastery of relevant methods and techniques (e.g. UML modelling
and SSM techniques).
Extensive range and consistent accuracy of information and
knowledge.
Fluent argument demonstrating independent thinking or critical
insight.
Outstanding presentation, structure and standard of English.

60- Very Good

A clear understanding of the subject.
69
mark Very good knowledge of project management tools and
techniques.
s
Competent application of relevant models and techniques (e.g.
UML modelling, and SSM techniques).
Wide and accurate range of information and knowledge
deployed.
Clear argument which may demonstrate a degree of
independent thinking or critical insight.
High quality of presentation, structure and standard of English
50-

Good

59
A sound understanding of the subject.
mark Good knowledge of project management tools and techniques.
Knowledge and some application of relevant models and
s
techniques (e.g. UML modelling and SSM techniques).
A standard and largely accurate range of information and
knowledge.
May rely more on knowledge rather than on argument.
Satisfactory quality of presentation, structure and standard of
English.
40- Adequate
Basic understanding of project management techniques.
49
mark A basic understanding of the subject.
Some knowledge and simplistic application of relevant models
s
and techniques (e.g. UML modelling and SSM techniques).
A familiar or limited range of information and knowledge
deployed, with some areas of inaccuracy.
Argument and analysis may not be fully developed.
Acceptable quality of presentation, structure and standard of
English.
<40 Unacceptable standard.
mark Lacking of basic understanding of the subject.
Minimal understanding of project management tools and
s
techniques
Insufficient or inaccurate knowledge of the subject, its models
and techniques (e.g. UML modelling and SSM techniques).
Inability to develop a reasoned argument.
Unacceptable quality of presentation, structure and standard of
English.

COMP1632: DETAILED MARKING SCHEME

Section for which mark is awarded:
Completeness and correctness
This is an evaluation of the overall completeness of the report; it is
made up of the following components listed below. Students are
awarded marks for their ability to use Software Engineering techniques
effectively.
A Rich Picture
Students are expected to draw the richest possible picture in an attempt
to explore the primary issues and stakeholders. The rich picture is not a
data flow chart, or a use case diagram. Rather it is a way to gather as
much information about the organisation as possible.
A Root Definition and CATWOE
The root definition should be used as the starting point for the initial
UML design as it explains what our system will do. Students also need to
complete the CATWOE. Attention should be paid to the correctness of
the T and W elements.
A list of functional and non-functional requirements Functional
and Non Functional requirements should be discussed here. For nonfunctional requirements, students should discuss about organisational
constraints, technical constraints, security constraints etc. (We have
covered all these in the lecture on requirements)
Detailed Use Case Diagram accompanied structured
descriptions
Detailed use case diagram accompanied by two narratives (which you
deem to be the main functionality) of the scenario.
Students here should create a detailed use case diagram, with
<<includes>> and <<extends>>. The idea is for them to focus on how
the staff will use the system.
Smart objectives and Key stakeholders
Students should make sure that the objectives are specific,
measurable, achievable, realistic and time-framed. The
appropriate stakeholders affecting the overall project should be
identified (as discussed in the lectures).
Gantt chart (including the work packages and activities)
Students should make sure the Gantt chart is printed in an appropriate
scale and only includes the work packages and activities (the
individual tasks should not be included in the Gantt chart). Students
should make sure the individual activities are clearly identified, and that
any dependencies and parallel activities are made clear.
2) Coherence, structure and sophistication, presentation
These marks are awarded for how well the whole report holds together
and how sophisticated it is. Does the analysis show a certain level of
complexity? How well do the diagrams show the skill of the student?
Here we are looking for demonstration of independent thinking. Also,
here marks are given for coherence and consistency between the
various diagrams. Marks are awarded for all elements of presentation,
particularly spelling and grammar, editing and diagram presentation.
Total

Comments

Marks

10

20
(10 for root
definition
10 for
CATWOE
10

20
(10 for
each diagram
and
narratives)
20

10

10

100

Final Mark

Marks
given