Assessment Details and Submission Guidelines/MN404 – T2 2017/Assignment1: UML Use Cases and Operating System/Computer components

 

Assessment Details and Submission Guidelines
Unit Code MN404 – T2 2017
Unit Title Fundamentals of Operating Systems and Java Programming
Assessment Type Individual, written
Assessment Title Assignment1:  UML Use Cases and Operating System/Computer components
Purpose of the assessment (with ULO Mapping) Main objectives of this assignment are to enable student to analyse the two case studies, gather requirements for OS and the components. After successful completion of this assignment, students should be able to:

a.      Analyse and discuss the significance of use cases of UML specification.

b.      To use your knowledge of modern computing components to select the appropriate components to create a number of computers.

Weight 20% of the total assessments
Total Marks 50
Word limit 1250 (approximately 5 pages)
Due Date        Week 7, demonstrate during laboratory class and submit report on Moodle
Submission Guidelines ·     All work must be submitted on Moodle by the due date along with a completed Assignment Cover Page.

·     The assignment must be in MS Word format, 1.5 spacing, 11-pt Calibri (Body) font and 2 cm margins on all four sides of your page with appropriate section headings.

·     Reference sources must be cited in the text of the report, and listed appropriately at the end in a reference list using IEEE referencing style.

Extension ·     If an extension of time to submit work is required, a Special Consideration Application must be submitted directly to the School’s Administration Officer, on academic reception level.  You must submit this application within three working days of the assessment due date. Further information is available at:

http://www.mit.edu.au/aboutmit/institutepublications/policiesproceduresandguidelines/specialconsiderationdeferment

Academic Misconduct  ·     Academic Misconduct is a serious offence. Depending on the seriousness of the case, penalties can vary from a written warning or zero marks to exclusion from the course or rescinding the degree. Students should make themselves familiar with the full policy and procedure available at: http://www.mit.edu.au/about-mit/institute-publications/policies-procedures-and-guidelines/Plagiarism-Academic-Misconduct-Policy-Procedure. For further information, please refer to the Academic Integrity Section in your Unit Description.

 

 

 

 

 

 

 

 

 

Assignment 1 Specification

Business case studies: You are required to answer all two case studies.

              Case study 1: UML Use cases

In a Learning Management System (LMS), e.g. Moodle, use cases define the interaction that takes place between students/teachers and LMS. Given figure shows an example use case diagram for an LMS subsystem. The Student actor represents the class of all students who will use the LMS subsystem. When you use the LMS to upload an assignment, you are an instance of Student using a particular instance of the use case Upload assignment. The student sitting next to you is another instance of Student, who will use the different instance of the use case Upload assignment. Someone else may use the instance of use case Delete the submission or Add a comment. You may successfully upload assignment from the LMS, but the student sitting next to you may find that file size is too large, and the use case instance will proceed a different course from yours, rejecting the request.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Diagram shows the actor (Student) and use cases (Upload assignment, Delete the submission and Add a comment)

 

Note – The term scenarios is used to refer to the different possible courses that different instances of the same use case might take.

  1. List at least two scenarios for each of the given use cases.
  2. List four other use cases for the Student actor and two scenarios for each use case   (other than the ones given in Q1.) for an LMS system.
  3. Specify four use cases possible for an LMS system for an actor Teacher and two scenarios for each use case.

 

 

Case study 2: (Computer components and the Operating System)

Objective:

To use your knowledge of modern computing components to select the appropriate components to create a number of computers.

  1. Identify the cost of building a computer using components bought individually from a store. You should create a Bill of Materials (including URLs to an online shop) including the cost of the individual components and the total cost for your system.

You should ensure that the components are compatible, and include a case.

You should select the components to match each of the following profiles and budgets.

  1. A server computer (you should ensure you use ECC memory) (max $2200) to be used in a doctor’s clinic, serving multiple doctors.
  2. A client computer (max $650) that would be used in the doctor’s clinic by doctors and receptionists.

You should briefly describe why the choices you have made would be appropriate for each of the computers.

The cheapest computer should be relatively small.

  1. Identify an appropriate hardware backup solution for the server computer, as well as a process to ensure that the backups are performed regularly, and are secure.

Identify possible risks associated with doing backups and how your strategy overcomes them.

 

Write each report under the headings given in marking criteria.

 

 

 

 

Marking criteria:

 

Section to be included in the report Description of the section Marks
Case study 1

Introduction

Q1

Q2

Q3

Conclusion

UML use cases 18

(1)

(4)

(6)

(6)

(1)

Case study 2

Introduction

Q1a

Q1b

Q2

Conclusion

Computer components and the Operating System 27

(1)

(12)

(8)

(5)

(1)

Demonstration Demonstration
Reference style Follow IEEE reference style 5
  Total 50

 

 

 

 

 

Marking Rubrics

 

Grades Excellent Very Good Good Satisfactory Unsatisfactory
Introduction Concise and specific to the exercise Topics are relevant and soundly analysed. Generally relevant and analysed. Some relevance and briefly presented. This is not relevant to the assignment topic.
Case study 1 Concise and specific to the case study Topics are relevant and soundly analysed. Generally relevant and analysed. Some relevance and briefly presented. This is not relevant to the assignment topic.
Case study 2 Concise and specific to the case study Topics are relevant and soundly analysed. Generally relevant and analysed. Some relevance and briefly presented. This is not relevant to the assignment topic.
Conclusions All elements are present and very well integrated. Components present with good cohesive Components present and mostly well integrated Most components present Proposal lacks structure.
Demonstration Logic is clear and easy to follow with strong arguments Consistency logical and convincing Mostly consistent logical and convincing Adequate cohesion and conviction Argument is confused and disjointed
IEEE Reference style Clear styles with excellent source of references. Clear referencing style Generally good referencing style Sometimes clear referencing style Lacks consistency with many errors

 

 

Leave a Reply

Your email address will not be published.