Assessment Details and Submission Guidelines
Unit Code MN404 – T1 2017
Unit Title Fundamentals of Operating Systems and Java Programming
Assessment Type Individual, written
Assessment Title Assignment1: Operating Systems and UML Use Cases
Purpose of the assessment (with ULO Mapping) Main objectives of this assignment is to enable student to analyse the two case studies, gather requirements for OS and the installations. After successful completion of this assignment, students should be able to:
a. Analyse and Discuss the significance of use cases of UML specification.
b. Install/upgrade OSs for the business, information, technology, and application domains.
Weight 15% of the total assessments
Total Marks 50
Word limit 1000 (approximately 4 pages)
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:
• 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 banking system, use cases define the interaction that takes place between customers and automated teller machines (ATM). Given figure shows an example use case diagram for an ATM subsystem. The Customer actor represents the class of all customers who will use the ATM subsystem. When you use the local ATM to withdraw cash, you are an instance of Customer using a particular instance of the use case Withdraw cash. The person standing on the line behind you is another instance of Customer, who will use the different instance of the use case Withdraw cash. Someone else may use the instance of use case Check balance or Print mini-statement. You may successfully withdraw cash from the machine, but the person behind you may find that he or she does not have enough money deposited, and the use case instance will proceed a different course from yours, rejecting the request.
Note – The term scenarios is used to refer to the different possible courses that different instances of the same use case might take.
Q1. List at least three scenarios that are common to the given use cases.
Q2. List the possible scenarios for all the use cases (other than the ones given in Q1.)
Q3. Specify any other use cases possible for ATM system.
Case study 2: (Operating Systems – Windows 10)
Microsoft described Windows 10 as an 'operating system as a service' that would receive ongoing updates to its features and functionality, augmented with the ability for enterprise environments to receive non-critical updates at a slower pace, or use long-term support milestones that will only receive critical updates, such as security patches, over their five-year lifespan of mainstream support. Terry Myerson, executive vice president of Microsoft's Windows and Devices Group, argued that the goal of this model was to reduce fragmentation across the Windows platform, as Microsoft aimed to have Windows 10 installed on at least one billion devices in the two to three years following its release.
Write a report on Windows 10 and answer the following questions in your own words
Q1. Give a brief history about Windows systems.
Q2. What are the minimum system/hardware requirements for Windows 10?
Q3. How to install/upgrade to the new Windows 10? And specify the configuration tasks performed following the installation.
Q4. What security features can be highlighted in the system?
Q5. Compared to other desktop operating systems, what are the advantages of Windows 10?
Q6. What are the criticisms about Windows 10?
In your report, you must provide operation examples to demonstrate your understanding of
Windows 10. Your report should be around three pages long and supplemented with diagrams and tables, if appropriate.
Write a report with the following contents:
• Case study 1 (UML use cases)
• Case study 2 (Operating Systems – Windows 10)
Section to be included in the report Description of the section Marks
Introduction Brief introduction to the reports on your case study exercises 2
Case study 1 UML use cases 12
Case study 2
Report on Windows 10 and answers to the questions
Conclusions Write clear conclusion to the case study. 2
Demonstration Demonstration 4
Reference style Follow IEEE reference style 5
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