# data[].attributes.body
this week we have done every task in the tutorial by brian stroming and stroming google out.we started with the kahoot where i have scored 9 out of 10 which is a bit awkward for me where i have expected 10. and then we have done self assessment and brief about all the diagrams.  we have also done bpmn and data flow diagrams not drawing but copy and pasting. this was a good week.

# data[].attributes.body
This week I completed the Kahoot quiz at the beginning of the tutorial as usual, referring to the content based in this week's lecture (DFD & BPMN). Following the quiz, I completed the self assessment of the performance of my group and I in Assessment B.

The activities in the tutorial file in Week 10 was then completed in class and pasted into Padlet.

# data[].attributes.body
For this week, we submitted our Assessment B in the lecture and during the tutorial, we started off with the weekly kahoot quiz. We also looked through the Sample Exam Practice Test so we know what to study for the exam. After that we did our self-assessment for our assignment B. Furthermore, we did the Task 4 of the tutorial which is making a simple visio diagram of all the diagrams we learnt this semester. Overall, it was a very proactive tutorial preparing for our exams in week 12.

# data[].attributes.body
a) The exam has 2 parts:
1. Part A - Consists of multiple choice questions
2. Part B - Open-ended questions
b) Part A - 40 MCQ, each worth 2 marks
Part B - 3 Open-ended questions, each worth 3-10 marks each(total of 20)
c) Part A covers content from Lectures Week 1 - 10
d) Part B covers content referring to requirements specification. (Written forms and in diagrams(models).
e)
1. Make sure you process the information: create meaningful connections, sort, rank, draw tables, diagrams, make lists
2. Self-test yourself in a variety of ways.

# data[].attributes.body
this week we had a group meeting and we have done the draft of class diagram and we have completed the state machine diagram almost and we have our methodologies are at ending and we also have completed the class diagram online by a tool . we hope we get good results in the assignment and the class diagram and state machine diagram was a bit complicated part for us because the book in us library couldnt have much states as expected.
the class diagram was challenging for us because

# data[].attributes.body
This week was all about combining everyone's individual contributions and polishing it up to a final report. Our weekly meeting was used to discuss the remaining 2 diagrams and finalised over the next couple of days via online chat. We read through eachother's work and made suggestions where we saw fit.

This week I created the class diagram and proof read through my work. I also created a new use case description as I used a different one for Assignment B. I also went through and made amendments to our Assignment A diagrams where necessary. Lastly, I made some final recommendations for my teams individual work.

This week was a busy week for everyone and finding time where we could all discuss things together was difficult. We managed to set a couple of periods at unusual hours to make up for this. Once we got together we were able to finalise our assignment.

# data[].attributes.body
For this week's meeting, we finalised our individual diagrams and shared them with each other. We also made a draft of our State Machine Diagram during our 2pm meeting. Other than that, our meeting was full of finalising diagrams and asking each other if we need help with anything and sharing our opinions about each other's works

During the tutorial, we asked our tutor for her brief feedback on our diagrams and asked for any finalisation.

For the rest of the week, we struggled to discuss our assignment as we all had our personal responsibilities to deal with but we found a way to make things work during late hours and in the end we were able to finish our assignment.

# data[].attributes.body
This week all our individual work from last week was combined and analysed together as a group in our usual meeting. The drafts of a State Machine Diagram and Class Diagram were collected from each group member. The best scenario from each from member's draft were taken to create a final version of each diagrams for the assignment.

# data[].attributes.body
For this week, our group had our weekly meeting at the homework room where we discussed what else we need to do for the assignment. We checked everyone's diagrams and made suggestion about what we think would be a good change.

During the tutorial we did a practice diagram for our Sequence Diagram and made a draft to show our tutor and ask for feedback and some pointers about what we can do for our Assignment B Sequence Diagram.

For my Sequence Diagram, I found it difficult to think of appropriate objects to use and the right messages in between the objects. In the end I asked my group mates for their opinions and made changes in my Diagram based on those.

# data[].attributes.attachment_link.title
Use Case Activity Diagram Borrowing Book

# data[].attributes.body
This week was set as our week to create our individual diagrams as well as to start thinking about the state machine and class diagrams.
We used our meeting to discuss what needs to be done in those diagrams and how to go about creating them.

This week I worked on my sequence and activity diagrams. I had drafts ready to get some feedback during the tutorial and once receiving it I amended my diagrams. I also created a state machine diagram for initial feedback. Finally, I completed my summary of my system development methodology.

The challenging aspect of this weeks work was the uncertainty due to combining information. For example on the diagrams, if a certain message should be a 'response', if we've missed any components or added too many etc. We solved this by pushing ahead of schedule to get feedback ASA

# data[].attributes.body
For this week we continued with our assignment B. We created a draft for our individual diagrams and asked our tutor if there are any changes that needs to be made.

During the tutorial we continued to finalise our individual Sequence Diagram and Activity Diagram. My diagram is based on the use case description that I made from Assignment A which is 'Borrowing Book' and for this Assignment, my diagrams are based on a successful scenario.

# data[].attributes.body
This week our group focused on completing our individual diagrams ready to be discussed in the next group meeting. A draft of a state machine and class diagram was also required in addition to our individual input.  This week I believe  that I used my time efficiently to complete all required tasks in preparation for next week.

During the process of creating the sequence diagram, I found it difficult to draw up my sequence diagram for my use case. I decided to discuss this issue with my group members. After getting a better insight on their diagrams, I was able to grasp a better understanding of how to better execute my diagram.

It was also discussed that we were to research a number of methodologies to include in our assignment and email it to our group leader.

# data[].attributes.body
this week i really concentrated on the growth mindset which was taught on our lecture which was very helpful for me which has changed my way of approaching the things and changed my perspective towards the situations related to my academic and my social life
so this week i have completed the sequence diagram it was a bit challenging for me as it is dealing with only object i have to think object oriented to finish this diagram successfully and i also have to study the use case diagram and activity diagram to get this done. though i have enjoyed working on sequence diagram because i have another subject called programming which deals with object oriented coding so i have enjoyed that this diagram would help me in many subject and in many ways.

I am also progressing in my research about the scrum looking up at the journals, articles getting to know about the different stages of scrum which helps me to know about the industrial processes being in use.

# data[].attributes.body
This week was quite productive in regards to Assignment B progression. In our meeting we created a timeline where our first milestone was to have each completed an activity and sequence diagram for our use case descriptions from Assignment A.

During our tutorial a suggestion was made to use a different use case as my sequence diagram was too basic. So I spent this week looking at a few use cases and selected one to use. After creating a draft I used the homework room to create my diagrams. I also did some more research on the RAD method.

My biggest concern was finding a use case which was significant enough whilst having enough steps to create worthwhile diagrams. However this was solved by seeking help from the team which was quite effective in helping me come to a decision. It's quite apparent how having a team can help come to a decision through the varying perspectives.

# data[].attributes.body
This week Awkward Turtles began to create an Activity Diagram each relating to our assigned use case scenarios. During the tutorial each member continued to create a Sequence diagram for our use case scenarios.

It was then discussed at the end of the tutorial that each member completes their diagrams at home and researches a methodology each, ready to discuss and implement into our assignments for next week. My use case scenario was ' Requesting from LRS ' and the methodology I chose to research was the SDLC, in which I defined what is involved in the process and what each phase of this process executes.

During the process of creating my activity diagram, it was suggested that I simplify some of the steps and focus on the main stages of my use case, as my diagram was too complex.

# data[].attributes.body
this week i have really tried to work on class diagram as individually but  I ended up as a mess. class diagram is very complicated as an individual thats why it is given as a group assignment
besides that i have done the activity diagram for paying fines in the library system that was pretty much easy for me as it is dealing with  many scenario of the object in the system    where i have realised very late that the diagram deals with many  scenario which has diverted my diagram initially
i am also doing research on the scrum which is a type of agile methodology where i got to learn more knowledge in the business world and advantages of the scrum.this week was a quiet progressive for our entire team as we have going through the diagrams and its aspects deeply to understand and analyse the core aspects of the assignment given.

# data[].attributes.body
we had a group meeting before the the tutorials and have discussed about the assessment-b brief and have discussed the improvements that should have been made to the assessment-a. and we have tried to make a draft of the class diagram. the challenging part was the class diagram that should be done at the last. we have confused ourselves by starting with the class diagram. which seems to be easy but not much. we took the class diagram of the car rental system which has been done in the previous week tutorial as a reference for class diagram of the uts library system which have cleared a bit confusion that me and our group had.
I have also tried to complete the activity diagram of uts library system. we have also done the activity diagram of the car rental system before the tutorial which made our tutorial go easy.

# data[].attributes.body
This week Awkward Turtles met as usual in PC at 2pm. It was discussed that we improve certain areas of our performance in completing the next assignment after receiving our feedback from the previous assignment.

As a group we also had a brief look at the scaffold of our next assessment task and discussed as a group the possibilities of how we could complete each sections.
A self-graded mark was assigned by each group member after our meeting. It was agreed as a group that we wanted to set a goal to complete each section of the assignment in relation to the topics that were learnt in the lectures each week.

# data[].attributes.body
Tutorial task

# data[].attributes.body
Week 6

# data[].attributes.body
Our group, Awkward Turtles had a meeting before getting our results from the tutorial where we discussed what we think we should improve on in our previous assignment. From that meeting we figured out that we all had different opinions on which parts of the assignment needs improvement. We also discussed our options when it comes to which diagram to use for our individual use cases

Later on in the tutorial, we got our marks for the first assignment and compared our self-graded marks to our actual marks. We further discussed what we can do to improve and what we should do for the next assignment. During the tutorial, we also asked our tutor why we got the marks that we did and asked what we did wrong and how to improve it.

# data[].attributes.body
This week Awkward Turtles met as per usual, in preparation for Assignment B. We brainstormed some ideas, as we viewed the Assignment B sample. It was agreed that each member of the group was to have a draft of the components that we have already learnt in the lectures such as Use Case Diagrams and Descriptions, and Class Diagrams.

After preparing for the assignment, we logged onto pan2 and completed our individual self assessments referring to our performance during the completion of Assignment A.

We also had a quick discussion of our performance as a group in Assignment A and how we could improve for the upcoming assignments as a team.

# data[].attributes.body
During this week our group met up twice in preparation to upload and hand in our assignment at the end of the week. This week was extremely productive for the group as many tasks were proposed in our first meaning by our group leader to complete before our second meeting, where it was decided that we combine all our individual ideas.

Some of the proposals included:
- Individual drafts of entity diagrams including cardinality relationships
- Interview questions & answers from our individual research
- A draft of our individual use case descriptions and diagrams

In our second group meeting we combined all our individual work and implemented the best of each of our individual work to add to our final assignment.

# data[].attributes.body
This week was a very productive week for Awkward Turtles. Along with our regular Monday 2-4pm meeting we added an extra from 1pm to roughly 6.30pm. In our first meeting we were able finalise our stakeholders and requirements. For our entity relationship diagram we chose to all make a draft and then in our second meeting combine all the best points from each into a 'final' ERD. We we were all confident on the use case diagram so we decided to effect that together in our 2nd meeting. Our second meeting was conducted partially in a reserved library room and the remainder in the homework room using visio. We used this time well and managed to finish our diagrams.

This week, I created a draft for the ERD, wrote the introduction for our assignment,  went through everyone's work and suggested any additions/changes and made some final additions to our diagrams alone on Friday. This has definitely been a very productive week.

The main challenge for our group this week comes from our choice for everyone to do a component and combining everyones work. This posed a challenge where there was a difference in ideas and how to include everyone's work. Through discussing the different options pros and cons we were able to reach mutual decisions without any conflict. As a group, for me a strength for Awkward turtles is our ability to come to an agreement regardless of our differing perspectives.

# data[].attributes.body
This week Awkward turtles had a regular meeting on monday between 2 - 4 pm where we have finalised and improvised  the requirements, entities and stakeholders and  we have worked a bit on ERD but we had a bit difficulty with the connections and cardinalities then we have discussed use cases.
our team had on more meeting on Wednesday from 1pm to almost 6:30 where we have discussed about the design of ERD and use case diagram, and we have also implemented on visio on that sitting, we have allotted one  use case each that should have description. we also have interviewed some of librarians to clear some of our doubts.
the ERD diagram part was challenging for us where all the entites and attributes were ready but it is difficult to connect them made a bit messy but somehow our team had came up different ideas to represent the diagram.working with visio was bit difficult as it is first time for us.
The use case diagram was a bit easy thing for us as majority of our team was familiar with that diagram in previous semesters, our team had collaboratively worked to get the work done.
it been a exceptional experience for me to work in this team for this project where everyone had different way to approach the topic and subject and managed to satisfy everyone with their contributions. This project is a combination of four different approaches and empathy of the subject.

# data[].attributes.body
For this week, our group Awkward Turtles had a meeting on Monday from 2-4pm where we started finalising the functional and non-functional requirements, our ERD diagram and UML Use Case diagram by asking our tutor to check if our given ones are correct. We also discussed how we would present our diagrams and what would be the best way to present it. We also had a meeting on Wednesday from 1-5pm in the library to finish our ERD and UML diagrams.

On Thursday we finalised the use cases that we are going  to use for the Use Case Table. We have chosen 'Borrow Books', 'Request LRS', 'Search Resources', and 'Enters Library'.

Overall, this week has been very productive. This first assessment has taught our group better ways to manage our time and how we can improve our productivity for our final group assessment. We also know how we can split future tasks and be more open with our own ideas to share with the group.

# data[].attributes.body
Awkward turtles had a face to face meeting from 2-4pm on Monday. During this time we managed to revise the lecture content from that morning, discuss the assignment and had a quick look through the tutorial work. In regards to the assignment, we started to identify some initial stakeholders, entities and requirements. Throughout the week we all contributed to collate the list you can see below.

For my contribution to the requirements gathering I interviewed a librarian and searched through the website. These tasks allowed me to think of some new requirements that could help with curating future texts.

Thus far, I haven't felt there were any major issues in the work we had to do or the methods we chose to go about it. My biggest challenge was to imagine the scenarios leading up to design and implementation of the system in order to capture all the important requirements. I think practice and asking questions will be key in achieving a solid understanding of requirements modelling.

# data[].attributes.body
Hey team, just wanted to put a quick summary of the things we've gotten so far.

Stakeholders
1. Dean of UTS
2. Dean of INSEARCH
3. Developers
4. UTS/INSEARCH Students
5. Teachers
6. Librarians
7. IT staff
8. Cybersecurity provider
9. High school/other major universities students
10. TAFE (borrowing agreement for students and staff)
11. Personal researchers
12. One-day visitors
13. Partnered libraries

Functional requirements
1. System shall allow member to log in
2. System shall allow member to borrow book/s
3. System shall allow member to browse online databases
4. System shall allow member to browse books
5. System shall allow member to request book online
6. System shall allow website user to search other libraries for texts
7. System shall allow student to reserve facilities (Rooms, computers etc.)
8. System should have an online chatbot
9. System should record data on borrowed books for research
10. System shall allow members to check current borrowed books/fines

Non-functional requirements
1. System shall only be accessible by members
2. Website component shall work on all browsers
3. Website component shall be mobile-optimised
4. Data collected from system should be stored in an online database
5. Website component shall be written using Query
6. Website should be optimised for android {NEW}

Entities
1. UTS/INSEARCH Students
2. Teachers
3. Librarians
4. Community members (Highschool student, personal researcher, one-day visitor etc.)
5. Computers
6. Printers
7. Rooms
8. Books
9. LRS (Library Retrieval System)
10. Fines
11. Loans
12. Returns

# data[].attributes.body
on Monday 30th October, Group named Awkward turtles had its group meeting for one and half hour discussing about the assignment and lecture notes to refer with UTS library. we are developing the entities and requirements for the system gradually by interviewing librarians and students in the library. we also have discussed more about entities and requirements which led to re checking of each others work to finalise the work in assignments the typical part was figuring out differences between functional and non functional requirements, but our team has successfully managed to solve the issues.
coming to my contribution i have contributed the functional and non functional requirements for the system, entities, attributes and i have interviewed two librarians to get a clear idea about entities

entities and attributes.

Students- Student ID, address phone number, area of study, name

staff- employee ID, name, position

books- book type, book name, authors, RFID tags.

LRS- RFID tags, size of the book, row and column number in the storage.

OER’s- name, license number, URL, Area of excellence.

database-name , type , database identification.

rooms-room number, building number, Room type.

Articles-name, ISSN, DOI,ISBN,,E-ISSN, type, Area of information.

membership-name, membership ID, membership type, membership length.

computers-Device ID, MAC, IP, name, Type, Usage.

printers-printer number, Printer Type, Printer Accessibility.

accessibility(non existing entity)- ID card, Product number, Projector ID , Usage Time.

website-Domain, Server IP, UUID.

people-name, phone number, Address, Amount.

non-functional requirements are

System shall allow extra hours accessibility

System shall allow users in research

System supports in referencing

website of the system shall inform about associated upcoming events

website of the system shall support secured protocol upon login

System shall support dynamic state website

System shall have FAQ's to make the users clear with the operation of the system.

functional requirements Are

system shall allow Self-service loans to users

System website shall allow users to lodge an enquiry.

System shall allow users to play games.

System shall support publishing journals

System shall allow users to take prints

System shall allow users to access the open licensed educational resources.

# data[].attributes.headline
Functional & Non-Functional Requirements – Car Rental System

# data[].attributes.subject
Functional & Non-Functional Requirements – Car Rental System

# data[].attributes.body
Task 3 - Requirements list Practice
Non-Functional
1. System shall operate on all browsers
2. System should be mobile optimised
3. System should have a mobile app
4. System shall have help/FAQs/guide
5. System shall consist of cyber security measures
Functional
1. System shall allow customer to log on
2. System shall allow customer to choose period of hire
3. System shall allow customer to communicate with Chat Bot

4. System shall consist of cyber security measures
5. System should allow customer to choose pick up location
New Functional & Non-Functional Requirements
Functional
- System makes recommendations  e.g. offering popular choices
Non-Functional
- System shall use a large online database
- System shall have information stored on the Cloud

# data[].attributes.body
Week 3 - 30.10.2017
Our group, Awkward turtles had our second meeting where we discussed Functional and Non-Functional requirements. We also allocated parts of the assignment to each member.

We've decided to interview shareholders (librarian), have anonymous surveys (survey monkey), interview family members/friends, and interview classmates.

So far we have all requirements needed for the assignment besides the introduction and appendix.

During Week 4 tutorial, we will be constructing our assignment and work on our ERD diagram.

# data[].attributes.body
On Monday 30th October, Awkward Turtles met up in the PC homework room to discuss the non-functional and functional requirements of the library system. It was decided that each team member was to think of a few examples of entities/ stakeholders to add the list in which we had discussed in our group meeting, ready for the following meeting.

It was also discussed for each member to gather information from stakeholders using distributing the role of performing certain methodologies among ourselves.

Next week we will be discussing all the results measured from each member to construct an ER diagram.

# data[].attributes.body
Week 2

# data[].attributes.body
Week 2 – Getting Started 23.10.201

A)

·         Finalised the group

o   Picked a team leader for the whole semester

·         First group meeting

o   Assigned parts

o   Discussed how we will do the assignment

o   Discussed when group meetings will be

o   Set goals for every week

o   Decided on how we will communicate and share documents

o   Discussed the level of work each member should contribute

o   Discussed that each member will help decide whether or not if the amount of work is by a member is satisfactory or not

B)

·         Discussed some entities for the library system

o   Librarian

o   Student

o   LRS (Library Retrieval System)

o   Website

o   Books

o   Computers

o   Rooms

o   OERs

·         Decided that we will go through sections of the assignment every week during the group meetings that was discussed in the lecture

o   This week we discussed entities, attributes etc. in the lecture, therefore we discussed the entities, attributes etc. for the UTS library system.

o   Next week we will be talking about Functional and Non-Functional Requirements

C)

·         Questions for the librarian
1. May I look at the initial requirements specifications of the library system?
2. May I look at the error logs?
3. Any issues you can think of that you are constantly running into?
4. Are there any periods of major congestion?
5. Is there a significant issue with missing or not returned books?
6. What improvements would you like to see in the system?

# data[].attributes.body
On Monday of 23 October 2017, group named awkward turtles has elected Andrew as the groups leader,the group has decided to meet at prince center in the homework room at 2:00 pm every Monday, the group gonna communicate through Facebook messenger and in person to share our ideas for this subject and prescribed assignments. we will combine our work on google docs and the group makes the decisions based on the acceptance of the major group members and leader. based on the peer judgement the group decides that the individual work is accepted or not.

the group has assigned a certain tasks every individual in the group and has discussed about entities and attributes and we gonna interview a librarian later this week to gather the user requirements.we have identified some entities and attributes related to our assignments and also related to the tutorial work
Entities we have discussed are
Librarian or staff

Student

LRS (Library Retrieval System)

Website

Books

Computers

Rooms

OERs

our team leader has the questions that should be asked to the librarian our team leader interviews librarian on behalf of whole team where all the team has contributed

# data[].attributes.body
a) On Monday 23rd October our group, Awkward Turtles elected Andrew as the leader for the group assignment and to remain leader throughout the whole semester. We decided on performing mixture of online and face-to-face communication during group meetings. During this meeting it was arranged that we meet every Monday, between classes in the Homework room, PC building at 2pm.  We will upload and combine on the assignment using Google docs and we will rely on each other to judge whether the work is of acceptable standard. If there is an experience where I am unhappy with a group member’s commitment it should be discussed as a group with the certain team member about their performance, if the person persists then I would continue to escalate it to the tutor.

b)  As a team we have so far discussed the following entities for the library system:
- Librarians
- Students
- LRS - Library Retrieval System
-  Website
- Books
- Computers
- Rooms
- OERs
We have decided to complete each section of the group assignment according to the topics learnt in each lecture. E.g. Week 2's lecture included information about entities, cardinality, primary keys and relationships. Thus in today's group meeting we discussed the following entities and cardinalities  related to the library system

c)
Questions addressed to librarian
1. May I look at the initial requirements specifications of the library system?
2. May I look at the error logs?
3. Any issues you can think of that you are constantly running into?
4.  Are there any periods of major congestion?
5. Is there a significant issue with missing or not returned books?
6. What improvements would you like to see in the system?

# data[].attributes.body
Our group is Awkward Turtles, we are a group of 4 from the Monday 4-6pm tutorial.

We have decided that I will be the group leader throughout the semester. We have chosen and created a facebook group chat as our medium of communication in Week 1 and thus far we have not had any issues. We have set Mondays 2-4pm in the PC homework room to meet and work on the assignment. Outside these hours we will be sharing our work through Google docs. So far, we have been able to come to an agreement as a group in regards to next steps and I am confident this will be the case throughout the semester.

In today's meeting (23/10), we discussed evenly distributing whatever work we can such as identifying entities and attributes. During our meetings, we will collate and refine our information. Thus far, we will individually be brainstorming entities and attributes by the following Friday (27/10).

6 Questions for Librarian
1. May I look at the initial requirements specifications of the library system?
2. May I look at the error logs?
3. Any issues you can think of that you are constantly running into?
4.  Are there any periods of major congestion?
5. Is there a significant issue with missing or not returned books?
6. What improvements would you like to see in the system?

# data[].attributes.body
In our weekly meeting, we begun discussing our assignment A and how we can translate that into Assignment B as best we can.
Naturally, we did an overview of assignment B so that everyone has a understanding of what will be required. We decided many components were best left until we learnt the topics in lectures, however we were able to allocate a methodology for everyone to start researching.

This week I set 2 priorities, for myself which were to start researching my method (RAD) and to analyse Assignment A and understand the feedback we were given.

The most challenging task for me was to think ahead and apply what I learnt about the RAD method to a library system. As a team, we are going to be discussing our methods to establish a general idea of what strengths are beneficial for us. Fortunately, there are a lot of resources online which was my predominant source of information.