包括introduction,功能性非功能性需求等

31269 BRM Spring 2019 Assignment 2
UNIVERSITY OF TECHNOLOGY, SYDNEY
31269 Business Requirements Modelling
Assignment 2 – Object-Oriented Requirements Analysis and Specification Customer Onboarding System (COS)
Due Date: Tuesday, 08 October 2019 at 5:00 PM
Submission:
Each group will submit a softcopy (Document or a PDF) of the group assignment 2 via Turnitin before Tuesday 08/10/2019 5:00 PM AEST. A group leader or representative will submit the assignment on behalf of the whole group. Use the Assessment item 2: Object-Oriented Requirements Analysis and Specification assignment Turnitin link (View/ Complete) on UTS Online for submitting your assignment.
Marks: 18%
Word Limits
There is no compulsory minimum and maximum word limit. The recommended word limit for this assignment is maximum 3000 words excluding diagrams, bibliography and appendices. The word limit will be regarded as recommended rather than compulsory, and no student will be disadvantaged by being under or over the recommended word limit
Group work
The assignment will be done in a group of maximum 6 students enrolled in the same workshop class and the same group as your assignment 1. For the group assessment in this subject, students will be assessed as a team; here each member of the team will receive the same mark for the assignment unless there are issues reported within the group. Students will self-organise themselves in groups. It is not the responsibility of teaching staff to find a group for you; however, they would help you to allocate a group if you have not found group members yet. Once the groups are formed and for any reason(s) you want to change the group, then it is solely your responsibility to make other arrangements and find another alternative group who is willing to accept you. This is a group assignment and you must respect other students in the same group, different groups and teaching staff. If you have any group issues, then you must inform your tutor as soon as possible and well before (at least one week or earlier) the assignment submission or due date.
1

31269 BRM Spring 2019 Assignment 2
Group assignment issues reported either a few days before or after the assignment submission date may not be considered. There will be zero tolerance for any academic and non-academic misconduct. For more details, refer University Rules, read Subject Outline, and read the section on Academic Misconduct provided in this document.
Workload
Each student in a group is expected to allocate and work approx. 10-14.5 hours on this assignment. Each student in a group must take their fair share of the workload, and in the template provided in the Appendix provide details of which tasks/diagrams each student did and when. Where there are problems with the performance of individuals in the group, the subject co-ordinator may choose to introduce peer assessments for the group.
Objectives: (Subject Objectives 2, 3, 4 and 5)
2. Apply modelling and systems analysis techniques that help understand the working of a business system.
3. Document and specify various requirements via Software Requirements Specification (SRS). 4. Develop various models using a range of systems analysis techniques to analyse and specify system and user requirements.
5. Work effectively in a small team.
Task
The assignment will require a group of six students to assess an updated case study on Epic Video and produce an Object-Oriented Requirements Analysis and Specification report for a new and improved system. The report will include UML diagrams and parts of a software requirement specification (SRS) document using the template provided on UTS Online.
The overall marking scheme for the report is as follows:
• Introduction and Document Management (1.0 mark) • Functional Requirements (9.0 marks)
• Data Requirements (4.5 marks)
• Non-Functional Requirements (2.0 marks)
• Contribution to Team Work (0.5 marks)
• Overall Quality of Report Presentation (1.0 mark)
• Total maximum marks: 18
Note: For more details, please see the section on marking scheme.
Criteria
The object-oriented requirements analysis and specification report will be assessed based on the following criteria.
Criteria Items
Objectives
Weight
Marks
Coverage of the system
2
92%
16.5
Correct use of any diagrammatic modelling technique
4
Overall quality of report presentation (e.g. (spelling, grammar, structure, cover sheet, table of contents, bibliography, references and clarity which their diagrams or models convey)
3
5%
1.0
Contribution to team work (evidence) (e.g. succinctness, courtesy, motivation, taking a fair share of the work)
5
3%
0.5
Total
100%
18
2

31269 BRM Spring 2019 Assignment 2
Overview of the Object-Oriented Requirements Analysis and Specification Report
Accompanying these instructions is an updated case study of the Epic Video company and its “Ka-ching” team. This updated case study provides enough information for you to produce an Object-Oriented Requirements Analysis and Specification Report for developing a new and improved Customer Onboarding System (COS). The report will include UML diagrams and parts of a software requirement specification (SRS) document using the template provided on UTS Online.
In the context of developing a new and improved Customer Onboarding System (COS), students are required to capture functional requirements, data requirements and non-functional requirements by using object-oriented specification techniques and UML diagrams. The new COS should address Epic Video’s goals for a better system, as well as any inefficiencies identified in the case study. The COS should be a significant improvement on the current system, described in the Case Study below.
Case Study: Epic Video “Ka-ching” Team – 12 months later.
Epic Video is a new Australian Company that has recently launched into the competitive online video streaming business, and the “Ka-ching” team are responsible for onboarding (signing up) new customers to their video streaming service.
It is 12 months since you last visited the company, and although Epic Video has recently received numerous awards for its quality video streaming service, the CEO and founder Nicola West still has some concerns about the time it takes to onboard new customers, deliver their services to match their expectations and provide a delightful customer experience.
Here is a transcript of a recent interview (new interview, it’s not the same as the one for assignment1) held with Nicola West:
“It’s been an exciting journey over the past 12 months since we last talked, with lots of challenges facing our staff and evolving our relatively small business to be just as competitive with the bigger players in the online video streaming market.
Our main concern at the moment is that currently, it takes 25 calendar days on average to onboard customers (sign-up) from an initial enquiry via telephone registration (expression of interest to sign up), verification of their identity and payment details over the phone, and then delivering appropriate content via online, tablet, mobile and smart TV channels. Other service providers are onboarding customers within 5 to 8 calendar days using online registration, and so we need to bring this time down and offer a similar, if not better service and customer experience than our competitors. I think it’s time we need to develop a new and improved system that is based online, rather than relying so heavily on telephones.
The way I see our business is that we bring the world to the homes of our customers at a time when it suits them, be it for entertainment after a hard working week, getting the inside view of a sporting event, presenting international cinema to stretch the imagination or learning more through our extensive documentary catalogue.
At the moment, during telephone registration, each new customer subscribes to one of 3 monthly billed packages which are organised over the phone: Epic Basix – the basic high definition (HD) streaming package for one device, Epic Lux – the enhanced ultra-high definition (UHD) streaming package for up to 3 devices, and Epic Max – the enhanced
3

31269 BRM Spring 2019 Assignment 2
UHD streaming package for up to 10 devices registered to one household. Organising the registration over the phone is very time-consuming for the “Ka-Ching” team, so moving this process online would go a long way to offering a better service and customer experience.
Right now, a customer can only change or end their subscription at any time by contacting a member of our friendly “Ka-ching” team through email or by leaving a callback contact phone number which we will call back when it is convenient. Our competitors have been offering online chat services, so changing or ending a subscription would be great to do via online chat as well. Even better would be allowing customers to change or end their subscription via an online dashboard instead of contacting us at all.
Each customer registration (register interest to sign up) needs to provide contact details such as name, address and email address, as well as 100 points of identification which are verified offline with a third-party service provider. Customers must also confirm that they are over 18 years of age. Their payment details (credit card or EFT) are also verified through a third-party service provider before a subscription service can be set up. Our third-party service provider has offered to help us integrate online verification of personal and payment details, which would be an essential next step for us.
Also, during telephone registration, there is an option for the customer to “opt-in” to receive marketing and service notifications by post or email. If we move more of our system processes online, then we would like to also offer the option for customers to receive marketing and service notifications via SMS in future.
Speaking of marketing, we have several marketing campaigns that are run throughout the year targeting seasonal peak viewing times such as during national holidays, autumn, winter and sporting events, which normally attract up to 10,000 new customers. We would love the ability to allow customers to redeem a discount code from one of these marketing campaigns and activate it online to receive a three-month promotional discounted price. This would reward customers who have “opted-in” to receive our marketing and service notifications.
I almost forgot to mention – currently, before a subscription (signing-up) is completed, a 12-month agreement contract with the details supplied from the registration process (expression of interest to sign up), payment authorisation and the service terms and conditions are automatically sent out to the customer via email, which the new customer needs to be sign and return to us within 21 calendar days via post or email to complete the sign-up process. Once we receive this, the “Fix-It” team can then set up the connection and welcome them to our online video streaming service and catalogue.
This takes up valuable time for the “Ka-ching” team to coordinate, and we are looking to place this process online. Further, when it comes to billing, customers occasionally provide incorrect payment details, so we would like them to be able to update their payment details (credit card or EFT) through an online dashboard, instead of ringing us.
After a successful set-up of connection, a follow-up telephone call is made to the customer within 14 calendar days to ensure that the new customers know how to get in contact should they have any questions or are having difficulties using the service. If they do have difficulties, then an incident ticket is raised and passed on to the support team aka the “Fix-it” team and they will work to resolve the issue. It would be good to have some of this process online or we are open for any recommendations on how we might improve this process to follow up with the customer.
4

31269 BRM Spring 2019 Assignment 2
If you could help us create a new and improved Customer Onboarding System (COS) by specifying our functional requirements, data requirements and non-functional requirements using object-oriented specification techniques and UML diagrams, that will help us in building an improved system that addresses the issues that I have discussed with you in my interview.”
As a Business Analyst, you and your team have been engaged to understand, analyse and describe/model the future customer onboarding system using user stories, use cases and various OO models. Analyse the above interview with Nicola West and identify the areas of improvement and identify how the existing business processes can be improved to create an improved COS. Please note you should not forget the features/services to be provided to customers, ones that were mentioned in the case study for assignment 1, even though they may not be listed in this updated case study and new interview. So, please do refer both the interviews with Nicola. Once you have identified these improvements, your user stories, use cases and OO models should be based/modelled on these improvements (improved COS).
To develop the new and improved Customer Onboarding System (COS), students should:
• Identify all possible User Stories for the improved COS. You should have at least six user stories. At least two of your user stories should be from the Customer’s perspective, and two user stories from the “Ka-ching” Team’s perspective.
• Develop a User Story Map for the improved COS. You need to estimate and prioritise each user story in the user story map.
• Document/narrate four Use Cases based on four user stories; two user stories from the Customer’s perspective, and two user stories from the “Ka-ching” team’s perspective. You may consult your tutor in selecting these four user stories that need to be expanded/narrated in to use cases.
• Draw two Sequence Diagrams for the improved COS – 1) for any one use case of your choice for a Customer, and 2) for any one use case of your choice for a “Ka-ching” Team.
• Document one Class Diagram for the improved COS covering all your user stories and use
cases (not just the four you have chosen to narrate).
• Document one State Transition Diagram for “Customer” object that covers all user stories
and use case narratives that the Customer participates in (across the entire COS).
• Document two User Interfaces or Wireframes for any two use cases (should be the same
as the ones you choose for the sequence diagrams).
• Document security and performance requirements.
• Include document management, introduction, bibliography, and contribution to teamwork.
Note: For more details, please see the section below on marking scheme.
Marking Scheme and template of submission report:
Use the following marking scheme to prepare and submit your Object-Oriented Analysis and Specification Report documenting a new and improved Customer Onboarding System (COS). A template showing the structure of this submission report is available on UTS Online. Students must use that template. The report should include the following sections:
SECTION
Maximum Marks
Note
Cover Sheet & Title Page
0.25
Signed FEIT declaration of originality cover sheet. Provide student ids and names of all students, and signatures by all students (scan and attach to your assignment). Only one cover sheet is required. Include a title page with the project deliverable title.
5

31269 BRM Spring 2019 Assignment 2
SECTION
Maximum Marks
Note
Table of Contents
0.25
Follow the format and sections expected in the report in correct order (use the template) with page numbers.
1. Document Management
0.25
1.1 Revision History
1.2 Intended Audience
1.3 Reference Documents
1.4 Glossary
2. Introduction
1.25
2.1 Document Purpose
2.2 Project Purpose
2.3 Project Scope
Provide Use Case Diagram as a Project Boundary Diagram showing all your use cases.
2.4 Assumptions
Provide valid and rational assumptions
3. Functional Requirements
9.0
Coverage and Correctness:
Apply user story and UML rules
3.1 User stories and User Story Map
(3.0)
Identify all possible user stories (2.5 marks) for the new and improved Customer Onboarding System (COS).
Please make sure that your user stories (at least six user stories) cover all the features/functionalities of the new improved COS.
– At least two of your user stories should be from the customer’s perspective, and two user stories from the “Ka-ching” team’s perspective.
– Please make sure that your user stories are testable for completion and they use the correct template. Follow the guidelines to write a good user story.
Develop a user story map (0.5 marks) by using the user story map template.
– List all your user stories in this map in correct rows of priority and under correct processes/journeys.
– Estimate and prioritise each user story on the map.
3.2 Use Cases
(4)
Select only four user stories from the user story map (may consult your tutor) – two from the customer’s perspective, and two from the “Ka-ching” team’s perspective.
Detail the selected four user stories in terms of four use cases by using the use case narrative template. – Please make sure that the Main Flow follows the format of actor/user actions and system responses. – You must provide Exceptions for all four use case narratives.
– Each and every alternate flow provided by students (if any) must be detailed in the “Alternate Flow” section. Not all four use cases may have an Alternate Flow, but at least one of the four use cases must have an Alternate Flow.
6

31269 BRM Spring 2019 Assignment 2
SECTION
Maximum Marks
Note
3.3 Sequence Diagrams
(2)
Document two Sequence Diagrams – one for a customer use case, and one for a “Ka-ching” team use case.
Both your diagrams must be drawn at an Object-level showing all the objects (participants) interacting within that use case (and within the COS) instead of just showing one object for the entire system such as COS object.
– Messages in the sequence diagram should match with the main flow of the corresponding use case narrative. These messages should be in a logical sequence and cover the narrative from the start to the end.
– Make sure that the messages start with a verb and sound like a method.
– Make sure that the messages are being sent to correct participants
– Any Alternate flows narrated in your use case narrative must be shown either in the same/original sequence diagram (preferred method) using an Alt frame or shown in a separate sequence diagram.
4. Data Requirements
4.0
Coverage and Correctness:
Apply UML rules
4.1 Class Diagram
2.5
Document one Class Diagram that covers the entire improved COS.
– Identify all the appropriate classes (minimum six). – Identify the correct relationship between these classes and define the multiplicities.
– Identify all the important and necessary attributes for each class in your class diagram. Provide data types for each attribute.
– Identify all the important and necessary methods for each class in your class diagram. Provide return type and parameters for all methods.
4.2 State Transition Diagram
1.5
Draw one State Transition Diagram for the “Customer” object across the whole COS covering all your user stories and use cases.
– State transition diagram must not look like a process flow.
– Show the initial and final states.
– Identify at least five correct states of the Customer object.
– Identify, label and correctly name the Events/Triggers.
– Students must provide at least one alternate flow in this diagram.
5. Non-functional Requirements
2.0
Coverage and Correctness:
Use non-functional requirements rules
5.1 User Interface Requirements
(1)
Document two user interfaces or wireframes for any two use cases of your choice (same as section 3.3).
7

31269 BRM Spring 2019 Assignment 2
SECTION
Maximum Marks
Note
0.5 mark for each user interface (one for the Customer use case and one for the Ka-ching team use case).
– Make sure the user interface/wireframe is linked (matches) to a use case and should be the same as the one that you choose for the sequence diagrams.
5.2 Security Requirements
(0.5)
Document at least two security requirements for the system.
0.25 mark for each correct, valid and sensible security requirement, one for Customer and one for Ka-ching team.
Requirement statements must satisfy the “SMART” requirements quality criteria.
5.3 Performance Requirements
(0.5)
Document at least two performance requirements for the system.
0.25 mark for each correct, valid and sensible performance requirement, one for Customer and one for Ka-ching team.
Requirement statements must satisfy the “SMART” requirements quality criteria.
6. Bibliography
Use correct Harvard referencing style
7. Appendices (Assignment Team Log)
0.5
Contribution to Team Work (Evidence):
1) Keep a record and submit the contribution of each team member to each task. Every team member should work on each task, though the contribution may be different. Contribution should be shown via the Contributions Table, refer and fill the template provided in Appendix.
2) Keep a record and submit the team communication (e.g. emails, meeting minutes, screenshots of online conversations, etc.)
8. Other Aspects related to the Overall Quality of Report Presentation
0.5
Overall Quality of Report Presentation:
Use correct spelling, grammar, structure, clarity, header, footer, page numbers, consistent font, new sections on new pages, presentation of diagrams, bibliography etc.
Total Maximum Marks
18
NOTE: You MUST use Assignment 2 Report template/structure provided on UTS Online.
Assessment Feedback and Return
Before submission, you must regularly get feedback on the assignment tasks and deliverables from your tutor during the workshop sessions. Assignments will be marked within 2 weeks after the assignment due or submission date and marks will be uploaded to Gradebook on UTS Online. Feedback will be provided to students in the workshop after the assignments have been marked.
8

31269 BRM Spring 2019 Assignment 2
Referencing Standards
All material derived from other works must be acknowledged and referenced accordingly using the Harvard Referencing Style (see http://www.bell.uts.edu.au/referencing/harvard_system).
Assessment: faculty procedures and advice
Extensions
When, due to extenuating circumstances, you are unable to submit or present an assessment task on time, please contact your subject coordinator before the assessment task is due to discuss an extension. Extensions may be granted up to a maximum of 5 days (120 hours). In all cases, you should have extensions confirmed in writing.
Special Consideration
If you believe your performance in an assessment item or exam has been adversely affected by circumstances beyond your control, such as a serious illness, loss or bereavement, hardship, trauma, or exceptional employment demands, you may be eligible to apply for Special Consideration.
Late Submission and Penalty
Assignment 2 is due at 5:00 pm on Tuesday, 08th October 2019. Work submitted late without an approved extension is subject to a late penalty of 10 per cent of the total available marks deducted per calendar day that the assessment is overdue. Each 24-hour period after this time is considered to be an extra day late. For example, a submission at 5:01 pm on Tuesday, 08th October is considered 1 day late, while a submission at 5:01 pm on Wednesday, 09th October is considered 2 days late. Work submitted after five calendar days is not accepted and a mark of zero is awarded.
Special Needs:
Students should email the subject coordinator as soon as possible (and prior to the assessment deadline) to make them aware of the impact on them meeting assessment component/requirements, and that they are seeking assistance through UTS Special Needs as detailed in Section 5.1.3 of Procedures for the Assessment of Coursework Subjects.
Academic Misconduct:
Students are reminded of the principles laid down in the “Statement of Good Practice and Ethics in Informal Assessment” (pages 5 & 6 of the Faculty Handbook). Unless otherwise stated in a specific handout, all assessment tasks in this subject should be your own original work. Any collaboration with another student (or group) should be limited to those matters described in “Acceptable Behaviour” section of the Handbook. For essay questions, students should pay particular attention to the recognition of “Plagiarism” as described in that section of the Handbook (page 6). Any infringement by a student will be considered a breach of discipline and will be dealt with in accordance with Rules and By-Laws of the University. Posting your assignment on the web and getting help through blogs, forums or other websites may lead to academic misconduct. Penalties such as zero marks for assignment or subject may be imposed.
Please also see the subject outline in conjunction with UTS policy and procedures for the assessment for coursework subjects, available at: www.gsu.uts.edu.au/policies/assessment-coursework.html
9

31269 BRM Spring 2019 Assignment 2
Querying Marks/Grades and Final Results
If a student disagrees with a mark or a final result awarded by a marker:
• where a student wishes to query a mark, the deadline for a query during teaching weeks is
10 working days from the date of the return of the task to the student More information can be found at: https://my.feit.uts.edu.au/pages/course/student_policies_rules
ELSSA
If you think you need help with your English for this subject, contact the English Language Study Skills Assistance (ELSSA centre) level 18, Tower building, Broadway, phone: 9514 2327.
APPENDIX
Each student in a group must take their fair share of the workload and in the Contributions Table provided below, provide details of which tasks/diagrams each student did and when. Diagrams must be prepared as a group rather than distributing diagram/s among the group members. Groups that distribute the diagrams among the group members may lose marks.
In the contributions table below, each group must provide their individual contribution to each task. Write a detailed description of what exactly you did for each task. Below are some (not all) examples of the kind of details you need to provide as a bare minimum:
• What was your contribution in the User Stories and User Story Map? Which user stories did you write and when? Was user story map done as a group or as an individual?
• What was your contribution in the Use Case Narratives? Which use case narratives did you write and when?
• What was your contribution in Sequence Diagrams and when?
• What was your contribution in Class Diagram and when was it drawn? Was class
diagram done as a group or as an individual? How and when were the classes identified?
• State Transition Diagram: What exactly did you do and when?
• Assumptions, recommendations
Each group member must check this contributions table before submitting the assignment as it will be used in the event of problem/s within the group and for distribution of marks among the group members. Each student must make sure that the tasks that they did are listed under their name.
Apart from the above contribution table, submit the team communication (e.g. emails, meeting minutes, screenshots of online conversations, etc.)
Contributions Table
Contributor:
Contribution(s): (Tasks/Sections/
Diagrams)
Student A (Name and ID)
Provide details and evidence of which tasks/diagrams did you complete, and what exactly you did in those tasks and when.
Be as detailed as possible.
10

31269 BRM Spring 2019 Assignment 2
Student B (Name and ID)
Provide details and evidence of which tasks/diagrams did you complete, and what exactly you did in those tasks and when.
Be as detailed as possible.
Student C (Name and ID)
Provide details and evidence of which tasks/diagrams did you complete, and what exactly you did in those tasks and when.
Be as detailed as possible.
Student D (Name and ID)
Provide details and evidence of which tasks/diagrams did you complete, and what exactly you did in those tasks and when.
Be as detailed as possible.
Student E (Name and ID)
Provide details and evidence of which tasks/diagrams did you complete, and what exactly you did in those tasks and when.
Be as detailed as possible.
Student F (Name and ID)
Provide details and evidence of which tasks/diagrams did you complete, and what exactly you did in those tasks and when.
Be as detailed as possible.
Note: Based on the contributions detailed above for each student, your marker may distribute the marks unequally even if the group member/s have not reported any group contribution issues. The above contributions table may be used for peer assessments and hence marks may be unequally distributed among the group members.
11