1. IT Faculty Software Engineering Seniors UML for a simple DataBase Management System Prepared by: أنس الأسود بشير الفروان زهير الزعبي ياسر المحمد

2. Tips: Who interacts with our system: - we’ll consider an administrator who manages the system itself, he can also create users and define their authority can also create users and define their authority - a user who uses the database, query, modify items… The NEW Functionality allows the user for multiple choices like: The NEW Functionality allows the user for multiple choices like: - new DataBase: creates an empty database - new table: creates a table in the current selected database - new Column: creates a column in the current selected table…. after defining a new column a user can define it’s constraints, like: after defining a new column a user can define it’s constraints, like: primary key, foreign key… if a user defined a primary key: after saving we can create an index by default for it we my allow checking referencing table and referencing column in foreign key definition

3. We could also make a new: We could also make a new: View, row, user, index, stored procedure… View, row, user, index, stored procedure… We assume these functions are achieved through an invocation for a data designer UI. We assume these functions are achieved through an invocation for a data designer UI. Any new command accompanies with checking the user authority i.e. : Any new command accompanies with checking the user authority i.e. : Not all users can make a new database Not all users can make a new database Some users can create tables, indexes, but others can’t Some users can create tables, indexes, but others can’t In general: the Administrator creates users and define their privileges In general: the Administrator creates users and define their privileges One who create a table considered to be the table owner One who create a table considered to be the table owner And he’s the one who defines who can access it and how. Users can create other users if they have the authority

4. Saving completes the creation, it can consist of: Saving completes the creation, it can consist of: checking duplicate items checking duplicate items updating data files if everything is ok updating data files if everything is ok updating metadata if structure changed updating metadata if structure changed report errors if any exists and redoing changes if necessary. report errors if any exists and redoing changes if necessary. We assume there is a query system inside the data base: Adding, deleting, modifying can be done using a UI but anyway it’s Executed Through the query system which also give the user the ability to retrieve info The diagrams are not relative to a specific database management system Now we’ll present the Use Cases: I

5. This is a simple use case We considered the manage system use case As a set of operation an administrator can do an no one else. When checking authority and it was denied it reports this Add, delete, modify runs it’s functionality through the query system The next pages contains more detailed use case.

8. We considered a query system which runs the real internal operations i.e.: We considered a query system which runs the real internal operations i.e.: When a user saves changes the system simply do a commit When a user saves changes the system simply do a commit When a user creates something the system simply builds an SQL commands, accumulate them, after saving it runs these commands internally. When a user creates something the system simply builds an SQL commands, accumulate them, after saving it runs these commands internally. Next we’ll present an introductory overview of the classes relative to our system as Notes: -We could consider an administrator is a special user( power user) so two kinds of users: ordinary and power users. -It is possible to make a DataBaseObject an ancestor for all objects(database, table, column, index….) with common attributes(like owner), this type is used mainly in generalized options like: authorities class