Expert answer:Final Project. Most of the work is already complet
Expert answer:I am attaching the work that has been completed through today. I am also attaching a sample of that the project could look like. the requirements are as follows:This final course project is to develop an individual project plan that focuses on the database aspects of the project development lifecycle. All design, research, and work by each student will be original work in the design and creation of a new database. Students will become familiar with data management, database modeling and design, and skills to develop a final project plan. A minimum of 3 resources should be used. These requirements include the following:Requirements Analysis –BackgroundPurposeBusiness goals and rulesUser requirementsData requirementsReporting requirementsProject schedule and project costsData model – In physical design format original student designData dictionary for all tables in data modelSQL statements:CREATE TABLE statements (for entities (tables defined in model)Minimum of two SELECT statementsAt least one insert, update, or delete statement.Identify the database management system (DBMS) that will be used for the database designCreate a basic database back-up and recovery plan
database_training_and_managment_final_project_rough_draft.docx
datamanagementproject_example1.docx
Unformatted Attachment Preview
Database Training and Management (rough draft)
Database Training and Management
Renee Randall
Wilmington University
11/21/17
Database Training and Management (rough draft)
Training and Management of Database
Background
Employee training is an important aspect for any organization that chooses to hire new
employees. New employees should feel a sense of belonging to the company or business and
they should know their way around the company. In a correctional facility training set up, there
exists a database management system where information about tracked cadet names, address,
contact information and instructors is stored. New officers therefore need to be equipped with
sufficient information to handle the technical issues surrounding this system.
Purpose
The purpose of database training is to equip new officers with sufficient knowledge that will aid
them in navigation around database systems in Delaware Department of Correction. They need
to be able to perform data entry for example enter name of cadets in the system, map each cadet
to instructors plus be able to interpret data modeling diagrams such as Entity Relationship
diagrams, Use case diagrams and their Logical and Physical interpretations.
Business Goals and Rules
While automating data entry and storage in every business setting, all aspects need to be
considered during the process. The rules are: specification business rules, recognition rules, and
management and implementation rules.
Therefore there is need for scrutiny, detection, categorization, modeling, and certification of
business rules. Apart from rules that influence business processes we have data application rules.
Relational database systems not only provide mechanism for storing information but also offer
Database Training and Management (rough draft)
data application control mechanism. These rules are implemented through: triggers, constraints,
and procedures stored. Constraints columns of a table that ensure only a given value of data are
contained with the sole purpose to preserve the reliability of databases. This integrity of database
model is both structural and behavioral. These procedural code modules (stored procedures) are
in databases and screening to execute a second time is not required of them. A trigger is a unique
procedure stored not invoked clearly but is automatically triggered upon detection of a particular
condition.
User Requirements
Before creating a database management system there is need to solicit user requirements in
order to find out the functional requirements that need to be achieved by the system. In the
case of a Delaware Department of Correction system the user requirements include:
•
The ability to be able to sort data in terms of date entered, gender or department.
•
Ability to map a cadet to instructor.
•
Ability to produce Erd diagrams so as to establish relationships between entities.
•
Ability to print reports that show a summary of data entered in the database system.
Data requirements
It’s important that data to be entered into the system fulfill the requirements needed i.e.
The data should be of the right data type, you cannot make an integer entry in a field
prescribed for variable characters.
The data should be of the right lengths, a field that is designed to host 50 characters cannot
hold 51 characters and above.
Database Training and Management (rough draft)
Reporting requirements
Reporting requirements for this project is SAP Crystal Reports. The utility will be able to
produce reports based on user requirements on click of a button.
Project schedule and project costs
Project Schedule
WEEK
1
2
3
4
5
ACTIVITY
PROJECT
January
PROPOSAL
10 to 15
FEASIBILTY STUDY
February
16 to
21
REQUIREMENT
March
ANALYSIS
to 6
SYSTEM DESIGN
April
8 to 14
USER
DESIGN
INTERFACE
May
15 to
20
6
7
8
Database Training and Management (rough draft)
CODING
June
22
to
27
IMPLEMENTATION
July
AND TRAINING
1 to
6
DOCUMENTATION
August
8 to
20
PROJECT BUDGET
ITEM
ESTIMATED COST ($)
Laptop(intel core i3, 2.2Ghz, 4.0GB RAM,
4500
500GB Hard Disk, with a CD_ROM)
Documenting the project proposal and Paper
1 000
MsSql Server
500
Crystal Report
4 000
Database Training and Management (rough draft)
Total estimate
51 000
Data Model
Cadet table
KEY
FIELD NAME
FIELD TYPE
LEGTH
NULLABLE
primary
id
Auto increment
45
NOT
Cadet name
string
45
NOT
National id No
integer
45
NOT
Contact information table
KEY
FIELD NAME
FIELD TYPE
LEGTH
NULLABLE
primary
id
Auto increment
45
NOT
National Id No
integer
10
NOT
Phone No
string
10
NOT
Address
string
45
NOT
Training evaluation table
KEY
FIELD NAME
FIELD TYPE
LEGTH
NULLABLE
primary
id
Auto increment
45
NOT
National Id No
string
45
NOT
Database Training and Management (rough draft)
Date
Date time
Marks
integer
Cadet
Contact information
Id
Id
Phone No
Cadet Name
National Id No
National Id No
Address
Cadet evaluation
IId
National Id No
Date
Marks
Sql Statement
Create table
NOT
5
NOT
Database Training and Management (rough draft)
Create table Cadet(idprimarykey,NationalIdNoint,CadetNameVarchar(20))
Create table ContactInformation(id
primarykey,NationalIdNoint,PhoneNoint,AddressVarchar(20))
Create table CadetEvaluation(id primarykey,NationalIdNoint,DateDatetime,Marksint)
Select Statements
Select *from Cadet where id=28145536
Select *from ContactInformationwherer Address=’Calofornia’
Select Max(id) from CadetEvaluation
Database Management System
The database management system to be used in this project is the Microsoft SqlServer. This will
be accompanied by Microsoft Sql Server management studio. This database will provide a
mechanism for data entry, querying of tables and generation of Entity relationship diagrams.
This database is a relational database and it contains tables which in turn have fields or columns.
This fields hold data arranged in rows called records. This data upholds data integrity hence data
entered follows all constrains described during table creation. The DBMS will provide a
centralized view of data as well as allow multiple users at a go. Each user will have his view
point and abstract the database at his own angle as prescribed by his goals in the business
organization. The DBMS provides physical and logical independence hence protecting the users
from details of knowing how and where the data is stored. Among many others, the following
will be the advantages of using Microsoft Sql Server Data Management System:
❖ Security of data
❖ Independence and concept of data
Database Training and Management (rough draft)
❖ Integrity of data capabilities
❖ A locking mechanism for concurrent access
❖ Auditing and sorting activities
❖ The capability of recovering from errors and crashes and errors as quickly as posible,
apart from recoverability and revive ability.
❖ Data administration procedures
❖ Uncomplicated access using a standard application programming interface (API)
Data backup should be done at leastdaily. Data should be backed up in an online facility such
as a cloud because it guarantees security of the data hence less risks of data loss. Once there
is data backup it can be recovered easily in case of loss of data and restored back into the
Database Management System using the tools provided by Microsoft Sql Server
Management Studio.
Database Training and Management (rough draft)
Work Cited
Santa Barbara,2014. Object-Oriented construction Software
J.A. Zachman, 2013-, http://searchsqlserver.techtarget.com/definition/database-managementsystem
http://www.w3schools.com/sql/sql_create_table.asp
IST7000 Data Plan Project
Wilmington University
Background and Purpose
To conform to international requirements, Lions Club International (“LCI”) is requiring
individual Lions Clubs to move from paper reports to an electronic reporting system (“the
Project”). The North East Lions Club (hereafter “the Club”) intends to facilitate this
effort by developing a database to maintain membership information, as well as other
reportable information. The reports required by LCI have been defined. The District
and Zone level reports are still being finalized, but will piggyback on the information
gathered for international reporting. The Club reports will be formatted as PDF files for
distribution to the District and Zone leadership. The international reports will be
formatted into Excel files that will be transmitted electronically and uploaded into an
international database.
Internally, the Club wishes to track information concerning its fundraising efforts to
become more efficient and increase the profitability of its events.
Requirements Management Approach
The local Zone Chairman will be the representative for LCI and will oversee the local
clubs report development. The Club Lion Tamer (Sergeant at Arms), Treasurer, and
President will have primary responsibility for steering the project to ensure it meets the
requirements set forth by LCI. The 1st Vice-President will handle interviewing the
chairpersons of the various fundraising events. The Club Secretary will provide the
information needed to complete the reports for LCI. The Secretary and 1st VicePresident will report the findings to the steering committee and develop the requirements
to complete the project. The President will make regular reports on project progress to
the Club Board of Directors. The Lion Tamer, as Secretary of the Board, will track
project progress. The project documentation will be maintained on a server provided by
LCI for this effort.
Business Goals
1. To facilitate electronic reporting to conform to LCI guidelines.
2. To reduce the time it takes to create reports required by all levels of the
organization
3. To provide more complete and accurate information to the Club’s leadership
4. To keep more accurate records of member involvement
5. To track trends on the success of fundraisers to increase efficiency and
profitability
User Requirements
1. To be able to enter information in a web-based interface
PAGE 1 OF 15
2.
3.
4.
5.
To be able to generate reports
To have the reports sent in the proper format required for electronic upload to LCI
To allow the Secretary and Treasurer secure access to sensitive information
To be designed in such a manner that will allow for future integration of financial
information.
Data Requirements
The Club needs to keep a record of all members past and present, including deceased
members. All other non-membership data will begin July 1, 2015. Historical data will be
maintained in present format for a rolling five (5) years, after which time it is no longer
subject to audit by either the IRS or LCI. Tracked data will include each member’s hours
volunteered and donations made. There will need to be a tracking of information about
each event that will allow for the creation of cash flow statements and future supply and
equipment needs.
After this phase of the project, financial reporting will need to be integrated into the
system.
Reporting Requirements
1. Chairmen of events should be able to print a list of equipment and supplies for the
events they chair.
2. Send an alert to the President and Secretary of the Club if any member’s donations
surpass $1000 in a fiscal year.
3. Summary reporting of Club activity and membership
4. Reporting of individual member information
Project schedule and project costs
The project is set to begin July 1, 2015. All international reports must be in place no later
than September 30, 2015. Zone and District-level reports are scheduled to be completed
ninety (90) days after final report requirements are delivered from the District leadership.
The scripts to create the structure and tables of the database will be delivered on July 28,
2015. LCI will then verify and execute the scripts on July 30, 2015. The HTML and
PHP portion of the application will be developed and ready for testing on August 10,
2015. Test data will be loaded and available by August 11, 2015. All testing and any
needed fixes will be completed by August 30, 2015. The Excel spreadsheet downloads
for export into the LCI systems has been supplied by LCI and are currently available.
By using the servers provided by LCI there is no direct hardware cost associated with this
project. Member dues at the international level are going up by $1.00 to cover the costs
of the Project.
By Using MySQL and PHP on the provided servers, there is no cost for Software
Licensing.
PAGE 2 OF 15
Club members have opted to do the development in lieu of cash donations; this may
impact donations for the year, but will prevent an upfront outlay of cash.
DATA MODEL
DATA DICTIONARY
Schema mydb
Table Member
Columns
Column
Key
Datatype
Name
PK idMember
INT
Name
VARCHAR(45)
Street
VARCHAR(45)
CIty
VARCHAR(45)
State
CHAR(2)
ZipCode
INT
TelePhone
VARCHAR(10)
Email
VARCHAR(45)
Dues
YEAR
Spouse
VARCHAR(45)
Not
Null
Yes
Yes
No
No
No
No
Yes
No
Yes
No
Default Comment
Member number assigned by LCI
Full name of member
street address
City
State
Zipcode
Phone number
email address if available
last year dues paid
spouse or significant others first
PAGE 3 OF 15
JoinDate
DATE
Office
VARCHAR(45) No
Indices
Index Name
PRIMARY
idMember_UNIQUE
Relationships
Relationship Name
FkChairman
FkMemeberMH
FkMemberDo
name
date joined
current office or chairs held if
applicable
Yes
Columns Primary Unique Type
Yes
No
PRIMARY
No
Yes
UNIQUE
Relationship Type
Non-Identifying
Non-Identifying
Non-Identifying
Table EventList
Columns
Column
Key
Datatype
Name
PK EventCode CHAR(4)
EventName VARCHAR(45)
Not
Null
Yes
No
Chairman
INT
Yes
Purpose
VARCHAR(45) Yes
Location
CHAR(4)
No
Indices
Index Name
Columns Primary
PRIMARY
Yes
Chairman_idx
No
FkLocation_idx
No
Relationships
Relationship Name
Relationship Type
FkChairman
Non-Identifying
FkLocation
Non-Identifying
FkEventD
Non-Identifying
FkEventMH
Non-Identifying
FkEventDo
Non-Identifying
Parent Table
Member
Member
Member
Kind Comment
Child Table
EventList
MemberHours
Donations
Card.
1:n
1:n
1:n
Default Comment
Code for Event
Member ID Who is chairperson for
the event
General Funds, Scholarship, Vision
Research, or specific individual or
cause
where the event was/is to be held
Unique
No
No
No
Type
PRIMARY
INDEX
INDEX
Parent Table
Member
Location
EventList
EventList
EventList
Kind Comment
Child Table
EventList
EventList
EventDetails
MemberHours
Donations
Card.
1:n
1:n
1:n
1:n
1:n
PAGE 4 OF 15
FkEventS
FkEventEq
Non-Identifying
Non-Identifying
EventList
EventList
EventSupplies
EventEquipment
1:n
1:n
Table Location
Columns
Key Column Name
Datatype
Not Null
Default
Comment
PK LocatinCode
CHAR(4)
Yes
Description
VARCHAR(45)
No
Contact
VARCHAR(45)
No
Phone
VARCHAR(12)
No
Indices
Index Name
Columns
Primary Unique Type
Kind Comment
PRIMARY
Yes
No
PRIMARY
Relationships
Relationship Name
Relationship Type
Parent Table
Child Table
Card.
FkLocation
Non-Identifying
Location
EventList
1:n
FkLocation
Non-Identifying
Location
Equipment
1:n
Table EventDetails
Columns
Key Column Name
Datatype
Not Null
Default
Comment
FK EventCode
CHAR(4)
Yes
PK Date
DATETIME
Yes
Costs
DECIMAL(6,2)
No
Revenue
DECIMAL(6,2)
No
Notes
LONGTEXT
No
Indices
Index Name
Columns
Primary Unique Type
Kind Comment
PRIMARY
Yes
No
PRIMARY
Relationships
Relationship Name
Relationship Type
Parent Table
Child Table
Card.
FkEventD
Identifying
EventList
EventDetails
1:n
Table Equipment
Columns
Key Column Name
PK idEquipment
Datatype
INT
Not Null
Yes
Default
Comment
PAGE 5 OF 15
Description
VARCHAR(45)
No
StorageLocation
CHAR(4)
No
Indices
Index Name
Columns Primary Unique Type
Kind Comment
PRIMARY
Yes
No
PRIMARY
FkLocation_idx
No
No
INDEX
Relationships
Relationship Name
Relationship Type
Parent Table Child Table
Card.
FkLocation
Non-Identifying
Location
Equipment
1:n
FkEquipmentEq
Non-Identifying
Equipment
EventEquipment
1:n
Table Supplies
Columns
Key Column Name
Datatype
Not Null
Default
Comment
PK idSupplies
INT
Yes
Description
VARCHAR(45)
No
Cost
DECIMAL(4,2)
No
Inventory
INT
No
Indices
Index Name
Columns
Primary Unique Type
Kind Comment
PRIMARY
Yes
No
PRIMARY
Relationships
Relationship Name
Relationship Type
Parent Table
Child Table
Card.
FkSupplyS
Non-Identifying
Supplies
EventSupplies
1:n
Table MemberHours
Columns
Key Column Name
Datatype
FK
Member
INT
FK
EventCode
CHAR(4)
PK
Date
DATETIME
Hours
INT
Indices
Index Name
Columns Primary
PRIMARY
Yes
FkMemeber_idx
No
FkEvent_idx
No
Not Null
Yes
Yes
Yes
No
Unique
No
No
No
Default
Type
PRIMARY
INDEX
INDEX
Comment
Kind Comment
PAGE 6 OF 15
Relationships
Relationship Name
FkMemeberMH
FkEventMH
Relationship Type
Identifying
Identifying
Parent Table
Member
EventList
Child Table
MemberHours
MemberHours
Card.
1:n
1:n
Table Donations
Columns
Key Column Name
Datatype
Not Null
Default Comment
PK idDonations
INT
Yes
Amount
DECIMAL(6,2)
Yes
Member
INT
No
EventCode
CHAR(4)
No
Notes
VARCHAR(100)
No
Earmark
VARCHAR(24)
No
Date
DATETIME
Yes
Indices
Index Name
Columns Primary Unique Type
Kind Comment
PRIMARY
Yes
No
PRIMARY
FkMember_idx
No
No
INDEX
FkEvent_idx
No
No
INDEX
Relationships
Relationship Name
Relationship Type
Parent Table
Child Table
Card.
FkMemberDo
Non-Identifying
Member
Donations
1:n
FkEventDo
Non-Identifying
EventList
Donations
1:n
Table EventSupplies
Columns
Key Column Name
Datatype
Not Null
Default
Comment
FK
EventCode
CHAR(4)
Yes
FK
Supply
INT
Yes
Indices
Index Name
Columns Primary Unique Type
Kind Comment
PRIMARY
Yes
No
PRIMARY
FkSupply_idx
No
No
INDEX
Relationships
Relationship Name
Relationship Type
Parent Table
Child Table
Card.
FkEventS
Identifying
EventList
EventSupplies
1:n
FkSupplyS
Identifying
Supplies
EventSupplies
1:n
PAGE 7 OF 15
Table EventEquipment
Columns
Key Column Name
Datatype
FK
EventCode
CHAR(4)
FK
Equipment
INT
Indices
Index Name
Columns Primary
PRIMARY
Yes
FkEquipment_idx
No
Relationships
Relationship Name
Relationship Type
FkEventEq
Identifying
FkEquipmentEq
Identifying
Not Null
Yes
Yes
Unique
No
No
Default
Type
PRIMARY
INDEX
Parent Table
EventList
Equipment
Comment
Kind Comment
Child Table
EventEquipment
EventEquipment
Card.
1:n
1:n
CREATE TABLES
— —————————————————— Schema mydb
— —————————————————— —————————————————— Schema mydb
— —————————————————-CREATE SCHEMA IF NOT EXISTS `mydb` DEFAULT CHARACTER SET utf8
COLLATE utf8_general_ci ;
USE `mydb` ;
— —————————————————— Table `mydb`.`Member`
— —————————————————-DROP TABLE IF EXISTS `mydb`.`Member` ;
CREATE TABLE IF NOT EXISTS `mydb`.`Member` (
`idMember` INT NOT NULL COMMENT ‘Member number assigned by LCI’,
`Name` VARCHAR(45) NOT NULL COMMENT ‘Full name of member’,
`Street` VARCHAR(45) NULL COMMENT ‘street address’,
`CIty` VARCHAR(45) NULL COMMENT ‘City’,
`State` CHAR(2) NULL COMMENT ‘State’,
`ZipCode` INT NULL COMMENT ‘Zipcode’,
`TelePhone` VARCHAR(10) NOT NULL COMMENT ‘Phone number’,
`Email` VARCHAR(45) NULL COMMENT ’email address if available’,
PAGE 8 OF 15
`Dues` YEAR NOT NULL COMMENT ‘last year dues paid’,
`Spouse` VARCHAR(45) NULL COMMENT ‘spouse or significant others first name’,
`JoinDate` DATE NOT NULL COMMENT ‘date joined’,
`Office` VARCHAR(45) NULL COMMENT ‘current office or chairs held if applicable’,
PRIMARY KEY (`idMember`),
UNIQUE INDEX `idMember_UNIQUE` (`idMember` ASC))
ENGINE = InnoDB;
— —————————————————— Table `mydb`.`Location`
— —————————————————-DROP TABLE IF EXISTS `mydb`.`Location` ;
CREATE TABLE IF NOT EXISTS `mydb`.`Location` (
`LocatinCode` CHAR(4) NOT NULL,
`Description` VARCHAR(45) NULL,
`Contact` VARCHAR(45) NULL,
`Phone` VARCHAR(12) NULL,
PRIMARY KEY (`LocatinCode`))
ENGINE = InnoDB;
— —————– …
Purchase answer to see full
attachment
How it works
- Paste your instructions in the instructions box. You can also attach an instructions file
- Select the writer category, deadline, education level and review the instructions
- Make a payment for the order to be assignment to a writer
- Download the paper after the writer uploads it
Will the writer plagiarize my essay?
You will get a plagiarism-free paper and you can get an originality report upon request.
Is this service safe?
All the personal information is confidential and we have 100% safe payment methods. We also guarantee good grades