Some ideas of database design (pattern and database design)

Design | data | database | Database design

Some conceptions of
database design (pattern and database design)





I've always had an idea. I want to be able to hook up with the pattern of database design, here I list the content may not be the model, but somewhat similar, so I hope that you can give some good advice. We also invite you to speak enthusiastically.

















 











 





 











 











 





 











 





 











 





 





Plus one of the following text I think I listed these similar to the pattern of things with the previous post is inseparable, two is to gather a word.





--------------------------------------------------------------------------------------------




Functional division of
:





1/Enterprise Organization structure


2/Corporate sector functions of the composition of the description


3/Departmental Hierarchy


4/Departmental function Division


5/Employee Job function Division


6/Functional Components


7/Functional Description of the job function (shown in departmental job level diagram)





Function Division Flow:





1/Functional Requirements Description (business, System)


2/Functional requirements of the collation and combination


3/function Coupling relationship


4/Functional Components


5/Function split description and implementation


6/function serialization or the description of
and lock wait

7/Show the concrete embodiment of the function in the way of flowchart





Process Division Document:





1/Realistic Business document collection


2/Document collation and combination


3/Document status changes in different periods of the functional implementation process


4/Document composition elements


5/Document split description and implementation (data source/Data flow/processing action)


6/Document user's permission description and control


7/presentation of specific documents (shown in spreadsheet format)





Document Division table:





1/document content split and consolidated (No field design is involved, only the column-level description of the document's specific content should be considered)


2/Document primary key and foreign key and constraints of the preliminary description


3/Document three paradigms and anti-normal design description


4/Document Data quantity estimate, the use frequency estimate of the document


5/Document Use the determination of the role (with the database user role to define document generation)


6/Document View design description, query table description, index requirements Description


7/Presentation (UML) of the relationship between the single room and the list of documents





table partition atomization:





1/table field design (data type, domain, property sheet)


2/Table PRIMARY key FOREIGN KEY constraint design


3/Table index design


4/Table rights assignment for different role users


5/views are created according to the scope of the application, such as common query/modify/statistics (recommended user Role level view creation)


6/Trigger and stored procedure design description


7/Show the concrete manifestation of the table in the way of ER graph