Week 2

This week, I focused on writing the description of our product. My main goal was to clearly describe the general factors that affect the product and its requirements, of course containing just a background information. I proceeded with the product context, if our product is independent or if it interfaces with other related systems. I created general customer profiles for each type of user who will be using the product. Listed any assumptions that affect the requirements and described any times that will constrain the design options.

I paid special attention to the tone of the description, making sure it accurately reflected the values and mission of our project. I wanted to ensure that readers would feel excited and motivated to learn more about our offering.

Throughout the process, I collaborated closely with my team to ensure that my work was accurate and aligned with our goals. I incorporated feedback and suggestions to ensure that the final product was polished and effective.

Overall, I am proud of the work that I accomplished this week and I am confident that the product description will help drive interest and engagement in out project.

Week 3

My task for this week was to create the Entity Relationship Diagram and Relation Schema. Therefore, I started gathering information about the project's requirements and data entities. I understood even more the purpose of our project, stakeholders involved and the data that will be used and manipulated within the project.

Next, I began identifying the entities and their relationships. I did this through brainstorming, reviewing project documents, and talking with my team.

Once I identified the entities and their relationships, I created an entity relationship diagram (ERD) that visually represents the relationships between the entities.

From the ERD, I then created a relation schema that defines the tables, columns, data types, and relationships for the database.

However it's important to review and refine the ERD and relation schema as needed, as the project progresses and new requirements arise.

Overall, the process of creating an ERD and relation schema was time-consuming and required attention to detail, but it is critical for ensuring that the project's data is organized and structured in a way that supports the project's goals.

Week 4

This week, I took some time to review my past work, and during this process, I noticed some inconsistencies related to the naming of the Favorites table. These inconsistencies were observed between the (ERD) and the (RS) diagrams. To address this issue, I have taken the necessary steps to correct these inconsistencies. It is crucial to maintain a coherent and organized documentation system, especially when it comes to crucial elements such as table naming.

Week 5

This week, I was assigned to work on collaboration diagrams for the project. My work was divided in half with another member of the group, Patrik Madhi, who as a matter of fact was a great understanding partner. I understood the interactions exchanged between components, for this the sequence diagrams helped a lot. I created a visual representation using draw.io, to illustrate the identified interactions. I did review the collaboration diagram for accuracy and clarity, but I'm also waiting for the teacher's feedback.

Week 6

This week, after we got some feedback from the teacher, I was advised to do some changes to my diagrams. Since I had the communication/collaboration diagrams, any changes in sequence diagrams I had to reflect it on my diagrams. Specifically removing the database as an object and replace it with the specific entity of the case. Then I had to make some other changes in the responses section. After getting the groups approval, I was done with it.

Week 7

This week, I found myself making adjustments to the collaboration diagrams once again due to some minor changes in the sequence diagrams.

Then we decided to do the extended use cases. Specifically, I had to incorporate the following actions: registering the librarian in the system, confirming librarian requests, viewing statistics, viewing profiles, editing profiles, deleting profiles, receiving feedback, logging out as an administrator. It required careful consideration to ensure that all the necessary interactions were accurately represented in the diagrams.