K&L Sims Development, Inc. Database Phase 1 Document Group One: Donald Luna Alison Lee Brooke Sims 1. Problem Statement: K&L Sims Development, Inc. is a fast growing development company based here in Rolla, MO. As a company grows, their need for organization within the company begins to play a major role in whether or not they are going to continue to grow and succeed. As this development company grows, they must keep everything well organized in order to make sure they continue to please everyone associated with the company. The easiest way to organize a company’s information is by utilizing a computer to do all of the hard work. Our intent is to help make the following portions of K&L Sims Development, Inc. completely paperless. The database we will design will help keep K&L Sims Development, Inc. organized as it grows. The database will assist the company by keeping track of the following items: Who their suppliers are, what the company’s account number is with each supplier, and each suppliers phone number and address. What houses are currently in the building process and the key information for each house. What lots/building sites they currently own. The homeowners that they have sold to and key information about each homeowner. Who are their available contractors that they can contact to perform specific jobs. 2. System Requirements: What it does do: This database system will allow K&L Sims Development, Inc. to input all of their current information that they have collaborated over time into the above listed categories (entities) in the database. Currently, all of this information that will be entered into the database is handwritten. Once the current information is entered, they will be able to quickly access all of this information in the database, instead of searching through paper files. They will also be able to add new suppliers, new houses that they intend/are building, new lots/building sites they have purchased, new homeowners that decide to buy from them, and any new contractors they want to add to their list. The ability to efficiently update each file will also be available through the database. The user of the database will be the construction manager, who is also the office/business manager. This individual will also be able to print out reports on any of the information that is in the database, such as a list of all the suppliers and the account number associated with each supplier. What it doesn’t do: This database system will not keep track of any financial information for K&L Sims Development, Inc. This would involve a whole new accounting aspect of the company. It will also not include the advertisement portion of the company, or any realtor contacts or information. 3. Conceptual Database Design: 4. Functional Requirements: Transaction Inputs Outputs Add Supplier The name of the supplier, K&L’s account number with that supplier, suppliers phone number, and suppliers address. Add Houses The cost of the house, the cost description, the completion date, and the unique house number. Add Lots The acreage of the lot, the unique lot number, and weather or not it is available. Add Homeowners Their contacts, name, address, warranty on the house, and phone number. Add Contractors Their specialty, business name, name, address, phone number, and liability insurance agreement. If an attribute is left blank, the user will be notified and will not be able to continue until a valid input is entered. Once all information is valid, a success statement will appear to let the user know the supplier was added successfully. If an attribute is left blank, the user will be notified and will not be able to continue until a valid input is entered. Once all information is valid, a success statement will appear to let the user know the house was added successfully. If an attribute is left blank, the user will be notified and will not be able to continue until a valid input is entered. Once all information is valid, a success statement will appear to let the user know the lot was added successfully. If an attribute is left blank, the user will be notified and will not be able to continue until a valid input is entered. Once all information is valid, a success statement will appear to let the user know the homeowner was added successfully. If an attribute is left blank, the user will be notified and will not be able to continue until a valid input is entered. Once all information is valid, a success statement will appear to let the user know the contractor was added successfully. Database Interactions This will create a new supplier entity and insert each input into the correct attributes. This will create a new house entity and insert each input into the correct attributes. This will create a new lot entity and insert each input into the correct attributes. This will create a new homeowner entity and insert each input into the correct attributes. This will create a new contractor entity and insert each input into the correct attributes. Update Attributes Any attribute in the database will be able to be updated. The user will find the attribute they wish to change and make the change, then click on an update button on the interface. When the update button is clicked on, a success statement will appear to let the user know that the system has successfully updated the attribute. This will modify the correct entity based on which attribute the user is changing in the system. 5. Estimate of Effort: This is an estimate in total hours for each phase of the project: Phase 1: 15 hours (collection of data, requirements, and documentation) Phase 2: 100 hours Phase 3: 155 hours Total: 270 hours The hours that it will take to implement this database during the next two phases are largely dependent on how well our group can learn to use SQL and Oracle. Our group has no experience in either of these tools.
© Copyright 2026 Paperzz