Database Design: Database Architecture<\/p>\n
A database is defined as an organized collection of data. Today most Database Management Systems use different database system architectures such as centralized and client-server systems, server system architectures, parallel systems, distributed systems and many others for system implementation. However, in this case, the database architecture being used for my subsystem is a three-level architecture that has external level, internal level and conceptual level (Hellerstein, Stonebraker & Hamilton, 2007).<\/p>\n
In physical database, the users\u2019 view of the data is defined. My subsystem is a customer relationship system (CRM) where customers interact with the system to purchase goods online. Conversely, the managers also interact with the system to manage the employees (Hopper, 2008). The following is an entity-relationship diagram (ERDs) of the subsystem for CRM. In the diagram;<\/p>\n
Manager manages Employees<\/p>\n
Manager manages Customers<\/p>\n
Manager control Goods<\/p>\n
Customer orders goods from website<\/p>\n
Customer signs up in a website<\/p>\n
5172710192405Goods name<\/p>\n
Goods name<\/p>\n
17081513970Employee name name<\/p>\n
Employee name name<\/p>\n
-914400170180Employee ID no.<\/p>\n
Employee ID no.<\/p>\n
1028700169545Managers ID no.<\/p>\n
Managers ID no.<\/p>\n
2723515163195Managers Name<\/p>\n
Managers Name<\/p>\n
3676650150495Controls<\/p>\n
Controls<\/p>\n
5229225215900Goods<\/p>\n
Goods<\/p>\n
646430215900Manages<\/p>\n
Manages<\/p>\n
-590550255270Employees<\/p>\n
Employees<\/p>\n
21443958255Manager<\/p>\n
Manager<\/p>\n
546735087630Goods no.<\/p>\n
Goods no.<\/p>\n
1885950200025Customer ID <\/p>\n
No.<\/p>\n
Customer ID <\/p>\n
No.<\/p>\n
715010200025Customers<\/p>\n
Customers<\/p>\n
3781425120015Warehouse<\/p>\n
Warehouse<\/p>\n
-208915103505Custome Name<\/p>\n
Custome Name<\/p>\n
The below diagram is a use case Diagram representation for the subsystem to be implemented. Use case diagram is the view of system that looks on the behavior of the system as it appears to external viewers. <\/p>\n
Database architecture is essential for system implementation in that it maintains a catalogue of schemas, users as well as, applications. Database architecture also allow for the storage, retrieval along with the manipulation of data. The other significance include; authorization and security, integrity and consistency services as well as, promotion of Data interdependence (Connelly, 2001).<\/p>\n
References<\/p>\n
HYPERLINK “http:\/\/www.bibme.org\/” o “Edit this item” Connelly, J. (2001). Architecture Database on DIALOG: a user’s manual. London: British Architectural Library, Royal Institute of British Architects. <\/p>\n
HYPERLINK “http:\/\/www.bibme.org\/” o “Edit this item” Hellerstein, J. M., Stonebraker, M., & Hamilton, J. (2007). Architecture of a database system. London: Now. <\/p>\n
HYPERLINK “http:\/\/www.bibme.org\/” o “Edit this item” Hopper, T. (2008). Distributed relational database architecture: connectivity guide (4th ed.). New York: Prentice Hall PTR. <\/p>\n","protected":false},"excerpt":{"rendered":"
Database Design: Database Architecture A database is defined as an organized collection of data. Today most Database Management Systems use<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-36017","post","type-post","status-publish","format-standard","hentry"],"yoast_head":"\n