# data[].attributes.body
Task 3: Final Exam Preparation

Go through ‘Final Exam Study Strategies’ from the Week 10 folder on UTS Online. We will implement some strategies in the Week 11 lecture to prepare for the exam. For now, answer the following questions:

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

Two parts, Multiple choice and draw two diagram.

b)         How many questions in each part, and how many points are they worth?

40 multiple choices each worth 2% .

Draw two diagram 1 for 12% other worth 8%.

c)         What content does Part A cover?

The same style and level of difficulty as your Kahoot quizzes

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

d)         What content does Part B cover?

All the questions are about requirements specification; We learnt to specify requirements in few written forms and in diagrams (models)

e)         What are two main study strategies that have been found very effective in improving students’ abilities, and, therefore, exam results?

Draw the diagrams again and answer the final revision question again without lecture note.

f)          If you have any questions, please post them in UTS Online under Discussion Board: Final Exam Questions. Please don’t post questions to which you could find answers in the slides – but if you read something, think about it, and are still confused or just want to understand it more deeply, then please feel free to ask. Make sure to check though if the same question has not been asked before.

okok

# data[].attributes.body
a)        How many parts does your exam have? What kinds of questions in each part?

2 part, draw diagram/ multiple choice question

b)        How many questions in each part, and how many points are they worth?

40 question 2 point each. One diagram is 8 the other is 12

c)        What content does Part A cover?

Kahoot quiz, weekly revision questions

d)        What content does Part B cover?

All diagrams drawn in assessments

e)        What are two main study strategies that have been found very effective in improving students’ abilities, and, therefore, exam results?

Draw all diagram by hand again and do revision questions without notes

# data[].attributes.body
During week 9  we have already learnt all the UML diagram so this week is a revision week which is to ensure we can understand each diagram clearly without any misunderstanding. We did some quizzes in lecture and tutorial.

# data[].attributes.body
In this week tutorial, we have improved the assessment work in charge of our group. Besides, in this tutorial I have reviewed the diagrams which I have learned in recent weeks, and the part which i responsible for in the assessment work has been completed.

# data[].attributes.body
This week Thursday we went to the UTS library to have last group meeting. The purpose of meeting is to ensure that every members have finished their works and improve the each individuals works through group discussion. The group meeting is useful way to expose existing errors in works because we have different prospective and knowledge. As a result, the assignment will be improved significantly.

# data[].attributes.body
Sequence Diagram Of Customer Top Up Opal Card

# data[].attributes.body
State Machine Diagram Of Opal Card

# data[].attributes.body
https://drive.google.com/a/uts.edu.au/file/d/1C5X-gxLbfGAEG5VMk3JfC7O4cMfyVZcU/view?usp=sharing

https://drive.google.com/a/uts.edu.au/file/d/1Vo8W600FKbu5KDYHGfXCvOs0uKAOYcg8/view?usp=sharing

https://drive.google.com/a/uts.edu.au/file/d/1jXi00j6RRuQvwOueMDwxdLi4n-aY8WfD/view?usp=sharing

https://drive.google.com/a/uts.edu.au/file/d/1soC-SMsV1gJ17Q9L00aIttsbOvuJF6sm/view?usp=sharing

# data[].attributes.body
Sequence Diagram Of Customer Buy Single Ticket

# data[].attributes.headline
State machine diagram and personal reflection

# data[].attributes.subject
State machine diagram and personal reflection

# data[].attributes.body
In the week 8, I learnt how to create a good state machine diagram. This diagram focuses on the life cycle of an object. The most important thing in this diagram is the state change of a class and the object of a class. In the state machine diagram, different objects can have the same state, and there will be a starting point and an ending point.

# data[].attributes.headline
State Machine Diagram + Personal Reflection

# data[].attributes.subject
State Machine Diagram + Personal Reflection

# data[].attributes.body
this week i have learnt the State machine diagram. this diagram mainly talks about a life time of a certain object. it shows all the different state that the object can be in. and the triggers of how each state transition to another. each state must be named as a adv which completes the sentence " 'object' is 'state' ".

# data[].attributes.headline
Sequence Diagram And Personal Reflection

# data[].attributes.subject
Sequence Diagram And Personal Reflection

# data[].attributes.body
In the week 7. I learnt how to make sequence diagrams. Sequence diagrams and activity diagrams graphically describe the steps of the use case, while the sequence diagram shows the internal view of the entire process.

# data[].attributes.body
This week i learnt the Sequence Diagram. Sequence diagram is similar to Activity diagram because they all graphically describing the steps of a use case. the key difference between these two is that the Sequence diagram shows the internal view but the activity diagram shows the external / user perspective .

Assessment B
I have almost completed my part in the Class Diagram. and starting on the activity diagrams.

# data[].attributes.body
1      Introduction (Jeremy)

2      Use Case Diagram and Descriptions (Weiyin)

3      Activity Diagrams (Jack)

4      Sequence Diagrams (Weiyin and Tommy)

5      State Machine Diagrams  (Weiyin and Tommy)

6      Class Diagram (Jack)

7      System Development Methodologies (Jeremy )

8      References (Jeremy)

# data[].attributes.body
In the sixth week, we introduced a new chart called the activity diagram. Activity diagram based on use case diagram and use case description.
Therefore, the use case description plays an extremely important role in the subsequent allocation. Any problems in the use case description section should be fixed or recreated before starting the activity diagram. Activity diagrams include several factors, such as start and end points, activity streams, decision points, branches/connections, and partitions. A valid activity diagram should contain only one starting point and one way of flowing. The function of the activity diagram is to display the workflow at a easy level that stakeholders can understand. This is an external and behavioral diagram.

Assignment part
The results of the assignment have been published, and our team has scored high distinction and we really moved it. It has greatly inspired our enthusiasm for learning. Because each member contributes to the assignment, we get good results. We discussed the teacher's feedback together at the first time to ensure that the problem was properly resolved and avoided in Task B. In addition, I am still looking at this week to search for some reliable resources on system development methodology.

# data[].attributes.body
In this week, I have learnt how to make a more complete activity diagram which is based on the use case diagram.And a complete activity diagram should include these factors, starting and ending, activity flow, decision point, branch/connection and partition.

# data[].attributes.body
This week during tutorial i have learnt how Activity diagram are drawn. Activity diagram is drawn base on the use case description which is a graphic way of showing the black box view (customer's view) of the system.

# data[].attributes.headline
Feedback of assignment A (chicken dinner)

# data[].attributes.subject
Feedback of assignment A (chicken dinner)

# data[].attributes.body
https://drive.google.com/open?id=1BmhFCpZuu-5TRpEd5MVZFZqEyt5QuSD1

# data[].attributes.body
In the week 4 of the Tutorial, I further improved the part I was responsible for in the Education. I asked Jeremy to determine what I needed to do in this part. And on Lecture I learned how to make object-oriented paradigm in more detail.

Assignment parts:

1      Introduction

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.

2      System Stakeholders list

1. System development companies

1. Chip development companies

1. Website development companies

2. Phone application development companies

3. Top up machines development companies

4. Internet providers

5. Bank Owners

1. Governments

1. Stores

1. Train staff

1. Passengers

2. Train stations

1. Opal system maintainers

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.

# data[].attributes.body
During tutorial, my team chicken dinner assembled our parts to and finalise the Assessment. In class I made sure the part I was in charged of is finished correctly and also helped my teammate with theirs.

# data[].attributes.body
This week we have collected each team member's work and checked with the checked list provided in the tutorial week 9 file. Also i have done some revising work on the past few week studies of the diagrams.
With the checklist provided i was able to find some mistake which i did not realised in the start, and i fixed all the problems i have find according to the list for my diagrams.
My part of the assessment is 90% finalised and ready to be uploaded.

# data[].attributes.body
Tutorial Part:
In this week, I learned the difference between use case diagram and descriptions and learned how to draw a more detailed use case diagram. In the use case diagram we can add more detailed extensions in the description section of the process.

Assignment Part:
I learnt more about the parts that this report needs to include and the requirements that we have in each section, and wrote the introduction section for this report, and also made a list for stakeholders of the Opal ticketing system.

# data[].attributes.headline
Introduction and stakeholder list for the assessment

# data[].attributes.subject
Introduction and stakeholder list for the assessment

# data[].attributes.body
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 very necessary. 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 effective. Train services and selected third-party transportation services in the Southern Highlands were also accepted.

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.

# data[].attributes.body
Still working on it

# data[].attributes.body
In week 3 Lecture and Tutorial class we have learnt about the new different parts of the use case diagram and descriptions. In use case diagram, we learnt that we need to have "include" use cases which is connected to the use case that needs the common procedure, for example like log in. "Extended" use cases are connected to use cases that might need this procedure.
In Tutorial class, I have created the use case diagram and use case description for the UTS library system.

Assessment part:
I began creating the functional and non functional list, and also thinking about the entities which will be included in the ERD.

# data[].attributes.body
Tutorial part:
In this week, we have learnt how to draw a quality use case diagram which includes system name and boundary, actor, communicate with and use cases. Actor can be divided into primary actor and secondary actor. Primary actor means who will interact with system more frequently. In addition use cases relationships contain two different components which are 'include ' and 'extend' relationship. 'include' relationship means by finish a use case must fulfill previous use case. For example,if user want check his balance he has to login first. As a result, enter account is a 'include' relationship with check balance. By the contrast, 'extend' relationship is like a supplemental functions. For instance, the bill can be paid by different methods such as credit card or online transfer. So, pay by credit card is a 'extend' relationship with pay the bill. Preconditions and post-conditions are important in use case description. an example for preconditions is that customer must have valid bank account then they can use ATM machine. Another example for post-condition is that if customer withdrew money from their account, the balance will be changed.

Assignment part:
We using survey and competitor analyzing to gather user requirement. Survey questions has been created completely which include 9 questions in this week. The questions contain  both open-ended and closed-ended questions. They have different advantages. Open-ended question can get extra information and experience for respondents. Closed-ended questions only provide 'Yes' , 'No' and 'Other' answer. It can be easier to further analyze. We already get 20 respondents so far, we will try to get enough quantity of respondents then start the analyzing.

# data[].attributes.body
use case descriptio

# data[].attributes.body
In week 8 I have learnt that how to create a good state machine diagram. It focus is on state changes in one class and objects of one class. Also, one state machine diagram per one class. However, the activity and sequence diagram are focus on specific use case. Object's states change means attribute change through specific methods. Moreover, the states of objects is limited for example book is available , book is unavailable and book is damage. One object only have a state at the same time. However, different object could have same state at the same time. State machine includes start and end point just like activity diagram but it has more component such as states, transitions, trigger, events, conditions and activities. Only the object removed or deleted in system will go to end point.

Assignment part
The compassion has been completed in this week. It through different criteria to compare the advantages and disadvantage for each methodologies such easy modified,  conserved time and budgets and user participation and so on. Also, the final recommendation will show the most suitable methodologies for Opal ticketing system through analyzing and cooperation above. The last group discussion will aim to expose the errors existing our UML diagram that we made and fix it to ensure the all the diagram can meet requirement and standard.

# data[].attributes.body
Use case description

# data[].attributes.body
Use case diagram

# data[].attributes.body
Use case diagram

# data[].attributes.body
Use case description.

# data[].attributes.body
In week 7 the sequence diagram has been introduced by teacher. The main purpose of a sequence diagram is to define sequence of events in one scenario of one use case. It normally shows most important scenario or complete scenario because it will be meaningful. Also, it is a behavioral and internal diagram. Sequence diagram includes some components like boundary classes, lifelines, message, returned message notation, Iteration (repetition) notation, and activation boxes. The actor only can interact with system through boundary classes. Any messages returned by system should show in returned message notation. Iteration means that the actions will repeat many times such as insert card to ATM.

Assignment part
The introduction part of assignment B has been finished. In addition, after the group discussion, we decided to search rapid application , extreme programming, system development life cycle and prototyping as our research objects. Two of them are agile because our want to compare the differences between agile and normal methodologies. The overview including properly citation for each methodologies will be finished in this week. Next week I will create a compassion table to compare the advantages and disadvantages of each methodologies.

# data[].attributes.body
During week 1, I had clearly understood what's the subject about, such as identify stakeholders, understand their needs, and Apply modeling and systems analysis techniques that help understand the working of a business system. Also get to know how made a great group.
At the lecture,  I learned the difference between functional requirements and non-functional requirements, for example, functional requirements capture the intended behavior of the system, and the non-functional requirements is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific actions.

# data[].attributes.body
Week 1 tutorial  functional and non-functional requirement.

# data[].attributes.body
Week 1 personal reflection
During week 1 tutorial I have learn that the user requirements can be further divided into non-functional and functional requirement. Functional requirement means that the system shall have various abilities to accomplish specific tasks. By the contrast, non-functional requirements likes external requirement which aims to improve system's security, usability and reliability. Both of them are extremely important to develop a new system because unclear and incomplete user requirement can lead to failure which can be really time, energy and money consuming. Good understanding of user requirements is able to design a useful system that users are needed and satisfying.

# data[].attributes.body
Week 2 tutorial ERD diagram

# data[].attributes.body
At week 2, we build a team which called Chicken Dinner,  then member included Jack, Tommy, Jinlin and me. we meet at tutorial class and talk about assesment, we distribution for each member, which can help us move fast to finish assessment.
Also, in this week, I have learned about the ERD model, which is described interrelated things of interest in a specific domain of knowledge. At tutorial, I had learned to use Visio to made the ERD notations show the relationship about the UTS library system.

# data[].attributes.body
During Week 1 I have learnt the important dates for the assessment 1 deadline.
I have learnt to create a Functional and Non-Functional requirement table which will be needed for the first assessment. During tutorial I created a table for the UTS Library System. As I was creating my table I learnt the difference between the Functional and Non-Functional requirement. Functional is mainly about what functions it physically has, these are easy to see when users starts to use the system. Non-Functional are things working behind which users don't see, in order to know what are they we have to think beyond the system interface, such as security.

# data[].attributes.headline
Sitao Cheng 2954647 Personal Reflection for Week 1

# data[].attributes.subject
Sitao Cheng 2954647 Personal Reflection for Week 1

# data[].attributes.body
During week 1 I have learnt the difference between functional and non-functional requirements and made a table for these two perspectives of the UTS Library System. Functional requirements are functions that users can see directly, that is, physical functions. Non-functional requirements are functions that users can't directly see. They are functions that need to be in the background of the system, just like security and reliability.
Functional requirement of UTS library system

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,

# data[].attributes.body
During week 2 I have created a padlet page for my group and started posting weekly reflections. My team leader Jeremy sort out the assessment works for the team so we can start this week. The part I am doing is the Entity relationship diagram and functional/non functional requirements.
In tutorial class i have learnt how to create a good entity relationship diagram. A entity relationship diagram have 3 main parts, Entity, Relationship and Attributes. After having to create the 3 main parts, I used lines to connect them up and identify the cardinality between the related entities. I have created a diagram for the UTS library system using Visio. Visio is a really good program for drawing diagrams, I have watched some videos to learn more on using Visio.

# data[].attributes.headline
Sitao Cheng 2954647 Personal Reflection for Week 2

# data[].attributes.subject
Sitao Cheng 2954647 Personal Reflection for Week 2

# data[].attributes.body
In the second week of the tutorial we created a padlet page for our group of chicken dinners and uploaded weekly reflections on it, and I will also be responsible for the introduction part of the assignment. We also learned how to use Visio to create an ERD diagram, which includes five parts: entity, attribute, primary key, relationships, and cardinality. We use straight lines to connect them and confirm the cardinality between related entities. The video I watched before also helped me.In the second week of the tutorial we created a padlet page for our group of chicken dinners and uploaded weekly reflections on it, and I will also be responsible for the introduction part of the assignment. We also learned how to use Visio to create an ERD diagram, which includes five parts: entity, attribute, primary key, relationships, and cardinality. We use straight lines to connect them and confirm the cardinality between related entities. The video I watched before also helped us.

# data[].attributes.body
Week 4 learning : I have learnt that object-oriented paradigm is used to analyse and design a system, and then in programming - link between analysis and design, and then implementation. It has many components like Class, Object and behavior. In addition, the child class is able to inherent from parent class. UML is a standard of developing a system which can provide a common vocabulary of terms and diagramming techniques that is rich enough to model any systems development project.

Assignment parts :
Group assignment has been submitted. Every members have great contributions for this assignment. Now I would like to post what i done in this assignment.

3      Requirements Gathering Methods

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.

# data[].attributes.body
Week 2 personal reflection
We has built a group called chicken dinner which including 4 members who are Jack, Tommy, Weiyin and me. I will be the leader of team throughout this subject which means I need to be responsible for each members and ensure assignment can be finished properly and on time. In week 2, I have learnt how to use Visio to draw an qualified chen‘s ERD diagram which includes 5 main components which are entity, attribute, primary key, relationships and cardinality. A entity (Uppercase singular)can have many attribute but only have one primary key(Underline) which uses most often and is not likely to change for example student's ID, book-code.The relationship between different entities will use a verb to connect each others such as Student pay the Bill. In addition, cardinality is used to explain how many occurrences of each entity type can be involved in an interaction previous example is one-many relationship because a student can pay many bills. To sum up, ERD is an crucial way to display system's structure and help systems analysis. It also can be used to develop a database in other subject. Also, the assignment works have been separated for each members. （Assignment process）Everyone is satisfied with the work assignment.I am in charge of user requirements gathering and list of stakeholders. I decide use survey to get user requirements because it is the most efficient methods than others. Also, survey is able to get many interviewees which can ensure that  user requirements are accuracy and complete. I will create meaningful question to get user requirements after I read 4 resalable survey guide websites.

# data[].attributes.body
Jeremy will be the leader of chicken dinner during whole subject.  We will make a discussion per week to make ensure every member clearly understand their works and check the work's status. We normally meet together in UTS library in Weekend. We will upload the team assignment work in Google drive or padlet to ensure that team members have completed their parts of assignment. Leader of team has right to decide whether individual meet criteria of assignment. If it is not acceptable , team members should fix it until satisfying the standard. If team members have any question or unpleasant can give advises to leader directly.

# data[].attributes.body
1       Introduction  Cheng

<< 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       Functional and Non-functional Requirements

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.>>

5       Entity Relationship Diagram  Wu

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

6       Use Case Diagram  Zhang

<<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). >>

7       Use Cases Descriptions Zhang

<< 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.>>