Database Models 1

Assignment-4
XXX
MIS 526.01W Models
XXX
October 10, 2012
XXX


Database Models 2

Assignment-4
1. Review of all the Requirements & Business Rules
The first part of assignment is to review all the requirements and business rules for the
database design modeling in case of Grandfield College The business rules are required in
database design to accommodate the contingencies which need to be taken care of in case of any
exception handling in the new database. Below are the requirements and business rules (table 1
and table 2 repectively) for software tracking database system in case of Grandfield College:

Type of
Requirement
Requirement
Data Requirement Allow staff to enter the installation schedule.
Allow staff to enter the installation requests.
Allow staff to enter the license detailed information.
Allow staff to enter the active and retired machines details
Allow staff to enter the users related details
Allow staff to cancel/approve/review the requests
Allow faculty to enter the installation requests.
Report Requirement
Allow faculty to review the installation details after the software
license is installed

Allow faculty to install and view the multiple versions of software
license (details).
How do you maintain the multiple versions of a software
Allow faculty to sign up for a software installation.
Allow faculty and staff to view and generate the related reports
Access and Security
Requirement
Allow faculty and staff to track the list of the users of the
machines and software licenses (in case more than one user works
on the same machine in different shift time).
Allow faculty and staff to review their installation request

Allow faculty and staff to check the license detailed information
for any software

Allow staff and admin privileged instructors to
insert/update/delete the records for all the tables and database
Table:1 Requirements for Grandfield College
The next table depicts the business rules for the modeling of this database. . Business rules
describe the rules that govern the way data are acquired, stored, and used by the business. They
are important for a database developer, who must make sure the database he or she develops can
support all the business rules and operations.
Database Models 3


Business Rule Category Business Rules
Business Rules related to admin
reports (reports useful for staff)
No. of software licenses owned by the Grandfield College
can be calculated from the License table (without counting
the multiple versions of software).
License Renewal and expiry dates can be seen from the
License table and triggers will be generated to renew the
license.
Machine and the software installed on that machine can be
viewed from making the join between Software and
Computer tables.
Business Rules for handling
installation requests
Faculty and other staff must enter the installation requests
and enter the relevant information about the request.
Staff must review and approve the installation request and
enter the relevant information
Students request or machine information is not dealt with
currently in this database.
Installation request review step will also confirm if the
software is readily available or Grandfield College has to
buy the software.
Business Rules for handling
licensing information
Each Software license (for the software which has multiple
versions of the software active) will have a primary key
associated with it.
Each user will have a list of software license information
associated to him/her.
Each license will have all the detailed information stored
about it.
The software which are uninstalled will be maintained as
well.
Business Rules for access to
database
Both staff and faculty with have admin privilege should
have the update/delete/insert privilege for the database
Table:2 Business Rules for Grandfield College
2. Dataflow Diagram
The second part of this assignment is to draw the dataflow diagram. A data flow diagram
(DFD) is a graphical representation of the "flow" of data through an information system,
modeling its process aspects. Often they are a preliminary step used to create an overview of the
system which can later be elaborated.[2] DFDs can also be used for the visualization of data
processing (structured design). The diagram on next page (diagram-1 and diagram-2) shows the
dataflow diagram for Grandfield College.


Database Models 4


Diagram :1 Dataflow Diagram for Grandfield College

Diagram :2 Dataflow Diagram for Grandfield College
Installation
Email for addition software
Pending request for
installtion
Purchase software Already have software
Get permission to purchase
the software
Purchased software arrived
Document the details
Install from network drive Install from media
Problem with installation
Trouble shoot the problem
Software installed
Document the details
Faculty/Staff
Staff
Staff
Staff Staff
School
Admin
Staff
User
Computer
Request
Software
1.0
License
3.0
4.0
6.0
7.0
User Puts the
Requests
Software license detailed
information
Request has the detailed information
about the requested software
Users Machine detail
Database Models 5

3. Entities, Attributes & Relations
The third part of the assignment is to list down the entities, attributes and relations in case of Grandfield College. There are seven
tables included in this database out of these two tables are the linking tables. Other five tables serve a significant purpose and include
viable information. Information stored in each table can be altered but the form should be used to serve this purpose.
The tables and their respected information in included in below table. This table includes basic information for each entity. Field
information is included in the second column of this table. Please note the fields that required for each table as the system will not
allow you to save your entry if the required field is blank.
Relationships
The relationship to link the SOFTWARE table to the LICENSE table is SOFTWARE_LICENSE table. The relationship is built
around the ID field which is the unique primary key number for software in the SOFTWARE table and is considered to the foreign
key of the SOFTWARE_LICENSE table. The relationship should be one-to-many. This means one ID (or each software) can have
multiple license versions owned by the Grandfield College in the database. Similarly other relationships are shown in the third column
of the below table and depicted in Diagram-3.
Entities Attributes Relations
Software o List of software owned by the school
o Category of the software
(staff/faculty/student)
o Versions of the owned softwares
o Date/Time when the software was installed
o Date/Time when the software was
uninstalled
o User who requested this software
o Flag: Was this software already available or
not
o If new Software the requested has been
reviewed or not
o If new Software the requested has been

Software_Id PK (Required information)

Software Name (Required information)
Software License (Required information)
Software License versions (Required information)
Software purchase Date (Required information)
Software Remove Date (Required information)
Software Owner Company (Required information)
Software License Type (Required information)


Database Models 6

approved or not
Linking Entity-
Software_License
o License Id
o Software Id
o
o License Name
o Software Name
o License version
o License Start Date
o License Expiry Date
o Software License Type
License Id PK FK1 (Required information)
Software IdPK FK2 (Required information)

License Name (Required information)
Software Name (Required information)
License version (Required information)
License Start Date (Required information)
License Expiry Date (Required information)
Software License Type (Required information)

Licenses (for the relevant
software)
o List of software owned by the school
o Versions of the owned softwares
o Date/Time when the license was expired
o Date/Time when the license was
renewed/was purchased
o License Terms and Conditions
o License Price
o License Pricing Unit
o Type of license agreement
o Available number of copies of Licenses
o Used number of copies of Licenses
o List of Computers on which license is active
o List of Computers on which license is
inactive
License IdPK (Required information)

License Name (Required information)
License version (Required information)
License Type (Required information)
License Start Date (Required information)
License Expiry Date (Required information)
License Owner company (Required information)
License Remove Date (Required information)
License Terms and Conditions (Required information)
License Price (Required information)
License Pricing Unit (Required information)

Requests (for installation) o First Name of Users of who raised the
request
o Last Name of Users of who raised the
request
o Software for which request is raised
o Availability of the software requested by the
users
o Date to install the software

Request Id PK (Required information)

Request Status (Required information)
Request Date (Required information)
Request Reason (Required information)
Requested Software (Required information)
Request Response from Staff (Required information)
Response Date (Required information)
Database Models 7

o Status of the request
o Request Reason
o Request Response date
Requester First Name (Required information)
Requester Last Name (Required information)
Request Close Date (Required information)
Machine (Computers on
which software to install)
o List of computers owned by the school
o Category of the computer (staff/faculty)
o List of software installed on the computer
o Location of these computers
o List of users of these computers
o Date/Time when the computer/machine was
retired
o List of Computers on which license is active

Computer Id PK (Required information)

Computer Name (Required information)
Computer Location (Required information)
Computer Active date (Required information)
Computer Expiry date (Required information)
Computer User First Name
Computer User Last Name

Users (Staff and Faculty) o User Id
o First Name of users
o Last Name of Users
o Category of users (staff/faculty/student)
o List of Software license owned
o Computers Owned by user
o List of requested software by the users
o List of available software requested by the
users
o List of unavailable (need-to-purchase)
software requested by the users

User Id- PK (Required information)

User First Name (Required information)
User Last Name (Required information)
User Category (staff/faculty) (Required information)
User Gender
User Requests (Required information)
User Owned Software (Required information)

Linking Entity-
User_Request_Software
o Request Id
o User Id
o Software Id
o Request Date
o Requested Software
o Response Date
o User Last Name
o Request Close Date
Request Id PK FK1 (Required information)
User Id PK FK2 (Required information)
Software Id PK FK3 (Required information)

Request Date (Required information)
Requested Software (Required information)
Response Date (Required information)
User First Name (Required information)
User Last Name (Required information)
Request Close Date (Required information)

Database Models 8

4. Logic Model (using Crows fee Notation)
Database contains major important information and therefore it is very important for any
database administrator to secure this information by implementing security rules for the
database. In case of Grandfield College software tracking database the security rules are listed as
below:

Diagram :3 Logic Model Diagram for Grandfield College
Software
User_Request
User
Computer
Request
License
Software_License
Software_Id
Software Name
Software License
Software License versions
Software purchase Date
Software Remove Date
Software Owner Company
Software License Type
License Id
License Name
License version
License Type
License Start Date
License Expiry Date
License Owner company
License Remove Date
License Terms and Conditions
License Price
License Pricing Unit
PK
PK
User Id
User First Name
User Last Name
User Category (staff/faculty)
User Gender
PK
Request Id
User Id
Software Id
Request Date
Requested Software
Response Date
User Last Name
Request Close Date
PK FK1
PK FK2
PK FK3
Computer Id
Computer Name
Computer Location
Computer Active date
Computer Expiry date
Computer User First Name
Computer User Last Name
PK
Request Id
Request Status
Request Date
Request Reason
Requested Software
Request Response from Staff
Response Date
Requester First Name
Requester Last Name
Request Close Date
PK
License Id
Software Id
License Name
Software Name
License version
License Start Date
License Expiry Date
Software License Type
PK FK1
PK FK2
Database Models 9

5. Entities & Attributes
6. Key Fields for Entities & Foreign Keys
Entity Key Field Foreign Key
Software Software Id -
Software_License License Id, Software Id License Id, Software Id
License License Id -
Request Request Id -
User _Request_Software Request Id, User Id, Software Id Request Id, User Id, Software Id
Computer Computer Id -
User User Id -
7. Role of Entities
Entity Role
Software Domain Entity
Software_License Linking Entity
License Domain Entity
Request Domain Entity
User _Request_Software Linking Entity
Computer Domain Entity
User Domain Entity
Entities & Attributes
Domain Entity-
Software
Domain Entity-
Users
Domain Entity-
Computer
Domain Entity-
License
Domain Entity-
Request
Linking Entity-
User_Request_Software
Linking Entity-
Software_License
Software Id
Software Name
Software License
Software License versions
Software purchase Date
Software Purchase
permission
Software Remove Date
Software Owner Company
Software License Type
User Id
User First Name
User Last Name
User Category
(staff/faculty)
User Gender
Computer Id
Computer Name
Computer Location
Computer Active date
Computer Expiry date
Computer User First
Name
Computer User Last
Name
License Id
License Name
License version
License Type
License Start Date
License Expiry Date
License Owner company
License Remove Date
License Terms and Conditions
License Price
License Pricing Unit
Request Id
Request Status
Request Date
Request Reason
Requested Software
Request Response from
Staff
Response Date
Requester First Name
Requester Last Name
Request Close Date
Request Id
User Id
Software Id
Request Date
Requested Software
Response Date
User First Name
User Last Name
Request Close Date
License Id
Software Id
License Name
Software Name
License version
License Start Date
License Expiry Date
Software License Type
Database Models 10

8. Documentation
As I sent the diagram and the documentation questions to other student I got the below
response for the respective questions:
a. Are all the major components of the software tracking system represented by
domain entities?
Yes, software, license, user, computer, request.
b. Does each entity contain the appropriate attributes to fully describe it and meet the
business rules you have gathered so far?
Yes, each entity has very detailed attributes to define it.
c. Does every entity have an appropriate primary key defined?
Yes
d. Are all many-to-many relationships resolved into one-to-many relationships by
linking tables?
Yes (however, there are other attributes listed as well).
e. Are the relationships valid (no cross-relationships)? Is the appropriate entity defined
as the one side of a one-to-many relationship? Do the tables have appropriate foreign
keys? Also check for other such issues.
The User-Request relationship appears to be one-to-many. (One user can do many
requests, but one request can only come from one user similarly one request for one
software installation, hence one to one from request to user software) The computer-user
relationship may or may not be needed?
f. Are lookup tables used for attributes that have a set list of values?
No attributes in this ERD have a set list of values and therefore, no lookup tables are
needed.


Database Models 11

REFERENCE
Ambler S. W., Sadlage P. J., (2006). Refactoring Database: Evolutionary Database Design
Retrieved from http://databaserefactoring.com/
Ball State University .Net SQL Administrative Console. Retrieved from
https://dotnetprod.bsu.edu/AdminConsole/Documentation/SQL/Design/Database.aspx
Conger S. (2012), Hands on Database an Introduction to Database Design And Development
Prentice Hall
DataNamic Design for Databases: The Ultimate Data Modeling Tool Retrieved from
http://www.datanamic.com/dezign/
Fehily C. Visual Quick Start Guide SQL: Learn SQL the Quick and Easy Way Peachpit Press
Government Technology. Industry Perspective: Time to Pull the Plug on Relational Databases.
Retrieved from http://www.govtech.com/budget-finance/Time-to-Pull-the-Plug-on-
Relational-Databases-.html
Larock T. Do You make these 5 Database Design Mistakes Retrieved from
http://www.techdocs.ku.edu/docs/database_design.pdf
Nielsen, P. Database Design ROI: SQL Server NVP Retrieved from
http://www.sqlserverbible.com/files/databasedesignroi.pdf
University of Kansas, Database Design Retrieved from
http://www.techdocs.ku.edu/docs/database_design.pdf
Wikipedia (2012) Database Design: Normalization Retrieved from
http://en.wikipedia.org/wiki/Database_normalization
Wikipedia (2012) Database Retrieved from http://en.wikipedia.org/wiki/Database