COM325 Database Development

MODULE SPECIFICATION FORM Module Title:

Module code:

Database Development

Cost Centre:

COM325

Semester(s) in which to be offered: Office use only: To be completed by AQSU:

Existing/New:

New

Level:

2

3

Credit Value:

20

JACS2 code:

With effect from:

September 2013

Date approved: Date revised: Version no:

August 2013 1

Title of module being replaced (if any):

Originating Academic Department:

Computing

Module duration (total hours): Scheduled learning & teaching hours Independent study hours

200 48

Module Leader:

Parvez Jugon

Status: core/option/elective (identify programme where appropriate):

152

Programme(s) in which to be offered: International Foundation Year BSc Applied Computing

Pre-requisites per programme (between levels):

Module Aims: This module focuses on equipping students with the knowledge and skills needed to be able to design, create and test fully working database applications to a professional standard. This module introduces the essential components of a relational database using Microsoft Access, one of the most popular and flexible database systems. The early part of the module concentrates on the theory and understanding needed to be able to design databases correctly. Students will learn a number of common techniques that are used to produce efficient and robust designs. Students will learn the basic skills and techniques necessary to design, create, enter, view, sort, select and print data.

Expected Learning Outcomes: At the end of this module, students will be able to: Knowledge and Understanding: 1. 2. 3. 4.

Demonstrate understanding in the uses of and tools/techniques used in databases Design create, populate and test a multiple table database Use advanced features of a database and test functionality Review the finished relational database

Transferable/Key Skills and other attributes: analyse information systematically; solve problems by breaking them down into more manageable subsets; begin to study independently; with guidance, digest, analyse and organise material to produce, to a deadline, efficient and structured solutions to problems; use written and electronic sources of reference to solve problems and enhance knowledge.

Assessment: Assignment 1 Design, implementation and test a database for a given scenario Design and implement a working relational database with five tables and set up relationships according to the user need Implement features in data entry forms to ensure validity and integrity of data Import data from an external source Devise and Test queries using multiple tables and multiple criteria Evaluate the database against the required user need Assessment number

1

Learning Outcomes to be met

Type of assessment

1-4

Coursework

Weighting

Duration (if exam)

Word count (or equivalent if appropriate)

100%

4500

Learning and Teaching Strategies: Lectures will be used to introduce the learning material and for demonstrating the key concepts by example. This is a very practical subject, and it is important that the learning materials are supported by hands-on opportunities provided by practical classes. During the practical tutorial sessions, students will acquire hands-on experience on designing and developing database application systems. Emphasis will be placed on the importance of regular working and learning by example. Students will be directed to read material from recommended literature as well as supporting material that has been prepared by the lecturing team. Some independent study time will be used by students to practice and develop the skills required to complete the assessment. Students will be expected to attend lectures, undertake preparation in advance of practical classes and engage in the practical classes.

Syllabus outline: Databases and relationships Types of databases, e.g.:local, online (web),flat file,relational Types of relationships, e.g.: one-to-one, one-to-many,many-to-many Designing a database Design documentation, including: ● hardware, software and other resources required ● entity Relationship Diagram (ERD), including entities, attributes and relationships ● validation and verification procedures ● input and output screens/forms and reports ● constraints (e.g. hardware and software availability) ● test plan with test data to test functionality ● a brief outline of alternative design ideas. Software tools and techniques to develop a relational database Create and edit: ● single and multiple table structures with appropriate field characteristics, including o field names o field data types, e.g. alphabetic (text and memo), numeric (number, currency, and date/time), alphanumeric (text and memo), logical (yes/no and true/false), web (hyperlink), lookup wizards o field sizes (e.g. byte, integer, long integer, single, double and decimal) o field formats (e.g. fixed and decimal places) o default values ● validation rules and text, which applies to a range, format and length for different data types including input masks ● indexing (e.g. primary key, foreign key) ● create new records (e.g. populate tables with data manually or import a data set from an external source (text file or spreadsheet)) ● edit and delete existing records of data ● create, edit and delete relationships

● use wizards. Create and edit forms, including: ● simple forms (e.g. data-entry and main menu forms with limited functionality) ● customised forms, which suit users and purpose, e.g. a data-entry form that facilitates accurate data entry, has an appropriate user interface with programmable buttons that run events (navigation, add new record, delete record, print record) and main menu forms allowing users to access sub-forms (e.g. data-entry forms), run queries and view reports ● sub-forms ● forms should o allow navigation between sub-forms o enable the entry of data into single and multiple tables o have appropriate entry-form field lengths o provide clear labelling of entry-form fields o provide instruction fields where necessary o include validation checks on field entries as appropriate o delete existing forms. Use reports: ● create and edit reports to present meaningful information for a purpose and specific users, using features (e.g. titles, page layout, colours, field selection, date/time, grouping, introductions and images) ● delete existing reports. Use sorts: ● sort records using a single field (alpha or numeric, ascending and descending) ● sort records using multiple fields. Use queries: ● queries with single criteria on one or two fields using relational operators ● queries with multiple criteria using at least two tables, making use of logical operators (e.g. AND, OR, NOT) and wildcards. Automation, security and usability e.g.: ● automated tasks using macros ● security to protect the database ● provide onscreen user navigation and instructions. Testing a database The testing process: ● Test the relational database for functionality, purpose and usability ● Use feedback from others, for example, on the database’s functionality, its usability, and its performance ● Consider possible improvements and/or refinements to the relational database, for example, additional tables, additional queries, forms, reports, automation (macros) and security ● Provide onscreen user navigation and instructions. Reviewing a database Review the finished relational database for: ● the user requirements and user experience (e.g. usability and reliability) ● fitness for purpose ● any constraints (e.g. hardware and software availability) ● strengths and improvements.

Bibliography: Essential reading: Grauer R.,Poatsy M.A., Mast K., Hogan L, (2011 ) Exploring Microsoft Office Access 2010 Introductory Prentice Hall Other indicative reading: Connolly, T. M, Begg, C E (2010) Database systems : a practical approach to design, implementation, and management, 5th Edition Addison Wesley Lambert J., Cox J., (2011) Microsoft Access 2010 Step by Step Microsoft Press