Posted: March 17th, 2023

SBM4201 Systems Analysis and Design Assessment

Assessment Details

Unit Code and Title: SBM4201 Systems Analysis and Design
Assessment Overview
Assessment Task Weighting Due Length ULO
Assessment 1: Case Study -1
Covers the following topics Systems
Development Life Cycle (SDLC), Work Breakdown Structure (WBS), PERT/CPM chart, NPV, ROI and payback period 30% Week 5 2500 words ULO1
ULO2 ULO3
Assessment 2: Case Study -2
Covers the following topics: use case diagram, ER diagram Class diagram, Sequence diagram, Activity diagram, user and system interfaces, and system testing, deployment and maintenance and 30% Week 12 2500 words ULO1
ULO2
ULO3
ULO4
Assessment 3: Project Design
Every two weeks exercises assess students’ ability to understand theoretical materials 40% Weekly N/A ULO1
ULO2
ULO3
ULO4
ULO5

Who Writes College Essays, Research Papers, and Dissertations For Students?

We handpick every writer with care, ensuring they bring the perfect mix of academic qualifications and writing skills for top-notch results in essays, research papers, and dissertation help. Each one has a university degree, more than a third with Masters certification; they’ve tackled tough tests and training to excel in thesis writing and research paper assignments at any time. They’ll team up with you diligently, keeping things easy and stress-free as they relate to being immediate students. That’s what makes us the best assignment help website for "help me write my essay, research paper, or dissertation" for college coursework. Trust our team—professional research essay writers and editors—to deliver your dissertation or thesis writing within your grading criteria and deadline.

Assessment 1: Case Study-1
Due date: Week 5
Group/individual: Group
Word count / Time provided: 2500 words
Weighting: 30%
Unit Learning Outcomes: ULO-1, ULO-2, ULO-3

Assessment Details:
In this assignment, you have to perform a system analysis and design for the Nuk Restaurant System (NRS) case study provided at the case study section.

Case Study: Nuk Restaurant System (NRS)
The Nuk is a restaurant that opened in 2020 after its owners, Mala and Ashli, graduated from university. Both determined to open their restaurant in Sydney. They realize that they can be successful by collecting, analysing, and using the data that is available to them. Therefore, Nuk aims to collect data from their customers in a way that they can keep individual sales, loyal customers, the most popular food, or drink. For this purpose, customers require to create an account before their first visit to Nuk restaurant. The Information records on the online system consist of first and last name, residential address, city, zip code, mobile number, and email address. For digital purposes, a unique identification number is created for each customer. If the customers face any issues for creating an account or reserving a table, the advisor needs to support them. In this case, the online system needs to record the assigned advisor for each customer, by recording the name of the advisor who supports customer for each time. Regarding services, the new online system keeps the information in terms of name and type of services such as food, drink and the payment method (cash, credit card). Regarding reservation, the system records the number of tables that are booked and information related to special events (birthday).
Mala and Ashli, managers of the restaurant, hope to run an entirely testable procedure to the whole online system to find out any bug and significant issues before the final launch of the system.
The Nuk restaurant considers different methods to estimate the investments in this project. Table 1 presents the information the accountant provided to the system analyst to calculate Net Present Value (NPV), Payback Period and Return on Investment (ROI).
Table 1: Five-year investment evaluation
Year
No. Category 0 1 2 3 4 5
1 Value of benefits $ 8,000.00 $ 8,000.00 $ 8,000.00 $ 8,000.00 $ 8,000.00
2 Development Cost -$ 20,000.00 -$750.00 -$800.00 -$770.00 - $750.00 -$730.00
3 Annual expenses -$ 2,000.00 -$ 2,000.00 -$ 2,000.00 -$ 2,000.00 -$ 2,000.00
4 Net benefit/costs $ 20,000.00
5 Discount factor 1.00
6 Net present value -$ 20,000.00
7 Cumulative NPV -$ 20,000.00
Tasks:
1. Develop your introduction and clearly define the aims and objectives of the report.
2. The Systems Development Life Cycle (SDLC) identifies all the activities required to build, launch, and maintain an information system. Discuss the six core processes of the SDLC required to develop the NRS project in detail.
3. Develop a Work Breakdown Structure (WBS) description supported with a table for the NRS project explaining the ID, description, and duration for each task.
4. Develop PERT/CPM chart explaining the early and late start for each task. Identify the critical path and the total time to finish the project.
5. Use the information in Table 1, calculate the net present value, the payback period, and the return on investment by using a discount rate of 6 percent. The development costs for the project were $20,000. Do a five-year return on investment.

You may need to make some assumptions as required. Whenever you make assumptions, please state these clearly.

Do You Offer Thesis Writing and Dissertation Help In Any Citation Style?

No matter what citation style you need for your research paper or dissertation, our skilled writers have you covered! We provide thesis writing and dissertation help in formats like APA, AMA, MLA, Turabian, Harvard, IEEE, and more. We’re dedicated to customizing your order to the exact guidelines of your chosen style, ensuring it fits your unique academic needs—whether it’s a dissertation, research paper, or essay for a specific course. We’ve got the flexibility to make it work for you!

Marking Criteria and Rubric: The assessment will be marked out of 100 and will be weighted 30% of the total unit mark.

Marking
Criteria Not satisfactory
(0-49%) of the
criterion mark) Satisfactory
(50-64%) of the criterion mark Good
(65-74%) of the criterion mark Very Good
(75-84%) of the criterion mark Excellent
(85-100%) of the criterion mark

Can I Change Instructions for Dissertation Help or Thesis Writing After Ordering?

You can absolutely reach out to your academic writer using our simple, user-friendly chat feature. It’s there so you can add details, clarify instructions, or tweak adjustments for editing your research paper or dissertation according to your grading rubric—even after you’ve submitted "help me with thesis writing or dissertation help" and they’ve started working on your project.

Introduction (10 marks) Poor introduction with irrelevant details Introduction is presented briefly and is missing the report outline Introduction is generally presented along with the report outline Introduction is well written, and the report outline is also discussed Introduction is very well written, and the report outline is also discussed
Systems
Development Life
Cycle (SDLC)
(25 marks) Poorly discussion of the six core processes of the SDLC required developing the NRS project. Brief discussion of the six core processes of the SDLC required developing the NRS project. Good discussion of the six core processes of the SDLC required developing the NRS project. Well discussion of the six core processes of the SDLC required developing the NRS project. Excellent discussion of the six core processes of the SDLC required developing the NRS project.
Work Breakdown
Structure (WBS)
(15 mark) Poor description with no poor table for the NRS project to include the ID, description, and duration for each task. Brief description with brief table for the NRS project to include the
ID, description, and duration for each task. Generally good description with good supported table for the NRS project to
explain the ID, description, and duration for each task. Very clear description with good supported table for the NRS project to explain the ID, description, and duration for each task.
Very good description with very good supported table for the NRS project to explain the ID,
description, and duration for each task.
PERT/CPM chart (20 mark) Lack of evidence of understanding of PERT/CPM chart with no identification of critical path and the total time to finish the project.
Evidence of basic understanding of PERT/CPM chart with no clear identification of critical path and the total time to finish the project. Evidence of good understanding and
identification of
PERT/CPM chart with clear identification of critical path and the total time to finish the project.
Very clear understanding and
identification of
PERT/CPM chart with clear identification of critical path and the total time to finish the project. Has excellent understanding and
identification of
PERT/CPM chart with clear identification of critical path and the total time to finish the project.
Table-1 (20 mark) Table-1 is missing or most of the required fields do not correct Some fields of the table not correct or missing All fields are available but many of them not accurate. All field are available and some not very accurate All fields are available and accurate
Summary
(5 marks) Summary not
relating to the
report Brief summary of the report with some relevance Generally good summary of the report A section clearly summarizing the
overall contribution A section very clearly summarizing the
overall contribution
References using
Harvard style
(5 marks) Lacks consistency with many errors. Unclear referencing/style Generally good referencing/style Clear referencing/ style Clear styles with excellent source of references.

5

Assessment 2: Case Study-2
Due date: Week 12
Group/individual: Individual
Word count / Time provided: 2500
Weighting: 30%
Unit Learning Outcomes: ULO-1 ULO-2 ULO-3 ULO-4

Assessment Details:
The Case Study-2 assessment covers the following topics: information system development, system development approaches, data modeling, IS project management, system requirements, user and system interfaces, and system testing, deployment and maintenance.
This assessment allows students to apply theoretical concepts to practice by analysing case studies and proposing a suitable design. The Case Study-2 assessment covers the following topics: information system development, system development approaches, data Modeling, IS project management, system requirements, user and system interfaces, and system testing, deployment and maintenance.
Case Study: Doc Medical Centre (DMC)
The Doc Medical Centre (DMC) would like to offer a user-friendly website that allows potions to access to the website through their phone. The site will facilitate the patients to book an appointment with their desire GP and access to their medical history. Upon the first use, patients require to enter their details in the system, including their types of insurance (e.g., Medicare, Private, etc. and their method of payments (e.g., credit card, PayPal, etc.). This will allow the patients to use the medical centre website in any following appointments. Users can simply log in to their registered accounts and make an appointment by choosing the day of the visit, time and their GP. The system will provide them with an estimated cost according to the type of their insurance details.

Suppose you are asked to develop this online system for DMC. You have been given only four weeks to present a plan for the system design. You will be presenting your design to a team of consultants. The online system should be able to perform several activities such as adding or creating a new patient, checking for the available appointment and requested GP, estimating the cost, issuing an online ticket or receipt for the appointment, and recording all the medical history of the patients. You may add any other possible functions that you deem necessary for this system to function in this business case. Tasks:
• Draw use case description for registering accounts and making an appointment.
• Draw use case diagram
• Identify all entities and their attribute and draw an E-R (Entity-Relationship) diagram.
• Draw the class diagram
• Draw a Sequence diagram
• Draw activity diagram
• Design a data entry screen for entering Personal Details.
PRV12007; CRICOS 03048D
Approved: 13/02/2019, Version 1

• Design a booking appointment input screen which includes the day of the visit, Patients Id, Name and the selected GP
• Plan suitable testing and deployment activities.
if you believe that you need to make additional assumptions, clearly state them for each situation *You can use Microsoft Visio or Microsoft Word to present your design.

Marking Criteria and Rubric: The assessment will be marked out of 100 and will be weighted 30% of the total unit mark.
Marking
Criteria Not satisfactory
(0-49%) of the
criterion mark) Satisfactory
(50-64%) of the criterion mark Good
(65-74%) of the criterion mark Very Good
(75-84%) of the criterion mark Excellent
(85-100%) of the criterion mark

Introduction (5 marks) Poor introduction with irrelevant details Introduction is presented briefly and is missing the report outline Introduction is generally presented along with the report outline Introduction is well written, and the report outline is also discussed Introduction is very well written, and the report outline is also discussed
Use Case description
(10 marks) Poorly discussion of the use case description Brief discussion of the use case description Good discussion of the use case description Well discussion of the use case description Excellent discussion of the use case description
Use Case diagram (10 mark) Lack of evidence of understanding of use case diagram Evidence of basic understanding of use case diagram Evidence of good understanding of use case diagram Very clear
understanding of use case diagram Has excellent understanding of use case diagram
Entities, Attributes and ER diagram
(10 mark) Poor identification and description of Entities, Attributes and ER diagram Brief identification and description of Entities, Attributes and ER diagram Generally good identification and description of Entities, Attributes and ER diagram Very clear description identification and description of Entities, Attributes and ER diagram Excellent identification and description of Entities, Attributes and ER diagram
Class Diagram (10 mark) Lack of evidence of understanding of Class
Diagram Evidence of basic understanding of Class
Diagram Evidence of good understanding and
identification of Class
Diagram
Very clear understanding and
identification of Class
Diagram Has excellent understanding and
identification of Class
Diagram
Sequence diagram (10 mark) Poor identification and description of Sequence
diagram Brief identification and description of Sequence diagram Generally good identification and description of
Sequence diagram Very clear description identification and description of
Sequence diagram Excellent identification and description of
Sequence diagram
Activity diagram (10 mark) Poor identification and
description of activity diagram Brief identification and description of activity diagram Generally good identification and
description of activity diagram Very clear description identification and
description of activity diagram Excellent identification and
description of activity diagram
Design a data entry screen (10 mark) Poor design of data entry screen Brief design of data entry screen Good design of data entry screen Well design of data entry screen Excellent design of data entry screen
Design a booking appointment input screen (10 mark) Poor design of booking appointment input screen Brief design booking appointment input screen Good design booking appointment input screen Well design of booking appointment input screen Excellent design of booking appointment input screen
Testing and deployment activities
(10 mark) Poor description of
testing and deployment activities Brief identification and description of testing and deployment activities Generally good identification and description of testing
and deployment
activities Very clear description identification and description of testing
and deployment
activities Excellent identification and description of testing
and deployment
activities
Summary
(5 marks) Summary not
relating to the
report Brief summary of the report with some relevance Generally good summary of the report A section clearly summarizing the
overall contribution A section very clearly summarizing the
overall contribution
PRV12007; CRICOS 03048D

References using
Harvard style
(5 marks) Lacks consistency with many errors. Unclear referencing/style Generally good referencing/style Clear referencing/ style Clear styles with excellent source of references.

Assessment 3: Project Design
Due date: Weekly
Group/individual: Individual
Word count / Time provided: N/A
Weighting: 40%
Unit Learning Outcomes: ULO-1, ULO-2, ULO-3, ULO-4, ULO-5, ULO-6
Course Learning Outcomes: CLO-1, CLO-2, CLO-3, CLO-4, CLO-5, CLO-7

Assessment Details:
A project has been developed for the students to work on that throughout the semester. Students will need to do various activities every week and will be required to provide answers and achieve identified outcomes.
Students will not be assessed on work that the tutor has not seen them produce in class so that attendance is required as part of this assessment. Students are required to submit the work that they have completed during the tutorial session.
Project Design: APIC Mobile Application (AMA)
APIC College wants to develop a Mobile Application for their students, along with all the features for e-learning. The App will allow students to access their e-mails, lecture notes, in/after-class activities and many other features. The project requires launching in January 2021.
You have just completed your Bachelor’s studies and got an opportunity to work in this project. You need to produce a design for this application based on the University's requirements.
Task:
• Week1: Develop the six core processes of the SDLC required to develop the project.
• Week2: Explain the responsibilities of the project manager for this project?
• Week3: Write a System Vision Document.
• Week4: a) Create a Work Breakdown Structure that lists all the steps to complete the project. b) Develop PERT/CPM chart explaining the early and late start for each task. Identify the critical path and the total time to finish the project.
• Week5: a) Draw Activity diagram. b) Draw the use case diagram.
• Week6: a) Draw the Class diagram. b) Draw an entity-relationship diagram.
• Week7: a) Complete a fully developed use case description for each scenario. b) Draw the System Sequence diagram (SSD).
• Week8: a) Draw a network diagram that will support this configuration.
• Week9: Design the complete User & System Interfaces for the App.
• Week10: Plan suitable testing and deployment activities.

PRV12007; CRICOS 03048D
Approved: 13/02/2019, Version 1

Marking Criteria and Rubric: The assessment will be marked out of 100 and will be weighted 40% of the total unit mark
Marking Criteria Not satisfactory
(0-49%) of the
criterion mark) Satisfactory
(50-64%) of the criterion mark Good
(65-74%) of the criterion mark Very Good
(75-84%) of the criterion mark Excellent
(85-100%) of the criterion mark
Systems
Development Life Cycle (SDLC) (5 marks) Poorly discussion of the six core processes of the SDLC required developing the project. Brief discussion of the six core processes of the SDLC required developing the project. Good discussion of the six core processes of the SDLC required developing the project. Well discussion of the six core processes of the SDLC required developing the project. Excellent discussion of the six core processes of the SDLC required developing the project.
Project manager responsibilities (5 marks) Poorly discussion of the Project manager responsibilities Brief discussion of the Project manager responsibilities Good discussion of the Project manager responsibilities Well discussion of the Project manager responsibilities Excellent discussion of Project manager responsibilities
System Vision Document (5 marks) Poorly discussion of the System Vision Document Brief discussion of the
System Vision
Document Good discussion of the
System Vision
Document Well discussion of the
System Vision
Document Excellent discussion of
the System Vision Document
Work Breakdown
Structure (WBS)
(7.5 mark) Poor description with no poor table for the project to include the ID, description, and duration for each task. Brief description with brief table for the project to include the ID, description, and duration for each task. Generally good description with good supported table for the project to explain the ID, description, and duration for each task. Very clear description with good supported table for the project to explain the ID, description, and duration for each task. Very good description with very good supported table for the project to explain the ID, description, and duration for each task.
PERT/CPM chart (7.5 mark) Lack of evidence of understanding of PERT/CPM chart with no identification of critical path and the total time to finish the project.
Evidence of basic understanding of PERT/CPM chart with no clear identification of critical path and the total time to finish the project. Evidence of good understanding and identification of
PERT/CPM chart with clear identification of critical path and the total time to finish the project.
Very clear understanding and identification of
PERT/CPM chart with clear identification of critical path and the total time to finish the project. Has excellent understanding and identification of
PERT/CPM chart with clear identification of critical path and the total time to finish the project.
Activity diagram (5 mark) Poor identification and
description of activity diagram Brief identification and description of activity diagram Generally good identification and
description of activity diagram Very clear description identification and
description of activity diagram Excellent identification and
description of activity diagram
Use Case diagram (5 mark) Lack of evidence of understanding of use case diagram Evidence of basic understanding of use case diagram Evidence of good understanding of use case diagram Very clear
understanding of use case diagram Has excellent understanding of use case diagram
Class Diagram (5 mark) Lack of evidence of understanding of Class
Diagram Evidence of basic understanding of Class
Diagram Evidence of good understanding and
identification of Class
Diagram
Very clear understanding and
identification of Class
Diagram Has excellent understanding and
identification of Class
Diagram
Entities, Attributes and ER diagram
(10 mark) Poor identification and description of Entities, Attributes and ER diagram Brief identification and description of Entities, Attributes and ER diagram Generally good identification and description of Entities, Attributes and ER diagram Very clear description identification and description of Entities, Attributes and ER diagram Excellent identification and description of Entities, Attributes and ER diagram
Use Case description (5 marks) Poorly discussion of the use case description Brief discussion of the use case description Good discussion of the use case description Well discussion of the use case description Excellent discussion of the use case description
Sequence diagram (5 mark) Poor identification and description of Sequence
diagram Brief identification and description of Sequence diagram Generally good identification and description of
Sequence diagram Very clear description identification and description of
Sequence diagram Excellent identification and description of
Sequence diagram
PRV12007; CRICOS 03048D
Approved: 13/02/2019, Version 1

Network Diagram (5 mark) Lack of evidence of understanding of Network Diagram
Evidence of basic understanding of Network Diagram Evidence of good understanding and
identification of
Network Diagram
Very clear understanding and
identification of Network Diagram Has excellent understanding and
identification of Network Diagram
User & System Interfaces (20 marks) Lack of evidence of understanding of User &
System Interfaces Evidence of basic understanding of
User & System
Interfaces
Evidence of good understanding and identification of User
& System Interfaces

Very clear understanding and identification of User
& System Interfaces
Has excellent understanding and identification of User
& System Interfaces

Testing and deployment
activities (10 mark) Poor description of testing and deployment activities Brief identification and description of testing and deployment activities Generally good identification and
description of testing and deployment
activities Very clear description identification and
description of testing and deployment
activities Excellent identification and
description of testing and deployment
activities

PRV12007; CRICOS 03048D