TPS & MIS Access Database Application Project
Objective
• Design and Develop a small transaction processing and Management Information System that Captures, Stores, and Updates data; and Extracts Information about Stakeholders (employees, customers, etc.) and Business Transactions .
The application will permit entry and updates of basic data and a management information system that permits retrieval of relevant management information. The focus here is on an internal information system only. A Customer Integrated System or a Business-to-Business web-based system is beyond the scope of this particular project. Student proposal must be approved b the instructor before proceeding to the design and development stage. You will use the Access DBMS to build the application. Keep in mind that it is only the tool to accomplish your goal. The key element for you is Design. That is independent of Access and must be done first. You will need to learn quite a bit about Access to perform the physical implementation successfully.
System Characteristics
Basic Functionality
• • • • • Enter Basic Entity Data with an appropriate User Interface (Form) Update Basic Entity Data with an appropriate User Interface (Form) Extract On-line Data (Query) Produce a management report (Report) Switchboard Environment for ease-of-use (optional)
This is an open-ended application and you are encouraged to use your own knowledge of the small business to enhance, expand or modify the application.. Correct ER design, and basic Functionality (does it work?) are the major criteria for marking. To manage the scope of the project, limit your primary entities to between of 3 to 5.
Design Issues
As is the case with any complex software, there are many different ways of accomplishing the same thing in Access. The following is a list of design issues that are recommended that you keep in mind. When in doubt, make the assumption that will result in the least amount of work. Do not get caught up on "what if the user does this?" issues. Stick to the requirements and assume that your users are perfect. Intelligent Table and Relationship design is the key to the whole project. Do not waste time on purely cosmetic things like perfect alignment, gratuitous clip-art, and so on. Where appropriate, use default values, validation rules, and input masks, and enforce referential integrity in your relationships. Use the report and form wizards but do not waste your time with the table or query wizards.
Table design
Keys - All your tables should have a suitable primary key specified. Field properties (e.g., captions, defaults, input masks, validation rules) The field properties for each field in your database should be specified. However, do not over-specify properties. Relationships Correct relationships and referential integrity constraints should be specified where appropriate. Basic forms – either use subforms where appropriate or combo-boxes to enter foreign keys. Forms to add or change data in tables. Users will use these forms to view, add, and change data. Other substantive interface enhancements or novel functionality use your imagination. Note, however, that one feature implemented on ten forms counts as one feature. Clipart may be used, but does not earn any bonus marks. Bonus marks are given sparingly, so concentrate on the core requirements first
Queries/Reports
Queries to extract information. The number and type queries/reports is a Design issue and is up to you, however, they must serve a useful business purpose. You should demonstrate the use of the following capabilities in your queries: • Complex criteria – AND/OR combinations • Expressions – calculated field • Multi-table query
Process and Deliverables
• • • Prepare ERD of the proposed Database, and associated information on paper and present to your instructor (Analysis and Design), and get approval before proceeding with using Access. Build the Application in Access (Implementation and Testing) and submit. The submission will be a working application, and supporting documentation (Word) o Benefits of Information System to the selected business,
o o o o o o o
ERD, Tables, Attributes (defaults, masks, validation rules, captions, etc..) Forms, Queries and typical reason for business use, Reports (typical reason for business use) Refer to Project submission guideline document at : ProjectFormat.pdf Copy the Access mdb file to the instructor’s “Labdatashares” folder - the name of your database should comply with the following format: • Bus141-yourlastname-yourfirstname Submit a hardcopy of the documentation to your instructor ( see guidelines link noted above for further details )
A Note on Backing Up You are ultimately responsible for your data and programs. Since no special concessions will be accorded to those who "lose" their assignments, you are encouraged to backup your work regularly.