Week 2

After the group meeting, we divided the project requirements in 6 parts. I was assigned to deal with Usability, Efficiency, Reliability, Monitoring & Maintenance and Integrity & Security which are part of the Non Functional Requirements. I then defined all the given topics according to our project and then consulted with the other team members to make sure our work was in alignment with each other.

Week 3

After the group meeting, we divided the diagrams of the software design part in 6 parts. I was assigned to deal with the Use Case Diagrams. I made sure to read all the functional requirements of the project given in last weeks work. I then divided them into 3 parts for the 3 different users of our system. I made a use case diagram for each actor as well as a larger use case diagram between the three actors and the system.

Week 4

This week, our given assignment was to review and correct any mistakes on our diagrams, as well as turning in chapter 3.1 of the Requirements Document. As previously stated in my last Wiki, I was assigned to deal with the USE Case diagrams. My work was previously checked by the professor and it was deemed correct. I still checked my diagrams once again and made sure all the functional requirements were listed correctly among all actors of the system. There were no changes made to the USE Case diagrams. As for the Requirements Document, we had previously divided our work for it and it was checked at least twice by each of us. Therefore there were no changes to the Requirements Document made by me for this week either.

Week 5

This week my task, along with Sara was to deal with the Sequence Diagrams for our program. We decided on the different interactions that needed to be designed into sequence diagrams for our system and came up with 10 interactions, 5 user operations and 5 book operations. We decided that I would deal with the user operations related diagrams so I had to generate sequence diagrams for User Login, Student Sign Up, Librarian Sign Up, User Edit profile and Student send feedback operations. To do so, I had to inspect the class diagram made by Amara and Anita and then model my sequence diagrams according to the operations listed in the large class diagram. Each diagram concretely explains the given interactions from the user's viewpoint, showing the input functions as well as the return functions from the system, taking into account all the possibilities of each interaction.

Week 6

This week we all had to revise our work from the previous week and make sure everyones work was aligned with one another's. As previously stated, last week I had to deal with the user operation Sequence diagrams. Previously, I had 5 diagrams in total: User login, Student Sign Up, Librarian Sign Up, User Edit profile and Student send feedback operations. This time, I had to make a couple of changes to the User Edit profile diagram. I had to make 3 different profile editing diagrams as the three different users had slight differences in their edit profile algorithms. Therefore there are now 3 different sequence diagrams for profile editing: Student, Librarian and Administrator profile edit. Along with this change, I also made a couple of changes in the other diagrams: User Login, Student Sign Up, Librarian Sign Up and Student feedback diagrams. These changes were mostly small details such as method names to match the names of methods in the new Class Diagram updated by Amara and Anita. The sequence diagrams are now fully in line with the class diagram as well as all the requirements previously posted.

Week 7

On the last week of the project, I was assigned to deal with User Scenarios along with Sara. Apart from my new assignment, I also added some final changes to my previous Sequence Diagrams in accordance to the tips I was given by the professor. As for the User Scenarios, Sara and I came up with multiple User Scenarios for each user of our system and then we each took half of the student, librarian and administrator scenarios. I searched online as well as the last year’s project given to us by the professor, and fully understood the way to write User Scenarios correctly. I then wrote my half according to our project and re checked them for any logical mistakes before sending them.