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. 

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.  

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

WHAT: Document Analysis, Survey, Interview

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. 

www.teknorix.com/methodology/requirements-analysis

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. 

 

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.

 

 

 

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. 

 

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.

 

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.

 

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

 

 

                        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.

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 31^st 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 1^st 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 2^nd 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.