COIT11226 Assessment item 1 — Written Assessment Due date: Due Monday (22 Aug 16) 09:00 AM AEST ASSESSMENT Weighting: 20% Length: 1000 words or less (Word Count of all Contents from Introduction to Conclusion) 1 Objectives This assessment relates to course learning outcomes 1, 3, 4 and 8 stated in the e-course profile. Assessment 1 is an individual assessment. In assessment 1, all students need to complete their assigned tasks and produce an individual reporting document for submissions by using an initial template file provided. Assessment 1 is a reporting document written about systems analysis. The reporting document is Written Assessment that adopts an essay writing format (see 'Help' below) with predetermined lay out and required contents (see 'Reporting Document Layout and Submission Guidelines' below). This Written Assessment is designed to assess your practical understanding of systems analysis within a system project. Having analysed the project case study, you are assumed to have a clear insight into the scope of the system analysis within a system development project. Assessment 1 aims to develop your understanding of relevant skills and issues in various aspects of systems analysis. Please note that ALL submitted assessments (MS Word documents) are passed through a computerized copy detection system and it is extremely easy for teaching staff to identify copied or otherwise plagiarised work. • Copying (plagiarism) can incur penalties ranging from deduction of marks to failing the course or even exclusion from the University. • Please ensure you are familiar with the University's Plagiarism Policy, available from: http://policy.cqu.edu.au/Policy/policy_file.do?policyid=1245 Requirements This is an individual assessment item. You will analyse the case study given in a separate document 'Project Case Study', identify critical elements, understand the task specifications and conduct relevant tasks to develop your individual reporting documents. The tasks You are assumed to have been appointed as a systems analyst right after you completed your study. For the purpose of assessment 1, you recently commence a system development project. Your role is to analyse the Project Case Study supplied to you, identify critical elements, undertake the tasks and develop a reporting document about systems analysis. For your tasks, you are expected to document the tasks within the project in a reporting document. In your reporting document, for each task (enriching graphical diagrams are welcome) you explain: • What you see as the identified problem and how you seek approval, • What you see as two possible methods to develop the system and your selected method towards system development,• What you will plan as your project work breakdown structure and timeline. Show you project work breakdown structure and schedule as a Gantt Chart; • Show in an Excel spread sheet your 5-year cost and benefit analysis. Your system development project documentation is a reporting document set within the following structure, layout, format and details. The Written Assessment You will produce the reporting document that aims to inform the management about your systems analysis results of the system development project for submission. In the reporting document, you have to adhere to the following presentation wordings, structure and contents. For submission, each student has to prepare the reporting document as a MS Word file, Cost/Benefit Analysis spreadsheet as an Excel file, an MS Project file with a work breakdown structure and a Gantt Chart showing a timeline for the information system project. All above three files are to be zipped into ONE SINGLE Windows Zip file for submission. Zipping requirement: Windows zip only Reporting Document Layout and Submission Guidelines As in a separate template file "COIT11226Assessment1TemplateFile" (in MS Word) provided to you, the reporting document for the 'Systems Development Project' has been organised using the following headings and guidelines. Please observe the word count in each section when developing your reporting document: • Title Cover Page with clear details of course title/name, student number/name, lecturer & tutor (Provided in template file) *Not for word count • Introduction (Provided in template file) *within 100 words o It clearly defines the aims of the reporting document and identifies the project objectives. • The identified problem for the information system project and project approval *within 200 words • Two (2) possible methods towards system development and justifications for the selected method (1) *within 200 words o Start discussing each approach in a new sub-section • The timeline of the information system project (work breakdown structure and Gantt Chart and their explanations) *within 200 words • The 5-Year cost/benefit analysis (an Excel spreadsheet and explanations) *within 200 words • Reflections and Conclusions *within 100 words o Present your reflections about this project (e.g. achievement and constraints). The conclusions are a summary of your findings. • References (must complete by showing 1 or more references; text book must be one of the references) *Not for word count Help To help the group members communicate, Forums and Wikis are created for your use on the course Moodle website for the purposes of Assessments 1 and 2. Please use them for your greatest benefits.Help on writing your reporting document is contained in the Faculty Guide for Students – Chapter 3 – available here: http://www.cqu.edu.au/__data/assets/pdf_file/0003/2289/Extract-of-Chapter-3.pdf You may also benefit from a video supplied by the CQUniversity Communications Learning Centre available here: http://www.youtube.com/watch?v=J0v9ekxeokoAssessment criteria Individual reporting document marking guide Marks for Assessment 1 will be allocated as follows: TOPIC Mark Result Title cover page (with course title/name, student number/name, lecturer, tutor) - for all above needed information clearly produced (5 marks) 5 Introduction - aims of reporting document clearly defined - covered contents in the reporting document clearly explained 5 5 Identified Problem and Project Approval (10 marks) - Identified Problem - Project Approval 5 5 Possible approaches towards system development (20 marks) - Two possible methods (10 marks x 2) - Justifications for the selected method 10 10 Project timeline of the information system project (20 marks) - Work breakdown structure and the explanation (5 marks x 2) - Gantt chart and the explanation (5 marks x 2) 10 10 5-year cost/benefit analysis (20 marks) - An Excel spread sheet for 5-year cost/benefit analysis - Explanation of details in the cost/benefit analysis 10 10 Reflections and Conclusions (10 marks) - Reflections of achievable outcomes and constraints - Summary of findings 55 References 5 TOTAL: 100 Assessment mark will be weighted to 20%. Page 1 of 2 COIT 11226 Systems Analysis & Design (Term 2, 2016) Case Study For Assignment 1 & 2 The Case: Education In Australia (EIA) "Education In Australia" (EIA) is a boutique student recruitment firm operated by Ms Toni Carlow and members of her family in the heart of Brisbane CBD. The firm specialises in recruiting international students for Universities, TAFE's and private registered training organisations. EIA began operating 10 years ago as a boutique student recruitment firm with Toni and her assistant Tina undertaking most of the work. Toni bought a Personal Computer, a multifunction device (Printer, Scanner & Copier) and hired a room in a business centre to set up the initial operation. The business operated 5 days a week, from 9 am to 5 pm and engaged in minimal advertising. EIA's business processes are manual, including the creation of client contracts, accepting payments and issuing receipts, generating letters to students and other stakeholders. Student details are maintained using a spread sheet, and appointments were maintained in Microsoft Outlook. All student files are paper based and staff would often need to spend time searching for a particular file. Once the student file was found, additional time was spent looking for documents within a particular file. Sometimes files would go missing and then reappear after a few days. The misplacement of files would create strain for the staff by causing embarrassment in front of students. Toni soon realised that valuable time was being wasted locating and managing files. In addition, Australian legislation required that the file from a closed case had to be kept on the firm's records for 7 years. Current Manual Process Student approaches EIA to discuss admission options and provides bio demo information, contact details, copies of passport, visa, English language proficiency and previous qualifications. EIA staff fill out application forms depending upon the course / provider selected by the students and send this to the provider requesting an offer letter. If the student is accepted by the provider, the provider issues an offer letter to the student via EIA. The student signs the offer and pays EIA the course fee. EIA remits the course fee along with signed offer letter to the provider who subsequently issues a COE. This completes the recruitment process. Subsequently after the student is enrolled with the provider, EIA accounting staff raise an invoice to the provider to claim commission for the student recruitment. Accounting staff have to often follow-up these invoices and chase payments from providers. Details that are currently manually recorded on file are:- • Student name, address, contacts details (phone, mobile, email) • Visa & Passport Details • Details of offers applied, received • Details of Fees paid by student to the provider via EIA • Details of COE Received like COE Number, COE Date, COE Duration & Fees • Student Education DocumentsPage 2 of 2 • Student English Proficiency Evidence (Like IELTS or PTE or OET Exam results) • Visit & Call Notes of all interactions with students • Reminders set by staff to follow-up offers, COE or payments • List of providers & the courses offered by each provider include start dates, end dates, course fees and entry requirements Accounting All invoices are created manually using pen and paper and outstanding payments from education providers are tracked by setting reminders in Microsoft Outlook Problems with the Current System 1. Only one staff member can access important information at a time which causes bottlenecks especially if staff are away 2. There is some duplication with paper and electronic records 3. Records are held in computer applications plus in paper form 4. The system does not provide an effective means for keeping deadline details Due to these problems, some transactions have not been handled well and customer complaints are increasing. Desired New System Toni Carlow owner of Education in Australia has identified that her major priority is to create a system that ties together all the key elements of student recruitment transactions. She has hired your company, Brisbane Business Systems as consultants to carry out analysis and develop the specifications for an automated Student Recruitment Management System. Toni has earmarked a budget of $50,000 for this project with a discount rate of 6%. She estimates that the new system will help her reduce her staffing cost by $2,000 per month and increase commission's income by atleast another $2,000 per month thus increasing her overall profitability by $4,000 per month. Maintenance cost could be estimated at around $1500 per month. Glossary of Terms EIA = Education In Australia TAFE = Technical & Further Education COE = Confirmation of Enrolment IELTS = International English Language Testing System PTE = Pearson Test of English OET = Occupational English Test