Project 1 Dropbox - Grandfield College Scenario

docx

School

Santa Fe College *

*We aren’t endorsed by this school

Course

2445

Subject

Computer Science

Date

Feb 20, 2024

Type

docx

Pages

3

Uploaded by AgentSardineMaster774

Report
Kelsey Hodge CTS2445.0T1 Project 1 Dropbox – Grandfield College Scenario 1. Major Topics for this database a. Software b. Machines c. Users 2. Draft statement of work a. HISTORY Grandfield College is required by law to adhere to specific software licensing requirements as designated by the respective type of software licensing agreement. License agreements use one of several schemes to track and confirm that software is properly distributed and used. The license schemes have different levels of use-restriction, and have requirements that limit use of the software on per-user and per-machine bases to varying degrees. Grandfield College owns and facilitates the use of many different software applications and versions, each with its own licensing requirement. The system currently tracking Grandfield College software usage, licensing requirement, and information necessary to adhere to these licensing requirements is presenting significant problems. The current system is not easily accessible, and a large amount of records are out of date. Grandfield College is in need of a relational database to keep track of all of these different variables, and ensure the law is being followed. A relational database would maintain data integrity by keeping track of software version, usage, licensing requirements, and whether or not software is being used and distributed properly. A database would also generate more accurate and reliable reports. b. STATEMENT OF SCOPE The software licensing database will manage and maintain critical software data for Grandfield College to ensure they are abiding by the law. It will track software owned by the College, software version, and licensing scheme. It will also track which software is installed on which machine, where that machine is located, and which users have access to that machine. The date of software uninstallation and machine retirement will also be tracked by the database. The database will produce quarterly and annual reports summarizing software usage, user access, and adherence to software licensing requirements as proof of their law-abiding practices.
c. OBJECTIVES - Centralize information on Grandfield College’s software usage practices - Gather software, software version, software licensing requirements, software installation location, and software access information - Better maintain records of Grandfield College’s software usage practices - Allow Grandfield College to better abide by software licensing laws d. PRELIMINARY TIMELINE 1. Gathering Data: This task will consist of a number of interviews, questionnaires, and observations. Time allotted: 3 weeks. Deliverables: A list of the software used, software licensing requirement, number and location of machines the software is installed on, and user access to machines. 2. Analyzing Data: The data gathered will be analyzed to determine the current accuracy of the College’s adherence to software licensing requirements and law. Time allotted: 2 weeks. Deliverables: List of software that are properly being used according to licensing requirements, and list of software that are not being used properly according to licensing requirements. 3. Normalization: The data model will be completed with entities and relationships normalized. Time allotted: 1 week. Deliverables: Entity Relation Diagram for Review. 4. Building the Physical Database: The data model will be translated to the relational database management system. Tables, columns with specific data types, and relational and other constraints created. Time allotted: 3 days. Deliverables: The schema of the database for review. 5. Testing and Security: Sample data will be entered and each of the software licensing requirements and software usage behavior will be tested. General database security and security related to software licensing requirements and software usage will also be tested. Time allotted: 3 weeks. Deliverables: Documented test results.
6. Database Completion and Installation: Final changes and corrections are made. Sampled data will be removed and the database installed on a server. Final testing for server access and connections. Time allotted: 2 weeks. Deliverables: The working database.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help