Assignment 1: SEEC Resource
Access Database
Design Project – Requirement
Analysis and Conceptual Design
1. Background
The School of Electrical Engineering and Computing (SEEC) at the University of Newcastle lends resources to staff and students for assignment and project purposes. The resources include cameras, speakers, software, phones, CDs etc.
Managing such services has become cumbersome and the support services of the School of SEEC have requested you to develop a database for their application. The project has been named as “SEEC Resource Access”.
2. Mission and objectives
The aim of the SEEC Resource Access project is to ensure the development of an efficient, convenient system for resource sharing in the School.
Main objectives of the project include:
• Organizing resources to provide efficient access to them
• Supporting research and academic activities by providing access to the required resources
• Monitoring equipment demand and use to facilitate best practical delivery of resources at SEEC
3. Main Features
In meeting its objectives, the following main features for the proposed resource access system have been identified.
• Catalogue Service: Develop a web-based searchable catalogue of all resources. Facilities will be needed to search the catalogue on various criteria including keyword, name, type etc.
• Loan Service: The loan service provides facilities to issue and to return resources. Resources can be classified as either movable (which can be taken away) or immovable. Resources are loaned to students or staff members of the School, who are also known as borrowers. The different types of borrowers are provided with varying degrees of privileges. The privileges of students will be affected by the courses they are working on.
• Acquisitions: The School consistently updates its resources. Suggestions for acquiring access to newer and updated materials are elicited from staff and students of SEEC. Priority is provided for acquisitions pertaining to teaching and research needs of the university.
• Reservation Service: The members should be able to reserve resources (if available) ensuring that they gain access to resources for specific periods of time. Requests for reservations are authorized on a first-come-first-serve basis.
4. Assignment
The proposed database system is developed in various modules, including requirements analysis, conceptual database design, logical database design, and physical database design. In this assignment 1, you are required to complete the first two stages of the database design, i.e., to develop user requirements specification and the conceptual database model for the database based on the business requirements provided in this document. There are two parts to be completed in assignment 1 as described below.
Part 1: Requirements
In this assignment, you are required to develop a user requirements specification truly fulfilling the data requirements (identify what types of data needs to be stored in the database), transaction requirements (identify the important and frequent database operations – data manipulation and queries), and business rules for the database mentioned above.
Assignment submission format for the Requirements part: The requirements document MUST have the following sections:
• Data Requirements – outlining the major data items
• Transaction requirements – outlining the data manipulation and queries
• Business Rules
Hint: Sample user requirement documents are discussed in weeks 2 and 3, and are available in appendices A and B of your main text
You may interview your client (i.e. lecturer) for clarification and include your interview questions and responses.
Part 2: EER Model with Data Dictionary
Draw an EER model for the requirements identified in Part 1. The EER Model must be shown in UML notation which is discussed in class and illustrated in our text.
The EER Model should be accompanied with a data dictionary which includes entity type table, relationship type table and attribute table.
Assignment submission format for the EER Model with Data Dictionary part: The requirements document MUST have the following sections:
• EER Model
• Documentation – Data dictionary details (description of entities, relationships and attributes)
Sample format for documenting the data dictionary is provided below.
Data Dictionary Format: Use the format described in your main text in documenting the data dictionary. The following provides samples for reference.
ENTITY TYPES
|
Entity Name
|
Description
|
Aliases
|
Occurrence
|
|||||||||||||
|
Collection
|
A collection is a physical
|
Physical area of the
|
||||||||||||||
|
collection of items in the
|
library is divided into
|
|||||||||||||||
|
library located at a particular
|
a set of collections
|
|||||||||||||||
|
physical location
|
||||||||||||||||
|
RELATIONSHIP TYPES
|
||||||||||||||||
|
Entity name
|
Multiplicity
|
Relationship
|
Multiplicity
|
Entity name
|
||||||||||||
|
PhysicalCopy
|
0..*
|
LocatedIn
|
1..1
|
Collection
|
||||||||||||
|
…
|
||||||||||||||||
|
ATTRIBUTES
|
||||||||||||||||
|
Entity
|
Attributes
|
Description
|
Data
|
Nulls
|
Multi-
|
Derived
|
Default
|
|||||||||
|
Name
|
Type &
|
valued
|
||||||||||||||
|
Length
|
||||||||||||||||
|
Student
|
studentId
|
A unique id
|
char
|
N
|
N
|
N
|
||||||||||
|
given
|
to
|
|||||||||||||||
|
every
|
||||||||||||||||
|
student
|
||||||||||||||||
Plagiarism Free Assignment Help
Expert Help With This Assignment — On Your Terms
✓ Native UK, USA & Australia writers
✓ Deadline from 3 hours
✓ 100% Plagiarism-Free — Turnitin included
✓ Unlimited free revisions
✓ Free to submit — compare quotes