Softwarica College of IT & E-Commerce

ST4003CEM Object Oriented Programming

Assignment Brief 2021

Module Title Ind/Group Cohort Module Code

Object Oriented Programming Ind May 2021 ST4003CEM

Coursework Title Hand out date:

ST4003CEM Exam Replacing Coursework TBD
Module Leader Due date:
Shyam Sunder Khatiwada TBD
Estimated Time (hrs): ST4003CEM Coursework type: % of Module Mark
Expects 100 hours of self-study over Phase Test and an individual project Phase Test 1: 30%
the semester. Individual project: 70%
Word Limit*: N/A
Submission arrangement online via Softwarica Moodle: Phase Tests will be conducted via ST4003CEM
Moodle Page. ALL project’s details on course Moodle Pages.
Mark and Feedback date: Mark from Phase Tests immediately with feedback to follow the next week.
Mark and feedback from Individual project viva expected within 3 weeks.
Mark and Feedback method: All marks delivered by Moodle. Phase Test feedback delivered in class
while Individual project viva feedback usually delivered in file of comments from viva marker.

Module Learning Outcomes Assessed:

1. Demonstrate an ability to use Object Oriented Programming (OOP) techniques.

2. Understand and write programs that make safe use of dynamic memory.

3. Understand Data Structures and Abstract Data Types.

4. Compare and contrast different programming languages/language features.

5. Evaluate their work in a useful manner, using technical skills such as debugging, profiling and
code testing.

The ST4003CEM Coursework has two Components:

1. Phase Test (30%)
2. Individual Project (70%)

These make up 100% of the module mark.

Phase Tests
The Phase Tests are online quizzes taken in class under exam conditions. Each one consists of 20
multiple choice questions in 35 minutes drawn from Softwarica Moodle page. All students will get
same questions from the page but the questions will shuffle. In each case a practice test will be
made available the week before.
Phase Test takes place in a student’s first ST4003CEM lab of Week 8. Students can only take
their test in a different lab under exceptional circumstances with permission of the module
leader. All tests must be taken by specific date of that week unless a student has a Faculty Registry
approved extension.

Individual Project

This project is an individual based project that is handled by each individual. The project is specific
to the student’s BSc. Computing degree course and assess this module Learning outcomes only.

Students should be able to demonstrate the use of all concepts taught prior to week 11.

Project description:
1. The project is based on open topic- student can choose their own topic but should be
approved by teaching staff.
2. The project will contain suitable Interface (Command Line Interface / Graphical User
Interface / Menu Driven Interface).
3. Should have persistence Storage.
4. Should have appropriate testing of Software (unit testing).
5. Should work with version control systems.
6. At the end, video report submission of your application.

Example project ideas include:

- Quiz application.
- Games (tic-tac-toe, snake game, shooting game etc.)
- Text editor or notes application where users can create, update and delete the text.
- Chat application.
- MIS application of any kind.

Note:

This project will be assessed by VIVA that will take place at the end of the semester. Students
should attend their allocated viva slot and can only take the viva at another time under
exceptional circumstances with permission of their Course Director. The VIVA will be focused on
assessing student’s understanding on the project of this module.

1. Student are encouraged to use their own user-defined data structure rather than built-in
data structure of given language.
2. You are expected to use the Coventry University APA style for referencing. For support
and advice on this, students can contact Centre for Academic Writing (CAW).
3. Please notify your academic services team and module leader for disability support.
4. The college cannot take responsibility for any coursework lost or corrupted on disks,
laptops or personal computer. Students should therefore regularly back-up any work and
are advised to save it on the cloud based services.
5. If there are technical or performance issues that prevent students submitting coursework
through the online coursework submission system on the day of a coursework deadline,
an appropriate extension to the coursework submission deadline will be agreed. This
 extension will normally be 24 hours or the next working day if the deadline falls on a
Friday or over the weekend period. This will be communicated via your Module Leader.
6. Collusion between students (where sections of your work are similar to the work
submitted by other students in this or previous module cohorts) is taken extremely
seriously and will be reported to the academic conduct panel. This applies to both
coursework and exam answers.
7. A marked difference between your writing style, knowledge and skill level demonstrated
in class discussion, any test conditions and that demonstrated in a coursework assignment
may result in you having to undertake a Viva Voce in order to prove the coursework
assignment is entirely your own work.
8. If you make use of the services of a proof reader in your work you must keep your original
version and make it available as a demonstration of your written efforts.
9. You must not submit work for assessment that you have already submitted (partially or in
full), either for your current course or for another qualification of this college, with the
exception of resits, where for the coursework, you may be asked to rework and improve a
previous attempt. This requirement will be specifically detailed in your assignment brief or
specific course or module information. Where earlier work by you is citable, i.e., it has
already been published/submitted, you must reference it clearly. Identical pieces of work
submitted concurrently may also be considered to be self-plagiarism.

Learning Outcomes matrix:

Question No. Learning Outcomes Assessed

Phase Test 1,2,3
Individual project 1, 2,3 4, 5
Mark allocation guidelines to students: marking rubric
40% >=above 50% >= above 60% >= above 70% >= above
Programming The application is fully Application coding follow the Application uses the different Application uses of third-party
Language functional and the specific programming language Structure and use of library given library and the techniques.
(20%) explanation of the code is coding convention. by the programming language.
clear
Algorithm & Application that uses Each function meets given Each function follows the Uses of functions that uses their
Data different functions for specification. convention of programming own logic rather than using in-built
Structures different task. language. i.e., docstring, function and having efficient time
(Functions) comments complexity.
(20%)
Layout and Use of CLI and properly Use of GUI and properly Use of GUI with appropriate user Use of Form based interface having
Design functioning layout and functioning layout and design. interface. Form based interface. clear, consistent and user-
(Interface) design. controlled interface.
(20%)
Persistence Use of only temporary way Use of Permanent storage Use of database as permanent Use of both file and database as
(20%) of storing data (volatile method, file as non-volatile storage of data of your storage of your data of your
storage). storage. application. application.
Version Use of GitHub repo and Use of GitHub repo with Use of GitHub repo with regular Use of branching and merging. A
Control unsuccessful attempt has multiple commits. Having commits over an extended period full suite of unit testing ensuring
and Testing been made to write simple limited number of tests written of time with a range of test full code coverage.
(20%) tests. and run. showing how they contribute to
code quality.