School of Computer of Science ASSIGNMENT BRIEFING SHEET (2015/16 Academic Year) – ANONYMOUS MARKING Assignment Title Progress Report 1 Date Submitted Module Title E-learning Applications Design & Development Module Code 6WCM0009 / 6WCM0010 Tutor Dr Mariana Lilley GROUP or INDIVIDUAL Assignment Individual FOR INDIVIDUAL ASSIGNMENTS – STUDENT TO COMPLETE By completing BOX A below, I certify that the submitted work is entirely mine and that any material derived or quoted from the published or unpublished work of other persons has been duly acknowledged. [ref. UPR AS12, section 7 and UPR AS14 (Appendix III)]. Please ONLY provide your ID (srn) number as this assignment will be anonymously marked BOX A Student ID Number (SRN) School of Computer of Science ASSIGNMENT BRIEFING SHEET (2015/16 Academic Year) – ANONYMOUS MARKING THE ASSIGNMENT TASK: As part of this task, you are required to report on and reflect upon your project progress to date. MODULE LEARNING OUTCOMES ASSESSED BY THIS ASSIGNMENT: Knowledge and Understanding. Successful students will typically have a knowledge and understanding of: 1. main principles relating to the design, implementation and evaluation of e-learning applications; 2. appropriate set of criteria to evaluate their own work and the work of others. Learning Outcomes: Skills and Attributes. Successful students will typically be able to: 3. identify and define a substantial practical task in the e-learning domain, and address this task through the application of a broad range of Computer Science techniques and methodologies; 4. plan and conduct a programme of practical work in the domain of e-learning that draws on knowledge from a broad range of Computer Science subjects; 5. work autonomously with minimal supervision, and within agreed guidelines and deadlines; document, report on and critically evaluate their work in a manner appropriate to the needs of a specified readership. SUBMISSION REQUIREMENTS: This assignment is to be submitted and marked anonymously. Students should ONLY use their student ID number to identify themselves on their work. Work submitted via StudyNet for anonymous marking will automatically have an anonymity number allocated to it. You are required to submit your report as ONE .docx file. Your report should not exceed 1,000 words (excluding references). FEEDBACK FROM THIS ASSIGNMENT The feedback will take the form of a score out of 5 and comments on the strengths and weaknesses of the work. The feedback will be made available via Studynet. MARKS AWARDED FOR: Please see attached. DEADLINES AND ASSIGNMENT WEIGHTINGS 1 This assignment is worth 5% of the overall assessment for this module. 2 You are expected to spend about 5 Hours to complete this assignment to a satisfactory standard 3 Date assignment set 31 May 2016 Date completed assignment to be handed in 20 June 2016 4 Target date for return of marked assignment 18 July 2016 INTERNAL MODERATION This assignment has been internally moderated. I confirm that the assignment set, meets the requirements of the module and that the brief provides appropriate content for students to successfully complete the assignment. Moderator name, signature and date   Progress Report 1 This assignment is worth 5% of your final grade for this module. Please note that this assignment will be marked anonymously, and therefore your name must not be included in any section of the report. Your report should not exceed 1,000 words (excluding references). Please submit your report as a .docx, .doc or .rtf document. Your report must include five sections, listed below: 1. Project aims and objectives (up to 2 marks); 2. Functional requirements (up to 2 marks); 3. Non­functional requirements (up to 2 marks); 4. Proposed Entity­Relationship diagram (up to 2 marks); 5. Evidence that a suitable development environment has been installed (up to 2 marks). Please refer to the recording of the Adobe Connect session "Progress Reports Explained" for further details. Background You have been commissioned to develop an e­learning solution in ASP.NET/VB.NET. The solution is intended to support individual learners in developing their practical skills in the use of SQL. All the collaborative aspects of learning (e.g. class discussions) will be implemented using free tools such as piazza. The requirements for your application must be refined in discussion with the client, Dr Mariana Lilley. If you have any questions, please contact her using the email address [email protected]. It is likely that your work will be informed by findings from the literature. Please use the Harvard Referencing System when referencing your sources. Additional information Project aims and objectives Every project should have an aim, and a set of objectives. An example of a project aim could be: • "Develop and evaluate an Artificial Neural Network to predict stock market indices" (Dawson, 2005: p. 59). The project objectives generated from the project aim above include (Dawson, 2005: p. 59): • "Complete a literature search and literature review of existing stock market prediction techniques"; • "Develop a suitable Artificial Neural Network model"; • "Identify and collect suitable data for analyses and evaluation"; • "Evaluate the model using appropriate statistical techniques"; • "Complete final report". The project aims should provide an overall picture of your project and will typically consist of a couple of broad statements of desired outcomes. It is not uncommon for students to list their system requirements as project objectives. This is not the correct approach to this section of the document. Please refer to the example above and note that project objectives differ from system requirements. . You should be able to classify your objectives into core and advanced. As a general rule, assume that core objectives are those objectives that you must complete in order to be awarded a good pass grade for the module. Advanced objectives should represent a significant challenge, and are likely to be achieved only by those students whose performance is at First Class Honours level. When writing your advanced objectives, it is important to remember that a project that is only moderately demanding, even if conducted to a high standard, would be unlikely to be awarded a First Class Honours grade. Requirements Analysis The aim of this task is to devise a set of clear and unambiguous requirements for your project. There are several approaches for requirements gathering. For instance, Sharp et al. (2007) suggest: interviews, focus groups, questionnaires, direct observation, indirect observation, studying documentation, and researching similar products. The approaches recommended for this project are: • Studying documentation (this should include assignment briefing sheets, and module units); • Researching similar applications; • Asynchronous interviews with the client (Dr Mariana Lilley). If you want to carry out any research involving individuals who are not part of the module, you are required to obtain ethics approval first. Requirements are typically organised into functional and non-functional requirements: • Functional requirements (what the system should do). • Non-functional requirements (constraints on the system and its development).