Sierra Geisel Final Project: Project Plan and System Design IT-415 Southern New Hampshire University August 22, 18

Project Plan The project plan details the work breakdown structure, project timeline, dependencies and tools used. Work Breakdown Structure: Phase One: Requirements 1.1 User requirements 1.2 Software & Hardware requirements 1.3 Research/Purchase software 1.4 Research/Purchase hardware 1.5 Review/Approve requirements Phase Two: Design 2.1 Review Requirements from phase one 2.2 Create example within software 2.3 Analyze example 2.4 Review/Approve design Phase Three: Development 3.1 Create required fields within software 3.2 Review/Revise required fields 3.3 Revise/Approve development Phase Four: Testing 4.1 Functional testing: enter data 4.2 Performance testing: perform necessary tasks with data 4.3 Revise/Review testing Phase Five: Production 5.1 Deployment 5.2 User training

Timeline: 7/2/2018 – 8/24/2018 Phase One Phase Two Phase Three Phase Four Phase Five 7/2/18 – 7/9/18 7/10/18 – 7/17/18 7/18/18 – 8/1/18 8/2/18 – 8/16/18 8/17/18 – 8/24/18 Dependencies: The Waterfall methodology is being utilized to guarantee this project is completed correctly and within the proposed timeline. A general dependency of the waterfall method is the strict order of phases; the preceding phase must be completed before the following can be started. Obtaining thorough, concise information during Phase One, the requirements gathering phase, will set the project up for smooth transitions throughout the rest of the phases. Correct development in Phase Three will also be very important to the project timeline. Using the analysis from the preceding phases to ensure the correct fields are input into the inventory database will keep the project on track. For example in this project specifically the database design cannot begin if the requirements of the inventory database are not listed.