Library Management System Database Design(Part1)

最新推荐文章于 2024-04-20 09:55:08 发布

eagleatustb

最新推荐文章于 2024-04-20 09:55:08 发布

阅读量968

点赞数

分类专栏： Database Design 文章标签： database library system table dictionary module

本文链接：https://blog.csdn.net/suppercoder/article/details/5659880

版权

Database Design 专栏收录该内容

1 篇文章 0 订阅

订阅专栏

Thinking of LMS(Library Management System) Design___________________________________ 2

Author: Michael Tan Data:2010-05-21 Version:1.0_______________________________________________________ 2

Chapter1: Data modeling concept design_____________________________________________________ 2

Chapter2: Transaction Design_______________________________________________________________ 5

Thinking of LMS(Library Management System) Design

Author: Michael Tan Data:2010-05-21 Version:1.0

Chapter1: Data modeling concept design

1. Module Level design digram;

2. Data Scope design;

3. Naming Rules: Database name, Table name, column name;

4. Data Dictionary;

5. Entity – Relation diagram;

6. IDEFE1X

Notice：

1. Module Level design include monitor module.

2. Need to design all data dependence relation according to mathimatic model before design key.

3. Updatetimestamp is needed in every table design.

4. Delete flag is needed in every table design and use define program to delete data.

5. Summary table should design sysid as PK.

6. Tranaction table should design sysid as PK when necessary.

7. All Table design need to raise the 2^nd normal form. Entity-Relation level must raise 3th normal form.

8. Metadata should not be ambigous.

9. Table should not be reverse.

Ø Transaction design

Ø Summary design

Ø View Design

Ø Monitor Design

Ø Data modeling concept design.

1. Module Level design digram

All data concept module is from inside entity to outside report,every shell will use it’s contain data but should not confuse will the inner data.

Entity-Relation cycle will contain entities and their attributes,they will have relationships but will not show if no transaction is occur.On this level, these entities is indepence.These entities contains physical entities and concept entities such as product name, recipe name.

Transaction cycle will show the tansaction of the activities of all entities. All relationships of the entities are display in this cycle.They depend on the entities and their actions.

Summary cycle is the history of all transactions.Summary will use Transaction and entity-relation data as reference.

Report face to user using Summary, Transaction, Entity-Relation data.

2. Data Scope design;

3. Naming Rules

Logic Naming Rules:

Entity Physical or Concept things must be a Noun.

Transaction must begin with a Verb.

Summary must follow the Transaction name and add “history” after the Transaction name.

Reports are dynamic as user request.

Physical Naming Rules:

Database name: DB_LMS;

Table name: LMS_TB_ER_EntityName; LMS_TB_TR_TransactionName; LMS_TB_SM_SummaryName; LMS_TB_RP_ReportName; They are different level data according to the module level design.

Column name: Must be include a Noun, separated by “_”; Noun or Adjective_Noun.

Column sufix	Meanings	example	Remark
_ID	ID must be a string unique to the entity or transaction, but they do not need to show off some meaning.	Book_ID=2010052301230031; EMP_ID=E019824; Reader_ID=R003241; Room_Id=L0210; TXN_ID=T123456789;
_Name	Name must have define meaning of the entity, but Name may be the same in some situation.	Book_Name=L’insoutenable legerete de l’etre Author_Name=Milan Kundera
_CNT	CNT must be a integer number as count.	Borrow_CNT=101; Fix_CNT=0; Book_CNT=12;
_Num

4. Data Dictionary

DataDictionary.xlsx

Vocabulary	Abbreviation	Description	Example	Related function
Identity	ID



Reader		All person have registed in Librarian are readers,reader have unique Reader_ID assigned by Lirarian system.

Librarian