# data[].attributes.body
In week 2 study, we focus on the topic with requirement gathering and ERD(entity-relationship diagram). As requirement gathering, there are a lot of forms to present it e.g. surveys. interview. For the ERD we do so much practice in the lucidchart and i also get some understanding with entity, attributes, primary attributes, relationship and cardinalities. But i also find hard with the ERD, as a result i need to practice more with other topic connecting to the business and be prepared for the assignment work with my teammates.

# data[].attributes.body
In week 3 's study. we discuss the assignment work and focus on the topic with "use cases", it include the use case diagram, use case descriptions and use case relationship. For the use case diagram i still find hard in the structure with the diagram and the "extend" and "include" relationships. After the class, i would do more practice on the use case diagram and get more understanding on the use cases relationships with classmates.

# data[].attributes.body
It took a few days for me to contact with the members of the group, because I was busy at the moment when the teacher facilitated initial group. But after send email to teacher, i quickly sent email to one of the group and offer to create a webchat group. But after that we didn't do anything relating to assignment too much, because we dicide to do it in week 3.

# data[].attributes.body
In week 2's meeting, we have discussed part 3 and 5 of this assignment which requirement gathering method and entity Relationship Diagram for the airline booking system(ERD), everyone has given their valuable idea about which method is more effective. To be honest, ERD is quite a challenge part for me, because it's a piece of new knowledge, the entity, attribute, relationship, it takes me time to understand it, but my group members are all activity to help me. At the end of the meeting, we decide to collect the functional and non-functional requirement for the system after this meeting.

# data[].attributes.body
In week 3‘s meeting, Our main goal is to classify and summarize functional requirements and non-functional requirements, We created a Google shared document to complete this part. Each member puts the part they find in the document that is because multiple people can edit the same copy of Google Docs, which is a very convenient function. We review the requirements that we have summarized one by one then make comments. I personally think that new requirements are a bit hard to find. Use case diagrams are another goal of ours. The addition of ‘extend’ and ‘include’ brought us some confusion at the beginning, but after combining the knowledge in the class, we have a deeper understanding.

# data[].attributes.body
1)     In this week, we have created the group of Assignment Part A with 4 members in the tutorial. After the tutorial, we created a group chat and invited other members to the group, and then we made the chat communication through Messenger on the mobile phone. In this group meeting, we discussed each part of this assignment and what we need to do, and in the end, we decided that we would do each part together instead of someone choosing certain parts to complete.

2)     For the lecture, I have learned requirements gathering, ERD model, some elements of ERD such as entities, attributes, and relationships, etc. and understand how to draw the ERD notations through watched the PPT of week 2. For some problems which I cannot understand, I can search them on Google and find answers. In the tutorial, we have reviewed the knowledge in the PPT and Kahoot quiz about what we learned. Kahoot quiz is interesting, we get scores by answering questions. We got scores for correct answers, zero points for wrong answers, and ranking. The importance is that the number of correct answers is related to our results this semester, so I need to answer the questions seriously. And then we practiced ERD drawing, but I was confused about the arrangement of each element and the beauty of the model, so I looked at some examples of the ERD model and found some good models in the Hall of Fame on the Canvas to improve my model.

# data[].attributes.body
Screenshot of our group

# data[].attributes.body
1)     In week 3, we continue to make group meetings through a chat conversation, it was decided that we should do the fourth part of this assignment firstly, which is function and non-function requirements. Each member wrote out some requirements, and then we created a Google document to facilitate sharing our ideas.  Then we found a problem, which is the number of function requirements is at least 16, but we listed more than 20 requirements in total, so we had to choose some better ones. Therefore, we have considered each requirement and excluded some inappropriate requirements. Through this group work, I found that the group is very efficient. Several members put forward many ideas in a short period of time. When we encounter disagreements, some people will provide opinions and reasons or find a shortage in the assignment, we will provide suggestions to correct them.

2)     In the lecture, I understand use case models, identify some elements in the use case model, and learned how to make use case description and draw the use case model. I watched the PPT weekly because the important knowledge is in there. For the tutorial, like last week, we still did lecture revision and a Kahoot quiz. And in the class, we also evaluated some ERD diagrams from the Hall of Fame and analyzed some of the mistakes, which is very helpful to correct my ERD. Finally, we did use case diagram exercises. Although the use case diagram is not very complicated, I will also watch some examples of use case diagrams on Canvas to help me think about use cases.

# data[].attributes.body
1)     Because we will submit the assignment in week 4, so we only have one week left to complete this assignment. This week, we use Google document to share our works and we did the work together through the Zoom meeting. We have to finish the entities relationship diagram, use case diagram, and use case description, therefore, we decided to make a group meeting every day. At about 8 pm every night, we will open the Google document and use the Zoom meeting to complete our assignment. We considered entities and attributes about the Airline booking system together and confirmed every entity is correct. To make the entity-relationship diagram is difficult and complicated, Chris Le is mainly responsible for making use case diagram, and then we provide some suggestions on which entities to use, attributes and how to arrange them by sharing his screen. We also searched for some airline websites as references to help us provide opinions. We spent a total of about two days to make the entity-relationship diagram, and then completed the use case diagram and use case description. After that, we designed survey questions together, and then these questions were sent to friends in the form of links. In the end, we got more than forty surveys. We also designed interview questions. We interviewed each other and also interviewed friends through social application. On the Sunday, I finished introduction and other members completed summaries of requirements gathering methods. Hope we will get a good result. In this assignment, almost every part was completed by the four of us, which made me realize the advantages and importance of group work. And because one of the members is Vietnamese, we use English to communicate most of the time in the group meetings, which is very helpful to improve my speaking and listening skills. During the boring drawing period, we also talk about the interesting culture of our country, so this group assignment is a great experience.

2)     In the PPT of this week, there are some great suggestions about how to do well in the assignment, this is helpful to complete the assignment. And I have learned object-oriented paradigm and understand classes and objects, as well as their attributes and operations, finally, I learned the knowledge of UML. In the tutorial, we still conduct a lecture revision and Kahoot quiz first. We then evaluated some use case models from the Hall of Fame and pointed out errors and provided suggestions. Similarly, I will use the same criteria to check my use case model and correct it. At the end of the online class, the miss divided the members of our group into a group chat channel, and we discussed what we need to do in the next few days and decide the time for the next group meeting.

# data[].attributes.body
In week 4 study,  we studied various  thing about the assignment which include the gathering requirement, functional requirement ERD to prepare for the assignment. Actually, i also find difficult in drawing ERD but the tutorial class was really helpful for our team to do the assignment together. Before we start in we plan a timetable for each part to finish everyday. In the evening we would have a meeting for do the assignment and discuss each other. In my opinion, group meeting was efficient for out team to make it perfect. We gave our personal suggestion, solve the problems find the new things also have good relationships with each other. Therefore, i though the Assignment 1 is corking for each one. Everybody make effort for it also get a lot from it. Actually i also put a lot of works and effort in our team work. I am looking forward to the assignment 2 with my teammates and make it wonderful.

# data[].attributes.body
Mail for finding team members

# data[].attributes.body
tryin' to contact team members

# data[].attributes.body
doc google which we use for put information and draft

# data[].attributes.body
At the first day to start doing the assignment, we got a little trouble about the communication app. First we tried to use webchat, but my laptop can't use the webchat application so we change to messenger. But Jack can't hear other members talking, so we decided to use Zoom. Zoom was such a good application to have a group meeting but it also has a limitation that we only can use zoom for first hour. Finally, we change back to Webchat to discuss and only use Zoom when we do diagrams together.
So at this week, we think about how we gonna do this assignment, there are few opinions (divide the work, do it together,v.v) but after all, we did some tasks together then divide the work into some particular tasks.  And it's quite convenient that we use the doc google as a draft for our team before we put every completed work to the doc file.

# data[].attributes.body
In this week, we really focus on speed up the team work. We usually spend 2-3 hours per day to do this assignment together. At the beginning we had little trouble about understanding differences of some theory definitions. But after joining lecture and sent email to the teacher, we know what exactly what we should do to improve our assignments. About collecting data, i ask all my friends on my facebook to do survey and besides interview myself and my best friend. It's little struggle to me, because sometimes i need to fix work of team members. And tryin' to find a good way to divide the work. But after all, i think me and my team have done a good work.

# data[].attributes.body
ask my friend to do survey

# data[].attributes.body
ask my friend to do survey

# data[].attributes.body
interview my friend

# data[].attributes.body
The fourth week is our sprint week. The use of zoom and google doc has greatly improved our work efficiency. Together we decided on the content to be used in survey and interview, and helped us collect responses through the Surveymonkey website, and collected responses from more than 40 people in total. Then we contacted our friends for interviews. The part of the use case description is not so difficult under the clear use case diagram. But when describing the process, you still need to confirm the order of each step and think about the connection between them. Because we need to come up with an alternative plan

# data[].attributes.headline
Please see assignment feedback in the first column

# data[].attributes.subject
Please see assignment feedback in the first column

# data[].attributes.headline
Please see assignment feedback in the first column

# data[].attributes.subject
Please see assignment feedback in the first column

# data[].attributes.headline
Please see assignment feedback in the first column

# data[].attributes.subject
Please see assignment feedback in the first column

# data[].attributes.body
1)     For assignment B, we are also the same group member to complete it, so we continue to talk about this assignment in the same chat group. This week, in the Zoom meeting, we have corrected and completed the use case diagram and individual descriptions through reading the feedback from our teacher on the Padlet.

2)     During the group meeting, we read the feedback from the teacher and corrected the mistakes based on the feedback. The feedback is clear in the report, through the group discussion, we can easily correct the use case diagram and descriptions. Because this week is the beginning of assignment B, we did not meet some difficulties, I hope we can keep high efficiency and complete this assignment together.

# data[].attributes.headline
Screenshot about correct use case diagram in Zoom

# data[].attributes.subject
Screenshot about correct use case diagram in Zoom

# data[].attributes.body
1)    This week, it is inconvenient to conduct a voice conference because there is a problem with a member's network. So, we discussed we need to do an activity diagram this week in the chat group. Because the activity diagram is an individual task, I completed it in my free time and uploaded it to the group Google document.

2)    In the lecture, I understood the purpose and role of sequence diagrams. And I have learned some elements of sequence diagrams such as actors, objects, boundary objects, messages. And then I also had some revisions about assignment B which are use case diagram, class diagram, activity diagram, and methodologies. In the tutorial, we still did the lecture revision and Kahoot. And then we looked at the activity diagrams from Hall of Fame and compared them with our diagram. I am honored that my activity diagram has also been selected into the Hall of Fame. Finally, we have practiced creating a sequence diagram, but I did not have enough time to complete it, so after the tutorial, I search some sources about making sequence diagram on Google and finish it.

# data[].attributes.headline
Screenshot about have a conversation in the WeChat group

# data[].attributes.subject
Screenshot about have a conversation in the WeChat group

# data[].attributes.body
1)     On weekends, we made a group meeting on the Microsoft Team to talked about how to create a sequence diagram and state machine diagram. The sequence diagram in this assignment is also an individual task, so we just talk some details about this diagram and completed it respectively after the meeting.

2)     The sequence diagram is not too hard to make, but there are a lot of steps between the object, it is troublesome to connect arrows and write messages. Finally, we completed our sequence diagram and upload it to our group Google document. For the state machine diagram, it is not relaxing. We listed two objects about this diagram and tried to make some states, but we still were not sure what states and triggers can be made. Finally, we decided to ask the teacher in class next week and look at the state machine diagram in the Hall of Fame.

# data[].attributes.headline
Screenshot about try to make state machine diagram on Microsoft Team

# data[].attributes.subject
Screenshot about try to make state machine diagram on Microsoft Team

# data[].attributes.body
1)     For this assignment, we have finished four parts which are the introduction, state machine diagrams, class diagrams, and system development methodologies. So, we decided to make a group meeting on Microsoft team every day. We planned to make state machine diagram after tutorial on Wednesday because we want to compare some state machine diagrams form Hall of Fame, and then complete our diagrams.

2)     We finished the class diagram on Monday, we first listed some classes in Google document, then a member shared the screen through the Microsoft team, and finally, we completed it together. On Tuesday, we did system development methodologies, each of us chooses a development method from PPT in lecture, we searched the sources about the method we choose, and then wrote a research of each method as requested. On Wednesday, during the tutorial, the teacher told some details about making the state machine diagram through check the diagram from Hall of Fame. And she gives us some time in the tutorial to do some works on assignment B. So, we had the discussion and made state machine diagram in the tutorial, then teacher joined our group chat, she corrected some mistakes in the diagram and provided some recommendations, this is very useful to complete the diagram. I think the state machine diagram is so hard, we spent a lot of time discussing which state and the trigger can be used, and we also looked at the knowledge in the lecture and searched for sources about making diagrams on the Internet. In the end, we have completed 2 state machine diagrams. On Friday, we finish the introduction of this report and check and correct every part of this assignment. Therefore, we finished the whole work for this assignment, we are all good at this assignment, so hopefully, we will have a good mark.

# data[].attributes.headline
Screenshot about make class diagram on Microsoft Team

# data[].attributes.subject
Screenshot about make class diagram on Microsoft Team

# data[].attributes.headline
Screenshot about make state machine diagram on Microsoft Team

# data[].attributes.subject
Screenshot about make state machine diagram on Microsoft Team

# data[].attributes.headline
Screenshot about list some classes of class diagram in the Google document

# data[].attributes.subject
Screenshot about list some classes of class diagram in the Google document

# data[].attributes.body
In this week, we used ZOOM to host the meeting. The goal of this meeting is to amend and improve our Use Case Diagram and use case descriptions by study and discuss Teacher's feedback from the last Assessment. For the meeting, firstly we have read through the feedback of use case diagram and description, then we marked where the problem down and start to discuss how to amend it. The benefit of a group discussion is we can have a more neutral perspective to view others work, it helps us to find out those problems that are hard to perceive by ourself. At the same time, it also helps to improve our tacit understanding at work.

# data[].attributes.body
At this week, we decided to plan a good schedule for finishing the assignment. So we agreed that everyweeks will spend 1 day to finish the tasks in template which we've already learned. This time, we did better, we changed to use another software (microsoft team), have more time to focus on the task, still use the doc file google to keep the work. First week, we did re-correct the use case diagram and description. Then next is activity diagram. Then after all, we evaluatede what we had done after that day, by giving perspective to others to improve what we had done.

# data[].attributes.body
In week 6 we discuss the part 2 of the assignment B which is the “use case diagram and descriptions” by using the Zoom.  For the “use case diagram and descriptions” we just fix the problem what the teacher gave us the feedback from assignment A. We are according the feedback to make our diagram and the description more integrated by using two days which are on Friday and Saturday. Actually, i have learnt more things during the meeting with my teammate. For example, they help me to fix my use case description and we planed we were going to have meeting on weekend for the assignment B.

# data[].attributes.body
In week 7 we discuss the part 3 of the assignment B which is the “Activity diagram”. Actually,  our plan is to finish the activity diagram and the sequence diagram both. But Chris’s network is not working during the weekend. Therefore we just do the individual activity diagram from our own use case. After I finish my activity diagram, I send my diagram to my tutor and ask her to give me some feedback. And I accord to tutor’s suggestion and fix my diagram correctly.

(For lecture and tutorial)
we discuss the assignment B content and request together which include the use case diagram, class diagram, activity diagram and system methodologies. However, we main studied the purpose and role of the sequence diagrams, design interactions between object in the systems in lecture. Also, i need to create a sequence diagram by a book system in tutorial. For the lecture content I find easy to understand for me but create the sequence diagram is hard for me. For example, like message notation, Iteration notation and set of repeated actions notation.

# data[].attributes.headline
The email content of tutor's feedback from the diagram.

# data[].attributes.subject
The email content of tutor's feedback from the diagram.

# data[].attributes.body
In week 7 we discuss the part 4 of the assignment B which is the “Sequence diagram”. Actually, we talk about a little bit detail for the state machine diagram. Because it was hard to understand and make it. Therefore we spend more time to make the Sequence diagram. The sequence diagram is also the individual works. We just use the Microsoft Team to have chat and voice together. During the meeting, I ask my group member to help me to make it. For example, like we discuss the scenario and the object of my sequence diagram and make it correct. After we finish, we share our sequence diagram and gave the advice for the diagram.

(For lecture and tutorial)

In week 8 we go through the group assignment B progress which talk about the most common mistakes in tutorials. In lecture, I have learnt about the purpose and role of state machine diagrams include the object’s states, patient and the notation for the state machine diagram. In tutorial, tutor introduce to us how to create a sequence diagram for the book. After the tutorial i still confuse about the patient and the notation of state machine diagram because it’s so difficult to understand and complicated. As a result, I need to spend more time to discuss with my teammate.

# data[].attributes.body
In week 9 we discuss the part 1, 5, 6 and 7 of the assignment B which are “Introduction”, “State machine diagram”, “Class Diagram” and “System Development Methodologies” by using Microsoft teams. Because we had some accident from last few week. Therefore we need to finish four parts for one week which we need to have meeting everyday. For the introduction part, we separate two groups to research information online and finish it spend one night. For the “State machine diagram” and the “Class diagram” we were making as group. Compare with the class diagram, i think State machine diagram is harder to make it. We watch the lecture and use the hall of frame to help us to finish the state diagram. For the Class diagram, we planned the “class” “attribute” “method” for our airline booking system before we make the diagram. Therefore we make it easily together. For the “System Development Methodologies” we though this part is really intricacy. As a result, we choose a system methodologies per person to research the information like the advantages and the disadvantages of methodologies. After that we compare each methodology and choose one as the suitable for our airline booking system. Actually, we speed most of time to finish this part and make result from each member. On weekend, we also have meeting to check each part are correct before we submitted the assignment.

(For lecture and tutorial)

In week 9 I have reviewed the UML, all the diagrams from the UML and the common mistake from assignment B in lecture. Also include the topic of the “Who Knows/Uses What of the UML” and the diagram of the topic. In tutorial, we mainly focus about the revision of the UML diagram therefore we did the KAHOOT for the topic of the UML diagram. Moreover, tutor prepared a quiz of us to make more understanding of the UML. Its goanna really helps me to spend less time to clearly comprehend those difference between each diagram. As a result, I need to redo the quiz again and again to deepen impression of the UML. Because the UML is the most important part in final exam.

# data[].attributes.body
In this week, our goal is to complete and amend the activity diagram as an individual. This week's meeting is suspended because one of our members have some unexpected internet connection issue, so we decide to finish the individual diagram drawing. At the same time, in order to make the diagram more accurate, I decided to ask the teacher to help me improve when I went to lecture. Undoubtedly, this provided me with great help. By the teacher’s help, I have found many problems that I had not noticed before.

# data[].attributes.body
In this week,  our topic are sequence diagram and state machine diagram. Sequence diagram also is an individual job, therefore like last week when I do my activity diagram. After I finished it, I went to the lecture and ask teacher for some advice, as my individual idea, I thought the messages in-between objects must be detailed but clear to let the reader understand. Also the choice of objects are really important, my first edition of the diagram have put  a wrong object in the diagram. For the state machine diagram, because we all have a bit  confusion with the state changes of the object and what are the right trigger event, therefore in the end of the meeting, we decide leave it to the next week and ask some helpful advice from teacher.

# data[].attributes.body
Because this week is due week, so we decide to have multiple meeting to finish the work. The class diagram was first part been done, we used Team instead of ZOOM, by one member sharing the screen then we can do it together, all of us are able to control it to give the advice. Then is the Methodology, I decide the RAD as mine topic, it's funny to have deeper research and understanding to it.The state machine diagram has take us to long to finish it, the change of state is really challenge to me, I always get it confused with the change of state.

# data[].attributes.body
At this week, because my internet got trouble, so we dicided will do the work (Sequence Diagram) by ourself then when my internet was fine and we did a group meeting to evaluate. I did use the hall of fame to fix my diagram a lots. It's very useful. Besides, i remind to group members that should ask teacher about feedback their diagrams. Because i thought sometimes our perspectives will have some mistakes. So make sure that the diagram looks good, i ask them to go lecture for asking feedback.

# data[].attributes.body
At this week, We dicide to make state machine diagram, but the this diagram is quite hard, so we did delay after Tian ask teacher for any recommend on monday, then we will have a group meeting in evening at that day too. So we did little bit for make sure in the next lecture i can ask teacher clearly. Then also after that day we finish the state machine diagrams. Also we did start to do methodology, we find the criteria for the methodology, and try to find main points of its to easy create a table to compare. Besides, we did class diagram, and find sutiable class to fit in, but we didn't do the relationship yet, because the members were tired at the momment so we delayed it till

# data[].attributes.body
At this week, we dicide to finish every last task and fix all the task, such as : introduction, table contents,  class diagram. Besides, i put all work to file doc word. At introduction part, i seperate it 2 parts: then divide it to me and Chris. Meanwhile, Tian helps Jack finishing his diagram, because it was not good. It was a long hard work. But i think we have done well.

# data[].attributes.body
This software is better than zoom, it's unlimited call/video call. It has full functions from zoom.

# data[].attributes.headline
This is draft idea of state machine diagram

# data[].attributes.subject
This is draft idea of state machine diagram

# data[].attributes.body
This is just a draft which i ask Tian ask teacher on monday, after that we did a new one then next tutorial it was better