Instructions for Group-Based Project on Open-Source Software Development

Task

a. Cover sheet to be attached to the front of the assignment when submitted

b. Question paper to be attached to assignment when submitted

c. All pages to be numbered sequentially

You are required to identify an open-source software project/product to improve anexisting solution to accompany with a report by applying of some of the techniques wecovered in this module. A template for the report will be provided (3000 word ± 10%). You must clearly outline and justify the additional features or software functions that your teamhave developed during the presentation and individual viva. Hence, change of interface orUI will not be considered as additional features or functions. Your tutors mightrecommend a list of existing software project for consideration. 

a. This component consists of a group-based project; each group has around 4 members.

b. This coursework was designed keeping this group size in mind.

c. Members of the same group will be part of the same Teams channel and each group canrefer to their common channel tutors.

d. This coursework was designed keeping this group size in mind and the size will be enforced unless there are exceptional circumstances.

e. You will also be required to designate a group leader. It is vital that each group nominates a group leader as early as possible because the group leader will beresponsible for all group communication with the module leader and for the final
submission of the work to Moodle.

f. Please note that group communication should only be done through the group leader unless there are exceptional circumstances.

1. If you are not in a group by the deadline you will be randomlyassigned to one. If your name is in multiple groups, you will also be randomly assigned to one.

2. In former iterations of this module, it has been observed that students that formtheir own group tend to do better, therefore, you are strongly advised to form your own groups.

3. Final list of groups along with details each member will be published on CN7021 page site:
this will be the final official allocation and will be strictly followed.

1. Intermediate PowerPoint presentation (by the 11th of November).

2. A PowerPoint presentation (max 15 minutes) summarizing the project report andintroducing a demo (by the 9th of December).

3. A video of the PowerPoint presentation followed by a demo of the main scenarios of therunning software to be uploaded on UEL Microsoft Stream platform (by the 9th ofDecember).

4. A web link to a UEL OneDrive folder containing all the project source code and anyadditional material (images, configuration or read me files). Alternatively, you canprovide the link to an open code repository (bitbucket or github), as long as it is freely
accessible. (by the 16th of December)

5. The Project report in MS-Word format (by the 9th of December, 2021).The link to the video and the link to the code must be in the title slide of your submitted Powerpoint presentation: “no links” means “no marks”.

6. The contribution of each group member must be highlighted in the slides, at the beginning ofthe video demo, stating who has done what: each group member is required to contribute tothe project and to the presentation.

7. The report must be structured according to a template that provided on Moodle: failure to comply will cause loss or marks.

1. The first is the intermediate presentation which will take place during the tutorialin week 7 in which you have the current status of the project (introducing theproblem, show a draft architecture, and use case diagram with some requirements);

2. The second is the final presentation that will take place during tutorials in week11 in which you will play the video demo you previously uploaded on MS Stream and the two tutors will make questions during and after the demo (this is to avoiddelays due to the demo-effect)

 

The University defines an assessment offence as any action(s) or behaviour likely toconfer an unfair advantage in assessment, whether by advantaging the allegedoffender or disadvantaging (deliberately or unconsciously) another or others. A
number of examples are set out in the Regulations and these include:“D.5.7.1 (e) the submission of material (written, visual or oral), originally produced byanother person or persons, without due acknowledgement, so that the work could be assumed the student’s own. For the purposes of these Regulations, this includesincorporation of significant extracts or elements taken from the work of (an) other(s),

 

Acknowledgement or reference, and the submission of work produced incollaboration for an assignment based on the assessment of individual work. (Suchoffences are typically described as plagiarism and collusion.)”The University's Assessment Offences Regulations can be found on our web site.Also, information about plagiarism can be found on the programme’s handbook