Activity 4: Managing the database with guaranties 20/12/2023 – 22/12/2023

Designing transactions and managing access control

Objective: Show the importance of dealing with guaranties on concurrent access and fault tolerance by defining transactions and reasoning about access rights (CRUD) to the database according to user types.

Theory background [PDF] 

  • Transactional model: ACID properties
  • Access control function in RDBMS

ToDo:

  • According to the users willing to access your database (Activity 3) propose use case diagrams showing the functions they can perform and thereby defining access control according to roles (user types).
  • Specify the transactions to be considered according to the CRUD operations associated to the application.
  • Propose sequence diagrams for the CRUD operations that exhibit the transactions.
  • Implement CRUD operations 
  • Propose testing use cases of your access control policies and transactions

Deliverables:

  • UML Use diagrams for associating user roles – access rights for interacting with the DBMS 20/12/2023
  • UML sequence diagrams for the CRUD operations 20/12/2023
  • Transactions specification  (specification) 20/12/2023 ; (pseudo-code) 22/12/2023 
  • Explanation of the role of the defined transactions (document) 22/12/2023
  • Implementation of CRUD operations (code) 15/01/2024
  • Testing use cases (code) 19/01/2024