The group project requires you to develop a database application to solve a real world data management problem. The entire project consists of three deliverables: 1) a project pr
Requirements : MS VISIO AND MS ASSESS
The group project requires you to develop a database application to solve a real world data management problem. The entire project consists of three deliverables: 1) a project proposal describing the nature of the problem(s), the proposed database solution to the problem(s), and the associated ERD. 2) An updated group proposal with an enhanced database/ERD, a prototype of the application that contains a preliminary Access database and a set of functionalities your database plan to provide, and 3) the final fully functional database application with actual tables loaded with data and working queries. The project will be completed as a group project with up to 2 students in each group.
The first deliverable is a proposal in MS Word document (using the attached template) that includes: 1) the description of the business context and the problem(s) that your application is trying to address, 2) a list of the entities involved (with descriptions) and their attributes (with descriptions and data types), 3) business rules that define all the relationships among entities, the constraints, and the attribute domains (if any). Note that each relationship requires 2 business rules (see examples in the template). 4) A tentative ERD with all primary/foreign keys, relationships, and constraints specified, and 5) a brief outline of the functionality of the application (i.e. what the users can do with this application). The proposed ERD should include at least 6 entities (a supertype/subtype hierarchy will count as one entity) and should have at least one of each of the following relationships – 1:1, 1:M, M:N (broken in 1:M through an associative entity), unary relationship, and supertype/subtypes with different overlapping/specialization constraints specified. Please read the attached sample file carefully and ensure all the above requirements are met.
Important: To ensure all group members participate in the group project and avoid free-riding. Every student should independently work on requirements 1), 3), and 4) first and submit the individual proposal to other group members for discussions no later than September 17 (you are encouraged to set an earlier date upon agreement of all group members). The group will then select one ERD and expand it into a group proposal that addresses the above 5 requirements. After the group develops the proposal, all students should submit a word document independently that includes the final group proposal and the individual proposal that contains requirements 1, 3, and 4). Both parts will be considered in the grading of this deliverable. If any student fails to submit their individual proposal to the group, the group should not share the the final proposal with this student and should notify the instructor immediately.
Every student should submit his/her individual proposal (that includes #1, 3 and 4) as well as the group proposal (that include #1 through #5) in one MS Word document, and include separate visio files for their individual ERD and the group ERD. Name the file as Deliverable_1_LastName.docx (and.vsdx). For example, if my proposal was not chosen to be the group proposal, then my 3 files will be named: Deliverable_1_Liu.docx, Deliverable_1_Liu.vsdx (individual ERD) and Deliverable_1_Liu_Group.vsdx (for the group ERD), respectively. For those whose individual ERD is chosen by the group, please indicate so in the proposal and submit only the first two files.
IS 3063 Term Project Deliverable 1 Template
Group Number:
Your Name:
Your email:
Note that in the first deliverable, each student should independently come up with a business problem/ERD with section 1, 3, 4 outlined below completed and exchange this individual proposal with other group members. The group will jointly choose one to develop as a group (you may also combine different portions of multiple ERDs to form a new ERD for the group). Your individual ERD cannot be the same as any example covered in the book, i.e. your ERD may contain some entities covered in the book examples but more than 50% of your entities or relationships should be different from any examples covered in the book/assignments.
Group proposal section (every student should include this section):
1. Description of the business context and related data management problem(s)
Perfect Furniture is furniture company that manufactures and sells different kinds of furniture to customers nationwide. The company is currently using different isolated database management systems to store and process data, which causes a lot of inconsistencies and discrepancies across its different business units. It also makes it very difficult for the management to monitor the inventory status and strategically prioritize its production capabilities.
For the Term Project, we would like to create a database application to help Perfect furniture integrate its fragmented data management systems and provide more effective data management… (this is only an example, please elaborate based on your actual problem/solution)
2. The entities and the attributes (with description, constraint and data types)
Entity: Orderline (Associative Entity between Order and Product) :
|
Description: records each line in an order placed by a customer |
|||
|
Attribute |
Description |
Constraints |
Data Type |
|
OrderID |
6-digit Numeric ID of each order |
PK, FK1 |
CHAR(12) |
|
ProductID |
8-digit Numeric ID of the product that appears on each line of the order |
PK, FK2 |
CHAR(8) |
|
OrderedQuantity |
Number of units purchased |
Unique, Not Null |
INTEGER |
|
SalesPrice |
The final sales price of the product |
Not Null, >0 |
DECIMAL(4,2) |
|
Backordered |
Whether this product is backordered |
Default value: No |
BOOLEAN |
|
DateShipped |
Date this product is shipped to customer |
DATE |
|
|
LineMemo |
Special notation for each order line |
|
VARCHAR2(40) |
Please use one table for each entity.
3. Business rules that define all the relationships among entities, the constraints, and the attribute domains (if any). Note that each relationship (i.e. each line in your ERD) requires 2 business rules (bi-directional), and each business rules should specify both the minimum and maximum cardinalities. The following is just an incomplete list for your reference.
Relationships:
a. Customer – Order: 1:M, a customer can place either no order or multiple orders, and order can be placed by one and only one customer.
b. Order – Order line: 1:M, each order may consist of multiple line (one line for each product ordered), and each order must belong to one and only one order.
c. Product – Orderline: 1:M, each product may appear in multiple lines in the Orderline table, each order line may contain one and only one product.
Constraint : a product cannot appear in in multiple lines of the same order.
….
4. ERD (can be modified in the next deliverable).
The ERD below is just an example. Your ERD must have all primary/foreign keys, relationships and constraints correctly specified. The proposed ERD should at least 6 entities with at least one of each of the following relationships: 1:1, 1:M, M:N (broken in 1:M), unary relationship , and supertype/subtypes with different overlapping/specialization constraints specified.
Below is another example for an ERD that includes the supertype/subtype example for your reference. You should have all entities in one ERD.
5. A summary of the functionality of the application (i.e. what the users can do with this application, future extension/integration with other systems etc.).
This new DBMS will allow users to keep track of the number of units available for each product and update the inventory when a sale occurs, it will also allow users to search the database to derive useful business information. For example, a user can search the DBMS to find out which product generates the most sales, which state has the most number of customers, what are the preferences of customers (i.e. the type of furniture ordered) from different states, etc. In the future, we can also connect this DBMS with a shipping tracking system to provide customers more timely update of the shipping status of the products they ordered…..
Continue on next page.
Individual proposal section (every student should include this section except those whose ERD was chosen by the group – indicate so if that’s the case ):
1. Description of the business context and related data management problem(s).
2. Business rules that define all the relationships among entities, the constraints, and the attribute domains (if any). Note that each relationship (i.e. each line in your ERD) requires 2 business rules (bi-directional), and each business rules should specify both the minimum and maximum cardinalities.
3. ERD.
image1.jpeg
image2.jpeg
Collepals.com Plagiarism Free Papers
Are you looking for custom essay writing service or even dissertation writing services? Just request for our write my paper service, and we'll match you with the best essay writer in your subject! With an exceptional team of professional academic experts in a wide range of subjects, we can guarantee you an unrivaled quality of custom-written papers.
Get ZERO PLAGIARISM, HUMAN WRITTEN ESSAYS
Why Hire Collepals.com writers to do your paper?
Quality- We are experienced and have access to ample research materials.
We write plagiarism Free Content
Confidential- We never share or sell your personal information to third parties.
Support-Chat with us today! We are always waiting to answer all your questions.
