DATABASE IMPLEMENTATION

Transcription

1 DATABASE IMPLEMENTATION Interior Design Management System Instructor: Dr. Stephanie Haas Information Science School of Information and Library Science University of North Carolina at Chapel Hill Wanchen Zhao Dec

2 Table of Contents 1 System Specification ER Diagram Database Schema Data Dictionary Database Implementation Queries and Results Lesson Learned

3 1 System Specification The Interior Design Management System will contain the following subsystems. 1) Project Management Subsystem This subsystem allows project leader to manage multiple projects, including designer, design plan (preliminary and final version), design contract (contract status and contract file if any), project status, project issues (issue statement and issue status), action plan, and completion due date. Every project issue must associate with one project. One project can only be assigned to one project leader for accountability concerns, while a project leader can manage multiple projects. The system also allows supervisor to review the status and financial records (sales revenue and profit) of all ongoing projects. 2) Design Plan Subsystem This subsystem handles detailed design plans, including initiate date, design file if any, detailed design action, schedule (start date and end date) and quantity for each feature, such as room features (wall, window, floor, etc.), furniture, household application, decoration for each room of a specific house owned by a client, as well as royalty rate and design fee according to the level of the designer, and cost estimation of the whole design. One designer can manage and develop multiple design plans, which must be referred to a particular design request from one customer. The system only records the preliminary and final design plan for each request. One custom request can only be assigned to one designer, while a designer can react to multiple requests based on the assignments allocated by the supervisor. 3) Client Requirement Subsystem This subsystem records the customers requirements for interior design, such as initiate date, design style, budget, due date and specific requirements. It also provides access to the basic information of the client s house properties, including the real estate type (attached/multi-unit dwelling, Semi-detached dwelling, Single-family detached house, portable dwelling), the address, number of rooms, and housing area. One client might have several housing properties for designing and he/she also be able to place multiple requests for one house (e.g. a client might intend to redesign his/her house a few years later). The system also provides dashboard for clients to review design plan details, design contract, and report of cost and progress, e.g. if any delay for each design feature. 4) Database Management Subsystem This subsystem allows data maintenance and storage. The functions include adding, searching, update, delete and archiving. The information contained in this subsystem includes, Employee Information It records employee s basic information, such as employee ID, system password, name, phone number, department, address. There are two types of employee specified by the system, project leader and designer. One employee can take multiple roles. For project leader, the system records his/her project management level additionally, while for the designer, who is rated by the design level (beginner, intermediate and advanced) and the design fee and royalty 1

4 rate of his/her design are different accordingly. Technically, the higher level of the designer, the higher design cost the custom might pay. Client Information It records clients basic information, such as client ID, name, system password, phone, and . Design feature Information It records information about distinctive interior design features for repeated usage. For each design feature, the system records its ID, name, supplier, unit, delivery method, cost and picture if applicable. It is not necessary that each design feature to be used in a certain design, but the designer would constantly explore interesting design features and store them for future usage. 2 ER Diagram 2

5 3 Database Schema Employee EmployeeID ELastName EFirstName Phone Department Street City USstate ZIP IfProjectLdr IfDesigner DLevelID Project ProjectID ProjectStatus EmployeeID InitiateDate DesignLevel DLevelID LevelName DesignFee RoyaltyRate Client ClientID CLastName CFirstName Phone Request RequestID InitiateDate Budget Style DueDate Requirement House HouseID ClientID RealEstateType HouseArea Street City USstate ZIP Room HouseID RoomType RoomArea Issue ProjectID IssueID IssueStmt DueDate ActionPlan IssueStatus DesignFeature FeatureID FeatureName Unit Supplier Cost Delivery Picture Design DesignID DesignPlanID FeatureID HouseID RoomType DesignAction Quantity StartDate EndDate ComplStatus DesignPlan DesignPlanID ProjectID DPType InitiateDate Description DesignFile ContrFile ContrStatus RequestPlace RequestID ClientID HouseID DesignManage DesignPlanID RequestID EmployeeID *Note: Different colors are for differentiating the reference lines when crossover 4 Data Dictionary Coding Legend: Y Yes N No N/A Not Applicable Highlight if the answer is Y 1. Employee EmployeeID Y N/A Y char(6) E00000-E99999 ID of the employee ELastName N N/A Y varchar(25) Last name of employee EfirstName N N/A Y varchar(25) First name of employee Phone N N/A Y char(10) 3

6 Department N N/A Y varchar(25) In (Design, Marketing, Engineering, Accounting) Street N N/A N varchar(30) City N N/A N varchar(20) Usstate N N/A N char(2) ZIP N N/A N char(5) IfProjectLdr N N/A Y char(1) In (Y, N) Flag if the employee is a project leader IfDesigner N N/A Y char(1) In (Y, N) Flag if the employee is a designer DlevelID N DesignLevel N char(2) ID of designer s level 2. Project ProjectID Y N/A Y char(6) P00000-P99999 ID of the project ProjectStatus N N/A Y varchar(10) In (Completed, The status of the Canceled, On-track, project Off-track) InitiateDate N N/A Y date Default today s date EmployeeID N Employee Y char(6) E00000-E99999 ID of the employee 3. DesignLevel DLevelID Y N/A Y char(2) L1-L3 ID of design level of a designer LevelName N N/A Y Varchar(15) In (Beginner, Intermediate, Advanced) DesignFee N N/A Y float(7, 2) The fixed fee of a design each time RoyaltyRate N N/A Y float(3, 2) The upcharge rate of each feature in a design 4. Client 4

7 ClientID Y N/A Y char(6) C00000-C99999 ID of the client CLastName N N/A Y varchar(25) Last name of client CFirstName N N/A Y varchar(25) First name of client Phone N N/A N char(10) N N/A Y varchar(30) address of client 5. Request RequestID Y N/A Y char(6) R00000-R99999 ID of client s request InitiateDate N N/A Y date The date client initiate a request, default as today Budget N N/A Y int The budget planned by the client Style N N/A N varchar(20) In (Modern Simplism, European, Rural, Ancient Rome, The design style Natural, Gothic, Other) DueDate N N/A Y date The planned delivery due date by the client Requirement N N/A N varchar(500) The specific requirements of design 6. House HouseID Y N/A Y char(6) H00000-H99999 ID of client s house ClientID Y Client Y char(6) C00000-C99999 ID of the client In (Attached/multiunit dwelling, Semidetached RealEstateType N N/A Y varchar(25) dwelling, The type of client s house, Portable dwelling) Single-family detached real estate 5

8 HouseArea N N/A N float Street N N/A N varchar(30) City N N/A N varchar(20) USstate N N/A N char(2) ZIP N N/A N char(5) The house area of client s dwelling in ft. 7. Room HouseID Y House Y char(6) H00000-H99999 ID of client s house In (DiningRoom1-3, MainBedroom, Guestroom1-3, RoomType Y N/A Y varchar(25) Kitchen1-3, The type of the LivingRoom1-2, room in a house Bathroom1-3, Balcony1-3, Study1-2, Cellar, Other) RoomArea N N/A N float The room area of client s dwelling in ft. 8. Issue ProjectID Y Project Y char(6) P00000-P99999 ID of the project IssueID Y N/A Y char(6) I00000-I99999 ID of the employee IssueStmt N N/A Y varchar(30) A brief statement of the project issue DueDate N N/A Y date The due date to solve the issue ActionPlan N N/A Y varchar(50) Action plan to solve the issue IssueStatus N N/A Y varchar(10) In (Solved, Open, The status of the Assigned, On-track, issue Off-track) 9. DesignFeature 6

9 FeatureID Y N/A Y char(6) F00000-F99999 ID of the design feature FeatureName N N/A Y varchar(25) Name of design feature Unit N N/A Y varchar(25) Measurement unit of design feature Supplier N N/A Y varchar(30) The Supplier of the design feature Cost N N/A Y float The cost of the design feature in $ Delivery N N/A N varchar(25) The delivery method of the design feature Picture N N/A N BLOB The picture of the design method 10. Design DesignID Y N/A Y Integer Autoincrement ID of design DesignPlanID N DesignPlan Y char(7) DP00000-DP99999 ID of design plan FeatureID N DesignFeat ID of the design Y char(6) F00000-F99999 ure feature HouseID N Room Y char(6) H00000-H99999 ID of client s house In (DiningRoom1-3, MainBedroom, Guestroom1-3, RoomType N Room Y varchar(25) Kitchen1-3, The type of the LivingRoom1-2, room in a house Bathroom1-3, Balcony1-3, Study1-2, Cellar, Other) DesignAction N N/A N varchar(100) Specification of design actions Quantity N N/A Y int The quantity used of the design feature StartDate N N/A Y date The date that implementation the design feature starts 7

10 EndDate N N/A Y date ComplStatus N N/A Y varchar(10) In (Completed, Canceled, On-track, Off-track) from, default as today The date that implementation the design feature ends The completion status of the design feature 11. DesignPlan DesignPlanID Y N/A Y char(7) DP00000-DP99999 ID of design plan ProjectID Y Project Y char(6) P00000-P99999 ID of the project DPType N N/A Y varchar(25) In (Preliminary, Final) The design plan type recorded InitiateDate N N/A Y date The initiate date of the design plan, default as today Description N N/A Y varchar(100) The brief description of the design plan DesignFile N N/A N text Design file ContrFile N N/A N text The contract file of the design ContrStatus N N/A Y char(2) In (Unsigned, The contract status Canceled, signed) of the design 12. RequestPlace RequestID Y Request Y char(6) R00000-R99999 ID of client s request ClientID Y Client Y char(6) C00000-C99999 ID of the client HouseID Y House Y char(6) H00000-H99999 ID of client s house 13. DesignManage DesignPlanID Y DesignPlan Y char(6) DP00000-DP99999 ID of design plan RequestID Y Request Y char(6) R00000-R99999 ID of client s request EmployeeID Y Employee Y char(6) E00000-E99999 ID of the employee 8

11 5 Database Implementation The database is created by the following sequence. 1. DesignLevel 2. Employee 3. Project 4. Client 5. Request 9

12 6. House 7. Room 8. Issue 9. DesignFeature 10

13 10. DesignPlan 11. Design 12. RequestPlace 11

14 13. DesignManage 6 Queries and Results 1. Designer Tom Jackson wants to know which requests are handled by him and who are the clients that placed those requests? Display the request ID and initiate date and clients information, including last and first name, phone number, and address. The result should be ordered by request s initiate date. SQL Statement: Database Result: 2. Are there any design plans whose estimated costs exceed the client s budget? If so, display the associated project manager s name (last and first name) and the client s information, including name (last and first name), phone and for negotiation. SQL Statement: 12

15 Database Result: 3. Display the design plan overview, including request ID, initiate date, budget, delivery due date, design plan initiate date, design plan description, estimated cost and estimate launch date (the next day that all design features are planned to complete) for client Linda Zhao, whose is It should contain all the requests Linda Zhao placed before. SQL Statement: Database Result: 13

16 4. Project manager Lucy Zhang want to see if any estimated launch date (the next day that all design features are planned to complete) of a design plan whose initiate date is after Sep would exceed the client s requirement under her management. If that is the case, display the design plan ID, its designer and his/her phone number. SQL Statement: Database Result: 5. Display a project dashboard of October for a project leader Lucy Zhang, including all the projects under her management that are initiated in October this year. Display the project ID, project status, total revenue and total profit. SQL Statement: Database Result: 14

17 6. Display an overview of project P00005 for a project leader Lucy Zhang, including project status, project revenue and profit, the number of design plan as well as the number of project issue it contains. SQL Statement: Database Result: 7. Any project issue happens associated with designer Jack Wang s designs? If so, display the issue statement, action plan, due date and issue status, ordering by issue due date. SQL Statement: Database Result: 8. Display a design plan dashboard for a designer Julie Wang, including all the design plans under her management, the design plan ID, the project leader for each design plan, design plan type, initiate date, 15

18 contract status, total estimated cost of the design features and profit by each design plan, ordering by design plan initiate date. SQL Statement: Database Result: 9. A designer Julie Wang whose employ ID is E00004 wants to review her design for a client s house H00001, including rooms and design information for each room, such as design feature s name, cost, supplier, delivery method, design action, quantity, unit, implementation start date and end date. SQL Statement: Database Result: 10. A supervisor wants to review the work load of all the designers and project leaders for rewarding purpose. The result should reflect the name and role of each employee who is either project leader, designer or both as well as the number of projects or(and) design plans he/she handles. 16

19 SQL Statement: Database Result: 7 Lesson Learned I am always happy to jump out of my comfort zone to learn something challenging and interesting that I have not practiced before. Taking database I is not that challenging for me since I have learned MS SQL Server before, however this course really played a significantly important role to shape my mind in the context of good design, which I really appreciate. I used to start creating a database from nothing, no consideration of entity relationship, normal form or data quality. I just created the tables the way it could serve the interface or function that an application needs. The advantage of this mind is that I would have a clear vision about what the database could achieve at the beginning but without a through thinking about the conceptual design, the database could easily end up in a poor design with many redundant data. So, I keep challenging myself to create something difficult as well as interesting throughout the semester and found it so fascinating when I finally tackled all the issues and delivered what I wanted. The hardest part is actually not the SQL statement but the holistic design to take you to the right place. I spent a lot of time to fix issues on ER development at the beginning to make sure I could deliver the functions I planned and in the end, it just became easy and smooth to implement. In the implementation phase, I started to review my design from the perspective of a client to input some meaningful data and tried something different to check if the database if robust enough. So, I encountered the issue of dynamic typing of SQLite. I think some of these problems could be fixed by data validation in the front end or just set up a AUTOINCREMENT for IDs in the database in my case. In the data entry phase of this project, I started to think about the real practice for a database or application. For example, the Design table must be inputted by a designer, who would record his design in a database and the DesignManage table is for capturing who entry the design plan for which request. So maybe a trigger in the database would be helpful in this case or maybe it could be realized by the front-end design by clicking saving button, the design s ID, his design plan and the request it associates with would be captured and saving in DesignManage table. I will be continuing focusing on improving the database in this area. 17