# data[].attributes.body
This week we focus on our assgniment B. My teammate help me a lot. I made further changes to my assignment based on their suggestions.
After several modifications, we all think that this part has been done very well.But I still asked tutor to have a look it. This is a wise choice because the teacher once again pointed out some shortcomings.
After I modified it again, I also made a comparison with checklist. A good work requires constant revision and consultation with others.Every members complete this assignment carefully, and we have fully communicated and given great help to each other. I believe we should get a satisfactory result.

# data[].attributes.body
So here we go week 9. In this week we have to finalise our work. Till now we were going very good and we are very much confident about our assignment that we will get a D but I am still thinking that if we can get an HD. So we all posted finalized part of our assignment and we told each other to review the work so that we can make a bit changes and finalise our work.Here I wanna mention that all our team members worked very hard especially Shakeeb and Tawsif. We planned to finalise all the work on Saturday. Tawsif was responsible for the compiling of work and now we are all set to submit our assignment. All our team members worked as a group and we learned many things from each other because team work matters a lot in group assignments and I hope that this knowledge helps me in my professional career. Hope we get an HD. Good Luck to our team……..

# data[].attributes.body
We have reached the end of our assignment and have worked to the best of our ability to reach this end. We believe that we have yielded in an optimum assignment via working very hard and effectively as a group. We had finished our individual task by Friday on 31st of August. I was responsible for making the Introduction, sequence diagram, System methodology and assisted Leee with his class diagram. Tawsif was responsible for the construction of both the state machine, activity diagram and also helped in assisting in Lee’s class diagram and Noman Use case diagram and description. Through Tawsif hard work our individual work were compiled by Saturday on 1st of September 2018. After which conducted a group meeting at the green room in person to the rectify any small mistakes that were found. Then, on Sunday we had a face book messenger group chat on finalising the assessment that would later be uploaded by 100pm on Sunday 2nd of September. Though, I believe we could have achieved a better result if we had completed the assignment on Wednesday so that we could get a the teachers review of the whole assignment which would have been much more beneficial than the individual tasks. This assignment, helped understand the importance of teamwork, effective communication and cooperation between teamwork, the importance of t a strict adherence to a schedule. Furthermore, the assignment gave us an idea of how software project is both planned and created in the professional world.

# data[].attributes.body
Assignment B

Today I want to reflect for the combining work of the assignment B of our team. We have finished our assignment on last Saturday according to our plan. I like to thanks to our all group members who contributed their hard work to complete the assignment on time. Shakib who was the most hardworking person of our team.He had done the sequence diagram , introduction part, System methodology and also help us in other work. Noman made correction of the use case diagram and description and also completed one activity diagram. Lee finished the class diagram and one activity diagram. My responsibility was to make two activity diagram , two State Machine diagram and compiling the whole assignment.  I had also made the correction of class diagram and activity diagram which was done by Noman and Lee.

On the whole assignment, we face a lot of problems but our hard work helped us to overcome the situation. There was a problem to complete the State Machine Diagram but the teamwork motivate us to complete it on time. The assignment teach us the discipline of teamwork, the participation on it as well as the responsibility of doing the work on time. I also taught us the importance of diagram in the business field and how they take further decision based on it. The necessity of activity, sequence and state machine diagram are immeasurable as it gives an outline of the work flow within the business as well as the activities and action completed.

I think this knowledge will help us in the professional field by giving us a clear idea on how uml diagram help in the planning of a software project and at the same time help us develop a system methodology for the creation of the software.

# data[].attributes.body
At the star of the week me and the other group started to list out the tasks that were completed. The ones that were mostly completed were then checked against the teachers lesson checklist. After which we still got the teachers feedback for more tweak that help us achieve a HD Standard. Through the feedback were we able to not only improve but to also assist in creating a more effective methodology component.

# data[].attributes.body
Guyz this is our final assignment. please check it

# data[].attributes.body
This week started with a rush. Because we were getting close to our submission. In this week we studied State machine diagram and Tawsif and Shakeeb planned to work on this part and they held a meeting to discuss this diagram. I and lee continued to discuss the activity diagram and planned a meeting for them. It was getting a bit harder week by week but we were excited about it. I am now continuing my work towards the use case and activity diagram and hope to complete the work by time and get a good grade. Our team  is working hard enough because we had planned to get a D and hope we finalise the work two days before submission so that we can confidently submit our assignment.

# data[].attributes.body
Guyz, I send the state machine diagram to you before but i finally submit it in here. please message me asap if something i have to change.

# data[].attributes.body
IT Knowledge Portal 2018, IT Standards and Methodology,viewed on 25 August 2018, < www.itinfo.am/eng/software-development-methodologies/>

What is Softare Development Methodology, wiseGeek,viewed on 25 August 2018, < https://www.wisegeek.com/what-is-software-development-methodology.htm#>

Opal, NSW Government,viewed on 19 August 2018, < https://www.opal.com.au/>

# data[].attributes.body
Agile Software Development Methodology:

This is a very common conceptual framework for undertaking software engineering projects which mainly focuses on minimising risk via developing software in iteration. Each iteration contains smaller mini projects from the main project which have its own

Special tasks. In most case each of the miniature projects need to be completed in order to progress, task such as planning, requirements analysis, design, coding, testing, and documentation. While iteration may not add enough functionality to warrant releasing the product, an agile software project intends to be capable of releasing new software at the end of every iteration. After the completion of each iteration, the team revaluates project priorities. Furthermore, require real time communication is one major requirements, hence will be effective for local projects. In addition, most agile teams are in a bullpen and include all the people necessary to finish the software. At a minimum, this includes programmers and the people who define the product such as product managers, business analysts, or actual customers. The bullpen may also include testers, interface designers, technical writers, and management.

Dynamic Systems Development model methodology:

The Dynamic System Development model is more of a traditional approach for the undertaking of software projects. It was developed around the mid-1990 and also the can be considered a more modern evolution of rapid application development(RAD) practices. Although, like the philosophy of nothing is built perfectly the first time like agile but unfortunately focuses on training and documentation and hence compromises other aspects of a system development model. This approach to the development of software project involve the user involvement, cooperating teams that can make decisions at an instant, and constant testing for further improvement. In addition, it requires a lot of collaboration and cooperation between all involved stakeholders, to ensure the successfulness of the project.

Lean Development (LD) Methodology:

The lean development method is a more modern approach as it focuses creation of software that can easily adapt to any changes made without any redundancy of work. This approach relies on the notion of self-motivated stability but also at time tries to ensure that they are able to embrace some controlled chaos. The project is usually split into three sections which are firstly the human effort, then development hour, and lastly, investment. This method focuses working both effectively and efficiently, to also cooperate as a team and focus on completing tasks rather than to constructing. Most of the successfulness of the project can only be decided via active customer participation.

Rapid Application Development(RAD) Methodology:

The rapid application method produces most of their projects via reducing the amount of construction. In addition, this approach allows the product to be effectively created in short time frame and will have a higher quality. This method requires the continues use of focus groups in order to achieve better requirements, while at the same time carrying out both prototyping and user tests continuously. Moreover, this method achieves results via the reusing of software, and strict adherence to the schedule and at the same time maintain the cooperation of each members of all teams involved with the project.

Evaluation:

The use of Agile Software development method will be the most ineffectual due to many factors. Firstly, the project is large scale national public transport software project, which will be very difficult to accomplish via the agile method. Moreover, the project is being developed by a Japanese company, which makes it near impossible to accomplish real time communication and document sharing will be difficult to accomplish. Plus, the use of iteration will not only be void but useless, as in some cases the minor projects functionality may not be improved, and hence can result in some major glitches and given that project is very vital for the use of public transport.

Although, both Lean development methodology and Dynamic Systems Development model methodology focus on creating early prototypes that can undergo testing and review, the lean development method is more effective in ensuring there are no redundant. Lean development makes use every piece of work and can be easily adept any minor changes while at the same time ensuring the software functions effectively. At the same time, lean development has a flaw in relying only on active customer participation, in this regard the Dynamic System development is more effective as relies on all the stakeholder that are involved.

The most recommended method for the development of the Opal System would be the Rapid Application Development. This is due the fact that it is able to reuse code which will ensure there are no redundancy in work like how Lean development does. Furthermore, it can ensure the development of the system is accomplished within a short time frame while ensuring high quality, which is failed to be achieved via the agile method. Moreover, this approach has a very strict adherence to the schedule and thus far more effective than other three in regards to time management.

# data[].attributes.body
Today, as team we studied the structure of the assignment and then proceeded in delegating the tasks that would meet each one of our skill set. Due to the fact that we were studying sequence diagram, which i not only understood week but able to complete at very high standard, i was delegated the task of completing the sequence diagram component of the report.

# data[].attributes.body
I received the first assignment result this week. I was expected to got scrap a C but unfortunately I got a very bad mark. that is when i relised the importance of reflection and how to use padlet. At the same time one of the factors for my bad mark was due to the fact that i was not part of team and so joined up noman, tawsif and lee. We discussed how we can make more perfect of our use case diagram and also look after the mistake that we did in our last assignment. Our team members agreed to be more cooperative in future. We have add Sakib to our group. In week 6 lecture I went through the Activity diagram lecture and I took notes of tutorial 6 from Noman to make it more better.

# data[].attributes.body
In this week, tutor told us that jess didn’t replied to her email so she suggested us to work anyways without her for the second assignment and suggested us a new group member who found to be the most hardworking person of our group Shakib. We were in conversation from week 6 on messenger. We discussed the ways that how we worked in the past assignment with Shakib and proceeded to start the work for the second assignment. In this week we were introduced to sequence diagram which is an integral part of our assignment. Our tutor told the ways to how to manage to make a good sequence diagram and after 1 hour materials she gave us time to discuss about our assignment. I was then told to work use case diagram and descriptions and activity diagram which was one for each group member. I carefully reviewed the comments given and mistakes pointed on the existing use case to start my work for a better use case diagram and description. Activity diagram was a bit harder so I decided to do it after completing use cases. I and Tawsif did a meeting in week 6 which helped a lot in making changes to use cases and that’s how from the end of this week we finally started to work on our assignment.

# data[].attributes.body
This week we must assign tasks to specific member but Jess still absent. We reflected this problem to the tutor and tutor decide to assign another student to our team. As a result, we can continue to do our assignment B. This week we learnt how to make sequence diagram. It is a challenge part for us. Our new team member take the responsibility to do this part at assignment B. He very helpful.

# data[].attributes.body
In the week 8, we are introduced to a new term called State Machine Diagram. Among all the diagram, it seem the most difficult to me. I took help of my group mates Shakib and we were arranging a meeting to overcome our problems. In the meeting Shakib help me a lot to understand the State Machine Diagram. In the week 8 , Our group members cant arrange a meeting together. So Noman and Lee making a separate group meeting on last Sunday and me and Shakib meet together on last Monday. Shakib had done the sequence diagram and lee has finished his class diagram part.I would like to mention our another team member Noman who take the responsibility of the correction of use case diagram and description as well as making a activity diagram.
It is really enjoyable to learn a new diagram and I am so happy and excited when I solve a problem. State Machine Diagram is really challenging to me in comparison to the other Diagrams. I accept the challenge of learning new diagrams and solve the problems confidently.
Finally, Every members of our group working hard and they need continue their hard work to accomplish the team goal.

# data[].attributes.body
In week 6, We received the results for our first assignment and we were a bit disappointment by our result because we expected D for our work but anyways C is not that bad. Tawsif was not present in week 6 and we told our tutor to email Jess if she is going to work in the second assignment or not. I brought the assignment on very next day and me and Tawsif discussed the mistakes and comments given by the tutor on the assignment and planned to avoid mistakes and perform better in the second assignment .As it was our first week of second assignment so we just generally discussed that how we will manage the second assignment as it was a harder one. I was satisfied with my part in which I got D but I think now we should focus on more teamwork and perform better as a team as compared to performing individually to hopefully get D or else HD if we work on that level. Hope we get better results in Second Assignment.

# data[].attributes.body
This week I got my result of assignment A. Our team got overall C and my part of work got D. I’m satisfied with my work but I need to improve my reflection part because I only got P at this part. After the team discussion of the result, we decided to divide works to every member, this method can in case one part of the work get low mark. This week one of our team member absent agagin. We are worried that weather she can finish our assignment B work.

# data[].attributes.body
Agile Software Development Methodology:

This is a very common conceptual framework for undertaking software engineering projects which mainly focuses on minimising risk via developing software in iteration. Each iteration contains smaller mini projects from the main project which have its own

Special tasks. In most case each of the miniature projects need to be completed in order to progress, task such as planning, requirements analysis, design, coding, testing, and documentation. While iteration may not add enough functionality to warrant releasing the product, an agile software project intends to be capable of releasing new software at the end of every iteration. After the completion of each iteration, the team revaluates project priorities. Furthermore, require real time communication is one major requirements, hence will be effective for local projects. In addition, most agile teams are in a bullpen and include all the people necessary to finish the software. At a minimum, this includes programmers and the people who define the product such as product managers, business analysts, or actual customers. The bullpen may also include testers, interface designers, technical writers, and management.

In reality, this method will be the most ineffectual due to many factors. Firstly, the project is large scale national public transport software project, which will be very difficult to accomplish via the agile method. Moreover, the project is being developed by a Japanese company, which makes it near impossible to accomplish real time communication and document sharing will be difficult to accomplish. Plus, the use of iteration will not only be void but useless, as in some cases the minor projects functionality may not be improved, and hence can result in a major glitches and given that project is very vital for the use of public transport.

# data[].attributes.body
Guys please check if I have to add something to this diagram

# data[].attributes.body
The main objective of this report is to provide a system analysis on the current transportation system known as Opal and also provides and insight on how to design new functions within the current Opal System. Although this report may be similar in some terms to the last, the essential goal is to try to not only further analyse the opal system but rather to provide some rather more detailed stages of a design process, focusing on mainly the UML diagrams.

Opal smartcard ticketing System is the major system that responsible for the public transportation in Sydney, Blue Montains, Central Coast, Hunter and Illawara. The system is fairly simple as it involves passengers to simply add value before they travel, after which they will be able to access public transport via taping on and off the checkpoints.

As stated before, the main purpose of this is requirement specification report is to firstly helps in understanding the current system capabilities so that the system can be further developed to make it both effective for the organisation and passengers. To do this an investigation has to be conducted in order to identify the current system stakeholders who may be affected via any development of the system.

Using requirement gathering methods such as interviews and surveys and effective research on articles and websites about opal, the current system’s functional and non-functional requirement were identified. Furthermore, it also assisted in the creation of new functional requirement that can be used to develop the new functional requirement that can be added to the current System to benefit many of the system stakeholders.

After the completion of the research component of this report complete, the planning for the design process came into fruition. After a thorough understanding of functional requirements of the opal system, the creation of the UseCase diagram and Description was possible. In turn which helped in the creation of the activity diagram, sequence, state machine and class diagram which will be the diagrams in helping both the programmers and the clients further understand not only how the program will function but also how it will behave also. Furthermore, through understanding the program function and behaviour will make it possible for it professionals to design strategies to best implement for the development of this system most effectively, which further reinforced by the system methodology.

# data[].attributes.body
This week we are introduced to new term called sequence diagram which is a really challenging for me. Our group decided to do it together. Last week we have work on activity diagram , use case diagram. Our new member Shakib working really well and he takes the responsibility of the sequence diagram.At the same time all group member will help him to make it perfect. Noman and me make a meeting in the library to discuss about the use case diagram and activity diagram and it was already done. All the group members works perfectly except Jess because she cant present in the class because of her sickness.
Finally, we already make a plan for meeting in the uts green room on the upcoming thursday..

# data[].attributes.body
I received the first assignment result from Noman because I cant go to week 6 class for the reason of the unavailability of train. I was expected to got D but unfortunately I got C in there. So our team member should be more careful about the coming assignment 2. We discussed how we can make more perfect of our use case diagram and also look after the mistake that we did in our last assignment. Our team members agreed to be more cooperative in future. We have add Sakib to our group. In week 6 lecture I went through the Activity diagram lecture and I took notes of tutorial 6 from Noman to make it more better. Our team are planning to improve our assignment. This week we had a conversion in facebook messenger and we discuss how to improve our mistakes in the future. Though my last assignment does not meet my expectation but this time we hope we will achieve the best grade by our hard work

# data[].attributes.body
We have managed to complete our assignment in opal system on time. Our group members Noman, Lee and Jess have finished their part successfully. However, I have done the use case description and Use case diagram. Though I have some confusion about the Use case diagram, but I discussed with my lecturer and she help to figure it out. Again, I have done 4 use case description which seems a little bit challenging for me.  But my hard work helps me to overcome the situation.

However, Jess compile the whole assignment and sent it to me for recheck. After checking the assignment, I found some errors and spelling mistake on the assignment and recompiling it together. But Jess have done excellent work for the assignment. I will like to mention my other group members Noman and Lee. Noman had done his assignment successfully on time. But Lee had the responsibility of doing the functional and nonfunctional requirements. However, he managed to do 10 Non-functional requirements and 9 functional requirements which are not meet the requirements. But personally, I appreciate his hard work on this assignment and help us to complete it before deadline.

Overall, my opinion is the quality of our assignment is satisfactory, but our team members need to do more hard work to make it better.

# data[].attributes.body
We managed to finish and compile the assignment a few days before the due date, leaving plenty of time for adjustments and such. Overall, I believe the quality of the assignment was satisfactory, however personally I think more work could have gone into it to make it a strong HD. I am happy however that everyone had managed to do their part, and whenever someone had issues, we worked as a group to solve them. I ended up not helping Lee as much as I wanted to on part 4 due to time constraints., however I still believe overall our teamwork and organisation for this assignment was good and I hope we receive a fair mark.

# data[].attributes.body
After some suggestions from my group members in the green room meeting I then started System Stakeholders part in the week 3. This week was quite a bit busy for us because we were heading towards the end of our assignment and we planned to finish the assignment two days before the deadline. I planned to complete my work by week 3 so that I can get a pre-submission review from my tutor. I reviewed some websites to find some major stakeholders of the system. And after 1-2 days I managed to complete the tasks I was told to do so. In the class of week 4 I showed my work to my tutor and made some changes after some suggestions by her. I also did some part of appendix and arranging he references. Overall it was a good time working with my people as all of my group members were very co-operative and we helped each other to complete the assignment and finally Jess was responsible for the compilation. I hope we get a good grade for our work as this assignment represents our teamwork and Dedication.

# data[].attributes.headline
USE case Transfer money between two cards

# data[].attributes.subject
USE case Transfer money between two cards

# data[].attributes.attachment_link.title
Use case D(TRansfer money between diff card

# data[].attributes.body
In WEEK 2 we divided the work each group member equally so that everyone can equally take part in the assignment. At First we decided the deadlines for the completion and then we decided the way of communication. We were suggested by our professor to use padlet as our way of communication to get updated about each others work because if there should be no better communication and understanding with the group members then you cant perform well as a group. For our general conversation we used SMS service to get connected all over the assignment period. My part was to cover the Introduction part and System stakeholders part. In every assignment introduction is very important as it gives the first impression. I also did these parts in my previous assignment in the last trimester so it was not very much tough for me to do the tasks. In week 2 I completed the introduction and discussed it with my team members in the meeting held at the UTS green room and then made aa bit changes in it and completed this part by the end of that week.

# data[].attributes.headline
Reflection week 3-zhengyang Li                         In the week 3.According to the recommendations of the lecture notes,i made a table to list 4 functional requirements and 4 non-functional requirements.It is a good way to show it clearly.We use SMS to communicate with each member.We show our work progress and encourage each other to finish their work earlier.In this week tutorial,i further perfecting my use case diagram of UTS libaray system and i learnt how to add different visual effects to the E-R diagram. 

# data[].attributes.subject
Reflection week 3-zhengyang Li                         In the week 3.According to the recommendations of the lecture notes,i made a table to list 4 functional requirements and 4 non-functional requirements.It is a good way to show it clearly.We use SMS to communicate with each member.We show our work progress and encourage each other to finish their work earlier.In this week tutorial,i further perfecting my use case diagram of UTS libaray system and i learnt how to add different visual effects to the E-R diagram. 

# data[].attributes.body
ftp://ftp.tu-clausthal.de/pub/institute/informatik/v-modell.../10d2fd4c1c35a1.html

www.teknorix.com/methodology/requirements-analysis

# data[].attributes.body
On the third week of our assignment, we are planning to make our use case diagram as well as use case description. It’s my responsibility to complete this part of assignment. We arranged a group meeting on last Saturday but unfortunately jess can’t attend to the meeting because of her health condition. This meeting was important for us to collaboratively work and help each other to complete the assignment.

In the meeting, we are using Visio 2016 to make a use case diagram of opal card system. We also decide how can we make a use case description according to the use case diagram. We are consisting of 4 group members, so we have to make at least 12 use case and 4 use case description. The group meeting was held in UTS Green Room. Noman and Lee working on their part of the assignment and help me to complete my task.

At the same time, I make 12 use cases and 1 use case description and planning to recheck this use case and discuss with my lecturer in order to be more accurate on my assignment. Again, Jess talk with us via phone and tell us she take the interview and survey from people to complete her task. Every team member of our group done their part successfully and try their best to complete it with in the deadline.

# data[].attributes.body
guyz, Use case diagram for opal. Please check if I have to edit it or not

# data[].attributes.body
1. Introduction (5%)
2. System Stakeholders
3. Requirements Gathering Methods (20%)
4. Functional & Non-functional requirements
4.1 Functional Requirements
4.2 Non-functional   Requirements
5. Entity Relationship Diagram (15%)
6. Use Case Diagram (15%)
7. Use Case Descriptions (20%)
8. Appendix
9. References

25% INDIVIDUAL WORK

Tawsif
- 6, 7, 8, 9

Nomaan
- 1, 2, 8, 9

Lee
- 4, 8, 9

Jess
- 3, 4, 5, 8, 9 (Combining Assignment)

# data[].attributes.body
In Week 3, due to multiple health reasons I wasn't able to get as much done as I originally wanted to, however I am still on track to finishing my parts before the due date. I have seen my other group-mates post their parts of the assignment in the Padlet, so there is reasonable assumption that the assignment is well on track and following the timeline we had created at the hand-out of the assignment. In Week 3, I had completed Part 3, and a rough outline of Part 4. Part 5 has yet to be started on, however I am planning to start that part very soon.

# data[].attributes.attachment_link.title
Business Modelling Assignment Final word

# data[].attributes.body
System stakeholder are an integral part of businesses because they are the ones revolving around ups and downs of the business. The whole business or system solely depends on them and their influence is very much important on the business or system.

Every Stakeholder in business or system plays a vital role in the success of the business. Here are some of the stakeholders who directly influence the OPAL system;

Following are the stakeholders of the OPAL system;

i)             Customers:

Customers are an important stakeholder of the opal system as they are the ones for whom the system is designed.

ii)            Transport Officers:

Transport officers are responsible for time management of trains and to check that customers are using valid opal cards or not.

iii)          IT Support Technicians:

IT technicians are responsible for online management of the opal system specially the app which updates the customers and shows accurate times regarding trains.

iv)          Police Officers:

Police officers are responsible for regularly patrol the trains so that customers don’t travel illegally.

v)           Marketing:

Marketing team is important because they use their techniques to force people to use public transport so that it can profit the government.

Investors:

Investors are always important for any system because if the business didn’t do well and they are not satisfied then it can be a problem.

vi)          Government:

Government along the with the customers is the most important stakeholder of this system because this system is run by them.

vii)         Banks:

Banks are also important stakeholders because of the money is transferred in banks.

viii)       Finance Managers:

Finance Managers are also important for because this whole system revolves around lot of money so the finances should be managed properly.

ix)          Engineers:

Engineers are also important stakeholders as they are responsible for any type of mechanical issue which can affect the business.

X) Retailers:

Retailers are also the stakeholders of this system as opal cards are sold by them.

# data[].attributes.body
Group Assignment Brief

# data[].attributes.body
Requirements analysis are very much important for any business or system because when the actual needs of customers are targeted, and a system tries to fill them so that’s how a business can make profit. If there will be no calculations targets or interviews or surveys taken to plan the business, then there will be no profits. Requirements analysis includes Use case Modelling, Interviewing and cost benefit analysis. Requirements analysis is the process in which first the areas and people for which system is necessary and usable are targeted. Then surveys and interviews are taken so that features required by the people to solve their problems can be added.

The Opal Card is used for public transportation which was introduced by the Government of New South Wales. The Opal card is a contactless card system through which fare is calculated when you tap on and off the card at the stations. It was introduced in 2012 and is used to travel in buses, trains and ferries and light rail services which operates in Sydney and other suburban areas of Sydney by the NSW government. It is a credit card sized smartcard which has a microchip and internal RFID that allows the smart card to communicate with readers. The microchip enables the value to be loaded in the card as well as allowing the journey details to be recorded and the appropriate fare deduction from the stored amount of money in the card. This system is very much convenient and easy to use as customer have to just tap on and off to travel all over the NSW.

The Purpose of this report is to understand the system of OPAL and how this system is serving people all around NSW and became so much popular in the whole world. This system is considered one of the best systems of the world. To make this report first we studied the whole system and how it can be improved. Then we used the interview and survey techniques to find out the functional and non-functional requirements of the system and then appendix is provided in which reviews of people were taken about the system.

# data[].attributes.body
Three requirement gathering methods were mainly used for this project: document analysis, survey and interview. Document analysis is the act of reviewing the existing documentation of comparable business process or systems (in this case, OPAL) in order to extract project requirements. The comparison will be between the similar transport system utilised in Melbourne, named MYKI. Comparative information through document analysis can be analysed and extracted to form comparative informative statements, such as “MYKI costs are much higher than OPAL regarding short trips”. The utilization of a combination of interview and survey allows for a wholistic information extraction to make up for existing weaknesses in each requirement gathering method. Surveys

Document analysis is a form of qualitative research in which documents are interpreted by the researcher to give voice and meaning around an assessment topic (Bowen, 2009). There are three primary types of documents (O’Leary, 2014):

Public Records: The official, ongoing records of an organisation’s activities. Examples include student transcripts, mission statements, annual reports, policy manuals, student handbooks, strategic plans and syllabi.

Personal Documents:

WHAT: Document Analysis, Survey, Interview

https://lled500.trubox.ca/2016/244

WHY: Provides broad outline and general understanding of subject, allows for comparison of OPAL and MYKI, two similar competitive transport systems used in different states. Can highlight the strengths and weaknesses of the researched system, allowing new functional requirements to be created out of the systems’ weaknesses. Survey allows the researchers to capture individual thoughts and criticisms about the subject, again potential system requirements can be created through analysing multiple individual responses. Finally interviews were conducted to ensure there was adequate exploration of requirements not seen in surveys, whether due to either the close-ended nature of the survey questions or simply just a lack of exploration on certain topics.

# data[].attributes.body
- Requirements Gathering Methods (3) by 15th -> Needed for Use Case Diagram/Description (6/7)
- Requirements Gathering Methods Selected: Document Analysis (Comparative OPAL vs Melb MYKI) and 1-2 Interviews (Pre/Post Document Analysis)
- Finalise by 27th of July, talk about compilation

# data[].attributes.headline
Zhengyang Li-week 2 reflection.                               In the class on week 2, with the help of the teacher, we confirmed our team members. When discussing how we do group meetings. Some panelists think we should use padlet and UTS discussion board because this will make us more familiar with how to use these two software.What's more.We separate works of assignment A to each group member.The topic of assignment A is the OPAL ticketing system and my work is to list the functional and non-functional requirement.As a result, i have look many command of OPAL ticket.Tried to find some useful information.

# data[].attributes.subject
Zhengyang Li-week 2 reflection.                               In the class on week 2, with the help of the teacher, we confirmed our team members. When discussing how we do group meetings. Some panelists think we should use padlet and UTS discussion board because this will make us more familiar with how to use these two software.What's more.We separate works of assignment A to each group member.The topic of assignment A is the OPAL ticketing system and my work is to list the functional and non-functional requirement.As a result, i have look many command of OPAL ticket.Tried to find some useful information.

# data[].attributes.body
As a group, Tawsif, Nomaan, Lee and I managed to review the assignment guidelines and requirements as a group to make sure each member understood every requirement of the assignment in order to achieve a high mark. We then divided the work in equal parts, and created a rough timeline in which due dates of both individual parts and final assignment needed to be given in, so that we would have adequate time to edit and review the final draft assignment so that every member was happy with the final outcome.

# data[].attributes.body
Opal Card Top up

# data[].attributes.body
Visio is used in this assignment to create Diagrams, make sure everyone is familiar and knows how to use it

# data[].attributes.body
Our group has decided to use a combination of the Insearch Discussion Board and Padlet for group meetings instead of traditional social Media sites such as Facebook, as the work on our selected sites are trackable, as such has potential to be marked. Furthermore it is easy to keep track of work done by each individual member.

# data[].attributes.body
Template