Assignment 3 - Specification

.docx

School

Central Queensland University *

*We aren’t endorsed by this school

Course

COIT2024

Subject

Computer Science

Date

Jan 9, 2024

Type

docx

Pages

Uploaded by DrGalaxyHamster27

1 COIT20258 Assessment 3 - Group Term 2, 2023 COIT20258 Assessment Item 3— Assignment 3 Due date: Exam Week (Friday 13 th October 2023) 11.45 pm AEST Weighting: 45% Length: Group 1,000 words report and application project code Individual : 500 words report

2 COIT20258 Assessment 3 - Group Term 2, 2023 1. Objectives The purpose of this assessment item is to assess your skills attributable to the following learning outcomes and achieving the expected graduate attributes of advanced level knowledge, communication, cognitive, technical, and creative skills, leadership, ethical and professional responsibility, self-management, and professional-level research. •Develop models of the proposed multi-tiered software application as per the requirements identified following formal requirements engineering procedures •Design system architecture and components using design patterns and object- oriented design •Develop three-tiered software applications using agile and plan-driven methods •Plan and conduct test-driven development, validation and verification testing •Assess software quality measures and maintenance requirements of software applications •Work independently and collaboratively in small teams. This assignment is a team-based software development project. You will work in a small team for the design and development of a 3-tier application. You will practice working collaboratively and communicate effectively as part of a productive team. Your submission for this assessment in addition to NetBeans Java project should also be report written in professional layout. Your team should create a GitHub repository, see week 8 on Moodle. Your GitHub repository will be accessible by your tutor where he/she can make comments and have discussions to guide you during the implementation of your assignment 3 project. 2. Team Membership Rules By default, a team works collaboratively; with all members performing their duties timely. The team leader submits the project, and each member must submit his/her teamwork report of Template A (see “Submission for Part 2” in this document) by the assignment due time. A large emphasis of this group project is solving minor collaborative problems as a part of teamwork, and this should be reflected upon in the teamwork report. Each team should minimise contacts with the lecturer/tutor/coordinator for minor collaborative problems, as too many contacts show the ineffectiveness or inefficiency of the team for solving minor problems and will result in loss of marks. Each team member should use the following rulls if a major problem arose. The unit coordinator should be contacted as a last resort, only when the dispute cannot be solved by the following agreement. When teams are formed in GitHub, each team member agrees that the whole team is to take its own risk when including an individual member and that the project progress can be delayed by that individual member. Some circumstances are:

3 COIT20258 Assessment 3 - Group Term 2, 2023 1. A team member cannot take his/her allocated duty normally for a particular reason, e.g. health condition. If an extension is given to that particular member, the extension is applied to the whole team. If there is no extension granted for that particular member, the whole team is to take the risk of a late penalty. In addition, the whole team is to take its own risk of any other impact, e.g. influence on the schedule of other units of study, which may be caused by the improper delivery of duty of that team member. 2. The other members of a team are to complete the whole project if a team member leaves in the middle of the project for any sound reasons or no reasons. 3. If a team splits into individuals in the middle of the project, each individual needs to complete the whole project separately. 4. If a team member does not take his/her allocated duty and cannot be contacted, the team can provide evidence of 3 contacts without responses or other relevant evidence to the unit coordinator. The unit coordinator reserves the final right to decide whether the member should be excluded from the team. However, as mentioned in point 2 previously, the rest of the team needs to complete the whole project if a team member is excluded from the team. 5. Any individual, who separates/quits from a team for any reason in the middle of the project, needs to complete the whole project and the teamwork report of Template B (see Part 2 of this document). 3. Required Tasks in This Assignment This assignment consists of 2 parts. 3.1 Part 1 – Project Code and Documentation (as Group) a) Requirement Specification The initial task is to complete the requirements engineering process by eliciting:  Functional,  Non-functional,  System and  User requirements. b) Design Models You should develop models of:  system architecture,  use cases, and  behavioural models such as sequence diagrams. Data security is important and there should not be any chance for the users to delete any records. Application should have an intuitive interface. The staff should be able to add users and all users should be able to login using a user name and password. Passwords can be eight characters long with letters and numbers. The system should be easily maintainable and robust. c) Quality Plan The system development should be quality driven. You should develop a quality plan to be followed for the design and implementation of the system. The quality plan should identify the quality requirements of:  The System,  methods,

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

4 COIT20258 Assessment 3 - Group Term 2, 2023  measurements, and  standards to ensure the desired quality. d) Design and Test-driven development You should follow MVP design pattern in your design. Identify the classes following this pattern and create a class diagram showing the association and cardinality. All the users of the system should be saved in the database with a user name, password, full name, email, and phone number. What to submit in Part 1? 1 Design Document You should submit a document file (.doc or .docx ) containing the following details. 1. Cover page with the team and individual information 2. Requirement specification 3. Quality Plan 4. Design - UML diagrams: i. Use cases diagram ii. Classes diagrams behavioural models such as sequence diagrams and iii. ERD for the database 5. Test plan showing input data, expected results, and actual results. 6. Evidence of testing including some screenshots. 2 Software You will need to provide the complete implementation code of the project, including Java source code and executable files. You need to provide your implementation by a NetBeans project , which can be compiled directly without any further revision/re- development or debugging. You must provide all the required libraries, resources, database scripts and everything that your project needs to run such as what JDK etc. You must provide detailed instructions on how to run and test your application Version Control You must use version control software (i.e., GitHub) as your code repository and provide the link to your repository in your report. Coding standards Include necessary accessor, mutator methods, constructors, and toString() method for each class. Also, follow good coding practices, using meaningful names, camel case notation for naming, constants as necessary, and include meaningful comments. You can use NetBeans or another IDE to develop your application. Follow the coding standards given on the Unit website. Application Data Provide SQL script to create and populate the MySql database used by your application Note 1: Only one submission of this part from the team leader is required. The complete project and the documents will need to be compressed into a zip file for the team leader to submit. This part will be marked, and the same marks will be given to all team members. Note 2: If your NetBeans project would not compile or run, it will still be marked by visual code inspection, but there will be 50% reduced marks penalty.

5 COIT20258 Assessment 3 - Group Term 2, 2023 3.2 Part 2 - Teamwork report (as individual) A student, who completes the whole project as a member of a productive team, is to prepare a document in the following format and address the following questions. Template A 1. Team Details a. Team Name (optional): b. Your Name and Student ID: c. Team Leader (Name and Student ID): d. Other Team Members (Name and Student ID): 2. Teamwork Report a. Describe team forming, task assigning, your role and responsibility and the project timeline b. List 2 technical problems in the project development and describe how the problems have been solved by the team. c. List 2 collaborative problems in the teamwork and how the problems are negotiated and solved by the team. d. Describe and justify what is important for the success of teamwork. e. Describe the communication skills that you have developed in this small team-based project. A student, who separates/quits a team in the middle of the project, is to prepare a document in the following format and address the following questions. Template B 1. Team Details a. Team Name (optional): b. Your Name and Student ID: c. Team Leader (Name and Student ID): d. Team Members (Name and Student ID): 2. Teamwork Report a. Describe team forming, task assigning, your role and responsibility and the project timeline b. Describe what major problems that cause you to leave the team or cause the team to break into individuals. c. Describe and justify the impact on you and other team members caused by your leave or the break of the team d. Describe and justify what are important strategies for successful teamwork. e. Describe and justify how you can avoid such hindrances of teamwork in future opportunities of teamwork. Note: this part is to address a team member’s individual experience with teamwork. The document is not shared between the team members; each team member needs to submit his/her document

6 COIT20258 Assessment 3 - Group Term 2, 2023 individually. The same/copying contents of this part by 2 or more team members will be treated as plagiarism.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

7 COIT20258 Assessment 3 - Group Term 2, 2023 4. Assessment Criteria Marks for Assessment 3 will be allocated as follows: Apendex 1 Project Scenario HealthLink Hospital is a medium-sized healthcare facility that offers a range of medical services, including inpatient care, outpatient clinics, diagnostic imaging, and pharmacy services. The hospital currently lacks a comprehensive digital system to manage patient records, appointments, billing, and inventory, leading to inefficiencies and errors. Project Goals: The primary objective of this project is to design and develop a Healthcare Management System that will streamline the hospital's operations and improve patient care. The system should encompass the following key functionalities: 1. Register users and enable user login with role-based user access. (DONE) 2. Patient Management: Allow hospital staff to register patients (DONE), manage their electronic health rec ords (EHRs), and schedule appointments efficiently. 3. Appointment Scheduling: Enable staff to book appointments with real-time availability updates. (Created UI need to add functionality) 4. Billing and Invoicing: Automate billing processes, generate invoices for services rendered, and provide an interface for staff to view and print bills. (NOT DONE) 5. Reporting and Analytics: Provide data analytics and reporting tools for hospital administrators to make data-driven decisions. (NOT DONE) 6. Security and Privacy: Ensure the system complies with healthcare data privacy regulations (e.g., HIPAA ) to protect patient information. (NOT MUCH IMPORTANT)

Recommended textbooks for you

Information Technology Project Management

Computer Science

ISBN:9781337101356

Author:Kathy Schwalbe

Publisher:Cengage Learning

Information Technology Project Management

Computer Science

ISBN:9781285452340

Author:Kathy Schwalbe

Publisher:Cengage Learning

Fundamentals of Information Systems

Computer Science

ISBN:9781305082168

Author:Ralph Stair, George Reynolds

Publisher:Cengage Learning

COMPREHENSIVE MICROSOFT OFFICE 365 EXCE

Computer Science

ISBN:9780357392676

Author:FREUND, Steven

Publisher:CENGAGE L

Principles of Information Systems (MindTap Course...

Computer Science

ISBN:9781305971776

Author:Ralph Stair, George Reynolds

Publisher:Cengage Learning

Enhanced Discovering Computers 2017 (Shelly Cashm...

Computer Science

ISBN:9781305657458

Author:Misty E. Vermaat, Susan L. Sebok, Steven M. Freund, Mark Frydenberg, Jennifer T. Campbell

Publisher:Cengage Learning

SEE MORE TEXTBOOKS

Recommended textbooks for you

Information Technology Project Management
Computer Science
ISBN:9781337101356
Author:Kathy Schwalbe
Publisher:Cengage Learning
Information Technology Project Management
Computer Science
ISBN:9781285452340
Author:Kathy Schwalbe
Publisher:Cengage Learning
Fundamentals of Information Systems
Computer Science
ISBN:9781305082168
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning
COMPREHENSIVE MICROSOFT OFFICE 365 EXCE
Computer Science
ISBN:9780357392676
Author:FREUND, Steven
Publisher:CENGAGE L
Principles of Information Systems (MindTap Course...
Computer Science
ISBN:9781305971776
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning
Enhanced Discovering Computers 2017 (Shelly Cashm...
Computer Science
ISBN:9781305657458
Author:Misty E. Vermaat, Susan L. Sebok, Steven M. Freund, Mark Frydenberg, Jennifer T. Campbell
Publisher:Cengage Learning