I want to be a books management system management system, what should I do database design, what are the steps to design a database? Finally how E - R diagram? Wish you a great god can guide to guide me, I can discuss with communication, thank you!

CodePudding user response:

1, the first thing you probably comb a books management system management system demand (what does it do, what to do, what is the target)
2, based on the requirements, make a general design, the relationship between the functional requirements and procedures, what need to design interfaces, in order to achieve these functions, what I need table)
Books management system management system, for example, I can not login to browse, but in order to borrow books, I must have a user login to use this feature, so you must have the user table t_user (user ID, name, password)
Users may be cancelled, this time is to delete user record directly or use stop sign, if you use a stop sign, in the table t_user whether also have stopped marking field
And so on...
Have the user, whether also have user rights, could not have a user can see all the features of the whole system, is must have permission to watch
How permissions control, through the role, or each user directly assign permissions, if use character, is also have character table, if there are users, roles and permissions list, still have to have the middle table to link
(don't directly in the role, the permission to add ID field) in the table, table just role related information, permissions list just access information (meet the atomicity), intermediate table put a user ID, ID, another character ID, authorization ID
And so on (record the user login, the password input error, etc.)
Solved the user login, consider the books related to things, administrator of new books, borrow books people borrow books, such as book report the loss, etc.

As long as you make it clear that, painting e-r diagram (how to use tools and e-r diagram concept are you sure you want to learn) handy when

CodePudding user response:

reference 1st floor shpery response:

1, the first thing you probably comb a books management system management system demand (what does it do, what to do, what is the target)
2, based on the requirements, make a general design, the relationship between the functional requirements and procedures, what need to design interfaces, in order to achieve these functions, what I need table)
Books management system management system, for example, I can not login to browse, but in order to borrow books, I must have a user login to use this feature, so you must have the user table t_user (user ID, name, password)
Users may be cancelled, this time is to delete user record directly or use stop sign, if you use a stop sign, in the table t_user whether also have stopped marking field
And so on...
Have the user, whether also have user rights, could not have a user can see all the features of the whole system, is must have permission to watch
How permissions control, through the role, or each user directly assign permissions, if use character, is also have character table, if there are users, roles and permissions list, still have to have the middle table to link
(don't directly in the role, the permission to add ID field) in the table, table just role related information, permissions list just access information (meet the atomicity), intermediate table put a user ID, ID, another character ID, authorization ID
And so on (record the user login, the password input error, etc.)
Solved the user login, consider the books related to things, administrator of new books, borrow books people borrow books, such as book report the loss, etc.

As long as you make it clear that, painting e-r diagram (how to use tools and e-r diagram concept are you sure you want to learn) handy when

Bosses, learning