COM4014M Software Engineering :
COM4014M Software Engineering ASSIGNMENT BRIEF
| Module Code | COM4014M | Module Leader | Dr Andrew Guest | ||
| Module Title | Software Engineering | ||||
| Level | 4 | Credit Value of Module | 20 | ||
| Assessment Task | Portfolio | ||||
| Word Count | 3200[NA1] Words | ||||
| Assessment No | 1 | of | 1 | Weighting | 100% |
| Type of Submission | Portfolio of SE Documentation | ||||
| Method of Submission | Digital through Moodle | ||||
| Publication Date | 10/03/23 | ||||
| Due Date | 01/06/23 12:00pm (Noon) | ||||
| Expected Feedback Date | 22/06/23 | ||||
| Resit Date | April 2023 | ||||
| Format of Feedback | Through moodle | ||||
| Anonymous marking | Anonymous | ||||
| Learning Outcomes | |||||
| Demonstrate knowledge and understanding of essential facts, concepts, principles, and theories relating to computing and computer applications. Recognise and analyse criteria and specifications appropriate to specific problems, and plan strategies for their solution. Demonstrate the use of knowledge and understanding in the modelling and design of computer-based systems for the purposes of comprehension, communication, prediction, and the understanding of user focus.Demonstrate ability to deploy appropriate theory, practices and tools for the specification, design, implementation and evaluation of computer-based systems.Demonstrate knowledge and understanding of methods, techniques and tools for information modelling, management, and security.Demonstrate an understanding of the link between theory and practice and ability to recognise and analyse criteria and specifications appropriate to specific problems, and plan strategies for their solution | |||||
| Assignment Description | |||||
| The assessment for this module consists of an analysis and design document. There is a marking scheme on page 3 and the assessment regulations are on page 4. | |||||
| Overview Your group is tasked with carrying out the data gathering, system modelling, requirements analysis, and design of an application for the (fictional) new YSJ halls of residence. Your group of three will work through the stages for this task and you will each, individually, submit the required documentation for one part of the application. The new accommodation will consist of five separate residences, a porters lodge, a canteen and a fitness centre. Each of the five residences will offer a different type of accommodation at different rates. The canteen facilities provide catering for breakfast, lunch and dinner. A packed lunch can be made up at the breakfast session. Students can opt to pay for the canteen facilities in addition to their accommodation fees. Those students that opt in are provided a canteen card and are allowed to use the canteen. The fitness centre will feature a full gym and rooms which can be used for classes and sports events. The fitness centre is free to use for all students though there are fees for specific items like sessions with a physical trainer and room bookings. Students can opt to become a fitness centre member for a fee which covers all fees and gives them early booking for classes and rooms. | |||||
| You are to consider the requirements for and design of a system to manage accommodation details. At the core of the system is a student database system that stores information on students The three main parts of the application are: An accommodation management system that tracks room assignments to students, fees paid, cleaning schedules, accommodation related complaints. It should contain contact details for services and emergencies. A canteen management system that is used to mark students as opted in or out of the canteen facilities, create student canteen cards, manage the menus and food ordering for the canteen. It should contain contact details for services and emergencies.A fitness management that identifies if a student has opted in to the fitness facilities to get priority access. Students should be able to use the system to book in to fitness classes. It should be able to manage access at peak times and be able to book trainer sessions. It should also track maintenance routines/cycles for machines and contact details for servicing. As a group you will work through the data gathering, system modelling. requirements analysis and design of the system. Collectively you will come up with a design for a simple student database system to design the rest of the application around. Individually you will each go through the stages for one of the three parts of the application described above. You can, and should, work through the stages together, discussing the system as a whole, but you are required to individually document each stage for your individual part of the project. One of the lab sessions will run as a data gathering exercise where you will be able to ask the lecturers questions as if we were customers requesting this software. (You will be able to ask further questions throughout the labs as well) | |||||
| Submission Your submission should consist of a single document submitted through moodle. It should have a title that identifies which part of the system it is for, a table of contents with page numbers, and the sections described below. | |||||
| Student Database Description – 10% A single page consisting of a class diagram (or similar) showing the data/tables required for the student database system. A bullet point list of functionality for the system (e.g. add/view student) This page should be identical for all students in the group. | |||||
| Requirements Analysis – 30% This section describes the requirements for your part of the application. An introduction/overview is not required, assume the reader has access to this document. You may include an overview if you wish to give context to specific requirements. It should detail the functional and non-functional requirements for your part of the system. You do not need to describe how the data was gathered but you should reference any material from outside of the class and note any assumptions you have made. There is nothing wrong with making assumptions, just note them. The requirements should be detailed enough to understand the later design. This section will include a model of your part of the system. This model should be in the form of a class diagram or similar. It should identify the main components of your part of the system and how they connect to the students’ database core and the other parts of the system (but it does not need to detail them). The section will include a series of user stories[NA2] /use case diagrams detailing the main interactions of this part of the system. | |||||
| Design – 50% This section describes the proposed design for your part of the system. This should be a high-level design that covers the components and functionality of the system but doesn’t need to go in to implementation specifics. This section should include: A design model (class diagram or similar to show structure)A design for the functional requirementsA design for the non-functional requirementsA description of the risks for the project (general and specific to this part)An overview of testing this part of the projectA schedule estimate | |||||
| Marking Scheme Student Database Description (200 Words) – 10% Marks Database diagram 50 Functionality List 50 Requirements Analysis (1000 Words) – 30% Marks Functional Requirements 25 Non-Functional Requirements 25 System Model Diagram 25 User Stories/Use Case Diagrams 25 Design (2000 words) – 50% (2000 Words) Marks Design Model 20 Functional Design 20 Non-Functional Design 20 Risks 20 Testing 10 Schedule 10 Structure & Style – 10% Introduction, conclusion, spelling, punctuation, etc 100 | |||||
| Assessment Regulations | |||||
| Your attention is drawn to the University policy on academic misconduct (Academic Misconduct Policy). Penalties will be applied where a student is found guilty of academic misconduct, including termination of programme. You are required to keep to the word/time limit set for an assessment and to note that you may be subject to penalty if you exceed that limit (Agreed Penalties Policy). You are required to provide an accurate word count on the cover sheet for each piece of work you submit.For a first assessment attempt a penalty may be applied for late or non-submission of work by the published deadline or an approved extended deadline (Agreed Penalties Policy). Where a re-assessment opportunity exists, late or non-submission of work receives a mark of zero and is not eligible for a capped mark (Agreed Penalties Policy and Reassessment) An extension to the published deadline may be granted to an individual student if they meet the eligibility criteria of the Exceptional Circumstances policy. | |||||
| Note | |||||
| Feedback Policy: Marks are to be returned to students with the caveat that all marks are provisional until final approval by the School Assessment Board (SAB). Confirmed marks will be made available via e:Vision after the SAB meeting. | |||||
[NA1]How can the word count be 000
[NA2]Would not the user stories be redundant given they are writing functional requirementsof COM4014M Software Engineering?
Visit:https://auspali.info/
Also visit:https://www.notesnepal.com/archives/767
YOUR COMMENT