Download IS4424

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Microsoft Jet Database Engine wikipedia , lookup

Open Database Connectivity wikipedia , lookup

Oracle Database wikipedia , lookup

Concurrency control wikipedia , lookup

Database wikipedia , lookup

Functional Database Model wikipedia , lookup

Relational model wikipedia , lookup

Clusterpoint wikipedia , lookup

ContactPoint wikipedia , lookup

Database model wikipedia , lookup

Transcript
IS4424
BUSINESS INFORMATION SYSTEMS
IS4424
ENTERPRISE DATABASE DEVELOPMENT
COURSE OBJECTIVE:
This module is designed to teach students the skills
needed to effectively exploit large scale database
management system (DBMS) technology in an
enterprise context.
LECTURES:
Wednesday
ASSESMENT:
Continuous Assessment
Final Exam
40%
60%
LECTURERS:
Dr. Frederic Adam
[email protected]
Ext. 3343
COURSE OUTLINE:
4pm – 6pm

W9
Designing Oracle databases
 Data Modelling
 Analysing requirements
 Development environment
 Sizing and scaling – space management
 Database configuration
 SQL – Review and Advanced
 Schema creation and administration
 Application development
 Report generator
 Connecting to an Oracle Database
 OLAP
 Organisational Intelligence Technologies
 Data warehouses
 Data Mining
 Object-Oriented databases
 Knowledge Management Systems
 Database and data Administration in large organisations
 Data integrity and Quality
 Crash recovery
 Database Tuning and Benchmarking
 Database Security
Page 1 of 2
IS4424
PROJECT
Students will be expected to develop a distributed system as an organisational
management tool. Individual and group marks will be allocated for the overall
development. Groups will consist of five students each representing a component of
an organisation (e.g. The Purchasing Department) combining to meet some common
organisational goal, such as selling a product. Each student will be expected to
develop individual databases that will be interconnected to form a Knowledge
Management System (KMS). The KMS will effectively be an interface (e.g. Visual
Basic) pulling useful information from the databases for both the different
departments and managers.
Note: Reports or prototypes not submitted by the dates stated will incur penalty
deductions of 10% per week or part thereof.
Project Stages
Proposal
Analysis & Design
Practical Exam (MCQ)
Prototype (Individual Marks)
Knowledge Management System (KMS)
Marks
N/A
5%
10%
15%
10%
Dates
15/10/03
12/11/03
10/12/03
28/01/04
25/02/05
Practical Exam (10%) – 2hr – SQL + Oracle Environment
The exam will focus on the material presented in practical sessions as outlined in the
Tutorial Handout.
Proposal – Written Document & System Specification
Groups are expected to identify and outline, in a document, an organisation of their
choice. The document should describe the Knowledge Management Systems (KMS),
and effectively a plan of the development process.
Analysis & Design (5%) – Written Document
The analysis stage of the project defines the problem or requirements to be addressed.
Groups are also expected to outline the logical design of the Knowledge Management
System (KMS). Techniques such as DFDs and ERDs as well as the development
methodology employed should also be outlined in this report.
Prototype (15% - Individual Marks) – System & Written Specification
Individual students will be expected to deliver a fully functional populated database
and system specification including data structures and security considerations.
Knowledge Management System (10%) & Written Document
A Knowledge Management System (KMS) is the final requirement of the project. The
system should interface with the departmental databases using for example a VB
front-end or a web based front end. Groups are expected to incorporate managerial
requirements into the system such as Sales Forecasting. The KMS should also include
different levels of protection to effectively prevent risks (proactive and reactive) that
the system could encounter.
Page 2 of 2