# data[].attributes.body
Main issues/mistakes/misunderstandings in each parts
1.Use case diagram

Wrong name of stakeholder
2. Use case description

Good
3. Activity diagram

Some steps are not valid and missing step in the Print Receipt Diagram
4. Sequence diagram

Incorrect context applied
5. State diagram

-Triggers not defined at all places

-Order of occurrence of states should be clear
6.Class diagram

Relationship name should provided

# data[].attributes.body
a)    How many parts does your exam have? What kinds of questions in each part?
-There are 2 part in the exams.
-For open-ended questions, All the questions are about requirements specification; We learnt to specify requirements in few written forms and in diagrams (models).
- Also you will need to write/draw 2 specific lists/forms/models

b)   How many questions in each part, and how many points are they worth?

-Part A includes 40 multiple choice questions,  each worth 2 points
- All questions are about the same system; your task is to answer 2 open-ended questions

The answers are worth 20 points in total

c)   What content does Part A cover?

All question from part A is based on lecture 1 to10

d)   What content does Part B cover?

All the questions are about requirements specification and
e)    What are two main study strategies that have been found very effective in improving students’ abilities, and, therefore, exam results?

For MCQ:Self-testing: You can use the same tools mentioned in the previous slide, just delete the content and then check your answers (so e.g. list, without checking notes, all structural/behavioural diagrams, or all black-box/external view diagrams; fill in the table with info about each diagram but without using notes this time)
For open-ended questions:

As in your Group Assignments, the requirements will be drawn from an existing system, though don’t forget that in real-life situations, you would need to conduct extensive requirements gathering

f)    If you have any questions, please post them in UTS Online under Discussion Board: Final Exam Questions. Please don’t post questions to which you could find answers in the slides – but if you read something, think about it, and are still confused or just want to understand it more deeply, then please feel free to ask. Make sure to check though if the same question has not been asked before.

# data[].attributes.body
Outcome:
a) How many parts does your exam have? What kinds of questions in each part? - There are 2 parts in the exam, part A is multiple choice questions, part B is open-ended questions.

b) How many questions in each part, and how many points are they worth? - Part A contains 40 questions, each worth 2 points, total is 80 points.
Part B contains 2 questions, the answers are worth 20 points in total

c) What content does Part A cover?

Questions from all the lectures, including BPMN and DFD (from Lecture 1 to Lecture 10)

d) What content does Part B cover?

All the questions are about requirements specification; We learnt to specify requirements in few written forms and in diagrams (models)

e) What are two main study strategies that have been found very effective in improving students’ abilities, and, therefore, exam results?

-Self-testing: I can use the same tools mentioned in the previous slide, just delete the content and then check your answers (e.g. list, all structural/behavioural diagrams, or all black-box/external view diagrams; fill in the table with info about each diagram but without using notes this time)

-My assignment work was your best practice; also checklists from tutorial

. Check my assignment feedback in Week 11 to understand all the mistakes to avoid them in the exam

# data[].attributes.body
In this week, we do revision of state machine diagram that we did last week. Then i have done the referencing on UTS Online to understand how to reference and check with our group assignment references. Our group will combined and submit the final of assessment B on Sunday and hand in the soft copy in week 10.

# data[].attributes.headline
Nguyen Tai Anh - 314285 - Reflection 4 Week 9

# data[].attributes.subject
Nguyen Tai Anh - 314285 - Reflection 4 Week 9

# data[].attributes.body
Outcome:
In week 9 tutorial, i have completed my diagram and show to our members.   they have contributed some suggestion for my tasks and i feel so confident now with my team.
Through the week, we will see again our assignment before submitting. On next week lecture , i and our team mates will submit the hard copy on time.

# data[].attributes.body
For this week, I have complete the research about Commonwealth Bank and also the 2 state machine diagram. I also send it to our leader to combined it together
On next week ( week 10), Our leader not gonna be here so we gonna hand in the hard copy to the teacher in the next lecture

# data[].attributes.body
In this week, I have done some research about the Commonwealth Bank for my diagram through there website and reference and I will try to complete it on time and send it to my leader to complete the assignment B. WE also do revision of sequence diagram and working together on my diagram the state machine diagram.

# data[].attributes.body
As of this week, i have completed my sequence diagram and also included all the necessary document needed to be in assignment B. as the team captain i have also brought together every diagram completed by my team members and connected it as one word document.

during this week, after researching the methodologies i have found out some useful information that can be used in the future. as i will not be in Australia during week 10, i have told my team members to hand in the assignment's hard copy in the lecture.

# data[].attributes.body
In this week, we introduce the assignment to the team member about how many diagram we have to do and organise the work for other team member, who do the introduction, who do research.
We divide the diagram into four:
Anh will do the class diagram
Carrick will do the activity diagram
I will do the state machine diagram
and the team leader Jason will do the rest

# data[].attributes.body
In week 8, we do revision of sequence diagram and working on the state machine diagram. I draw a state machine diagram for objects of class ‘Book’ in the UTS library system.
Also we still working on the assessment B. I have to do 4 diagram of activity diagram so it's really messy. I will try to finished these next week and then combined with other group's member

# data[].attributes.headline
Nguyen Tai Anh - 314285 - Reflection 3 Week 8

# data[].attributes.subject
Nguyen Tai Anh - 314285 - Reflection 3 Week 8

# data[].attributes.body
Outcome:
In week 8, i have almost finished the Commonwealth Bank class diagram. i still go really smooth with my class diagram though the layout is quite messy. i will
fix it as soon as possible for easily understanding. All of the concept about class diagram we have learnt from Lecture and Practice in Tutorial. However, i think it hard to think out the classes for our Assignment. i will try to update and improve my diagram better in coming week

# data[].attributes.body
In week 8, i have finished up the introduction( i have included more Commonwealth Bank information in this part ,table of content, reference and i will complete the sequence diagram in the coming week to complete assignment B

I have also Completed the System methodologies and included some diagrams and pictures to depict The waterfall model, Joint Application Development Methodology, Rapid Application Development  and Dynamic System Development methodology and as for the recommendation i have completed it by recommending Rapid Application Development for assignment B

My last work in the coming week would be the sequence diagram and putting together all the diagrams from my team members.

# data[].attributes.headline
Nguyen Tai Anh - 3142851 - Reflection 2 Week 7

# data[].attributes.subject
Nguyen Tai Anh - 3142851 - Reflection 2 Week 7

# data[].attributes.body
Outcome:
In the week tutorial, we have decide how to finished our assignment 2.
All of us have contributed really well for the final date.

9 classes have been completed. I have almost done the class diagram, which i think it is the most difficult. i had trouble in analysis what is the class and its methods. however,  After reading more deeply in the lecture related to my concept. i have been broaden my mind and easily understand how it is work. my goals for this week is to complete my tasks for our assignment 2 and also check again other members' works.

I have experienced a long time with the amazing team. they show their teamwork skill and also individual skill. From the Assignment and Tutorial, i have learnt self study and analysis. It was a great experience for me.

# data[].attributes.body
In week 7, we discuss and divide the work in assignment 2 evenly for every member and decide the due day. My part is the state machine diagram, At first, I think it quite harb but after doing some research and spent more time for it. I found that it not that hard and I almost done it but I think it still need some modification. We will try our best to get the best result
I have experience many this but this is the best team I have ever had. We have a good leader, the best team made and a "can do" attitude. They help me to improve my team work skill alot and learn how to self study.

# data[].attributes.body
In this week, we have to discuss and decide about assessment 2 which about drawing diagram. There are 5 diagram we have to do which include use case diagram, activity diagram, sequence diagram, state diagram, class diagram. All of these we have learnt and practice through lecture and tutorial. I have chosen Activity class diagram as my job. I think it's not easy to draw, the diagram require many step and different actor, activity. i will try to improve better in this assessment and get better result.

# data[].attributes.body
State Machine Diagram (Book)

# data[].attributes.body
State Machine Diagram :Book

# data[].attributes.body
As of this week, i have completed the introduction, use case diagram description ( I have improved these from Assignment A), and i have also completed half of system development methodologies.

i have chosen to write the waterfall model, Joint Application Development Methodology , Rapid application development methology and Dynamic System Development. I have completed some research on these methodologies and will begin writing them in the coming week.

as for the recommendation i have chosen to recommend rapid application development, the reason for that is because Commbank ATM is an ongoing bank system, you cannot stop the system for a long period of time as it will cause customer to complaint.

# data[].attributes.body
Sequence diagram

# data[].attributes.body
Week 7

# data[].attributes.body
Activity Diagram

# data[].attributes.body
week 6

# data[].attributes.body
Activity Diagram

# data[].attributes.headline
Week 6 Group (Jason) Reflection Assignment B Planning

# data[].attributes.subject
Week 6 Group (Jason) Reflection Assignment B Planning

# data[].attributes.body
In this assignment, we are to do Activity Diagram, Sequence Diagrams, State machine Diagram, Class Diagram, Research and recommendation on system development methodologies

we have divided the work as such
Anh-Class diagram
Carrick- activity Diagram
Christian - state machine diagram
Jason - Sequence Diagram
Jason - Research and Recommendation on system methodologies
Jason - Will Put together everything as the team captain.

# data[].attributes.body
a) Introduction

Lacks information, purpose of requirement in the systems development analysis and its industry context

b) Stakeholders

explain the importance in creating a requirement specification report

c) Requirements gathering methods with evidence

online surveys – enables faster and easier data collection

-easy to analysis information

-stats is auto generated

d) Functional and non-functional requirements

Functional requirements should be system related not user.

The system Shall allow user to deposit money

e) Quality of E-R diagram (both content and presentation

-Cardless cash is more of a method or service

-incorrect carnality issues M:n 1:n 1:1

-relationship names are verbs

f) Quality of use case diagram (both content and presentation)

-Validates account not needed

-Staff actor

g) Quality of use case descriptions (both content and presentation)

pre condition and post condition are opposite

# data[].attributes.body
UTS Library Class Diagram

# data[].attributes.body
After discussion, we choose Jason to be our team leader
I think only one team leader is better because a bad team leader can lead all the team go to wrong way.
we communicate through we chat app
we will have team metting at UTS library and we make dicision by everyone giving there opinion and we will choose the best one.
We upload work on google drive and share it with the other member in the group.
We let each other to choose the individual work because each person have their own strong point so we cover each other like a team by let them choose the part that they can do their best.
We will tell the teacher if their are any issue but I think it will never happen because we are a good team

# data[].attributes.body
Do you elect the leader?
-After discuss, we decide to choose Jason as team leader.
Do you want a different leader for each week? Or a different leader for each part of the assignment?
-No, i think we just need only one leader for all assessment
How will you communicate?
-We communicate through wechat app.
When/where will you meet? How will you make decisions (for example, when there is no agreement on some issue)?
-We will discuss time and place for meeting in class before the assessment.
How/where will you upload/combine work?
-We work together on google drive
Who can decide whether individual work is of acceptable standard?
- A final group work should go through everyone in group to double check and decide the final one

What should you do if you’re not happy with a group member’s commitment?
-We will talk with teacher to solve problems by change group member or speak with them.

# data[].attributes.body
Improved Use Case Diagram

# data[].attributes.body
week 4

# data[].attributes.body
Improved Use case Diagram

# data[].attributes.body
Use Case Diagram

# data[].attributes.body
week 3

# data[].attributes.body
Use Case Diagram

# data[].attributes.body
Nguyen Tai Anh
Outcome:
In week 4 tutorial, we have made effort to HD Assignment A. All of the members have contributed ideas well in use case diagram and use case description for our assignment.

On the Use case diagram hall of fame. i have chosen  Symac's use case diagram. From my perspective, although these diagram are look easy and simple for everyone, it still keeps and contains meaningful ideas with fully concepts. this diagram helps me to understand a lot of what i need to do and i learnt how to collect the correct resources. However, the diagram also needs to have more use cases to describe deeply how the system works.

From the Assignment and Tutorial, i have learnt self study and analysis. It was a great experience for me.

# data[].attributes.body
Christian
Outcome:
In this week, My target is complete the use case diagram in week 3, analyse and improve it.
In 7 diagram in Hall Of Fame padlet, I choose Danny's use case to analyse. In my opinion, his use case is really wide and have every essential use case that it need. However, Just one week point it quite messy and make it hard to read

# data[].attributes.body
Carrick

This week, we looked back at the use case diagram week 3 and suggest one improvement/correction to one use case diagram. I have also choose Hansen's diagrams  in Use Case Diagram Hall of Fame to fix and improve.

We also working on the assessment A. Everyone in our group share ideas to improve our assessment. The goals of our group is to get HD for the assesment.

# data[].attributes.body
Carrick

# data[].attributes.body
Nguyen Tai Anh
Outcome:
In week 3 tutorial, we have contributed equally in stakeholders and discussed further about the use case diagram and use case description that we will use in assignment A.

We also did the functional and non-functional requirement and the ERD diagram. The main tasks for everone have divided to finalised the Assignment A as soon as possible.

# data[].attributes.body
In week 3, our group worked the ERD from Week 2 and start create the use case diagram of UTS Library system. My UTS Library System diagram include 7 use cases and some of them are "include" and "extend" use case. We have to work on the  use case description as well.

This use case diagram will help us on the assessment. Also we have start to divide the task on assessment A, decide meeting day for team members, discuss on the assessment

# data[].attributes.body
Christian
Outcome:

In week 3 tutorial, we discuss about the assignment and the work have to be done before week 4, choosing the day for the team meeting and separate the work for each member

Everyone will contribute for the entity diagram and use case diagram while the use case discription is individual work

# data[].attributes.body
Jason
Outcome:
Our Expectation for Assignment is HD.

My goal for this week is to complete the 3 use case diagram and 1 use case description for assignment A and also draw up the ERD Diagram and finalize Assignment A.

In the hall of fame , i have selected Danny's diagram and as you can see it is too messy. the enter the library use case is not needed. while the fix damaged resource and put resource back to selves could be generalised into manage resource. the teacher's upload study material use case should also need a log in the system. while request new resource and report damaged resource can also be generalised into manage resources.

As of this week, we have completed all the work required to finish Assignment A

# data[].attributes.body
Jason
Outcome:
During the tutorial, we have distributed the work needed to be done equally and everyone has agreed on the work they are assigned to.

Everyone will complete 4 functional requirement, 3 non-functional requirement, 3 ERD Diagram, 3 use case and 1 use case description, as for appendix, everyone will contribute to this part, we have decided on using online survey (Survey Monkey).

I have started on the introduction and stakeholders during this tutorial and i have also learnt the right way to do a use case diagram and use case description including"Include" and "Extend" in which we will use in our assignment A. i have also saved all the reference that are needed to be written on the reference page.

I have set my goal to complete the introduction and stakeholders during this week.

# data[].attributes.body
ERD Diagram

# data[].attributes.body
Christian 3133395

# data[].attributes.body
ERD Diagram

# data[].attributes.body
Jason
Outcomes:

Do you elect the leader?

We have selected Jason as the leader.

Do you want a different leader for each week? Or a different leader for each part of the assignment?

No, It would cause a lot of confusion if we keep changing it around.

How will you communicate? When/where will you meet?

We will use Wechat as the communication tool.

How will you make decisions (for example, when there is no agreement on some issue)?

When there is no agreement on some issue, we have agreed on voting.

How/where will you upload/combine work?

We have chosen google drive because it allows online editing of the document .

Who can decide whether individual work is of acceptable standard?

The work completed should be decided on everyone, it will go through everyone before it is accepted as the final work.

What should you do if you’re not happy with a group member’s commitment?

We will tell the teacher and let the teacher decide on the issue