# data[].attributes.body
In the 9th week, our team completed the final task B. In the eighth week of study and team member cooperation, the complete cabin map and state machine map of the QANTAS flight reservation system has been improved.

Due to the feedback from the tutorial class, the improvement of the class diagram is not very difficult. We have improved some of the problems with class diagrams. The first improvement is the multiplicity of all relationships. Other members of our team reviewed the chart and provided some suggestions for the class map of the QANTAS flight reservation system. As a result, Kai corrected the multiplicity and relationship of some errors.
Second, we improved the readability of class diagrams and state machine diagrams. I changed the theme and increased the font size of the chart so that the chart is easy to see.

After that, our team checked the complete report together. Then we adjusted the margin and checked if the directory corresponds to the article.

# data[].attributes.body
In the 8th week, our team basically completed the draft of Assignment B. In the one-week study and cooperation of team members, the complete class diagram and state machine diagram of the QANTAS flight reservation system was drawn.

Drawing of class diagrams is difficult. I have identified fifteen related courses, which requires me to organize and collect many relationships between classes. This work took me a lot of time. The last problem I encountered was the multiplicity of all relationships. When I finished this chart, I was not sure if some of the multiplicities were correct. As a result, I published the chart in our discussion group. The other members of our team checked the chart and together we improved the class map for the QANTAS flight reservation system. I learned a lot in the group discussion.
After the tutorial feedback, we will improve and state machine maps for final distribution.

# data[].attributes.headline
Week 9 Individual Reflection by Jiazhi Lin 

# data[].attributes.subject
Week 9 Individual Reflection by Jiazhi Lin 

# data[].attributes.body
In this week's tutorial class we are asked to work on finishing the group assessment as it allows students to learn interactively. Moreover the researchers report that, regardless of the subject matter; students working in small groups tend to learn more of what is taught and retain it longer than when the same content is presented in other instructional format. There are number of possible reasons why students are asked to work in small groups. Some of them are as follows:

Generating a broad array of possible alternative points of view or solution to a problem. Giving students a chance to work on a project that is too large or complex for an individual. Allowing students with different background to bring their special knowledge, experience , or skills to a project , and to explain their orientation to others. Giving students a chance to teach others，and also giving students a structured experience so they can practice kills applicable to professional situations

# data[].attributes.headline
Week 9 Individual Reflection By JunKai Li

# data[].attributes.subject
Week 9 Individual Reflection By JunKai Li

# data[].attributes.body
In the week seven business requirements modelling lessons, we did a revision of all the UML diagrams. We are asked to watch two YouTube video, in order us to finish two quiz. After the quiz we did a text to identifies the  different between the those UML diagram.

In this weeks lecture a were  asked to have a mistake check to our Assessment B. We being continuously find out the mistake from the diagram. For example, not choose (diamond) in the activity diagram, wrong state name on the state machine diagram, wrong lifeline in the sequence diagram and not enough class in the class diagram. We finished all three state machine diagram before the lesson end. By working effectively on the assessment B with my group, I acknowledged that the responsibilities that I need to put on the work the important of teamwork. During the work, I have learned that when the time are limited, team working will became the key for us to be success. From giving different point of views, it assisted me to understand their ideas, which it helps in the decision making.

# data[].attributes.headline
Week 8 Individual Reflection By JunKai Li

# data[].attributes.subject
Week 8 Individual Reflection By JunKai Li

# data[].attributes.body
In the week seven business requirements modelling lessons, we learned the state machine diagram. The state machine diagram looks similar to the activity diagram. Which they both have the circle start point and end point, but I was wrong. The state diagrams are used in the area of embedded systems to help to see the life cycle of objects and thus help to provide a better understanding of state-based systems.Either it have the similar symbol with the activity diagram, but they all different. The lines of the state machine diagram are the transition. The rounded boxes represent the state of the object.

The activity of the tutorial lessons are all the same. We are asked to create a sample of the state machine diagram. It is quite difficult for me. I always select the wrong state name in the boxes. So I asked help from my tutor. She told me a quick way to fix this, that I can put a 'is' after the title to see is this sentence make sense or not, for example book(title) is borrow is correct, but check in(title) is check baggage is not.

Group discussion are always happened after the tutor lessons. We had a discussion of the sequence diagram. I found out that some of our group member still put database in the diagram. So I have to tell them to fix it again.

# data[].attributes.headline
Week 7 Individual Reflection by JunKai Li

# data[].attributes.subject
Week 7 Individual Reflection by JunKai Li

# data[].attributes.body
In the week seven business requirements modelling lessons, we learned a lot about the sequence diagram, which it is a part of the structural and behavioural diagrams. It is useful for the project development, because  it shows the interaction logic between the objects in the system in the time order that the interactions take place. We are told two different kind of the sequence diagram,  the system-level sequence diagrams and detailed sequence diagrams. There are many symbol in this kind of diagram, for example the lifelines, messages, message notation, returned message notation, Iteration notation, set of repeated actions notation and activation boxes.

We created a sample of the sequence diagram in this week's tutorial. It takes me a long time to understand and  create this diagram. The most challenge part of the creation are the lifelines. I put database in the diagram, which is not allow. I finally understand the rule of this diagram with the help of our tutor.

We having a group meeting at the end of the lesson to have a chat of the activity diagram we did last week. It is helpful for us to get fix of our own diagram as soon as possible.

# data[].attributes.headline
Week 9 Individual Reflection by Qijiao Chen

# data[].attributes.subject
Week 9 Individual Reflection by Qijiao Chen

# data[].attributes.body
We have no lecture courses this week and we also need to meet the final group assessment assignment. We were asked to turn in our soft assignment before Saturday and hand in our hard copy next week.Through this assessment, the team members can communicate well.
All of us did a lot of diagram, in my mind machine diagram is one of the most difficult diagram because when we did it we always confused about its structure. To be honest Kai helps me a lot until I finished it he also help me completed it and made my diagram more clear.This type diagram is a new challenge for me but I think I can understand it clearly during the assignment.

# data[].attributes.headline
Week 9 Individual Reflection by Vinsensius Kelvin Wang

# data[].attributes.subject
Week 9 Individual Reflection by Vinsensius Kelvin Wang

# data[].attributes.body
In this week's class, we were given the opportunity to elaborate and discuss on the various UML diagrams that we have been taught over the past few week.s We were given a set of questions in a quiz to test our understanding on UMl diagrams. I was able to complete the quiz with a perfect score after several attempts and understand furthermore on the UML diagrams that are taught towards us. We discussed on the different uses of each diagrams such as the state machine diagram which simulates all of the lifecycle of an object in a system, activity diagram which simulates the activities that are conducted in one use case, and other UML diagrams.

# data[].attributes.headline
Week 8 Individual Reflection by Qijiao Chen

# data[].attributes.subject
Week 8 Individual Reflection by Qijiao Chen

# data[].attributes.body
There is a happy week for me,because our teacher told us there is the last lecture class for this semester.It means that we will have more time to make our assignment.
In the lecture class,there are two new diagrams needed us to master. UML State Machine Diagrams is the topic statement in this week.State machine diagrams are used to describe the state-dependent behavior of an object and the trigger is like the "key", they are really close and the trigger is the cause of the transition.Therefore understand the conception of them is necessary.

# data[].attributes.headline
Week 8 Individual Reflection By Jiazhi Lin

# data[].attributes.subject
Week 8 Individual Reflection By Jiazhi Lin

# data[].attributes.body
In this week's class, we were introduced the state machine diagram.
The behaviour of an entity is not only a direct consequence of its inputs, but it also depends on its preceding state. The past history of an entity can best be modelled by a finite state machine diagram or traditionally called automate. UML State Machine Diagrams (or sometimes referred to as state diagram, state machine or state chart) show the different states of an entity. State machine diagrams can also show how an entity responds to various events by changing from one state to another. State machine diagram is a UML diagram used to model the dynamic nature of a system.
The reason why we use a state machine diagram is that State machine diagram typically are used to describe state-dependent behaviour for an object. An object responds differently to the same event depending on what state it is in. State machine diagrams are usually applied to objects but can be applied to any element that has behaviour to other entities such as: actors, use cases, methods, subsystems systems and etc. and they are typically used in conjunction with interaction diagrams.

# data[].attributes.headline
Week 7 Individual Reflection by Jiazhi Lin

# data[].attributes.subject
Week 7 Individual Reflection by Jiazhi Lin

# data[].attributes.body
In this week's lecture class we were introduced the sequence diagram.
A  sequence diagram  simply depicts interaction between objects in a sequential order i.e. the order in which these interactions take place. We can also use the terms event diagrams or event scenarios to refer to a sequence diagram. Sequence diagrams describe how and in what order the objects in a system function.
Overall UML Sequence Diagrams are interaction diagrams that detail how operations are carried out. They capture the interaction between objects in the context of a collaboration. Sequence Diagrams are time focus and they show the order of the interaction visually by using the vertical axis of the diagram to represent time what messages are sent and when.

# data[].attributes.headline
Week 8 Individual Reflection By Vinsensius Kelvin Wang

# data[].attributes.subject
Week 8 Individual Reflection By Vinsensius Kelvin Wang

# data[].attributes.body
In this week, we were introduced and were explained thoroughly on the state machine diagram. Based on a thorough explanation, the state machine diagram is a UML behavioural diagram which demonstrates the different states of objects that are changed by different trigger events in a class. The states machine diagram will show the various states of an object, what order it is demonstrated, as well as the trigger events that causes the change in state.

# data[].attributes.headline
Week 6 Individual Reflection by Jiazhi Lin

# data[].attributes.subject
Week 6 Individual Reflection by Jiazhi Lin

# data[].attributes.body
In the week 6 lecture class,  I learned what is a UML activity diagram,  Activity diagram is another important behaviour diagram in UML diagram to describe dynamic aspects of the system. Activity diagram is essentially an advanced version of flow chart that modelling the flow from one activity to another activity.
In the tutorial class we were ask  to evaluate on our mistakes that we have make in the assessment one, We found out that we used wrong enteritis in our ERD diagram and we miss the point in our introduction. After the evaluate on our mistakes, we trying to create an activity diagram using the knowledge that we learned from lecture class.

# data[].attributes.headline
Week 7 Individual Reflection by Qijiao Chen

# data[].attributes.subject
Week 7 Individual Reflection by Qijiao Chen

# data[].attributes.body
In week 7 our study topic is Sequence diagrams and we learned a lot of knowledge about the topic.Through the lectures, we learned a number of important symbols and techniques, such as lifelines, message symbols, returned message symbols, iteration symbols, and activation boxes. All of these factors form the basis of the Sequence diagram.
Through the last week of study, we have basically learned the basic structure of some diagrams.
This week's learning is different from the previous ones. We are exposed to System-level sequence diagrams and we should pay attention to the relationship between objects and actors when we study topics.
Sequence diagram notation - lifelines is a new challenge for me. At first I couldn't easily distinguish the boundaries. When I was making the diagram, I studied this topic carefully this weekend. I hope that this topic will be studied in the future. Learning to help me

# data[].attributes.body
This week, I learned how to create a UML activity diagram. We briefly introduced this type of chart and identified the various symbol hats included in the figure.
We were told to make a bug check on our assessment. We found that we added the wrong entity to the ERD diagram and put forward the wrong view in the introduction. After the error check, we made an activity diagram to practice chart creation. We are also asked to assess the mistakes we made in our assessment report. We have discovered a few mistakes we made in the report. We found that we added the wrong entity to the ERD diagram and put forward the wrong view in the introduction. After the error check, we made an activity diagram to practice chart creation.

# data[].attributes.body
In the seventh week, our research topic is sequence diagram. Through lectures, we learned many important symbols and techniques, such as lifeline, message symbol, returned message symbol, iteration symbol and activation box. We are exposed to system-level sequence diagrams, and we should pay attention to the relationship between objects and roles when studying topics.
In general, we have already understood the purpose and function of the sequence diagram, and the sequence diagram should define the sequence of events for a scene of the use case. We also briefly introduced a communication diagram that shows only the messages sent and received by the object, not their sequence.

# data[].attributes.headline
Week 7 Individual Reflection By Vinsensius Kelvin Wang

# data[].attributes.subject
Week 7 Individual Reflection By Vinsensius Kelvin Wang

# data[].attributes.body
In this week, we were introduced and explained briefly on the various types of sequence diagram as well as its uses. Based on what is taught on the lecture, we learnt a lot of important notations that is used in a sequence diagram such as lifelines, message notation, returned message notation, iteration notation, and activation boxes.

We've learnt that there are sequence diagrams such as system-level sequence diagram which shows the interactions between the actor and the system in a scenario of a use case as well as a detailed sequence diagram which shows the internal view of the use case.

Overall, we have understand on the purpose and role of a sequence diagram and that a sequence diagram should define the sequence of events of one scenario of a use case. We are also briefly introduced to a communication diagram which shows only the messages being sent and received by objects and not their sequence.

# data[].attributes.headline
Week 6 Individual Reflection by Qijiao Chen

# data[].attributes.subject
Week 6 Individual Reflection by Qijiao Chen

# data[].attributes.body
In week 6 lecture class teacher has teaches  us a lot of various diagram and some skills about sequence diagram.Besides the most important things that we should prepare is our assignment B. The assignment is different from last group assignment it need we use some methods and use various skills when we make our diagram.We also make some recommendation for our assignment. To be honest there are some new challenge for me in this week. For example it is really difficult for me to distinguish structural and behavioural diagrams at the beginning and I understand them clearly until after the tutorial. The team members of our entire team were also asked to assess the mistakes we made in the assessment report. I found that there are a lot of errors around the Use case. Although our final result is D, but some errors are very serious, so in the following assignment we will pay attention to the skill and accuracy of the use case.

# data[].attributes.headline
Week 6 Individual Reflection By Vinsensius Kelvin Wang

# data[].attributes.subject
Week 6 Individual Reflection By Vinsensius Kelvin Wang

# data[].attributes.body
In this week, I have been taught on how to create a UML Activity diagram. We were briefly introduced to this type of diagram and identify the various symbols hat are contained in the diagram such as the fork and join which allows simultaneous activities to be done at the exact time.

We were also asked to evaluate on our mistakes that we have done in the assessment report. We have identified several mistakes that we have conducted at the report such as the wrong entitites being mentioned at the ERD, not putting enough points at the introduction that furhter discusses on the topic, giving wrong points and documentations on the different appendixes. Moreover, we did pretty well in cooperating and being able to produce a report. In my opinion, i was anticipating for a P or a C from the report. Instead, I was given a D for my overall work.

This had satisfied me overall and given me a better chance to write a better report.

# data[].attributes.headline
Week 6 Individual Reflection by JunKai Li

# data[].attributes.subject
Week 6 Individual Reflection by JunKai Li

# data[].attributes.body
In the week six business requirements modelling lessons, we are told the different system development methodologies and how to create an activity diagram.
The system development methodology refer the framework that is used to structure, plan, and control the process of developing an information system. The activity diagram is similar to the swim-lane diagram  that I have study in semester 1. It is a diagram that is  used to show workflows of what happens in a workflow of a use case and what  can be done in parallel. We are also told we need to started to do the assessment B this week.

We were told to do a mistake check to our assessment. We found out that we putting wrong enteritis in our ERD diagram and wrong point in the introduction. After the mistake check, we did an activity diagram to practice for diagram creation.

Group meeting was happened after the tutorial lesson.  In order to start our assessment  as soon as passable. So we planed finish the writing of system development methodologies. Which kai will write SDLC, Jiao will write prototyping, Kelvin will write agile, Jiazhi will write waterfall and Oliver to write DevOps.

# data[].attributes.body
System development methodologies

§Systems Development Life Cycle kai

§Rational Unified Process (RUP)

§Rapid Application Development (RAD)

§Extreme Programming

§Scrum

§Waterfall Kelvin

§Prototyping(Jiao)
(http://www.itinfo.am/eng/software-development-methodologies/)

- Agile development methodology  Kelvin
- Waterfall development method Leo
- Rapid application development
- DevOps deployment methodology Oliver
(https://www.synopsys.com/blogs/software-security/top-4-software-development-methodologies/)

# data[].attributes.headline
Week 4 Individual Reflection by Jiazhi Lin

# data[].attributes.subject
Week 4 Individual Reflection by Jiazhi Lin

# data[].attributes.body
In this week's tutorial class we are asked to work on finishing the group assessment as it allows students to learn interactively. Moreover the researchers report that, regardless of the subject matter; students working in small groups tend to learn more of what is taught and retain it longer than when the same content is presented in other instructional format. There are number of possible reasons why students are asked to work in small groups. Some of them are as follows:

Generating a broad array of possible alternative points of view or solution to a problem. Giving students a chance to work on a project that is too large or complex for an individual. Allowing students with different background to bring their special knowledge, experience , or skills to a project , and to explain their orientation to others. Giving students a chance to teach others，and also giving students a structured experience so they can practice kills applicable to professional situations

# data[].attributes.headline
Week 4 Individual Reflection by QiJiao Chen

# data[].attributes.subject
Week 4 Individual Reflection by QiJiao Chen

# data[].attributes.body
In the fourth week of the course, the subject we studied was "Object orientation and UML." Through this week's lecture and tutorial courses, we learned about introductions, requirements gathering, functional and non-functional requirements, entity relationship diagrams, and use case knowledge.Learning this knowledge can help us better accomplish our assignment. I think the most important thing is to understand the questions about evaluation and the object-oriented paradigm. At first I didn't quite understand its meaning. Later, my team members explained the meaning of it. It is a chart of analysis system design.Of course, I am most interested in the Unified Modeling Language in this week's course. UML is the standard language for specifying and building artifacts for software systems. It is very necessary to learn how to apply it.
In addition, we have found many new challenges. First of all, from the perspective of the group, in the section on demand collection, we did not give examples of interviews and online surveys. Not only did I find this shortcoming, but the team leader of our group also mentioned this. Secondly, from my personal point of view, some functional and non-functional boundaries I did not understand very deeply led to many of the examples I gave when doing assignment1 are not very good.So this week my reflection center is to learn how to use UML as much as possible, and to better understand the difference between functional and non-functional use cases through communication with the team members.

# data[].attributes.body
In the fourth week of the course, we learned how to create a suitable ERD diagram. Explain what the object is, how the class works, how the object stores its data, and how they behave. After learning about the assessment, we learned about the object-oriented paradigm, which is a diagram of the analysis system design. The object-oriented example diagram has three parts, the top is the class name, the middle is the attribute, and the following attribute is the method. We are also told that a new kind of knowledge is called UML (Unified Modeling Language), which is the standard language for specifying and building software system artifacts. We also learned about inheritance, which is also explained in application programming and encapsulation, which basically hides the information that specifies the data and operations that are unique to the object.

In the fourth week of this tutorial, we refined the introduction, requirements collection, functional and non-functional requirements, entity relationship diagrams and use cases, and a large number of requirements collection methods. And many problems were found in the assessment and they were solved in class. First, some of the functional requirements and non-functional requirements are the same, and we have not kept them consistent. Finally, we used incorrect words in the use case diagram.

# data[].attributes.headline
Week 4 Individual Reflection By Vinsensius Kelvin Wang

# data[].attributes.subject
Week 4 Individual Reflection By Vinsensius Kelvin Wang

# data[].attributes.body
In this week, I have learnt a lot during lecture about the common issues in making the report we are assigned on. We are taught on how to create a good introduction, a great sampling on the requirements gathering methods and how to paraphrase most of the words used.we are also taught on how to create a proper ERD diagram, a proper use case diagram as well as its descriptions. We were also introduced to (OO) Object-oriented paradigm. We are thoroughly explained on what an object is, how classes works, how objects stores their data and their behaviour. All of these explanations are mostly the same as what we are taught in IPRG001. We are also taught on inheritance which is also explained on Applications programming and also encapsulation which is basically hiding the information on the data and operations that is designated to be exclusive to the object. We are also explained thoroughly on UML which is the unified modelling language. It was first implemented by Grady Booch, Jim Rumbaugh, and Ivar Jacobson. They proposed a better object management group which creates a standard UML for everyone to use. UML focuses mostly on creating a standardised set of diagrams for business uses as well as technological uses.

# data[].attributes.headline
Week 4 Individual Reflection by Junkai Li

# data[].attributes.subject
Week 4 Individual Reflection by Junkai Li

# data[].attributes.body
In the week four business requirements modelling lessons, we are told to do an assignment progress review on the both parts. In this lessons we learned the common issues on the introduction, requirements gathering, functional and non-functional requirements, entity relationship diagram and use cases, common which it help us in doing our own assessment. After learning the issues of the assessment, we learned the object-oriented paradigm, it is a diagram that analyse the design of a system. There are three parts in the object-oriented paradigm diagram, the top of it is the class name, the middle is the attribute and the the one under the attribute is methods. It is similar to what I have learned in the programming lessons. We are also told a new knowledge call UML(unified modelling language), which is is a standard language for specifying and constructing the artefacts of software systems.

After the lecture lessons we focused on our assessment. Based on the week 4 lecture powerpoint we found out lots of problem on our works. Firstly, in the requirements gathering methods parts, we did not put the example for interview and the online survey. Secondly, some of the functional requirements and non-functional Requirements are the same, and we did not put consistency on it. Thirdly, we used incorrect word in the use case diagram. For example, payment should be written paying for the flight booking. Lastly, Jiao wrote the conclusion to a reflection. In solving this problem, we have a group meeting on Thursday tutorial lesson and  rewrite the conclusion.

# data[].attributes.headline
Week 3 Individual Reflection by Jiazhi Lin

# data[].attributes.subject
Week 3 Individual Reflection by Jiazhi Lin

# data[].attributes.body
This reflection will summarize what I have learnt in week 3 lesson. During the lecture class I have gain some basic understanding on the use case diagram, then on the tutorial class, we did a Kahoot quiz which is all about the knowledge that we learned from last week, it helps me to review and consolidate the understanding on ERD diagram.

After the quiz, we learnt some example on the use case diagram, then I actually make a use case diagram of the UTS library system by myself.

For our group，we decided to have a meeting on Friday to discuss about the assessment and to finish some work together for example the use case diamgram of the Qantas flight ticket booking system.

Challenge

While doing the assessment，I found that it's hard to find a time that everyone is free to hold a group meeting.Also everyone has their own ideas on completing the assessment
its quite improtant and quite hard to decide who's idea is the best for this assessment.

# data[].attributes.headline
Week 2 Individual Reflection by Jiazhi Lin

# data[].attributes.subject
Week 2 Individual Reflection by Jiazhi Lin

# data[].attributes.body
This reflection will summarize what I have learnt in week 2 lessons. During this lesson I understand how to use and make a Chen’s ERD Diagram for the UTS library system.

I have joined a group with other four members which are Kelvin, Kai, Jiao and Oliver, after our group discussion we decide to divides our assessment into several parts and each of our group members will take at least one part to finish with. For example, I am responsible for completing the introduction for our report.

Challenge 1

For a group assessment, I believe that the most challenge part is that everyone in the group knows what they need to do and finish it on time especially for our group, most of us don’t speak English as their first language, it’s quite importance to get overcome the language barrier.

Challenge 2

Another challenge for a group assessment is that the coordination costs represent time and energy that group work consumes that individual work does not, including the time it takes to coordinate schedules, arrange meetings, meet, correspond, make decisions collectively, integrate the contributions of group members, etc. The time spent on each of these tasks may not be great, but together they are significant.

Coordination costs can’t be eliminated, nor should they be: after all, coordinating the efforts of multiple team members is an important skill. However, if coordination costs are excessive or are not factored into the structure of group assignments, groups tend to miss deadlines, their work is poorly integrated, motivation suffers, and creativity declines.

# data[].attributes.headline
Week 3 Individual Reflection by JunKai Li

# data[].attributes.subject
Week 3 Individual Reflection by JunKai Li

# data[].attributes.body
This reflection report will summarise my week three Business requirements modelling lessons and the group meeting. In the lecture lessons we gain a  clear understanding of how to draw a use case and write a use case descriptions. I found out that is a huge different between the use case we have learn in semester 1 introduction to information system lessons. The major different of them are the include and extend relationship of one use case to another use case.For the use case description, we are required to write post-conditions and pre-conditions this time. In the tutorial lessons, we did a Kahoot quiz to revises the knowledge that we learn in lecture, after the Kahoot quiz, we did an example of the use case and use case description for the UTS Library system.

We have a new member joining our team, which is a good news and it is also a bad new. Good new is for some of the part we can have more people to do, but bad new is we need to do 10  more answers for the online survey. After our last lesson on Thursday, we decided to meet on Friday in the build building to finish up our use case diagram and the entity relationship diagram. Firstly, we meet on the building on level 4 and do it on the in search computer. Secondly, we divided the work to Jiao, Oliver and Leo to think of the use case for the use case diagram, Kai finish up the entity relationship diagram. The entity relationship diagram did not takes me too many time to finish, so as I finish entity relationship diagram, I started to help on the use case diagram. We finished all the diagram at 2pm and we  dismiss after we discuss what we only have functional and non-functional requirements, use cases descriptions and conclusion left.

Challenge 1
The only and biggest challenge of this week are creating the use case and the entity relationship diagram. Both of the diagram takes time and hard to do. To solve this problem, we separated to two little team me and Kelvin in one team to do the entity relationship diagram and JIao, Leo and Oliver to do the use case diagram. The reason of separate a team to two little team are we can have two teams to brainstorm in their own work to increase our speed to finish the assessment. After brainstorming we swap the work to make sure we have all the information right.

# data[].attributes.body
In the third week, I learned a lot about using and understanding the use case diagram. After our last class last Thursday, we decided to hold a meeting in the building building on Friday to complete our use case diagram and entity relationship diagram. First, we met on the 4th floor building and searched on the computer. The reason for dividing the team into two small teams is that we can let the two teams brainstorm in their own work to improve the speed at which we complete the assessment. After brainstorming, we exchange work to make sure we have all the right information. We completed all the charts at 2 pm and we dismissed after we discussed only the functional and non-functional requirements, use case descriptions and conclusions.
One of the challenges we have to overcome is to finally create a completed report before the tutorial. This reflection report will summarize my third week of business requirements modeling courses and group meetings. I found that the use cases we learned in the introduction of the information system course in the first semester were a huge difference. The main difference between them is the inclusion and extension of the relationship between one use case and another.

# data[].attributes.headline
Week 3 Individual Reflection By Vinsensius Kelvin Wang

# data[].attributes.subject
Week 3 Individual Reflection By Vinsensius Kelvin Wang

# data[].attributes.body
In week 3, I have learnt a lot in using and understanding the use case diagram. Based on the lecture that is taught to us,  there are various symbols that are assigned to each elements of the use case diagram such as an oval which represents a use case diagram, a stick figure to represent an actor, and a rectangular box to represent the system .
In addition, in class, we also did a Kahoot! quiz which revises on our understanding of the use case diagram.  On the tutorial, we are also asked to use Microsoft Visio to understand how to create a use case diagram easily and understand how to form new factors using it. We were taught on how to create a use diagram the right way by making use of all of the different symbols available. There are also new matters that are taught to us such as the 'include' use case, which is an additional use case used for an action that is necessary for the use case attached to it to be done, as well as the 'extend' use case, which is an additional but not necessary use case attached towards a use case to show a possibility of the 'extend' use case in being conducted.
One of the challenges that we have to overcome is to finally create a finished report before the tutorial so that we can show it to our teacher and obtain an evaluation from it.

# data[].attributes.headline
Week 3 Individual Reflection by QiJiao Chen

# data[].attributes.subject
Week 3 Individual Reflection by QiJiao Chen

# data[].attributes.body
This reflection will shows what I have learned in the third week. The topic of this week is"Use case". It is really a good topic for me,because I have learned something about this topic last semester. However, when I saw the lecture and tutorial files I find the assignment is really difficult. So I think there is a new challenge for me. But I also believe we can learn it well and do our assignment better.
Firstly, in lecture class all of us learned a lot of ways about how to use case and we all understand the most important part of use case after the lecture class. In my mind, the most important part is how to make Use case diagram.Therefore, I thhink we must distinguish the difference of 'Include'relationship and ‘Extend’ relationship. It is really important,because when student make use case diagram they should link all the elements and use different line.
Secondly, in tutorial class we actually make use case diagrams and all of our group members try to do our assignment. Kai made a really nice diagram about Quatas flight booking system before the class. After the class he showed us the diagram, to be honest the diagram is really useful for us, I had a good idea after he showed that. Then we talked about each other, finally we decided have a meeting of our assignment on Friday.
Finally, we meet each other and make the group assignment together on Friday. The most difficult part is that we should think a lot of new ideas of Quatas's flight booking system and we spend a lot of time to do the second diagram better, every line and every part are similar. However when we finish the diagram, everyone feel relax and happy. The two diagrams are very useful for our assignment. Through these two week I have learned so many new knowledge and I am prepare to do conclusion on next week!
Challenge 1
We only have 26 replys of the survey so we should collect more answers as soon as possible.
Challenge 2
The intruduction of the assignment is really important and hard I think we my group member do it I can give him a lot of good ideas.

# data[].attributes.headline
Week 2 Individual Reflection by Vinsensius Kelvin Wang

# data[].attributes.subject
Week 2 Individual Reflection by Vinsensius Kelvin Wang

# data[].attributes.body
In week 2, I have learnt a lot in using Chen's ERD Diagram. I have formed an ability in understanding each and every symbols that are assigned to an entity, cardinality, as well as other ERD-related symbols. Also, in this week, I have also learnt on the different types of cardinality such as one-to-many relationship, many-to-many relationships, as well as one-to-one relationships.

To add up, we formed a group in this week which includes me, Kai, Oliver, and Jiao. We assigned each and every member of the group with tasks and we have planned several group meetings for our assignment. We have also started to get to know each other thoroughly and able to cooperate with one another in this week and hopefully the following week.

There are also several challenges that I have faced throughout this week. One of them is that is that there is a language barrier between me and my group members. Most of them mainly speaks Chinese as their first language while me, on the other hand, speaks mainly English and Indonesian. Another challenge that I have faced is that we have different social media platforms which thus made our plans and other group-related aspects harder than to be expected

Also, in week 2, a Kahoot! quiz is conducted in order for us to reflect upon what is taught on the lecture in Week 2. I have siccessfully obtained a satisfying mark on the Kahoot! quiz as well as able to understand more on the various aspects on Chen's ERD diagram.

# data[].attributes.body
There are 4 members in our group (Kelvin, Kai, Jiao, Oliver). After our group discussion, Kai, as our leader, divides our tasks into several parts, and we are responsible for completing the respective parts according to this plan. For example, I will write the imported part separately. The remaining parts, functional and non-functional requirements, entity relationship diagrams, use case diagrams, use case descriptions and appendices will be completed by all team members.

It is inevitable that problems are encountered in teamwork. I think that disagreement and delayed tasks are the most likely problems in teamwork. Therefore, communication is very important. In addition, if you are unable to solve the problem after the group meeting, we will use WeChat to communicate. This is a very convenient and effective method of communication.

In this lesson, we did a sample of the ERD diagram (the version of Chen) for the UTS library system, which is still the knowledge I learned in class. Entity - A diagram consists of four important parts: entities, attributes, relationships, and cardinalities. The symbols used in each section are also different. For example, an entity is a square symbol, an attribute is an ellipse, and a relationship is a diamond.

In the tutorial course, I joined Kai and Kelvin their original team, which is good news for me, with a group of better team members to complete the project together. Kai decided to plan interviews and surveys will be the two methods used in the demand collection method, so Kai created Surveymonkey and asked us to forward it to our friends to complete the survey.

Challenge 1
It is inevitable that problems are encountered in teamwork. I think that disagreement and delayed tasks are the most likely problems in teamwork. Therefore, communication is very important. In addition, if you are unable to solve the problem after the group meeting, we will use WeChat to communicate. This is a very convenient and effective method of communication.

The ER diagram I made in class is shown below.

# data[].attributes.headline
Important to read before you write your Reflection 

# data[].attributes.subject
Important to read before you write your Reflection 

# data[].attributes.body
1. At the end you should have minimum 3 posts, one from each week

2. Pls post your Reflection in Green
Border between   Assignments in Blue
Assessment Plan in Yellow
Important Note in Red

What should be in the ur Reflection ?
3.  Outcomes :

2.1 Describe the meetings
2.2 Summarise all the main achievements/outcomes from this week, both as a group, and from your individual work.

4. Process :

Reflect on your learning progress, and learning and/or group work
For Example
- What did you do to learn and progress?

- What strategies or resources did you use to progress in the assignment, both individually and as a group?

- What did you find challenging in contributions that you described in Q1?

- Did you struggle with anything?

- How did you or your group solve it?

- How did you go about your learning and progress in this assignment?

Mark each of your posts clearly with your name and week number.

# data[].attributes.body
Assessment 1

Business/System Requirement Specification Report

Qantas Flight Booking System

1. Introduction / Oliver & Leo
2. System Stakeholders /Kelvin & Kai
3. Requirements Gathering Methods / Kai & Jiao & Oliver
4.1 Functional Requirements  N*4
4.2 Non-functional Requirements  N*3
5. Entity Relationship Diagram  N*3
6. Use Case Diagram  N*4
7. Use Cases Descriptions
8. Appendix
9. Conclusion / Jiao
10. References

https://docs.google.com/document/d/1CxIwCKIQDvsHdelKGvo-trldfgr6RjKGhHd11_6zucs/edit?usp=sharing
Google doc (Pls access with ur UTS email address)

# data[].attributes.body
Qantas Flight Booking System

System Stakeholders

1. Customer
2. IS Manager Team
3. Employee
4. Airline Manager
5. Airport Manager
6. Media ?
7. Suppliers ?
8. Government
9. Airline Unions
10. Bank ?
11. Client
...

- List as many system stakeholders as you can
- Identify and explain why such a list would be important in creating a requirements specification report such as this one.（One sentence）

# data[].attributes.body
Qantas Flight Booking System

Functional Requirements & Entity Relationship Diagram

4.1   Functional Requirements

- At least [n x 4] functional requirements for the system.
- At least [n x 2] of them must be new, using at least 2 different requirements gathering methods showed in section 3

4.2   Non-Functional Requirement

- List of at least [n x 3] non-functional requirements

5   Entity Relationship Diagram

- [4*3] entities with attributes, and their relationships and cardinalities

# data[].attributes.headline
Week 2 Individual Reflection by JunKai Li

# data[].attributes.subject
Week 2 Individual Reflection by JunKai Li

# data[].attributes.body
This reflection report will summarize what I have study in week two Business requirements modelling lessons. The purposes of writing this report can remind me the knowledge that I study in lecture and tutorial lessons, and it can also present me some useful suggestion that I can work better next time.

In the tutorial lesson, me and my original team member Kelvin have gain two more member from the class, which it became a such a good news for us. Firstly, based on the Assessment A we made a plan for each part on padlet.  We planned that the introduction(Oliver), system Stakeholders(Kelvin), requirements gathering methods(Kai) and conclusion(Jiao) can be written separately. The rest of the part, functional and non-function requirements, entity relationship diagram, use Case Diagram, use cases descriptions and appendix will be done by all of the team member. In the lesson we  did a sample of the ERD diagram(Chen's version) for the  UTS Library system, which it has remain me the knowledge that I study in class. For example, circle is attribute, rectangle is entity and diamond is relationship. I started to write my assessment on Friday after I finish all my lesson on Thursday. I planned that interview and surveys are the two different method that I will use in the requirement gathering methods, so I created a survey on Surveymonkey(https://www.surveymonkey.com/r/VVZTF9J) and a interview guide, in order to get the user feedback for the Qantas flight booking system.

Challenge 1
During the meeting, it is important that people can still remember what to do after the meeting, so I take the role as a note recorder to maintain a permanent record of what me and my team member have read or discuss in the meeting. I find hard in communicate with my team member when I group with another team in semester 1. This time we created a discussion group on WeChet to prevent lack of communication happen in our team, because it maybe the direct cause of numerous problems that can cause dysfunction in the team.

Challenge 2
The most challenging problem are using padlet. When the first time I post  note on padlet, it makes me feel so annoying, it is not only because it is such a new method for us to learn and it makes me feel bewildered as I look at the  structure of the note. To solves this problem, me and my team decide we should use different colour in different type of note, in order we can find them easily, so we  posited our reflection in Green, assessment plan in Yellow and important note in Red.

# data[].attributes.headline
Week 2 Individual Reflection by QiJiao Chen

# data[].attributes.subject
Week 2 Individual Reflection by QiJiao Chen

# data[].attributes.body
This reflection will illustrates what I have learned in the second week. The topic of this week is"Gathering Methods and ERD". There are four group members in our group. Luckily,it is different from last term that we just have two group members in our group. This time I joined Kai's group, we are classmates last term I think he is really a good student and he always has a lot of useful methods. When we confirmed our group,Kai began to write all the assessment plan and assign tasks to us.

I was assigned the task of making a conclusion. To be honest,this part is my favourite part,because I like make summary after read something. So I believe I can do it try my best and I can do it very well. In the tutorial lesson,we deeply learned what is the differences of functional and non-function and we also learned a lot of diagrams.In the end of the lesson, I tried to do a ERD diagram for library system.

Challenge 1
As a group summary personnel, the most important thing is to listen carefully to the group discussion content. Last semester, there were only two people in our group, so the work was not evenly distributed and the layout was quite chaotic. This time we created a discussion group on WeChet, which allows us to discuss it in real time, in order to prevent a lack of communication on the team, which can lead to layout chaos and work efficiency.

Challenge 2
The most challenging problem is that the content of this semester is brand new, which will feel a little strange at first. Besides, I have to use the brand new software padlet, which will not work well at first.

# data[].attributes.body
Qantas Flight Booking System

Requirements Gathering Methods

Surveys & Interviews
Interviews* 8

Surveys*50
https://www.surveymonkey.com/r/VVZTF9J

- 2 different requirements gathering methods
- At least 4 sources/articles (with
in-text referencing)
- One paragraph for the overview of the main findings