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.

 

 

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. 

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.

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.

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.

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.

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. 

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.