SBM4201 Systems Analysis and Design
APIC Asia Pacific International college
Assessment Overview
Assessment Task |
Weighting |
Due |
Length |
ULO |
Assessment 1: Quiz 30 minutes test comprising of multiple-choice questions |
10% |
Week 4 |
30 mins |
ULO1 |
Assessment 2: Case Study -1 Covers the following topics Systems Development Life Cycle (SDLC), Work Breakdown Structure (WBS), PERT/CPM chart, NPV, ROI, payback period and use case diagram |
20% |
Week 6 |
2000 words |
ULO1 ULO2 ULO3 |
Assessment 3: 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 |
30% |
Week 9 |
2000 words |
ULO1 ULO2 ULO3 ULO4 |
Assessment 4: Tutorial Participation and Submission Weekly exercises assess students’ ability to understand theoretical materials |
10% |
Week 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 |
N/A |
ULO1 ULO2 ULO3 ULO4 ULO5 |
Assessment 5: Proposal It covers user and system interfaces, and system testing, deployment and maintenance |
30% |
Week 12 |
2000 words |
ULO4 ULO5 |
Assessment 1: Quiz
Due date: |
Week 4 |
Group/individual: |
Individual |
Word count / Time provided: |
30 minutes |
Weighting: |
10% |
Unit Learning Outcomes: |
ULO-1 |
Assessment Details:
This online quiz will assess your knowledge of key content areas (Week 1, 2 and 3 contents) and to identify further support needs. For successful completion of the quiz, you are required to study the material provided (lecture slides, tutorials, and reading materials), engage in the unit’s activities, and in the discussion forums. The prescribed textbook is the main reference along with the recommended reading material. By completing this assessment successfully, you will be able to identify key aspects of system analysis and design including system vision, work-breakdown structure (WBS), SDLC, methodology, approaches to software development.
The quiz will be completed online through the APIC Online Learning System (CANVAS).
Marking Information: The quiz will be marked out of 100 and will be weighted 10% of the total unit mark.
Assessment 2: Case Study-1
Due date: |
Week 6 |
Group/individual: |
Individual |
Word count / Time provided: |
2000 words |
Weighting: |
20% |
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 Gold- Cinema (GC) case study provided at the case study section.
Task:
You have to read the Gold- Cinema (GC) case study below and write a report to answer the followings:
- 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 GC project.
- Develop a Work Breakdown Structure (WBS) description supported with a table for the GC project explaining the ID, description, and duration for each task.
- 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.
- 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 $15,000. Do a five-year return on investment.
- Develop a use case diagram which models the actors in GC system.
You may need to make some assumption as required. Whenever you make assumptions, please state these clearly.
Case Study: Gold-Cinema System (GCS)
The Gold- Cinema is a ticket office that would like to develop the online system for keeping the track of customers, productions, performances, and seats. The Gold- Cinema intends to keep the track of their customers in a way that they can notify their customers about upcoming events, and identify those who frequently support the Cinema. For this purpose, customers require to create an account prior to booking any thicket for the first time. 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 with any issues for creating account or booking a ticket, 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 support customer for each time.
Regarding productions, the new online system keeps the information in terms of name and type of the productions such as movie, play or concert. Regarding performance, the number of tickets sold and the date of performance are specifically recorded.
The management of the cinema wishes to operate an entirely testable procedure to the whole online system in order to discover any bug and major issues prior to the final launch of the system.
The company 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 |
$ 9,000.00 |
$ 9,000.00 |
$ 9,000.00 |
$ 9,000.00 |
$ 9,000.00 | |
2 |
Development Cost |
-$15,000.00 |
-$700.00 |
- $850.00 |
-$770.00 |
-$750.00 |
-$730.00 |
3 |
Annual expenses |
-$ 3,000.00 |
-$ 3,000.00 |
-$ 3,000.00 |
-$ 3,000.00 |
-$ 3,000.00 | |
4 |
Net benefit/costs |
-$15,000.00 | |||||
5 |
Discount factor |
1.00 | |||||
6 |
Net present value |
-$15,000.00 | |||||
7 |
Cumulative NPV |
-$15,000.00 |
Marking Criteria and Rubric:The assessment will be marked out of 100 and will be weighted 20% 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 |
Systems Development Life Cycle (SDLC) (20 marks) |
Poorly discussion of the six core processes of the SDLC required developing the GC project. |
Brief discussion of the six core processes of the SDLC required developing the GC project. |
Good discussion of the six core processes of the SDLC required developing the GC project. |
Well discussion of the six core processes of the SDLC required developing the GC project. |
Excellent discussion of the six core processes of the SDLC required developing the GC project. |
Work Breakdown Structure (WBS) (15 mark) |
Poor description with no poor table for the GC project to include the ID, description, and duration for each task. |
Brief description with brief table for the GC project to include the ID, description, and duration for each task. |
Generally good description with good supported table for the GC project to explain the ID, description, and duration for each task. |
Very clear description with good supported table for the GC project to explain the ID, description, and duration for each task. |
Very good description with very good supported table for the GC project to explain the ID, description, and duration for each task. |
PERT/CPM chart (15 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 (15 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 |
Use Case Diagram (20 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 |
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. |
Assessment 3: Case Study-2
Due date: |
Week 9 |
Group/individual: |
Individual |
Word count / Time provided: |
2000 |
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 student 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: Online System for Kangaroo Taxi
Kangaroo Taxi is a new company in Australia, offering online-booking services for their users. Kangaroo Taxi is about to launch an easy-to-use website allowing its users to access from smart phones. The website will enable the users to plan and book their trip. Upon the first use, users would be able to enter their details into the system including their means of payments (e.g., credit card, PayPal, etc.). This will allow the users to use the Kangaroo Taxi in any subsequent bookings as well. Users can simply login to their registered accounts and make a booking for a taxi. What is needed is to enter their trip’s origin and destination. The system will provide them with an estimated cost according to the trip information.
Suppose you are asked to develop this online system for Kangaroo Taxi. You have been given only three weeks to come up with a blueprint of the system design. You will be presenting your design to a team of consultants. The online system should be able to perform a number of activities such as adding or creating a new user, checking for available taxis and drivers in the area requested by the customer, calculating cost of trip, issuing online ticket or receipt and processing all bookings transactions. You may add any other possible functions that you deem necessary for this system to function in this business case. Task:
- Draw use case description for registering accounts and making a booking.
- 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
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 |
Case description (10 marks) |
Poorly discussion of the case description |
Brief discussion of the case description |
Good discussion of the case description |
Well discussion of the case description |
Excellent discussion of the 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 (20 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 (15 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 (15 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 (15 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 |
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. |
Assessment 4: Tutorial Participation and Submission
Due date: |
Week 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 |
Group/individual: |
Individual |
Word count / Time provided: |
N/A |
Weighting: |
10% |
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:
Different exercises assess students’ ability to understand theoretical materials on a weekly basis. Students will be given simple activities each 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. The details of the tutorial work and requirements are provided on the online learning system.
Marking Criteria and Rubric:The assessment will be marked out of 100 and will be weighted 10% of the total unit mark
Marking Criteria |
Not satisfactory (0-4) mark |
Satisfactory (5-8) mark |
Excellent (9-10) mark |
Week-1 (marked 0 - 10) (10%) |
Attendance and no submission |
Attendance and satisfactory submission |
Attendance and excellent submission |
Week-2 (marked 0 - 10) (10%) |
Attendance and no submission |
Attendance and satisfactory submission |
Attendance and excellent submission |
Week-3 (marked 0 - 10) (10%) |
Attendance and no submission |
Attendance and satisfactory submission |
Attendance and excellent submission |
Week-4 (marked 0 - 10) (10%) |
submission |
satisfactory submission |
excellent submission |
Week-5 (marked 0 - 10) (10%) |
Attendance and no submission |
Attendance and satisfactory submission |
Attendance and excellent submission |
Week-6 (marked 0 - 10) (10%) |
Attendance and no submission |
Attendance and satisfactory submission |
Attendance and excellent submission |
Week-7 (marked 0 - 10) (10%) |
Attendance and no submission |
Attendance and satisfactory submission |
Attendance and excellent submission |
Week-8 (marked 0 - 10) (10%) |
Attendance and no submission |
Attendance and satisfactory submission |
Attendance and excellent submission |
Week-9 (marked 0 - 10) (10%) |
Attendance and no 8 submission |
Attendance and satisfactory submission |
Attendance and excellent submission |
Week-10 (marked 0 - 10) (10%) |
Attendance and no submission |
Attendance and satisfactory submission |
Attendance and excellent submission |
Assessment 5: Report
Due date: |
Week 12 |
Group/individual: |
Individual |
Word count / Time provided: |
2000 |
Weighting: |
30% |
Unit Learning Outcomes: |
ULO-4 ULO-5 |
Assessment Details:
The Proposal assessment covers the following topics: information system development, system development approaches, user and system interfaces, and system testing, deployment and maintenance.
Proposal: Design for Library website in your local area
Your local’s Library has hired you to design two online data entry screens. Visit various library websites and based on what you know and gather about the operation of a library services, submit your proposal while including the following questions:
Task:
- Design a monthly operations summary report that will comprise overall data on student ID, loans, late charges, requests and anything else you think a library staff might want to review. Be sure to include numeric activity and dollar totals.
- Design a data entry screen for entering Personal Details.
- Design a book loan input screen. In addition to the book data, the book loan form must include the following fields: Student Number, Name, and Date.
- Plan the 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 |
Case description (5 marks) |
Poorly discussion of the case description |
Brief discussion of the case description |
Good discussion of the case description |
Well discussion of the case description |
Excellent discussion of the case description |
Design a monthly operations summary report (20 mark) |
Poor design of summary report |
Brief design of summary report |
Good design of summary report |
Well design of summary report |
Excellent design of summary report |
Design a data entry screen (20 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 book loan input screen (20 mark) |
Poor design of book loan input screen |
Brief design of book loan input screen |
Good design of book loan input screen |
Well design of book loan input screen |
Excellent design of book loan input screen |
Testing and deployment activities (20 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 |
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. |