# data[].attributes.body
This week is the start of the assignment 1B. In this first week, we do nothing much, we only discuss how and when should we done each of the task. Basically, we only allocating the portion of each member's work and each week's target.

In this week, since we haven't done anything about the assignment B, we have no problem. We just hope that we would be able to complete this part of assignment better than our last assignment, and i do hope that every single group member contributed in each task given like the assignment before.

# data[].attributes.body
ALFRED-3028710

# data[].attributes.body
This week, we are given information about the assignment B. On this particular week, we start off our assignment progress by making planning for weeks ahead. Our group meeting was held on 13th November 2017 during the tutorial. This planning will be used in the next week to determine the job split among the group members.

Personally, there is no real issue during this week. As our group motto implies, “A successful team is a group of many heads and one mind”, we cannot get to this point of our work if from the very beginning we did not support each other. I do hope that we can maintain this communication among each other. If we face any uncertainty or problems, we will talk about it and settle it straight away

# data[].attributes.body
Partner: Alfred (3028710)

# data[].attributes.body
Partner: David Gunawan (3091294)

# data[].attributes.body
a) 2 parts ( consists of two part; A multiple choice and  B open-ended questions )
b) Part A: 40 multiple choice questions (worth 80 marks)
Part B: 3 open-ended questions worth 20 marks
c) Part A multiple choice from week 1- week 10 lecture
d)  Part B covers the diagrams we made in Assignment A & B, as well as Functional and Non-Functional requirements.
e)Read and practicing the material, do some revision , practice on the sample examination.

# data[].attributes.body
a. 2 parts, multiple choice and open ended questions
b. Multiple choices 40 questions (80%). 3 Open ended questions (20%)
c. All learning materials from week 1-10 (lectures and tutorials)
d. All diagrams from assignment a and assignment b

e. Deep processing and testing yourself.

# data[].attributes.body
A) There are 2 parts, part A & B. Part A is multiple choice questions, Part B is open ended questions
B) Part A contains 40 questions (80 mark), Part B contains 3 questions (20 mark)
C)  Part A covers material from lecture from week 1 - 5
D) Part B covers the diagrams we learned through our case study through week 5-9
E) Test yourself & Processing information through continuous practice

# data[].attributes.body
a) 2 parts; consists of Part A multiple choice and Part B open-ended questions
b) Part A: 40 multiple choice questions (worth 80 marks)
Part B: 3 open-ended questions (worth 20 marks)
c) Part A covers lecture material from week 1 - 10
d) Part B covers the diagrams we made in Assignment A & B, as well as Functional and Non-Functional requirements.
e)Process the information and Self-test practice.

# data[].attributes.body
In this week, it is the stage where this is the final week of our assignment, we are very glad that we didn't have to commute everyday to work on our assignment. Wondering around, Arguing about the system, Tons of adjustments. At last, we finally made it.
Me and My group have finally contributed well throughout the assignment. We hope that every point we have made in the assignment can prepare us for our professional practices in the future.

# data[].attributes.body
3028710

# data[].attributes.headline
Reserve a Physical Resource - Use Case Description (newly created based on the feedback)

# data[].attributes.subject
Reserve a Physical Resource - Use Case Description (newly created based on the feedback)

# data[].attributes.headline
Reserve Physical Resource Sequence Diagram (Revised)

# data[].attributes.subject
Reserve Physical Resource Sequence Diagram (Revised)

# data[].attributes.headline
Activity Diagram: Reserve a Physical Resource (Revised)

# data[].attributes.subject
Activity Diagram: Reserve a Physical Resource (Revised)

# data[].attributes.headline
Group Work - State Machine Diagram (Revised and Finalized)

# data[].attributes.subject
Group Work - State Machine Diagram (Revised and Finalized)

# data[].attributes.body
This week ,the week of getting feedback and critics is here, I am glad that we all have done the draft. However there is some things that need to be done before it is ready to be submitted. We got alot of things to be focused on when Angelin told us that there is some mistake on our draft, from the use case description to the system development methodology.
The way we face this issue is by dividing the task in order to get the next phase of repairation which is week 9.
I am working on adjusting system development methodology by adding 1 table to compare them. Because what Angelin said is that our explanation of why we choose the Agile Methodology is too ambiguity . There is why by providing table she said will be more easy to understand and its very effective-friendly.

# data[].attributes.headline
Activity Diagram (After 1st feedback): Renew Loan

# data[].attributes.subject
Activity Diagram (After 1st feedback): Renew Loan

# data[].attributes.headline
Activity Diagram (After 1st feedback): Pay Fines

# data[].attributes.subject
Activity Diagram (After 1st feedback): Pay Fines

# data[].attributes.headline
Activity Diagram (After 1st feedback): Borrow Book

# data[].attributes.subject
Activity Diagram (After 1st feedback): Borrow Book

# data[].attributes.headline
Activity Diagram (After 1st feedback): Book A Room

# data[].attributes.subject
Activity Diagram (After 1st feedback): Book A Room

# data[].attributes.body
ALFRED - 3028710

# data[].attributes.headline
Group Work - State Machine Diagram (Finalized)

# data[].attributes.subject
Group Work - State Machine Diagram (Finalized)

# data[].attributes.body
: Car

# data[].attributes.body
In this week we try to finalize everything we got on deciding the methodologies on what we are going to use for our assignment. It is very tempting where all the choices available are very confusing because some of them offers the same thing to the other.
We have to put alot of deep research and make sure that things are going fine. We have also been struggling with everything from the Activity Diagram, Class Diagram to finalize it before monday. And at last we can spare 2 weeks to revise and get feedback on what we did.
Thankfully it turns out that everything goes well with the plan...

# data[].attributes.body
30 November 2017
16:30 - 18:00
UTS: Library Level 3, Room 3E

# data[].attributes.body
ALFRED - 3028710

# data[].attributes.body
In the first week of working towards our next assignment is very tempting. Because we have to manage to overwrite all our mistake we done in the previous assignment. We have to work more on improvising the use-case description, ERD-diagram and alot more. But thats not the whole thing.
We are thankful that we have manage to choose our methodologies to be used in our assignment. By doing a very critical and on-point researches.
We also have done alot of progress eventhough this is just the first week in doing the assignment, because we really dont want to push time really close so we get a room for improvement if we may have done something wrong.
I hope that the next 2 weeks we can finalize everything in place .

# data[].attributes.body
Research and Planning session

# data[].attributes.body
ALFRED - 3028710

# data[].attributes.body
Creating an activity diagram

# data[].attributes.body
Car Rental Class Diagram

# data[].attributes.body
Things need to be done !!!
1. Introduction
2. Use Cases Diagram and Descriptions
3. Activity Diagrams
4. Sequence Diagrams
5. State Machine Diagram
6. Class Diagram
7.  System Development Methodologies
8. References

Week-6
1. Finalize the Class Diagram
2. Split the job among the members
3. Finalize Use Case Diagram and Use Case Description
4. Discuss and learn each methodologies together

Week-7
1. Finalize the other diagrams
2. Deciding the methodology to be used in UTS: Library systems

Week-8
1. Draft is done and Feedback is requested

Week-9
1. Finalize the assignment

# data[].attributes.body
#taking interview by phone
Date: 1 November 2017
Place: Blue Building Level 2 Student Lounge

# data[].attributes.body
Date: 31 October 2017
Place: UTS Library level 3

# data[].attributes.body
In this entire project A, I finally got to learn something really crucial, which is how to be goal-oriented type of person. By means, this project doesn’t finish in just over night. It has to be planned and improvised through days by days, it needs feedbacks, comments, and even critics in order to be perfect. I feel like my team has contributed cooperatively, maximumly, and competitively, because as a team we strive not to be best amongst all other group, and we can’t promise to be one, but we as a solid group promise and emphasize really on being the best towards ourselves.

Talking about the challenges we face on this assignment is massively a lot, I feel like there is a lot adjustment we made, not only from the ERD-diagram, Use-Case, even on the simplest thing which is the functional and non-functional requirements. The most educative feedback that I got so far is about the degree of comparison, by means the words we use to visualize or show something has to be definite. Take for example the Functional and non-functional requirements that we made, we had use a lot of auxiliary in the functional requirement which makes the reader confuse which is prioritize more. This is a very crisis situation especially when we are in the professional workplace, this is a very crucial mistake.

I am truthfully lucky to work on a lot of things in this assignment, I got to work on my critical thinking, observation, my senses of art and etc. Talking about the presentation of the work we done, it is very important to make our works look ethical, beauty, and good looking in order to make our reader which could be our client in the future interested about our work.

# data[].attributes.body
(ALFRED-3028710)

# data[].attributes.body
In this week we finally work on our assignment for which will be submitted in week-4, we have equally divide our job, and I am working on some problem in the assignment which is on how I can decide which case in the interview should be the key improvement in our assignment, and In the introduction section,  I find alot of difficulties and obstacle because alot of things need to be done before the introduction, which is ironic because introduction were meant to be the first of the assignment but in fact it has to be done after all the content is 100% ready.  Time pass by my team has finally finish with a good draft where I can start working on design of the assignment. I hope that we will make our assignment to the maximum before the end of week 4

# data[].attributes.body
(ALFRED - 3028710)