The assignments allowed all groups to answer questions regarding Concurrency Control and the importance it plays in Database Management. The work was divided well among the group members and each person contributed well. This assignment helped us understand how this type of work is applied. This is basically something that is used to fix conflicts within the system when multiple users are accessing data or maybe even altering it. The concurrency system is made to sort out this data in a way where it will not be harmed by muti-user activities. An application like this is something that can be viewed in how we undertook the group work. We are four users who had access to the same assignment and each contribution would alter the results. There was a need for harmony within our work.
All of the work done, especially the case study on ProSoft were small steps to build the puzzle of Database Management. An application like this cannot simply be learned by reading text book or listening to lectures. Group work was necessary to get hands-on experience on the topic. The tasks given were a great way to get people involved. Since the tasks were not simple, we helped each other answer the questions and gave our own interpretations of how the system worked.
The different strategies were discussed for this concept. Illustrative examples are the best ways to learn how to apply these things in Database Management. My role was to provide the group with the answers to my designated questions. The team could not have worked well if there was no sense of togetherness. I believe that my contribution with the group leaned towards the roles of a leader. The output is something that is defined by the effort given. I believe that we have produced a sound output which could not have been achieved if one or more of the group members lacked in terms of contribution.
I was in charge of creating the task type. This is an important part of the group work because other members relied on it to do their own work. Additionally, I completed the sessions and employee tables. My part in the concurrency work was to answer questions three to five. This helped understand the importance of some commands, deeper knowledge of concurrency tables and a broader understanding of database management systems. My part in security was to specify all the access privileges for the engineer. This was important for other members to continue their work, so we really had to submit on time and work together.
Conflicts are those that occur everywhere, even in database management. I think that this sort of task was given in group work so that we could see how conflicts can be resolved in real life so that we can apply it within the system. The tasks I was to complete involved the creation of the task type, I needed the contribution of other group members for this so that the work is fluid and consistent. If I had gone my own way, it might not have worked with the other pieces the other members were creating. Like in concurrency tasks, we had to be in harmony so that the final output’s integrity is not disturbed.
Conflict is something seen everywhere. If there is any type of conflict, from minor to major, it needs to be resolved sot that events can push forward and no productivity is hindered, or in terms of database management “livelocked”. I believe that we worked well as a group and handled all the task accordingly. No one slacked off or gave the team dead weight. All group members contributed well and we generally had a good flow in terms of work.
Part of my task was to define the roles in given SQL data control language within database management. These commands are very important when it comes to concurrencies. For example, the SAVEPOINT will save the data at the certain point of transaction. The COMMIT command will permanently change the transactions that have been made. This is something that is also needed in group work, people have to agree to commit to a style or an output. The ROLLBACK will erase all changes made up to the last COMMIT point. These are very important in database management so that all transactions are managed. This allows the users to create reliable and user defined transactions. Additionally, there is room allowed for recovery of data; this is most helpful when system failure occurs. The roles these commands play is crucial in any units of worked performed. These commands also allow isolations when there is multi-user activity on going in a system. If there is no known isolation in the system, the outcome or output will become erroneous.
I guess this is also why group work is so important in learning how database management works. If one group mate failed to complete given tasks, there, the system will not automatically fail. There are different ways to handle the situation since there are other members. Of course, this does not mean that there is room for someone to not contribute to work. However, the point of failure can be pinpointed to that one group mate who might have failed to give output.
My portion also included the pessimistic and optimistic controls. These were very interesting to learn about, especially in the cases of locking. These strategies would assume outcomes when multiple users are seen to have activity. In the case of pessimistic locking, the system will prevent any changes made because it might jeopardize the data. All data alterations or deletions are prevented during this type of locking. Conversely, the optimistic lock will allow alterations to be made and will detect any collision within entries. The conflicts, if there are any, are dealt with when they happen. Resolutions are come up with in the event of a conflict within the data. The optimistic type of locking is more proactive and I believe this is the way group work should be handled. We should anticipate for mistakes or delayed work, yet we should not try to control everything ourselves. If there is a chance of conflict within any given work, that is the time to try to come to a resolve. All group members must be part of this resolution or intervention so that the data or work is still up to standard and is not compromised.
When assessing myself, I believe that I worked well with other people. I was able to learn more by trying to solve the problems of other group members. The ideas given in the work assignment were difficult, yet it gave us time to collaborate our ideas and build a relationship on interpersonal levels. I would score myself “excellent”, an A4 grade. Like I mentioned above, I believe that I was able to contribute to the team well and show leadership amongst members. There were a number of challenges within the work given, but I believe that I have met those challenges well and was able to deliver work in a timely manner. I also think that I was able to understand the work given on a level where I can apply it in real life. For this task, In would grade myself an A2, which is also under excellent. The tasks given were tackled well though difficult they might have been. The level of understanding that was displayed with the output, I believe was consistent. Also, we were able to show flexibility in terms of work. We adjusted to each others’ roles well and we were able to create a harmonious relationship. We all got to help each other when it came to delivering the project. In terms of the contribution, I think that the group did well. There were no instances of slacking off. All members showed integrity. For my self reflection, I will grade myself here at A4 again since I believe we did really well in handling the responsibilities given to us.
The overall task given was quite interesting. At the start, I do admit that everything seemed confusing and too much to take in. However, the tasks given were done in such a way that they were easy to undertake. The group work, reflections and meanings behind it all helped in understanding the concept or topic better. Once the information or ideas started to surface, the puzzle of database management became a lot clearer. It is very easy to relate something like this to real life. I think that making this into group work was a smart idea for applying management to real world problems.