# data[].attributes.body
Christian's posts are all missing, and Ony and Arel only posted once. Manh Tuong Ta added all the posts but in one day. Unfortunately this means lacks of evidence of most of your contributions to the assignment. The reflections are an important part of your assignment, to make sure you improve working in the team, and to give evidence of your contributions.

# data[].attributes.headline
Week 10 reflection Manh Tuong Ta 2949709. Our group held a meeting on sunday night to finish the assignment. Although a team member didn't show up and didn't do the work, Arel and Ony and me still finished our own tasks. However, Arel and Ony still needed time to fix their diagram. Therefore, I did the two diagram left which are state machine and class diagram and Arel plus Ony are in charge with the methodology. 

# data[].attributes.subject
Week 10 reflection Manh Tuong Ta 2949709. Our group held a meeting on sunday night to finish the assignment. Although a team member didn't show up and didn't do the work, Arel and Ony and me still finished our own tasks. However, Arel and Ony still needed time to fix their diagram. Therefore, I did the two diagram left which are state machine and class diagram and Arel plus Ony are in charge with the methodology. 

# data[].attributes.headline
Week 9 reflection Manh Tuong Ta 2949709. Because of the busy schedule of our group member, we couldn't hold a meeting. However, I still finished the task I was assigned which is creating sequence diagram for the "return a book" use case. I think I'm on track of the assignment. 

# data[].attributes.subject
Week 9 reflection Manh Tuong Ta 2949709. Because of the busy schedule of our group member, we couldn't hold a meeting. However, I still finished the task I was assigned which is creating sequence diagram for the "return a book" use case. I think I'm on track of the assignment. 

# data[].attributes.headline
Week 8 reflection Manh Tuong Ta 2949709. On Wednesday our held another meeting on 7th floor of the Blue Building. As all the tasks are divided we all worked on own task. I created activity diagram for "return book" use case. What I like about working in group is that I can get opinion from my team member.

# data[].attributes.subject
Week 8 reflection Manh Tuong Ta 2949709. On Wednesday our held another meeting on 7th floor of the Blue Building. As all the tasks are divided we all worked on own task. I created activity diagram for "return book" use case. What I like about working in group is that I can get opinion from my team member.

# data[].attributes.headline
Some good reflections to start with but many missing.

# data[].attributes.subject
Some good reflections to start with but many missing.

# data[].attributes.body
There are no reflections from Week 8 and 9 here - don't forget that this forms part of your mark for the assignment, under Individual Contribution. Weekly reflections also help to solve any potential issues, and let me monitor your progress and help you if needed. See the assignment handout for reflection questions. Good luck with finalising the assignment :).

# data[].attributes.body
Last wednesday our group held a meeting. It was in 7th floor of the Blue Building at 11am.
Our group divided the tasks to all member. As for the first step we would have to fix our use case diagram and use use case description. The thing I like about working in group is that we can share our ideas and really help each other through difficult task. We will hold the next meeting and start working on all the diagram needed for the subject.

# data[].attributes.headline
Week 7 reflection ( S M Fazle Rabby Ony-2959356

# data[].attributes.subject
Week 7 reflection ( S M Fazle Rabby Ony-2959356

# data[].attributes.body
Previous Wednesday i had a meeting with my group mate. the meeting was about the topic of our assignment. it was held in the  7th floor of the Blue Building at 11 am.
i really like to working in my group. they are sincere about their own work as given for the assignment. all member support the decisions of others. they shared their idea about the topic. since now they are working very well. i think if we arrange more meetings and share our ideas with each other we can get a expected mark in the assignment.

# data[].attributes.headline
week 7 reflection(Arel Pranta Gomes 2950865)

# data[].attributes.subject
week 7 reflection(Arel Pranta Gomes 2950865)

# data[].attributes.body
Last Wednesday I had a meeting with my group members. Our meeting held in the 7th floor of the Blue building at 11 am. All our group members attended the meeting. In the meeting,  We discussed about the topics of the assignment.
I like working with my team. They are very active. All the members supported my decisions and helped me by suggesting me some better ways to do the assignment. They shared their ideas with me. We have the same type mentality that is the main strength of our group. Communication problem due to the different class times is the main weakness of our team. Currently everything is going good within our team because all the members are very active and helpful. I think if we can meet more often we can share more ideas and thus we can improve teamwork.

# data[].attributes.headline
[Ony] Learning Activity 02 – Assignment A feedback                a)    Quality of description of system development environment (introduction, stakeholders, functional, and non-functional requirements)                                              =It I was quite good. But some points in non-functional and functional requirements r missing. Like in functional requirements are not functional.                                                                  b) Quality of E-R diagram (both content and presentation)                                                                            =It was good.                                                                             c) Quality of use case diagram (both content and presentation)                                                                      =Quite bad. some points were missing. like 4 character, verbs are missing. Everything needs to update the information. i did really bad in my use case diagram.      d) Quality of use case descriptions (both content and presentation)                                                                        =Not good. We got 3 thins were missing. Like in descriptions access the books making no seance, trigger was missing. Everything needs to update the information. Presentation was very bad                                   e) Individual contribution to groupwork, as evidenced by the student's Padlet contributionsWe tried our best to contribute individually.                                             ----=Everybody worked very good. I tried my best to do make the use case diagram better. But I did bad, as a result it effects everyone’s rseult.

# data[].attributes.subject
[Ony] Learning Activity 02 – Assignment A feedback                a)    Quality of description of system development environment (introduction, stakeholders, functional, and non-functional requirements)                                              =It I was quite good. But some points in non-functional and functional requirements r missing. Like in functional requirements are not functional.                                                                  b) Quality of E-R diagram (both content and presentation)                                                                            =It was good.                                                                             c) Quality of use case diagram (both content and presentation)                                                                      =Quite bad. some points were missing. like 4 character, verbs are missing. Everything needs to update the information. i did really bad in my use case diagram.      d) Quality of use case descriptions (both content and presentation)                                                                        =Not good. We got 3 thins were missing. Like in descriptions access the books making no seance, trigger was missing. Everything needs to update the information. Presentation was very bad                                   e) Individual contribution to groupwork, as evidenced by the student's Padlet contributionsWe tried our best to contribute individually.                                             ----=Everybody worked very good. I tried my best to do make the use case diagram better. But I did bad, as a result it effects everyone’s rseult.

# data[].attributes.headline
Hello, could you please change in Settings "Show authors' names in posts"?

# data[].attributes.subject
Hello, could you please change in Settings "Show authors' names in posts"?

# data[].attributes.body
Thanks, Agnieszka

# data[].attributes.headline
Week 5 | Christian Tran 2944975 | Reflection

# data[].attributes.subject
Week 5 | Christian Tran 2944975 | Reflection

# data[].attributes.body
In our last week before this assignment was due. We planned our last meeting on Wednesday the 16th of November. Combining all our efforts into finishing and finalising this assignment.

The outcome of this assignment could of been better if we concentrated more. By revising over past lectures and activities could have further given us a better outcome.

# data[].attributes.body
Non-functional requirements constrain the system being developed or the development process (related to usability, availability, performance, security, supportability, laws etc.).

1.    Functionality

a)     Logon Capabilities: The UTS library system shall provide the users with logon capabilities.

b)     Mobile Devices: The UTS Online Library System shall also be supported on mobile devices such as cell phones.

2.    Usability

The UTS library system shall permit the members to get to the system from the Internet utilizing a web browser or it's subordinate advances. The system utilizes a web program as an interface.

3.    Reliability

The UTS library system shall be extremely reliable because of the significance of information and the harms wrong or inadequate information can do.

a)    Availability: The UTS library system shall be accessible 100% for the students and is utilized 24 hours a day and 365 days a year. The system might be operational 24 hours a day and 7 days a week.

b)    Mean time to repair: If the system fails, the system will be recovered back up within an hour or less.

c)    Access reliability: The system shall provide 100% access reliability.

4.    Performance

a)    Response time: The system shall react to the user in at the very least two seconds from the season of the request submittal. The system might be permitted to take additional time while doing huge preparing occupations.

b)    Capacity: The system shall be capable of handling 250 users at a time or more.

c)    Resource utilization: The assets shall be altered concurring the user prerequisites furthermore as per the books asked for by the users.

5.    Safety

The UTS library system shall be able to operate without catastrophic failure.

6.    Security

The UTS library system shall be able to protect itself against accidental or deliberate intrusion.

� � � E � 1��g��1H�L

# data[].attributes.headline
Week 4 Refection(Arel Pranta Gomes : 2950865)

# data[].attributes.subject
Week 4 Refection(Arel Pranta Gomes : 2950865)

# data[].attributes.body
On Wednesday week 4, our group met up at prince centre room 228 early in the morning. We discussed about the rest of the assignment and worked for what is left.

Later I finished my part of the project which was Non-functional requirements. Moreover I discussed ERD with my team mates and me and Ony tried to upgrade the ERD which was initially done by Tony and Christian.

I fell happy working with my team mates. They are very helpful.

# data[].attributes.body
During our meeting on Wednesday 16th of November. Christian and I worked together to compose a introduction for this assignment
---------------------------

In this Group assignment part A, our main goals and objectives are to provides an in-depth report that indicates our knowledge on what we have learnt about stakeholders, modelling technique, user requirements, ERD and lastly teamwork. It is then narrowed down to system stakeholders, where all the stakeholders are listed. Functional Requirements that contains 9 existing functionalities of UTS Library system and 3 proposed functionalities to improve the system. A non-functional requirement contains 5 detailed analyses that convey the additional conditions for the functionalities. Entity Relationship Diagram (ERD) demonstrates how all entities connect with each other and their attributes. Lastly a Use Case Diagram that reveals the perspective of how the outside user interacts with the system, along with its detailed description.

In this report each member will demonstrate our understandings on the subject. The report will be divided in 6 sections, where each of us is assigned to individual work. However some of the sections require a great amount of teamwork such as ERD and use case diagrams/descriptions, we then have to schedule meetings to brainstorm ideas. �

# data[].attributes.body
On Wednesday week 4, our group met up at prince centre room 228 early in the morning. We discussed about the rest of the assignment and worked for what is left.

I have finished my Stakeholder analyst and the conclusion with recommendation which are assigned to me by the group. on Top of that, we also have done the entities of the ERD and getting into designing part to make the ERD more readable.

I feel happy with the meeting as we all did our partand just a few need to be modified. We are on track to finish the assignment by the due time.

# data[].attributes.headline
Week 4 | Christian Tran 2944975 | Reflection

# data[].attributes.subject
Week 4 | Christian Tran 2944975 | Reflection

# data[].attributes.body
On Wednesday a few days following from our last tutorial. All members met up at prince centre in the morning. We discussed what we have worked on over the past few days and shared our work. We then work individually on our assigned jobs then came together again to discuss the Entity Relationship Diagram.

Since last Friday i've completed the Functional Requirements.

-------------------------------
Functional requirements is to capture the behaviour of the system. Such as services, tasks, or functions that the system is required to perform.

1. UTS Library shall allow the rental/booking of private rooms.

UTS library allows to book private rooms online in advance for students or teachers to privately use.

2.  UTS Library shall allow stakeholders to use online system.

UTS Library online allows any users weather you’re an registered student or not to conduct research, collect resources and show available books online.

3. UTS Library shall only allow access with a registered ID card. (P)

UTS Library will only give you access with their facilities if you attain a student or registered ID card.

4. UTS Library shall allow stakeholders to borrow books with ease.

UTS Library allows stakeholders to borrow books weather it is online or even physically at the library.

5. UTS Library shall allow users to easily access the system.

This system allows the users to access their system on any device. Weather its Mac, Windows or even mobile. With the requirement of internet access.

6. UTS Library shall allow users to navigate within the system easily.
UTS Library is a user-friendly GUI that allows any stakeholder to navigate the system with no problems. With major headings and also the help function if need be.

7. UTS Library shall allow stakeholders to view computer availabilities online in real time.

UTS Library allows any stakeholder to view computer availabilities online in real time. Displaying which level, location, how many are available and also the total amount.

8. UTS Library shall allow stakeholders to attain specific materials if you are a registered student.

UTS Library allows registered students to search and attain specific materials of your subject course. Allowing access to past papers, lecture notes and also assignments.

9. UTS Library shall allow stakeholders to search any item within the data in many degrees.

UTS Library allows stakeholders to search an specific item in fine detail. Such as accessing the “Subject Database” selection available. Searching in specific categories or subjects to allow your search be more refine.

10. UTS Library shall give stakeholders various options in the “help” function.

UTS Library gives stakeholders various guides and solutions in the help function section.

11. UTS Library system shall allow the access of its mobile application, UTS Mobile.

UTS Library system newly introduced the new functional mobile application, UTS mobile. With the same functionalities as the web browser, it allows stakeholders to access this systems functions and families more easily and effectively.

12. UTS Library should allow the Library Retrieval System (LRS) to become more time efficient. (P)

UTS Library’s LRS should become more faster as its stakeholders are growly in large numbers. Due to this the system will have to process larger quantities.

-------------------------------

On the conclusion of our meet up, I'm glad that our members have put in the time to complete some of the work. We are on track with this assignment. Further following up on Friday (11th Of November) to discuss more.

On Friday the 11th of November, I was unable to attend class due to doctors appointment. Ive contacted my fellow team members about the issue. We talked on Facebook about another meeting scheduled planed for Wednesday the 16th.

# data[].attributes.body
This is the entities diagram which I and Christian have done this morning. for Arel and Ony, you guys need to have modify this diagram with more entities and attributes, have a look at Christian functional requirement. You guys can make some entities about the proposed functional requirement that he did and add more to the diagram itself. Get it done by tomorrow night 6pm

# data[].attributes.headline
Week 3 | Christian Tran 2944975 | Reflection

# data[].attributes.subject
Week 3 | Christian Tran 2944975 | Reflection

# data[].attributes.body
On Friday (4th of November) was my first class of BRM. I was unable to attend the first two weeks due to adjusting working hours that interfered with my time schedule. During the class I was assigned to a group for the upcoming Group Assignment A. Upon meeting my group members we discussed each of the roles that we are going to part take in this assignment.

I was assigned to complete the Functional Requirements, Introduction and also working together with the Entity Diagrams. We then scheduled another meeting on Wednesday morning to further discuss.

My team mates are friendly and outgoing guys that I would really enjoy studying and working with.

# data[].attributes.body
Last Wednesday I had a meeting with my group members. Our meeting held in the 7th floor of the Blue building at 11 am. All our group members attended the meeting. In the meeting, each of the members showed what they have done of the assignment. We discussed how to complete the remaining parts of the assignment.

I have done my part which is stakeholder analyst, mainly through observation and researches. Also, i've come up with 3 functional requirement, one of those is a new requirement, which can be used to improve the system.

Working with team comes easy to me as we divide the tasks equally to individual. That means less work for everyone. Plus, I think although we have 1 new member who miss a few lectures, we are still on track for the assignment

# data[].attributes.body
Stakeholder analysis

According to R. Edward Freeman (1984) the definition of the word “stakeholder” is ‘any group or individual who can affect or is affected by the achievement of the organization’s objectives’. As the main purpose of the UTS library is to provide information regarding the subjects being taught by lecturer and studied by the students. With the focus on studying purpose, the stakeholder of UTS library is vary from many levels of intelligentsia such as: students, lecturers, book authors, etc. Not only that but many indirect stakeholders are involved in process of the library, they take part in making sure the library works smoothly. Those indirect stakeholders are less affected by the library; however they play an important role in the process of the library.

·         Student: this is the group that gains the most benefits from the UTS library system, their interest is to find useful information for study purposes from books, websites, documents, etc provided by the library system either via internet or physical like books. However, their fear could be overload of information or unable to find the correct information needed.

·         Teacher (lecturer): The second group that also gains most of the benefits from the system is the teachers (lecturers) of a subject as the library is a great tool to support their teaching job. For example, when a student got lost in a subject, recommending a book or a website that could be found on the library is a good advice from the teachers.

·         Author of a book or a website: when writing an educational book or an academic website, it’s better to be known by more and more people. The library system of UTS is a great tool to advertise their work to many people especially students in UTS. Their fear could be their work being used for the wrong purpose (academic misconduct for instance)

·         Librarian: These people work in the library with various tasks such as: maintain the book condition, manage the library resources, solve student problems, etc. Basically. Their job to make sure everything in the library runs smoothly. Their fear could be when things go out of control, or unexpected problem happens that are difficult to solve.

·         IT department: this group of stakeholder plays a substantial part of the library system as other than books, the library is equipped with plenty of electronic devices (computer, lab, game console, projector, etc) and they are also connected to the same network system. Therefore, the jobs of the IT department are quite diverse since they have to maintain all the equipment, install new equipment when needed, fix the problems happened. Their fear could be unexpected error, or serious problems.

·         Network department: this group could be a part of IT department, however, their function are quite different. Their main job is to manage the UTS online network. As the UTS online library are linked to various academic source, therefore, students of UTS are provided with all the information needed and easy to find by the search system. The network department in charge of improving the online system, network security, maintaining the system, etc. The job is quite hard therefore a high level of knowledge is required. Their fear could be the unexpected error happened to the system or lack of security.

·         Educational Cooperation: as being said above, The UTS library is linked with many educational or academic resources. An educational cooperation provides academic course for UTS student (Cisco for instance) through the online network and students can complete the course remotely then receive a qualification. Their fear could be unable to ensure the quality of the course.

Besides those stakeholder mentioned above. There are also other stakeholders that might be affected by the achievement of the library but is not as much.

·         Security: their job is to make sure the security for the library as well as the students using the facilities within the library. Their fear could be unable to protect the facilities and the student which could lead to losing job.

·         General public: As the library are being used by many students. There are still some service outside the library especially food and drink selling based on the number of student visiting the library. Their fear could be low sale number. nM �����

# data[].attributes.headline
Week 3 reflection(Arel Pranta Gomes 2950865)

# data[].attributes.subject
Week 3 reflection(Arel Pranta Gomes 2950865)

# data[].attributes.body
Last Wednesday I had a meeting with my group members. Our meeting held in the 7th floor of the Blue building at 11 am. All our group members attended the meeting. In the meeting, each of the members showed what they have done of the assignment. We discussed how to complete the remaining parts of the assignment.

This week I discussed the Non-functional requirements of UTS library with my members and summarized the discussion and wrote it as a part of our assignment.

I like working with my team. They are very active. All the members supported my decisions and helped me by suggesting me some better ways to do the assignment. They shared their ideas with me. We have the same type mentality that is the main strength of our group. Communication problem due to the different class times is the main weakness of our team. Currently everything is going good within our team because all the members are very active and helpful. I think if we can meet more often we can share more ideas and thus we can improve teamwork.

# data[].attributes.body
Everyone please comes up with 3 functional requirements and adds in this post. One of the functional requirement must be new and hasn't been used in the existing system, please put the propose requirement in Bold and Italic front.
>Tony:
The UTS library system shall allow students to access the online academic resources.
The UTS library system shall make sure all the electronic equipment is in perfect condition to use for study purpose
The UTS library system should speeding the Library Retrieval System (LRS) into process as soon as possible.