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

# data[].attributes.body
Date:  28 October 2017
Place: UTS: Library Level 2
Time: 1 p.m. to 6 p.m.

# 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
Date: 31 October 2017
Place: UTS Library level 3

# data[].attributes.headline
Getting Started Week 2 (Task 3) - Group Assignment

# data[].attributes.subject
Getting Started Week 2 (Task 3) - Group Assignment

# data[].attributes.body
A) We plan to have a different leader for each week because we as a group are willing to develop the leadership ability of each of our members. For this week, I am the leader of this group. Thus, I am in charge of upload what we have discussed together. Next week, another group member will be in charge of the same assignment. In this group, We offer flexible ways to communicate through direct conversation, social media (Whats App), and group gathering. Furthermore, through those communication methods, we will share our opinions on this assignment and make the best decision according to the agreement of all the team members on the opinions/ideas. In case there is no agreement on some issues, we will do voting method that will determine which idea the majority of the team members choose. All of us will decide whether individual works is of acceptable standard. The key of a successful group is communication and trust. If the issues occurred, we will be open to each other and propose a solution to address those issues.
B)
- Week 1

Able to complete the introduction (determining the objectives and methods of the requirement gatherings), also able to identify system stakeholders. This part of group work is crucial because it is the root and foundation of the assignment, so it is better to work it together as a group to get the best results.

- Week 2

Able to determine functional requirements, and nonfunctional requirements. And if possible, start working on the Entity Relationship Diagram. The process of determining requirements is not necessarily worked in a group, therefore, each team member will contribute by working it individually. On the other hand, the Entity Relationship Diagram needs to be worked on as a group.

- Week 3

Able to complete the Entity Relationship Diagram, Use Case Diagrams, and Use Cases Descriptions. For Entity Relationship Diagram and Use Case Diagram, it will be worked on as a group, but the Use Case Descriptions will be worked on individually and split equally between the group members.

- Pre-week 4

Able to complete the appendix, and able to complete table of contents. Also, able to revise the sentences and the layout of the assignment. In addition, able to add some finishing touch. All of them might be worked on individually.

C)
1.     How often do you visit the library?

2.     What do you like about UTS library current systems?

3.     What do you dislike about UTS library current systems?

4.     What library service do you occasionally use?

5.     Do you find that service completely helpful and easy to use?

6.     What do you think can be improved from this current system?

What to explore from UTS library current system:

1. Book a room
2. Borrow books
3. Find database
4. Lynda.com

# data[].attributes.body
“A successful team is a group of many hands and one mind.”
Reinaldo

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

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

# data[].attributes.body
Car Rental ERD (Updated Version)

# data[].attributes.body
Car Rental ERD (Updated)

# data[].attributes.body
Car Rental ERD - Updated

# data[].attributes.headline
Week-3  Task 3 ( Requirement List Practice )

# data[].attributes.subject
Week-3  Task 3 ( Requirement List Practice )

# data[].attributes.body
Functional

1. Customer can book a car for rent

2. Customer can make payment online. (As this is a website portal renting site.)

3. The system can update the customer information details into the database of the company

4. Customer can check all the details of the car.

Non-Functional
1.     24 hour access to the website

2.     Authorized user only
3.     Regular maintenance of the system

4.     The system shall protect customer data

# data[].attributes.body
Use Case Diagram - Online Car Rental System

# data[].attributes.body
Use Case Description - Choose Car

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

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

# 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.headline
Individual Reflection Week 2 (DAVID GUNAWAN 3091294)

# data[].attributes.subject
Individual Reflection Week 2 (DAVID GUNAWAN 3091294)

# data[].attributes.body
Today, on 23 October 2017, we formed a group named ‘Victorious Secret’. The group itself consists of Ananda, Alfred, Reinaldo and me. To encourage the communication among the members, we created two social media group (What Apps and Line). Through these platforms, we will be able to share and discuss about our roles in this assignment. This main goal of this week tutorial is to create our personal padlet account then connect to other members to form a group. Padlet will be our media to share both our individual and group work.  We manage to achieve that goal in this tutorial.

This week, I manage to navigate and use Microsoft Visio that will be essential in making entity diagram in this assignment. The entity that we created were posted in our padlet page as well as our personal reflection. Furthermore, as a leader for this week, I was able to lead my team members to start a communication and discussion on the social media group that we created together. This helped us to know each other more and to build a good teamwork.

For this is the first week, we are officially a group. We have not encountered any issues yet. I do think that communication and trust are the main keys of a group success. If we face any issues in the future, we will discuss any issue in an open communication. We believe that we can avoid any problem if we build a good communication and a solid trust on other members.

# data[].attributes.body
1) This week, we finally create our team, which is the prideful Victorious Secret. In this week, we are able to create our own social medias group to help us communicate flexibly with each other, which is a group on Whats App and LINE.

2) I contribute on the Task 3 Assignment, and I also contribute in making Entity Relationship Diagram. For the group work itself, we haven't done anything significant yet.

3) For this moment, we don't have any problems in our team. Our strategies and plans are well thought and is able to read in the Getting Started Week 2 point b. I personally think this group consists of great students, and we are going to perform well in this assignment.

# data[].attributes.body
The first session of our Business Requirement modeling is quite intense especially this subject is the integration to Information System. Where this subject is all about the requirement analysis.
The first week of the tutorial class, we've been struggling to team up with a group, because we find it less challenging if we use the same group formation to the last semester. So we made a quick swap with one other group and let's take the challenge to the next step, where I analyze the composition of the group, we lack in delivering a good looking output. We are more into strategical and more on logical to bring up our work.
But this doesn't stop us to perform great in this subject assignment.
The second week of the tutorial, we are swimming in practical touch with the Microsoft Visio itself, where some students find a lot of difficulties in operating it, while some others thought that it is just a wrap-up exercise. The good thing about the Microsoft visio for me is that it is very compatible with any format or development kit for us to use and built a good looking diagram.
Whereas Microsoft Visio is one of the tools that we can use to work on our assignment.
We have been planning a lot of strategies on how to complete our assignment on time, especially for some of us this is still the first time for using this type of software to work on the assignment.
I hope that we are going to strive good emotional dependencies towards other until the end of the semester and work as a good team.

# data[].attributes.headline
Individual Reflection Week 2 by ALFRED (3028710)

# data[].attributes.subject
Individual Reflection Week 2 by ALFRED (3028710)

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

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

# 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
30 November 2017
16:30 - 18:00
UTS: Library Level 3, Room 3E

# data[].attributes.body
ALFRED - 3028710

# 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
: Car

# data[].attributes.body
ALFRED - 3028710

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

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

# 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): Pay Fines

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

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

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

# 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
Group Work - State Machine Diagram (Revised and Finalized)

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

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

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

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