A3 BISY2001-ISY2001-ISY201 T1 2020 Case Study Unit BISY2001-ISY2001-ISY201 System Analysis and Design Assessment Type Case Study Group Assessment Number 3 Assessment Weighting Essay 30% Alignment with...

1 answer below »
PLEASE READ THE ASSIGNMENT DESCRIPTION CAREFULLY AND THE DUE DATE IS 23/09


A3 BISY2001-ISY2001-ISY201 T1 2020 Case Study Unit BISY2001-ISY2001-ISY201 System Analysis and Design Assessment Type Case Study Group Assessment Number 3 Assessment Weighting Essay 30% Alignment with Unit and Course Unit Learning Outcome Graduate Attributes Assessed LO 1: Describe and discuss concepts and principals of systems analysis and design. LO 2: Examine the stages of the systems development life cycle. LO 3: Apply basic diagrammatic modelling tools to systems analysis and design. LO 4: Use specifications such as user interfaces, databases, and systems interfaces to design systems to meet specific business/project purposes. GA 1: Communication GA 4: Critical Thinking and Problem Solving GA 6: Flexibility Due Date/Time Week 10 – 29th May 2020 5:00 pm via Moodle Assessment Description In this assessment, students must work in a group to prepare a case study analysis of a systems development project. You are required to form groups of Three to Four (3 to 4) students. Your group is required to research and analyse a real life situation and prepare a full analysis of a systems development project. Feel free to discuss your real life situation project with your lecturer before engaging in any work. Suggested topics below. You may use www.creately.com, www.diagrams.net, MS Word, Visio or any other modeling tool to create diagrams. Your systems analysis and design project should include the following: • Executive summary (max. 1/2 page). 2.5 Marks • Introduction including description of the business, problem/opportunity identified and goal and objectives of this project (max. 1 pages). 2 Marks • Data gathering methodology and results (max. 1 pages). 2.5 Marks • Existing system including current system overview, FDD, DFD, and Data Dictionary. 6 Marks • Proposed system including system overview, system requirements checklist, DFD, Data Dictionary, Object relationship diagram, Use Cases, Class Diagram, and Sequence Diagrams. 12 Marks • Conclusions and recommendations (max. 1/2 page). 2.5 Marks • Group reflection on Assessment 3 (max. 1/2 page). 2.5 Marks Suggested topics (list is not restricted): • Hotel Booking System • Library Management System • Car Rentals System • Online enrolment System • Entertainment System ( movies , songs , Books and games ) • Online Shopping System • Real Estate System • Parking lot booking system • Student information chat bot Detailed Submission Requirements • This assessment must be submitted by one student per group through the link on Moodle page for this unit. • Include a cover sheet that has students’ name, subject, date, report title and WORDCOUNT. • The assignment should not exceed 1,200 words. Diagrams, charts and Data Dictionary do not count towards wordcount. Misconduct • Engaging someone else to write any part of your assessment for you is classified as misconduct. • To avoid being charged with Misconduct, students need to submit their own work. • Remember that this is a Turnitin assignment and plagiarism will be subject to severe penalties. • The AIH misconduct policy and procedure can be read on the AIH website (https://aih.nsw.edu.au/about-us/policies-procedures/). Late Submission • Late submission is not permitted, practical submission link will close after 1 hour. Special consideration • Students whose ability to submit or attend an assessment item is affected by sickness, misadventure or other circumstances beyond their control, may be eligible for special consideration. No consideration is given when the condition or event is unrelated to the student's performance in a component of the assessment, or when it is considered not to be serious. • Students applying for special consideration must submit the form within 3 days of the due date of the assessment item or exam. • The form can be obtained from the AIH website (https://aih.nsw.edu.au/current-students/student-forms/) or on-campus at Reception. • The request form must be submitted to Student Services. Supporting evidence should be attached. For further information please refer to the Student Assessment Policy and associated Procedure available on (https://aih.nsw.edu.au/about-us/policies-procedures/). Marking Schema Rubrics Marking Criteria HD D C P F ULO 1: Describe and discuss concepts and principals of systems analysis and design ULO 2: Examine the stages of the systems development life cycle ULO 3: Apply basic diagrammatic modelling tools to systems analysis and design ULO 4: Use specifications such as user interfaces, databases, and systems interfaces to design systems to meet specific business/project purposes. Executive summary: Reflects all of the following characteristics: conciseness, accuracy, and objectivity. Introduction: Description of the business, problem/opportunity identified and goal and objectives of this project are clear and reflect a true work on the project. Data gathering methodology and results: Clear and reflect a true work on the project. Existing System: System overview, FDD, DFD, and Data Dictionary are fully correct. Proposed System: System overview, system requirements checklist, DFD, Data Dictionary, Object relationship diagram, Use Cases, Class Diagram, and Sequence Diagrams are fully correct. Conclusion and recommendations: Clear and reflect a true work on the project. Reflection: Genuine and accurate. (25 - 30 marks) Executive summary: Reflects the following characteristics: conciseness, accuracy, and objectivity with minor mistakes. Introduction: Description of the business, problem/opportunity identified and goal and objectives of this project are somewhat unclear and reflect a good effort on the project. Data gathering methodology and results: Somewhat unclear and reflect a good effort on the project. Existing System: System overview, FDD, DFD, and Data Dictionary are fully correct with minor errors. Proposed System: System overview, system requirements checklist, DFD, Data Dictionary, Object relationship diagram, Use Cases, Class Diagram, and Sequence Diagrams are fully correct with minor errors. Conclusion and recommendations: Somewhat unclear and reflect a good effort on the project. Reflection: Genuine and accurate with minor mistakes. (22 – 25 marks) Executive summary: Unclear and does not reflect all of the following characteristics: conciseness, accuracy, and objectivity. Introduction: Description of the business, problem/opportunity identified and goal and objectives of this project are unclear and do not reflect a true work on the project. Data gathering methodology and results: Somewhat unclear and do not reflect a true work on the project. Existing System: System overview, FDD, DFD, and Data Dictionary are partially correct with a few errors. Proposed System: System overview, system requirements checklist, DFD, Data Dictionary, Object relationship diagram, Use Cases, Class Diagram, and Sequence Diagrams are partially correct with a few errors. Conclusion and recommendations: Somewhat unclear and reflect a good effort on the project. Reflection: Appears to be unauthentic and partially accurate. (19 - 22 marks) Executive summary: Inaccurate and does not reflect any of the following characteristics: conciseness, accuracy, and objectivity. Introduction: Description of the business, problem/opportunity identified and goal and objectives of this project are inaccurate and do not reflect any effort in the project. Data gathering methodology and results: Inaccurate explanation and does not reflect any effort in the project. Existing System: System overview, FDD, DFD, and Data Dictionary are not accurate. Proposed System: System overview, system requirements checklist, DFD, Data Dictionary, Object relationship diagram, Use Cases, Class Diagram, and Sequence Diagrams are inaccurate. Conclusion and recommendations: Are no accurate. Reflection: Appears to be unauthentic and inaccurate. (15 - 19 marks) Executive summary: Is not attempted or quite unclear and incomplete. Introduction: Description of the business, problem/opportunity identified and goal and objectives of this project are not attempted or quite unclear and incomplete. Data gathering methodology and results: Are not attempted or quite unclear and incomplete. Existing System: System overview, FDD, DFD, and Data Dictionary are not attempted or incomplete. Proposed System: System overview, system requirements checklist, DFD, Data Dictionary, Object relationship diagram, Use Cases, Class Diagram, and Sequence Diagrams are not attempted or incomplete. Conclusion and recommendations: Are not accurate. Reflection: Is not attempted or dishonest. (0 - 15 marks)
Answered Same DaySep 18, 2021BISY2001

Answer To: A3 BISY2001-ISY2001-ISY201 T1 2020 Case Study Unit BISY2001-ISY2001-ISY201 System Analysis and...

Neha answered on Sep 21 2021
119 Votes
65678 - library system/65678 - library system.docx
Executive Summary
The University is the best place where it is very important to manage the books as the number of students is increasing day by day. The University wants to help their students who have already finished their educati
ons or going for higher educations. The college provides short term courses to the students through training either in class or distance learning mode. The college has plans to provide high quality educations and they want to increase the success rate of the students in their University. Now the college wants to develop infrastructure of the library which can help the students to pursue their courses in an efficient way. They want to develop and expand their current library management system by involving digital methods and create a new automated process which can manage the library. In this report I have included detailed information about the current system and the flow of library management system along with the new process which will be implemented in the new University and help them to store data more accurately. The report shows data flow diagrams, control flow diagrams, sequence diagram, class diagram and few more things which can help the reader to understand about the library management system and its importance for the University.
Introduction
As we have already discussed about the increase in number of the users who can access the library, so it is very important to have a better management system. The library management system is mainly focused on improving the management of library which are present in the University. It should be easier for every user to access the book from the library. The new library management system is designed in such a way that it can ease out the process of issuing a new book, renewing a book or reserving a book from the library without paying any physical visit to the library. The new library management is developed using Java language and the major focus is to allow the user to perform major functions using the system. The new system is designed for students who have to visit the library and waste their many hours in searching of books (Amato, G., Gennaro, C., Rabitti, F. and Savino, P).
Purpose
The purpose of developing the new project is to help the users and managers of the library to manage the process of issuing the books and managing the details. The clients can issue their books using the system and also search for their books without going to the University.
Scope
The system is developed using Java language and it will allow the registered user to search for the books which are available in the library and they can borrow the book using the system or cell phones. The automated system will have the capabilities to show details of the book, limitation of issuing a book, fine of the...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here