<< EXPLAIN THE PURPOSE OF THIS REPORT (IN THE SYSTEM DEVELOPMENT/INDUSTRY CONTEXT, NOT IN TERMS OF YOUR LEARNING). YOU NEED TO PROVIDE AN OVERVIEW AND PURPOSE OF REQUIREMENTS ANALYSIS, AND OF ITS STAGES (BOTH REQUIREMENTS GATHERING AND SPECIFICATION).>> 

 
2       System Stakeholders  Han

 << LIST AS MANY SYSTEM STAKEHOLDERS AS YOU CAN IDENTIFY. EXPLAIN BRIEFLY (1 SENTENCE IS ENOUGH) WHY SUCH A LIST WOULD BE IMPORTANT IN CREATING A REQUIREMENTS SPECIFICATION REPORT SUCH AS THIS ONE.>> 

 

 3       Requirements Gathering Methods Han

<<DESCRIBE IN DETAIL METHODS THAT YOU USED TO ELICIT THE SYSTEM’S REQUIREMENTS, AND EXPLAIN WHY YOU USED THESE METHODS (USE AT LEAST 4 SOURCES/ARTICLES ABOUT THE METHODS TO SUPPORT THIS SECTION, with in-text referencing). YOU NEED TO USE AT LEAST 2 DIFFERENT REQUIREMENTS GATHERING METHODS.>> 

  

 4.1     Functional Requirements Wu

 << LIST AT LEAST [N x 4] FUNCTIONAL REQUIREMENTS FOR THE SYSTEM. AT LEAST [N X 2] OF THEM MUST BE NEW, PROPOSED BY YOU, AND NOT DERIVED FROM THE EXISTING SYSTEM (MAKE SURE TO MARK THEM AS NEW). YOU NEED TO DISCOVER THE [N] NEW REQUIREMENTS ON YOUR OWN, USING AT LEAST 2 DIFFERENT REQUIREMENTS GATHERING METHODS (SEE SECTION 3).>> 

 

4.2     Non-functional Requirements  Wu
<< LIST OF AT LEAST [N x 3] NON-FUNCTIONAL REQUIREMENTS. NOTE THAT IN REAL-LIFE SITUATIONS, EXTENSIVE REQUIREMENTS GATHERING INVOLVING NUMEROUS STAKEHOLDERS WOULD BE UNDERTAKEN IN ORDER TO ARRIVE AT SUCH A LIST. HERE, THE REQUIREMENTS CAN BE DERIVED FROM THE EXISTING SYSTEM OR FROM YOUR REQUIREMENTS GATHERING METHODS. YOU CAN ALSO MAKE ASSUMPTIONS AS LONG AS THEY ARE REASONABLE.>> 

 

 <<DRAW A DETAILED ENTITY RELATIONSHIP DIAGRAM FOR THE PROPOSED SYSTEM THAT SHOWS [Nx3] SYSTEM ENTITIES WITH ATTRIBUTES, AND THEIR RELATIONSHIPS AND CARDINALITIES.>> 

  

 <<DRAW ONE USE CASE DIAGRAM FOR THE PROPOSED SYSTEM. IT MUST CONTAIN AT LEAST [N x 3] USE CASES, 2 ACTORS, 1 ‘INCLUDE’ AND 1 ‘EXTEND’ RELATIONSHIP. AT LEAST [N] USE CASES NEED TO BE BASED ON SOME OF NEW REQUIREMENTS THAT YOU PROPOSED IN SECTION 4.1. (MAKE SURE TO MARK THEM AS NEW). >> 

  

 << WRITE USE CASE DESCRIPTIONS FOR [N] USE CASES MODELLED IN SECTION 6. YOU ARE ENCOURAGED TO USE THE USE CASE DESCRIPTION TEMPLATE FROM WEEK 3 TO ENSURE THAT YOU COVER ALL THE REQUIRED ELEMENTS.>> 

UTS library system shall have ability to find the status of books by title.

UTS library system shall have ability to let users book books.

UTS library system shall have ability to let users book meeting rooms.

UTS library system shall have ability to let users find the history of borrowing books.

UTS library system shall have ability to let users log in by use their id and password.

 

Non-functional requirement of UTS library system

UTS library system shall ensure only users can log in to their account.

UTS library system shall ensure their users can log in to their account and using the system 24 hours a day.

UTS library system shall ensure that users can use multiple languages in the system.

UTS library system shall ensure different types of member have different functions and accessibilities.

UTS library system shall ensure that users can bind mobile phone numbers to their account to improve security,

 

The purpose of this report is to find the user requirement for the OPAL ticketing system. This is the first and very important step in building this system. If you make a mistake in this step, it will lead to very serious consequences. For example, if you have a system that does not meet the needs of the user, this will cause the system to waste time and money and not have the role he should have, so meeting user needs is very important for making a new system.This article will be divided into System Stakeholders, Requirements Gathering Methods, Functional and Non-functional Requirements, Entity Relationship Diagram, Use Case Diagram and Use Cases Descriptions. In the System Stakeholders section, you will list the people or groups that have an interest in the Opal ticketing system and explain why these stakeholders are an important part of this report. Requirements Gathering will explain the two different approaches used to gather information on system requirements for this report and why these two different approaches are used. Functional and Non-functional Requirements will be divided into Functional Requirements and Non-functional Requirements. In the Functional Requirements section, you need to develop a new list of functional requirements from the Requirements Gathering section. In the Non-functional requirements section, you can use a part of the non-functional requirements of the existing system, or you can use the requirements derived from the assumptions under reasonable circumstances to make a list. The Entity Relationship Diagram section draws an entity relationship diagram for the Opal ticketing system to show in detail the properties of the system and the relationship between these attributes and the cardinality. In the Use Case Diagram section after this, our team will draw a case diagram of the system based on the new requirements presented in Functional Requirements.
 
 Stakeholder list

 
 System development companies

 

Chip development companies

 

Website development companies
 
 

Phone application development companies
 
 

Top up machines development companies
 
 

Internet provider
 
 

Bank Owner

 

Governments

 

Stores

 

Train staff

 

Passenger
 
 

train stations

 

The stakeholder can be defined as any person who will be affected or associated directly and indirectly by Opal system. The stakeholder list is extremely crucial because in this list it is possible to visualize which groups are closely related to the system, which will make the scope of the survey population more precise.

 

After the group discussion, we decided to use survey and competitors’ systems analysis to obtain Opal ticking system user requirement. The reason why choosing those methods is that they have many advantages. 

 

The online survey can overcome geographical restrictions by sending questions to the user’s email or social media which also can expand the survey audience significantly (DeFranzo 2012). In addition, Vannette 2015 states that an online survey is quite flexible and convenient because the interviewer is able to change the questions easily and retrieve the results directly. However, the online survey also has some limitations. For instance, respondents could feel annoying when they receive the survey. As a result, the answer that respondents provided may inaccurate or incomplete. Also, most of the questions in the survey are closed which means that respondent’s specific experience could be overlooked (Smith 2013). Therefore, before we set up the survey question we have researched various survey advises on the internet that are really useful and helpful to build an effective survey. For example, the first advice is that clearly define the purpose of our online survey (Johnson 2018). The goal of this survey is to find Opal ticketing system user requirements and system deficiencies. Consequently, the background information of users is not a crucial part of this survey. For example, the respondent’s occupation, gender, and age would not be asked in this survey because they can all be divided into passengers. It can truly help us to avoid unnecessary questions. Moreover, Johnson 2018 states that the questions of the survey should be short and simple. The statistic shows that shorter surveys generally have more respondents because nobody wants to spend 30 minutes to answer a survey which can be time-consuming. As a result, the questions of the survey were built as simple as possible and only ask only one question at a time. Another advice stated by Johnson 2018 is that the survey should not only contain closed-ended questions but also include open-ended questions. Closed-ended questions only provide specific choices like Yes or No, making it easier to analyze. By the contrast, Open-ended questions are excellent supplemental questions which can offer additional information and experience of users. Combining these two different types of questions can help us get better results. Using a Google survey to create a survey is a great approach because of free and flexible. It can be modified in anytime. Our survey contains 9 questions that all follow the advises above. Also, it already captured 46 respondents when this report has been finished. 

 

The second method using to gather user requirement is competitors’ systems analysis. This method throughs comparing different countries’ transportation ticketing system to identify the disadvantage and advantage of opal ticketing system. Currently, we are living the information age, existing technology could be replaced quickly. According to internet research, we have found that Wechat pay is available using in public transportation system in some Chinese’s cities. Brennan 2017 states that the system works through WeChat's internal program called ‘Tencent Ride Code’ which is kind of QR code. In addition, opening the QR code will only cost 0.2 seconds and it even not needs to access the internet in cellphone which makes sure passengers are able to take public transportation when they have no internet service(BRENNAN 2017). By scanning WeChat QR code to replace the physical card is quite convenient because it can avoid losing the physical card and insufficient balance on the card. Moreover, Wechat pay not only can use in daily transportation like subway, bus, and public bike but also can use check-in at the airport and a high-speed train in China. Tencent is not the only one company to develop in this direction. Another company named Alipay has similar functions for public transport services. It uses NFC functions to make a connection with transport ticketing system in their own mobile phone payment application. That means, passengers only need to scan their smartphone to ride public transport and no longer need to buy a ticket or top-up their physical card. It can save passenger’s time significantly without line up in front of the top-up machine.

To sum up, providing users with better and more convenient services is the final goal of the system. China is currently leading in this area. Opal ticketing system needs to join this rank to improve its performance and functionality.



8.Survey results summary

When finished this report, the survey has received a total of 46 responses which meet the assignment criteria. Results of the first question clearly show that the majority of respondents can accept Opal ticket system’s performance reached 52.2 percentages. However, about 70 percentages of respondents have encountered issues when they used the Opal system. There are 4 main problems that are mentioned most frequently which are Top-up machine insufficient especially in major stations reached 56.5 percentages, cannot find the lost card reached 34.8 percentages, Opal card no sensitive to be scanned reached 45.7 percentages and duplicate charge reached 41.3 percentages. Furthermore, more than half of the respondents care that bank cards are associated with opal card because they concern the safety of opal card which can be found in fifth questions. Almost all respondents believe that Opal card should be replaced by mobile phone approximately 93.5 percentages sixth question. The same phenomenon occurs in the next question. It shows that about 89 percent of respondents hope opal card can be used in the convenient shop. The eighth question shows that over 80 percent of respondents argue that it is not environmentally friendly using disposable paper as a single-trip ticket.

 

In addition, the fourth and ninth questions of the survey is an open-ended question which is an excellent way to supplement extra user requirements. Some respondents stated that when the balance is low, he/she cannot enter the station, but there is a very little top-up machine. Also, sometimes the top-up machines are even out of order. It leads to time-consuming and annoying. Other respondents suggest that Opal company should provide student card for overseas students because it is unfair only offer student card to local students. Moreover, Opal company should use the reusable material as a single trip ticket rather than disposable paper that is not environmentally friendly. Also, English is the only language can be displayed in opal ticket system which is not user-friendly for the overseas traveler.

 

To sum up, although the survey only contains 9 questions, it also successfully retrieves various user requirements of opal ticketing system because the questions are built up in a proper way without any unnecessary questions. The overall results of the survey show that the performance of opal system is accepted by the majority of respondents, but it still exists some problems which need to be fixed. Also, passengers focus more on functional- requirement like operated by cell phone and used in the shop. User requirement plays an extremely role in system development because inaccurate and incompletely user requirement can lead to user unsatisfied which means system failure. 

When it is necessary to improve people's living standards, it is often necessary to introduce new technologies into society to make technological changes. This process of developing commercial information systems is essential. The Opal ticketing system is a contactless toll collection system for public transport services in Sydney, New South Wales, Australia. The project was first launched at the end of 2012, with buses in Sydney and the adjacent Central Coast, Hunter, Blue Mountains and Illawarra areas. Railway, light rail, and ferry services are all useful. Train services and selected third-party transportation services in the Southern Highlands were also accepted.

 

The purpose of this report is to find the accurate and complete user requirements for the Opal ticketing system. It plays an essential role in the development system. Making mistakes in the beginning stage can lead to severe consequences. For example, if a company develops a system that does not meet the requirements of the user, it could cause system failure because users would not operate a system that they dislike. It can be time, money and energy-consuming. This article will be divided into System Stakeholders, Requirements Gathering Methods, Functional and Non-functional Requirements, Entity Relationship Diagram, Use Case Diagram and Use Cases Descriptions. In the stakeholder's list section which will list the people or groups that have interests in the Opal ticketing system and the reason why these stakeholders are a vital part of this report will be explained. Requirements Gathering will explain the two different approaches used to retrieve information of users’ requirement and the reason why these two different methods are used. Functional and Non-functional Requirements will be divided into Functional Requirements and Non-functional Requirements. In the Functional Requirements section, a new list of functional requirements is included based on Requirements Gathering section. By the contrast, in the Non-functional requirements section only contain existing non-functional user requirements. The Entity Relationship Diagram section draws an entity relationship diagram for the Opal ticketing system to show specific the properties of the system and the relationship between these attributes and the cardinality. By following sections is Use Case Diagram section which includes the majority of functions in the Opal ticketing system. Also, the 4 primary functions will be illustrated in the User case description section. The last two parts of this report are appendix and references. Raw materials of this reports, original questions and a brief summary of the survey will be displayed in Appendix.

 

 

 

 

 

 

 

 

 

 

     14. Opal card external designers

 

     15. Opal companies employees.

 

The stakeholder can be defined as any person or organization who will be affected or associated directly and indirectly by the Opal system. The stakeholder list is extremely crucial because in this list it is possible to visualize which groups are closely related to the system, which will make the scope of the survey population more precise.

a)         How many parts does your exam have? What kinds of questions in each part?

             Two parts, Multiple choice and draw two diagram.

Questions from all the lectures, including today’s BPMN and DFD (so from Lecture 1 to Lecture 10)