CET211 (Intermediate S.D) PPW1/Sprint 2 Task and Submission

Details

Category: Level 2, Intermediate Software Development

Published: Friday, 22 January 2021 19:07

Hits: 871

Task

CET211

Professional Practice Week One

29^th October to 31^stOctober, 2018

Schedule of events

Monday9 AM – Sprint 1

• At 9am on Monday you will be issued with the first phase of your problem specification for CET211, andprovided with guidance for the week.
• Sprint one contains 3 tasks, all of which should be completed and submitted via canvas. Our recommended submission time for Sprint 1 is 5 pm on Monday, although the assessment space will remain open after thisuntil 13:00 on Tuesday 30^thOctober. It is therefore up to you to manage your time effectively, and ensure you leave yourself adequate time to complete the second sprint.
• Canvas Submission: Sprint 1 Deliverables (UML model, Design Rationale, and prototype implementation) 

Tuesday 9 AMto Wednesday 1 pm - Sprint 2

• At 9am on Tuesdayyou will be issued with Sprint 2 tasks.
• Sprint 2 deliverables should be uploadedby 1 pm on Wednesdayvia canvas.
• Canvas Submission: Sprint 2 Deliverables (Updated UML and prototype version 2) 

Sprints should be submitted as single zipped folderswith all tasks clearly named. 

CET211 IntermediateSoftware Development

Professional Practice Week 1

 (2018/19) 

Professional Practice Week 1 contributes 40% to your final module mark and assesses learning outcomes 1, 2,3 & 4. 

The PPW is designed to reflect on and assess all learning outcomes for CET211.  Over the duration of the assessment timeline you will be given a series of programming and related modelling tasks. Details of each will be released daily. We anticipate this assessment will constitute a maximum of 18 hours of work.  You must submit all sprints as a single zip folder on canvas, by the time and day indicated in the schedule. 

Scenario

Sunderland Despatch Agency (SDA) have received your initial prototype and are pleased with the completed work.The have now provided you with sprint details for the second phase of development, details of which are given below. You must complete and upload all sprint 2 tasks by Wednesday at 1 pm. 

Sprint 2 – Tuesday (9 am), with submission by 1 pm on Wednesday (20 Marks) 

SDA have requested the following code extensions: 

1. The system should also allow delivery of Boxes. Boxes are a special type of Parcel. They have the same data as Parcels, plus the following additional data fields: 

2. The system should incorporate a single form, which allows users to display the following reports:
   1. View all Parcels, including poster tubes and boxes.
   2. View all parcels of a certain type, e.g. only standard parcels, or only boxes. 

3. All code should be appropriately commented to ensure readability. 

Your deliverables, which should be submitted via Canvas by Wednesday, 1pm, are: 

Deliverable2.1 - Update your UML design to model Boxes. 

Deliverable 2.2 – Extend your prototype system to allow report generation. Demonstrate this new functionality. As the system is still a prototype, you can use hardcoded event data to demonstrate form based functionality. You should create an appropriate number of Parcels to demonstrate the system effectively. 

Sprint 2 Marking Criterial

 Submission details

Hand drawn UML diagrams are acceptable but must be neat and clearly legible and then scanned for online submission. You may use a UML drawing tool e.g. Software Ideas Modeller for this task but if you do so then the UML notation used must be consistent with that covered in the module and you should export the diagram to an image file which can be embedded within the report document. 

Programming deliverables should be submitted as Visual C# solutions (version 2017), containing your application.

All work should be clearly named according to the task, andzipped and uploaded to Canvas by the specified hand-in date, using the assignment icon provided in the assessment area. 

Important Information

You are required to submit your work within the bounds of the University Infringement of Assessment Regulations (see the Programme Handbook).  Plagiarism, paraphrasing and downloading large amounts of information from external sources, will not be tolerated and will be dealt with severely.  Although you should make full use of any source material, which would normally be an occasional sentence and/or paragraph (referenced) followed by your own critical analysis/evaluation.  You will receive no marks for work that is not your own. Your work may be subject to checks for originality which can include use of an electronic plagiarism detection service. You are not expected to put your commentary report through Turnitin (however the module leader reserves the right to do so if they deem it necessary). Where you are asked to submit an individual piece of work, the work must be entirely your own.  The safety of your assessments is your responsibility.  You must not permit another student access to your work. Where referencing is required, unless otherwise stated, the Harvard referencing system must be used (see the Programme Handbook).

Submission

Deliverable2.1 - Update your UML design to model Boxes.

Deliverable 2.2 – C# Prototype System Expansion.

Download Source Code