FIT9130 Systems Analysis and Design Assignment 1, Semester 2 | MU

1. FIT9130 Assignment Overview

In this assignment, you will produce a Systems Analysis specification (requirements specification) report for the case described in Section 9 using several UML analysis techniques. Note that this is a group assessment.

The assessment consists of three main segments:

1. an analysis specification report containing the narrative overview (including all requirements of the systems);

2. the analysis component, which includes the diagrams that represent the narrative;

3. An interview conducted by the tutor based on the analysis specification you submit.

The purpose of the assignment is to simulate a proper systems development consulting project where you, as the systems analyst, will need to identify and elicit user requirements. In addition to the included case text in Section 9, you can do further requirements gathering of business processes such as user registration, record a task entry (including text-based diary entries), social interaction, and generate reports during weekly consultation sessions with your tutor or through email communications.

2. FIT9130 Assignment Due Dates

Systems Analysis specification – 11.55 pm Sunday, Week 8 (15 September 2024)

Interviews – Based on the interview schedule given to you by your tutor. The interviews will be scheduled to take place in week 9.

3. FIT9130 Assignment Value

• 25% of your overall grade for FIT9130.

4. FIT9130 Learning Objectives 

Successful completion of this assignment will lead to knowledge of and skills in:

• techniques for functional analysis of a business problem;
• communicating an understanding of a business problem, as well as a proposed solution to a non-technical audience;
• the purpose of, and techniques used to develop, requirements specification for an information system;
• requirements modelling of data and processes using the following techniques:
   
  a. Use Case Diagrams
  b. A fully developed use case description
  c. Domain Class Diagrams
  d. Activity Diagrams
  e. System Sequence Diagrams

The assignment assesses your understanding of materials covered in Weeks 1-6.

5. FIT9130 Deliverables

The assignment has one deliverable, which is the analysis specification report, and this is assessed in the interview. For the interview, you do not require uploading anything; this is a question-and-answer session with the tutor to assess your knowledge about the specification report you uploaded on Moodle. You will submit a complete analysis specification report containing:

1. The narrative overview - 20 Marks (A sample format is available in Section 10).
2. Requirements - 20 Marks
3. The following analysis models:

a. a single complete Use Case diagram for the functional areas listed in the case which should include some <<include>> and <<extend>> scenarios when they are needed. - 15 Marks.

i. Ensure that you include a use case called “Lesson Booking Confirmation”
b. A fully developed use case description/narrative related to “Lesson Booking Confirmation .” - 10 Marks.
c. a single complete Domain Class Diagram for the functional areas listed in the case - 15 Marks.
d. an activity diagram for the use case “Lesson Booking Confirmation ” - 10 Marks.
e. A system sequence diagram for the activity diagram above in section d - 10 Marks.

The narrative overview should outline your understanding of the business problem based on the case material provided below. It should also give some idea of the proposed solution. The narrative overview should not just paraphrase the case study document. Furthermore, the narrative overview needs to establish your understanding of the scope and nature of the problem to be solved, as well as any other information necessary for the client to understand the proposed solution.

6. FIT9130 Assessment Criteria

1. Completed design specification report

1. Narrative overview:
a. Completeness of discussion of project background
b. Completeness of understanding of the scope and nature of the analysis process

2. Diagrams:

a. Quality of the analysis solution and support for the business requirements
 b. Correctness of execution of diagramming technique

3. Quality and professionalism of presentation, including layout, structure and grammar

A detailed marking criteria is available in the Assignments section on Moodle.

2. Interview

You are required to attend an interview in week 9 to explain the models to your tutors depending on your scheduled time.

7. Submission

One student from each group is required to submit an electronic copy of their submission on Moodle. The submission link is Turnitin-enabled. Please read the details given in Sub Section 3 below carefully before you submit the assessment online. Submissions must be in either Microsoft Word or PDF format.

1. Penalty for Late Submission

Late submissions without an approved extension will be subject to a penalty of 10% per day. Weekends count as a single day. No submission will be accepted more than one week late.

2. Turnitin

Turnitin is an online tool to assist students and staff in understanding and supporting the ethical and appropriate use of materials. Students are required to submit an electronic version (in .doc format and WITHOUT the cover page) of each submission through the Moodle site of this unit.

Turnitin generates the initial originality report quickly. However, if you resubmit your assignment for analysis, there will be a 24-hour delay before a new report is generated.

You are permitted multiple submissions to Turnitin until the due date of the relevant assignment. You may want to make improvements based on the report and resubmit it through the same Turnitin submission link. Each submission will overwrite the previous submission, and only the last submission/originality report will be viewed.

8. Plagiarism and Collusion

While general collaboration between students in terms of understanding of modelling concepts is acceptable, the assignment and the solution contained in it must be entirely your group’s work.

You must not:

• Use another student’s work as the basis for your own.
• Use another student’s work to help ‘give you ideas.’
• Steal, appropriate or make use of the work of another student without their knowledge.
• Lend your work to another student for any reason.
• Borrow work from another student for any reason
• Use the ideas, words or other intellectual property of anyone without proper attribution.
• Leave your work unattended on the student laboratory computers or give your authentication details to anyone.

Penalties for plagiarism and/or collusion can include formal reprimands, notes being attached to your student file, failure in the assignment, failure in the unit or even suspension or exclusion from the university.

See the Unit Guide for more information on plagiarism and cheating, and for links to Faculty and University policies on this topic.

9. The Case: Melbourne Yoga Centre (MYC)

A yoga centre, known as “Melbourne Yoga Centre (MYC) is run by Mr Peter Weber. Peter has provided the following brief information on the system he would like your team to build for use by his office staff, clients, and himself:

Our centre offers yoga classes for adults. In addition, we sell yoga instruments to our clients. We are looking into offering group classes as well. Our teachers are enthusiastic with considerable yoga experience. The teaching side of our business, involving teaching various types of yoga techniques such as yoga for anxiety, yoga for weight loss, yoga for beginners, etc. is gradually growing, and our current manual systems are not coping. We would like your team to develop a website to promote our business, and enable prospective clients to use our website for searching suitable yoga teachers around Melbourne based on a range of criteria. Once they find a teacher of their choice, they should be able to view all the relevant information about the teacher, and then send us a yoga lesson booking request if they want to start regular lessons.

At the moment, when our clients inquire (through phone or email), we then email them a .pdf file of all the teachers for the particular yoga technique they are enquiring about.

We also want all our teachers to be able to update all their information online once they are registered with us. Described below are the key functions we would like to have.

Function 1: A website

We would like a website to promote our business, with a ‘Contact Us’ and a ‘Testimonials’ page, so that clients can see testimonials for all the teachers. Clients should also be able to ‘Find a teacher’ from the website, and we would also like clients and teachers to be able to log in to see teachers’ information.

Function 2: Find a teacher

We want prospective clients to be able to search for suitable teachers around Melbourne based on a range of criteria. These criteria include:

• the yoga technique they want to learn
• the distance they are willing to travel from their home address – we do this in 5 km increments, eg, 0-5, 0-10, 0-15, etc.
• our teachers’ lesson cost rate (they should have a range that they can select from).

Once prospective clients put in their criteria, we would like them to see a list of yoga teachers that match their criteria. They can then choose a yoga teacher and see all the information
 
about that teacher. We basically want them to see most of the information that is on the Teacher Registration Form, plus all their testimonials and their regular availability. The availability does change from week to week as students are sometimes absent, and they also swap around. However, the availability we want prospective clients to see is our teachers’ availability for regular lessons. It would be good if it could be shown in a timetable grid format.

Function 3: Lesson Booking Request

When the prospective clients find a yoga teacher they like, we want them to be able to send a lesson booking request to us via the website. It should include:

• The teacher's information that they are requesting
• the regular day/time slot they are requesting
• the client details

Our clients can also request a single lesson. As soon as the request is sent to us by a client, the time slot should show as ‘tentatively booked’ on the teacher’s information, so that it is not misleading for other prospective clients. The system should send an automatic email reply to that client with a reference number. That email should let the client know that we will contact him/her in the next five days. The reference number can be just a sequential number. Our clients can use either the reference number or just their name when they want to follow up on their request. Currently, when clients enquire, we email them a .pdf file of all the teachers they are enquiring about.

Function 4: Lesson Booking confirmation

Once we receive a booking request, we want to contact the teacher to check if he/she is willing to take on the new booking (regular or a single). We would love this to be done automatically, and then reminders sent to us when the teacher has responded, or if the teacher has not responded, so that we can follow up. When the teacher says no, we then advise him/ her to update his/her availability so it is actually correct. After that, we need to contact the client to let him/her know that, unfortunately, the teacher is unavailable. The client is advised to choose another time slot for that teacher.

However, when the teacher does say yes, then we send a confirmation email to the client requesting the admin payment of A$50 (for regular bookings) or $25 (for a single booking) online or via the phone. This is our commission for organising the lesson. There are 10% discounts for family members or if the same client has booked lessons for different yoga techniques. The client can pay using a credit card only. Once a client has made the admin payment, and the lesson is confirmed with the teacher, the client can download their payment confirmation receipt (as a pdf) with his/her lesson details.

The teacher’s availability is also updated with the confirmed lesson date and time. If the client does not pay within 5 days, we contact him/her by phone to confirm whether he/she is going to start the lessons. We do this every 5 days up to 3 times, and then cancel the booking request if the payment is not made. When the request is cancelled, we also want to remove the tentative booking from the availability. For single lesson booking requests, we just give the teacher the client’s contact details once they have paid the admin fee. The teacher then contacts the client to organise the single lesson.

Function 5: Manage Teacher Information

Our registration process is very strict. Whenever anyone enquires to be a yoga teacher at our centre, the first thing he/she has to do is complete the Teacher Registration Form (see attached). The prospective teacher is then required to come to our office for an interview with us. When he/she is successful at the interview, we do all the required reference and qualification checks. We would like your team to help us better manage this registration approval process and give us reminders, so that we know where we are up to with the process. We receive plenty of enquiries from many prospective teachers, and it would make it a lot easier if we could manage it all online.

Once we have approved a teacher, we let him/her know. In the new system, we would like a standard email that we can send to him/her, and we would like to give him/her a login ID and password. Our approved teachers can use the new system to view their details and update their availability for lessons. However, if they want to update any other details, they need to put in a request to us, as we are required to check/approve any updated information before it can appear on the website. When a teacher no longer wants to be a part of our business, he/she contact us and we archive his/her details, as we still want a record that he/ she was a part of our business in the past, and he/she sometimes do re-join at a later date.

The teacher needs to record all the actual lessons that have taken place, so we have a complete record of all lessons for Central Admin. Teachers also need to perform the following activities:

A teacher should be able to see what classes he/she has booked for any given time period
A teacher should be able to send a message to any individual student or all his/her students, possibly using an email template.

10. The Narrative Overview(20 Marks) Sample Format(Refer to the Marking Guide for detailed Marking)

Executive summary

This section should:

a. Describe the purpose of this document;
b. Specify the intended readership of this document.

Background about the client

This section should include information about the company. Not the project.
Who are the customers, Stakeholders (using the Stakeholders Matrix)
 
Business scenario

The problems or the opportunities of the company that have led them to come up with a new solution. The section should focus on the problems or the opportunities, not the product to be designed

Scope

• identify the products to be produced;
• explain what the proposed system will do (and will not do, if necessary);
• define relevant benefits, objectives and goals as precisely as possible;
• define any security risks associated with the system;
• be consistent with similar statements in higher-level specifications, if they exist.

Key business requirements – 20 Marks

• If you search on Google for detailed software requirement specifications and go to the business requirement section, you will see how different systems analysts have depicted this. Further, you must have 2 separate sections for functional requirements and non-functional requirements.
• constraints and limitations on the design
• assumptions made