# data[].attributes.body
JPG

# data[].attributes.body
State machine JPG

# data[].attributes.body
State machine JPG

# data[].attributes.body
sequence diagram JPG

# data[].attributes.body
sequence diagram JPG

# data[].attributes.body
sequence diagram JPG

# data[].attributes.body
sequence diagram JPG

# data[].attributes.body
activity diagram JPG

# data[].attributes.body
activity diagram JPG

# data[].attributes.body
activity diagram JPG

# data[].attributes.body
activity diagram JPG

# data[].attributes.body
Chenming Yuan 3061176
Outcome:

In week 9, we did our UML diagram revision on class. I read lecture notes of last 8 weeks, checked the structure, theory of all diagrams. These helps me a lot of remembering how to draw diagrams and it is really benefit for our assignment B. Week 9 ,we have already almost finished our assignment B excepted introduction and system development methodologies. Sunday is our due day, so we decided to make all diagrams together in one file this week.

Process:

We had a meeting this week in PC 228, we re-checked all diagrams we did before the convert them in to PDF type. We did introduction and methodologies together and make all stuff together in one file. We hope we will have a good grade.

# data[].attributes.body
Chenming Yuan 3061176

Outcome:

In week 8, we have leanrt the structure and notations of state machine diagram. State machine diagram is really a hard diagram for us and I made a lot of mistakes of drawing it in tutorial class. At the beginning of the class, I cannot understand what should state machine diagram consists of. After study and ask question to our classmate and tutor, I realized what should I draw in this diagram. According to this week’s study, I know how to draw it and how to avoid mistakes of doing it in our assignment B.

Process:

This week, we decided to draw state machine diagram and we had a meeting at Friday in PC 228. We checked each other’s work at the beginning. We found some problems of our diagrams. In order to fix it, we checked our lecture notes and modelling hall of fame then fix it. Then we drew state machine diagrams this week.

# data[].attributes.body
Wenhao sun 2936613
Outcome:
In this week, we almost finished the assessment B. And we revision the UML diagram once again. More over, we checked all the lecture notes and improve our assessment B. In this Sunday, we will combine all things together and submit it.

Process:
We meeting in every week in order to finished the assessment B and improve our learning skill. We did introduction and methodologies together and combine it together. Every one did a good job, i guess we can have a good mark in this assessment because we spent lots of time and worked on that really hard

# data[].attributes.body
Outcome:
This week, we finished the introduction and methodology. That means we totally finished this assignment. That is a good new for us. So we should start the revision of the final exam. And get a high grade.

Process:
In order to finish the assignment quickly and have enough time to double check it and correct it. We put each other to draw the diagram and write and introduction. Finally, we done it. So in the next few days, we will have another double check to make this assignment perfect.

# data[].attributes.body
Chenming Yuan 3061176
Outcome:

In week 7, we learned the structure and notations of sequence diagram, we have successfully draw a sequence diagram of booking room on tutorial class and our tutor gave me some suggestion of fixing our diagram. At the same time, I told my members and avoid having same mistakes of drawing sequence diagram of assignment B.

Process:

In week 7, we started to do our assignment B.        We have learnt activity diagram and sequence diagram before. So we decided to do these two diagrams this week. We assigned our tasks. After our discussion, each of us do each of these two diagrams, we use “top up”, “check balance”, “order opal card” to do our diagrams. We discussed together and finally finished this week’s task.

# data[].attributes.body
Chenming Yuan 3061176
Outcome:

In week 6, we have learnt the structure of class diagram and knew how to draw class diagram. Also this week, we were requested to start to do our assignment B. We had a good grade in assignment A, so now we are so confident of our group work and we believe that we can also do a good job of assignment B. At this week, we also had a revision of our assignment B , we found that we had some problems of some of our use cases, we have to pay more attention on fixing these problems in our assignment B and come up with more efficient method to get use cases.

Process:

In order to finish assignment B perfectly, we decided to have a meeting at the weekend via wechat. Because we hadn’t leanrt how to draw state machine and sequence diagram yet. In order to finish it more efficiently and get a better grade, we decided to start check more information on the website and re-read lecture notes. We will start to do our assignment B next week.

Wish we have a good grade.

# data[].attributes.body
Bowen Wang 3008299

Outcomes:
This week, we almost finished the Assignment B. we have already draw the rest of the diagram and  have conversation between each group member. in the tutorial class we had discussion on the state machine diagram and also do the revision for all the diagram we have learn in the past few week.

Process:
During the class we have enough time to double check the work properly and finalise the assignment. we have doing good so far. so in next few days we will conducting the final version for the Assignment B. hope we can get good result for this assignment.

# data[].attributes.body
Outcome:
This week, it is a good week. The good news is that we almost finished all the diagrams. So, the things that we did not finish is the introduction and methodology.

Process:
we leaned the state machine diagram, so it makes us to finish the state machine diagram in Assignment B easily. Other diagrams are not hard for us. So, we did a good job this week. I hope we can keep this power to do better next week!!

# data[].attributes.body
Bowen Wang 3008299

Outcomes:
in this week, we have finish most parts of diagram in this assignment. we discussed the sequence diagram a lot. furthermore we still got some improvement in working time.

Process:
Based on the what we learn in this week tutorial state machine diagram. we already have conversation with each group member. Anyway, being good so far work with teammate and hope before next week we can finish the work early

# data[].attributes.body
Outcomes:
In this week, we distributed the particular part for each members. our group were all did the a diagram in the class.
Process:
we leaned the a diagram in lecture and worked it on the tutorial class. In the next week, we should finished some of part and analysis all the work. We will do it better than the fist assessment.

# data[].attributes.body
Bowen Wang 3008299

Outcomes:
This week, we have already distributed the parts, our group have go through the class diagram and analysis the diagram deeply.

Process :
For last week, our group was divided work for each work, we distributed work and talk about what we should do. so in week eight is very important for the assignment.

# data[].attributes.body
Outcomes:
In this week, we done some parts of this assessment, every body did good job. We did the diagrams and some practices. Moreover, we will improve our diagrams again.

Process:
We leaned the diagram in this week class. And we done some of works in this assessments. In this weekend we will complete our work and improve it for the best mark!!!!! Everybody did a good job!!!!

# data[].attributes.body
Outcome:
This week, we have already distributed the parts, so we discuss those diagrams deeply.
Process:
As same as last week, we met each other after the tutorial, and re-discussed the work, told each of our group member what they should do. The most important thing is that we told us should finish half of their works. That is key point of this week.

# data[].attributes.body
Out come:
In this week, we learned about how to use a new project which is class diagram in the class. Moreover, we discussed about the assignment two and distributed the work in the class.
Process:
Our group member meet in the class, and talk about the assignment. We can clearly understand what should we do for each group members.

# data[].attributes.body
Bowen Wang 3008299

Outcomes:
This week, we have learn about new project of the class diagram and also discuss the new Assignment B which needs us to draw lots of diagram. After that we have distributed the work for each group member. we had discussion in the particular parts .
Process:
when finished the week 6 tutorial class, our group member have met together and discuss this Assignment B. distributed the work into weekly material work .and we decide to start work next week .

# data[].attributes.body
Outcome: This week, we knew about there is a new assignment called Assignment B which needs us to draw lots of diagrams. So, we distributed the parts for each one. And discuss what is the key point in each part.
Process: After we having the week 6 tutorial, our group member met together and discuss this assignment. Distribution and discussion are the main parts of meeting. And we decide to start it on Next Monday. We hope all of us can do a good job.

# data[].attributes.body
Outcome: This week, we have finished all the works and in order to conducted the work properly.
processed:
each group members have put their work on the padlet and we have discuss the third part requirement gathering methods and also made some changes . after we finished the each parts. we got organised the structure in the report. However this time every group members has doing well.

# data[].attributes.body
Outcome: This week, we finished all the works and organized them together.
Process: Each of our wrote a part of Requirement Gathering Methods and organized the results of interview, survey and observation putted them to the Appendix. After we finished and organized all of works. All of us did a double-check which can fix the errors and some grammar mistakes. Totally, we did a good job.

# data[].attributes.body
outcome: in this week class, we learned how to fix the problem of the use case and improve this part. Moreover, we done all of the group work and checked by our tutor, so we know which part we need to change and improve. Every group members did a good job.
Process:
we did all of work, and combine this together by our group leader. We face to face to finished all the part, and interview the costumers of around our topic Opal system. Everybody did well!!!

# data[].attributes.body
Outcomes:
In this week classes, we leaned how to write the use case and use case description, then we done those two part in this week, we also   almost finished the introduction and system stakeholders. Every group member did well.
Process:
we finished some of those part, but we still have the problems need to be fixed, we will try hard and do more works in next weeks and check what we did then change the mistakes. Everybody did well!!!

# data[].attributes.body
1. passengers
2. station guide staff
3. Technical department
4. station service staff (help the people who need a wheelchair and cannot get on the train)
5. government (tax)

# data[].attributes.body
Introduction:

A good operation system will help user to improved their work and increment their productivity. Opal system is a significant essential role to the NSW transportation. The opal system was developed to improve the people life quality for using public transportation. The purpose of this report is to exemplifies the development an opal system.

In this report, through the use case diagram of previous work is to still using to analysis the some user requirement and keeping to develop the system. The opal system can be analyzing by using the different diagram, such as the activity diagram, the sequence diagram, the state machine diagram and the class diagram, its to demonstrates the flow of how the use case can be developed to the opal system. The stakeholder analysis is essential to help the system gathering requirements work on the most accurate group. The requirements were analysis into two parts, which are functional requirements and non-functional requirements. The purpose of requirements analysis is to help developer accurately understand the needs of system. Both kinds requirements were concluded into three level (Desirable, Essential, Luxury), and the source of requirements was list to help developer understand the most important part of requirements.

The list of using: activity diagram, sequence diagram, state machine diagram and class diagram. The system can be developing by using these diagrams. The entire diagram has implies the flow of the how use case developed in the system. The activity diagram shows the operations workflow of use case, the sequence diagram shows the connection between objects, the state machine demonstrates the life cycle of the objects and alterations after each trigger event.  The class diagram symbolises the relationships , some essential attributes and operations.

The system development methodologies was used in this report. there are four methodologies were used in the system which are Crystal Methods Methodology, Feature Driven Development Methodology, Lean Development(LD) Methodology and System Development Life Cycle(SDLC) Methodology.

The System Development Life Cycle is important method which can be useful tool for managing the System and planed development methods effort.
It's to improved the old system. The opal system is important system to playing a crucial role as a new system. the SDLC is to helps system in this case and upgrading the system in easy way.
Crystal Methods also being a important role. this method is focus on the people and interaction between the system and business role and also that increase the communication in the business process.
The LD method will be focus on the creation of change-tolerant software. that can helps to provide best value to the system. in addition, Feature Driven development Methodology are be part of vital tool used in this report. A system for building a opal systems is necessary in order to scale to larger projects. Furthermore, this method also can be encouraging creativity and innovation for the business.

# data[].attributes.body
Last week we did the online group meeting, in that meeting, we finish the requirement gathering, come up with the use case and fix the problem of week 2, as the group leader, my job is drawing ERD and use case diagram, I did the use case diagram, it was drawing by group discussing use cases and everybody finished doing their use case descriptions.

In this week, every group member in our group has find problems after deep consideration. We found that we missed some functional and non-functional requirements and some use cases, in order to resolve that problem, we went to NSW government opal card website, read the opal home part and some articles of opal card policies. I helped my group to come up with more use cases and fixed their use cases descriptions.

In this week’s meeting, I find that reading assignment template and guidance is really important and useful for our job. After carefully read the template, we can easily understand the mission of our assignment.

Finally, I realized the most important thing of the assignment is the process of we find the problem and solve it. It improved our ability of analysing and resolving problems. Everybody in our group works so hard this week, I’m so proud of them.

# data[].attributes.body
Outcomes:
this week, we finished the use case diagram and four use case descriptions. Vincent finished the diagram, ray and Barry finished two use case descriptions and i finished two.

Process:
our group has meeting a few time outside the class and also share ideas to the other members. in the WeChat group we discuss the progress. For check the work process, we have confident to finished work early and everyone has doing the work great. hope next week we can finalised the assingment

# data[].attributes.body
Outcome: this week, we finished the use case diagram and four use case descriptions. Vincent finished the diagram, Barry and Bowen finished two use case descriptions and i finished two.
Process: I don't know if we progress is slow or not, we just finished the introduction, System Stakeholders, Entity Relationship Diagram, use case diagram, use case descriptions and survey. i think each group members did a great job. And i hope we can keep this fire to finish all the work and get a high mark finally.

# data[].attributes.body
Outcomes:
in this week tutorial, we have already discuss the group assignment and distributed the work for each group member and set up the time to finish the work. in that tutorial we talk about the what requirements gathering and specification . And plan hat will do in the next few week.
Process:
our group have finished the ERD digram and have a conversation with teachers, and tutor have give us some suggestion to make better. and Due to the members missing
we cannot meet every one at outside the class , so we decide to check the progress on the WeChat. however , we still have enough time to work on the assignment and finished the draft early.

# data[].attributes.body
Outcome: this week, we discuss what work each group member should do and   tell them the works should be finished at what time. We discuss this after our tutorial.  This week, we understand what the requirements gathering and ERD are. And plan to finish it in this two weeks.
Process: we finished the ERD this week, and each group member saw and gave some suggestions to make it better. I found that study and work in a group can make me has a high efficiency work.However, there were any problems during this week. All of our members cannot meet and face-to-face discuss. But it does not matter, we still can finish the work, even though it made our communicate difficultly. So in next two weeks, we will enhance our communication and make our group work better.

# data[].attributes.body
Outcome: in this week, we created a group, Ray, Bowen, Barry are group members, as the leader of the group,  I’m so pleasure that my members trust me. In order to make our assignment A get a better grade, we discuss a lot of plans of this assignment.Then we had done the ERD part in this week.
Process: we plan to finish the next two part on the next week, because the teacher will teach us the structure of how to write these. Every body did well in this week, we done our own job as a group and them combined those things together. We will combine this our work in every week at home or UTS library. Leader Vincent will decide the individual work for everyone.

# data[].attributes.body
This week, we created a group, Ray, Bowen, Barry are group members, as the leader of the group,  I’m so pleasure that my members trust me. In order to make our assignment A get a better grade, we discuss a lot of plans of this assignment.

As a group, we decided to communicate with each other at least 3 times a week via wechat and have a meeting once a week if it is necessary.

We read the assignment template, there are some tasks we have not learned. Therefore, we decided to allocate tasks in next few weeks.

In order to finish this assignment, we need to start this week, we checked some information of opal ticketing system and ready to do tasks.

# data[].attributes.body
Week2:  In this week, we designed a group for finishing all the assignment in this subject. In our group, Vincent is our group leader since now until end of this subject. In our group, we designed Wechat is our communication software to share our information in every weeks. Therefore, we will have a meeting in every weeks. The meeting area is library in  Saturday. In this group, we use the method which is obeying the majority to design how to make the decisions. We will combine this our work in every week at home or UTS library. Leader Vincent will decide the individual work for everyone. Whether we unhappy for the work distributed, we will communicate with others members to change some work.

# data[].attributes.body
week 2 we select the Vincent is the leader of our group. we do not want to change the different leader for each week ,it because will impact on the progress.
we will try our best to do the meeting every week and discuss about the assignment or we also can do the meeting online.

when facing the problem on to the decision or have different idea with assignment.

we use decide to listen the majority suggestion. In addition, we used Padlet to upload the work.

listen leader can decide the work is of acceptable standard or not.if there is someone not happy with the decision and talk to other group member. finally make agreement with everyone

# data[].attributes.body
Week 2 reflection
Q1:
Vincent is the leader of our group.
Q2:
We do not want to have a different leader for each week.
Q3:
we will try our best to meet each other weekly and if someone may not come, we will have an online meeting.
Q4:
from now on, we decide to meet each other in the library on Saturday.
Q5:
Minority obeying majority.
Q6:
We will upload our work to the padlet and must before the Sunday 11:59 pm of that week.
Q7:
Absolutely, our leader can decide the work is of acceptable standard or not. If there is someone who is not happy with a group member's commitment, other group member will decide whose action or work is correct and follow the mr.correct's action to do the work continually.