Language:EN
Pages: 24
Rating : ⭐⭐⭐⭐⭐
Price: $10.99
Page 1 Preview
create table machine machinecss int identity prima

Create table machine machinecss int identity primary key not null

Chapter 1

Major Topics for Database:

History
The law requires that any business, including a school, track its software. It is important to know what software the school owns, in what versions, and what the license agreement for that software is. Whatever the license agreement for particular software, it is essential for the institution to know which software is installed on which machine, where that machine is located, and which users have access to that machine. It is also important to track when the software is uninstalled from a machine and when a machine is retired. Grandfield college currently uses several spreadsheets to track this information. They also track requests for new software, software checkouts to faculty with administrative privileges on their machines, and if installs are successful or run into any problems.

When requests for software are received, the software management team must manually access a spreadsheet to see if the school has the data. When new software arrives, they must manually check the licensing agreement online when they don’t know off the top of their head. These agreements vary between being accessible to any computer on site via a server install or having a limited number of copies that must be installed client-side.

● Track the location of the faculty and staff computers and who has access to each.

● Track requests for new software and when software is checked out to faculty with administrator privileges on their machines.

Deliverables: List of business rules. Their basic entities and attributes. To be reviewed.

3. Normalization: The data model will be completed with entities and relationships normalized. Time allotted: 1 week.

Time allotted: 3 weeks.

Deliverables : Documented test results.

Chapter 2

1. Questions about data
1. Is there documentation by software on how many times a piece of software has been installed/uninstalled?

Software Management Team
Faculty / Staff
School Administration
Clients
Software companies

3. Plan for interview with stakeholders (one hour)
Find out what makes everyday tasks difficult for staff and find a solution.

6.

OSs have to be the same
7. How are updates handled? -don’t need it right away
8. Which software is installed from the network drive and which must be installed from disk? Is this tracked anywhere? -should be tracked
9. Are administrative privileges on machines tracked? should be tracked, doesn’t have to be.

10. Is there privileged access to certain data (if so which data and what does it concern) - security isn’t a huge concern
11. Is there privileged access to certain software i.e. how is need for certain types of software evaluated? (Design programs vs. programming programs) -anyone can if they have some reason

Administration: (5minutes)
1. How are requests for new software evaluated?

2. Who is the Admin(s)?

○ What kind of security is implemented to secure the databases / software / servers?

● It is difficult to track which software is on which machine.

● It can be difficult to get/track licensing agreement information.

● Allow faculty to see software that can be installed via the servers so that they can

install it on their own.

Software Management Team (SMT)

● Allow SMT to check licensing agreements





Allow SMT to document machine configuration Allow SMT to record installation issues
How will everything be secured
Allow SMT to track pending installations
Allow SMT to check requests for software

licensing rights.

List of business rules

software, perhaps from home, they must ask the IT admin(s).

● How requests are tracked.

they don’t have the privileges.

● Keep minimum and maximum 2 - 3 admins employed. Let admins delegate certain

Installed Programs

Install Date

OS

[User]

Email

Faculty ID

Reason for request

New or Existing License

Software Program
● Name / Version
Installs
● Surrogate key
License

Surrogate key Machine
● CCS
User
● ID #
Requests
● Surrogate key

Entity Roles:

Chapter 6

10. )

******************************************************************************** Below Is The Syntax That Successfully Complied Used In Our Database ********************************************************************************* GO
Use Granfield
GO

CREATE TABLE Install

(
InstallKey int identity(1,1) Primary Key Not Null,
InstallDate datetime Not Null,
InstallMachine NVarChar Not Null,
InstallSoftware NVarChar Not Null,
InstallSuccesful NVarChar Not Null,
SoftwareKey int Not Null,
CONSTRAINT fk_Software FOREIGN KEY(SoftwareKey)
REFERENCES Software (SoftwareKey),
)

(
RequestID int identity(1,1) Primary Key Not Null,
RequesterFirst NVarChar Not Null,
RequesterLast NVarChar Not Null,
RequestDate Date Not Null,
RequestSoftware NVarChar Not Null,
RequestReason NVarChar Not Null,
RequestStatus NVarChar Not Null,
)

CREATE TABLE RequestSoftwareUser
(
UserRequestID NVarChar Not Null Primary Key,
UserID NVarChar(64) Not Null,
RequestID int Not Null,
CONSTRAINT fk_UserID FOREIGN KEY (UserID)
REFERENCES [User](UserID),
CONSTRAINT fk_RequestID FOREIGN KEY (RequestID) REFERENCES Request(RequestID),
)
**************************************************************************

FROM Machine
WHERE LocationKey = 5

2. Two or three queries using aggregate functions
SELECT MachineCSS, COUNT(InstallationKey) AS [Total Installs] FROM Install
GROUP BY SoftwareKey

INSERT INTO Software(
SoftwareName,
SoftwareVersion,

You are viewing 1/3rd of the document.Purchase the document to get full access instantly

Immediately available after payment
Both online and downloadable
No strings attached
How It Works
Login account
Login Your Account
Place in cart
Add to Cart
send in the money
Make payment
Document download
Download File
img

Uploaded by : Logan Reed

PageId: ELI3B7456D