Module Information for CS3IP, 2023/4 - APPROVED

Module Title/Name: Individual Project Module Code: CS3IP

School: Engineering & Physical Sciences Module Type: Standard Module

New Module? No Module Credits: 45

Module Management Information

Module Leader Name Megan Robertson

Email Address m.robertson8@aston.ac.uk

Telephone Number Not Specified

Office MB265D

Additional Module Tutor(s):

None Specified

Programmes in which available:

Level Description: Computer Science
Level 6 (Bachelors) Cybersecurity
Computer Science with Business

Contributing School & Subject Groups (and %): Credit Value & ECTS Credits:
None Specified 22.5

Available to Exchange Students?

Yes

Conditional Details:
None Specified

Module Dependencies

Pre-requisites: Co-requisites:
None Specified None Specified

Prohibited Combinations:
None Specified

Module Learning Information

Module Aims:
The individual project provides experience with planning, executing, and reporting formally on a substantial computing task within a
 set time. Students will develop their understanding of relevant areas of computing (including learning new languages or techniques
as applicable) and their capabilities in time management, practical engineering, reporting, and presenting their work; and so
demonstrate their competence as candidate computing professionals.

Module Learning Outcomes:

On successful completion of the module students will be able to:
1. Specify and carry out an independent Computer Science project of significant scope and size.
2. Integrate knowledge from a variety of sources.
3. Produce a high-quality technical report describ ing and evaluating the results of their work.
4. Deliver a coherent demonstration and verbal exposition of their work.

Indicative Module Content:

Each student will carry out a project on an agreed topic, and will produce a report on the background, conduct and outcome
of the work.
A list of suitable projects will be provided, and students may also suggest their own projects, subject to suitability and the
agreement of the prospective supervisor.
All projects will involve elements of preliminary investigation or research, design, realisation of that design (typically
although not necessarily software implementation), and evaluation. Some projects will be more researchorientated,
replacing software implementation with experimentation or investigation.
All projects must result in an end product, be that software or the results of research. This end product should demonstrate
practical and analytical skills, and engage with at least one stage of the software life cycle.
Projects that have a business context should include an analysis of that context and an evaluation of the business value of
the end product.
Students will submit a brief report at the end of Term 1 covering the background research done for their project to date and
providing a secure basis for advising them as to their future work, including any areas of weakness requiring attention. This
report does not contribute to the final mark but enables students to receive feedback on the relevant parts of the final report
as it serves as a first draft of the initial stages.

International Dimensions:
Computing is a discipline that transends national boundaries and has the capacity to embrace different cultural perspectives.
Students will be encouraged to reflect on the international dimensions of their project as applicable.

Corporate Connections:
Students are encourage to propose projects arising out of their placement year (if taken) and members of the Computer Science
Industry Club are invited to submit projects to be offered to students.

Ethical Approval:
Yes

Links to Research:
Potential supervisors are invited to propose projects linked to their research interests, and supervisors are selected based on their
interests when students propose their own projects.

Ethics, Social Responsibility and Sustainability:

Projects should be conducted in an ethical and professional manner. Students are required to complete a basic ethics form, and
those projects requiring formal approval must be presented via the University procedures.

Module Delivery

Methods of Delivery & Learning Hours (by each method):

Method of Delivery Learning Hours

Independent Activity: 450 hours

Total Learning Hours: 450 hours

Learning & Teaching Rationale:

The module is designed to give students practical experience in managing and delivering a Computer Science project. The
majority of the work is carried out independently by the student. Each student will have an academic supervisor who they will meet
for half an hour per week (or one hour per fortnight). At the end of the module, each student will have to present their deliverable
and write a report.
Module Assessment

Methods of Assessment & associated weighting (including approaches to formative assessment as well as summative):

Common
Duration/ Modules/
Assessment Assessment
Category Submission Exempt from
Type Weight
Date Anonymous
Marking

Individual
Report TBC Yes 100%
Assignment

The report should be 5,000-10,000 words and should describe and

evaluate the project work and its outcomes carefully. It should be a self-
contained, complete record of the final state of the work done and include
Details comments about further developments. Where applicable, assessors
should have access to code developed via upload to Blackboard,
CD/DVD/memory stick or directions to an online repository. Students will
be required to give a demonstration of their deliverable.

Total: 100%

Method of Submission:
Electronic Copy Only

Assessment Rationale:
All learning outcomes will be assessed by a combination of a demonstration of the final deliverable and a written report.

Feedback Rationale:
Continuous assessment 100%. The supervisor and a second member of staff will assess the project work based on the report and
a demonstration of the end product. They will prepare individual written assessments of the project work, which will be reconciled
to yield a percentage mark reflecting the overall quality of the project work. Assignation of marks will be in accordance with
descriptor-based guidelines that will be provided to students. These guidelines will have some flexibility to allow for legitimate
variations in the nature of projects within the
guidelines stated above.