For faster services, inquiry about  new assignments submission or  follow ups on your assignments please text us/call us on +1 (251) 265-5102

WhatsApp Widget

Get T2 2023 HI5030 Systems Analysis and Design Assignment

HI5030 Systems Analysis and Design

Group Assessment – Group Case Study

Cover Page

Unit Details Name Systems Analysis and Design
Code HI5030
Year, Trimester 2023, Trimester 2
Assessment Details Name Group Assignment
Due Date and Week 03 / 09 / 2023, Week 7 01 / 10 / 2023, Week 11
Group Student Details Student ID First Name Family Name Work Contribution
       
       
       
       
Group Submission Declaration Integrity Declaration Student ID Full Name Submission Date
We have read and understand academic integrity policies and practices and our assessment does not violate these.      
     
     
     

Instructions

Academic Integrity Information Holmes Institute is committed to ensuring and upholding academic integrity. All assessment must comply with academic integrity guidelines. Important academic integrity breaches include plagiarism, collusion, copying, impersonation, contract cheating, data fabrication and falsification. Please learn about academic integrity and consult your teachers with any questions. Violating academic integrity is serious and punishable by penalties that range from deduction of marks, failure of the assessment task or unit involved, suspension of course enrolment, or cancellation of course enrolment.
Format Instructions Most assessments must be in MS Word format with no spacing, 11-pt Calibri font and at least 2cm margins on all four sides with appropriate section headings and page numbers.

You must name your file with the Unit Code and Group Number (e.g. “HI5004 Group 4”).

Check that you submit the correct document as special consideration is not granted if you make a mistake.

Student IDs need to be indicated on the cover page. Non-contributing students do not receive marks.

Penalties All work must be submitted on Blackboard by the due date and time along with a completed Assessment Cover Page. Late penalties apply.

Reference sources must be cited in the text of the report, and listed appropriately at the end in a reference list using Holmes Institute Adapted Harvard Referencing. Penalties are associated with incorrect citation and referencing.

Purpose

The purpose of the group system analysis and design project is to demonstrate students’ ability to apply the knowledge learned in this course to a real-world project.

Assessment Description

The system analysis and design project must be realistic and it will be done using techniques covered in this course. You should select any of the following projects that are based on any real-life example. For example, if you choose the ebay bidding system as your project, you must analyze the requirements of that system and base your analysis and design activities on the identified requirements and the processes associated. You are free to identify the issues with the current system and suggest improvements and include suggestions for your project. Find more information about these systems by browsing their details on the web.

  1. Ebay Bidding System
  • Uber Eats delivery System
  • Commonwealth bank’s CommSec pocket investment system
  • Bupa OSHC Health Insurance Claim system
  • Easypark car park system Melbourne
  • Realestate.au rental system
  • KFC Order on the Go system
  • Flybuys rewards management system
  • Ampol’s EG Club system
  1. Plenty of Fish Dating System
  1. Seek employment System
  1. DogPack app – Dog Park Finder system
  1. Ticketek AU sports and entertainment ticketing system
  1. LinktGo Toll App System
  1. PTv App – Public Transport Victoria transport search system.

Project Deliverables

The project requires students to perform two phases: (a) requirements Analysis (b) System Modelling.

Title page (project name, author, and date)

Phase 1: Requirement analysis (Due Date – Week 7)

  1. Introduction to the selected project and System description
  • Objectives of project
  • Requirement Specification (functional and non-functional) and Constraints
  • Description of the proposed system
  • Logical model design
  1. Data flow diagrams – Context diagram
    1. Data flow diagrams – Diagram 0/Diagram [Diagram 1 is optional]
    1. Descriptions of processes in each diagram (Process descriptions in Structured English]

Marking Criteria and Rubrics

Marking Criteria Marks
Introduction, Objectives and Requirements 1
Requirement Specification 3
Context diagram 2
Dataflow diagrams and Process Descriptions 4
Total 10

Phase 2: System and database design (Physical model design) (Due Date – Week 11)

A.  Object Oriented Modelling

Use a suitable UML diagramming software such as IO.Draw, Visual Paradigm (community edition) or Lucid charts to model the following diagrams of your selected project. Hand-drawn diagrams or diagrams developed using office suits are not accepted. Based on your project requirements, you may include the entire model in one diagram or subdivide the model into several subsystem diagrams.

  1. Class diagrams
    1. Activity diagrams
    1. Class diagram
    1. Sequence diagrams

B.  User interface

Design an overall user interface consisting of screens, commands, controls, and features to enable users to use the system. Choose at least 4 main fictionalizes of your project to develop user interfaces. Your design should demonstrate how data will be input to the system? That includes the physical layout for input, the input design and procedures, and how data will be output from the system. Use suitable wire framing software such as Lucid Charts online wire frame tool, Balsamiq Wireframes, or figma.com to design your interfaces.

C.  Data design

Develop a physical plan for data organization, storage, updating, and retrieval.

  1. Entity-relationship diagrams

Use a suitable UML diagramming software such as IO.Draw, Visual Paradigm (community edition) or Lucid charts to model this diagram.

  • Database design
  1. Database tables with their attributes should be presented (however theirimplementations are not required)
    1. Primary key(s) should be identified in each table, if any
  • Three steps of normalization should be included.

Marking Criteria and Rubrics

Marking Criteria Marks
Use case diagrams 4
Activity Diagrams 4
Class diagrams 4
Sequence diagrams 4
User Interfaces 8
ER Diagram 2
Database design 2
Documentation practices and presentation 2
Total 30

The post Get T2 2023 HI5030 Systems Analysis and Design Assignment first appeared on Marvel Assignment Help.

WhatsApp
Hello! Need help with your assignments?

For faster services, inquiry about  new assignments submission or  follow ups on your assignments please text us/call us on +1 (251) 265-5102

GRAB 30% OFF YOUR ORDER

X
GET YOUR PAPER DONE