Management Information System - Term Paper Example

project management plan for the MANAGING FIRE EXTINGUISHER AT QATAR PETROLEUM 07/05 PREFACE Good This Project Management Plan (PMP) is intended to provide guidance on the management of the fire extinguisher at Qatar Petroleum.  It gives brief explanation about the project along with why and how this project came about. In addition, it highlights restrictions that might affect the project’s direction. As well as the project deliverables, master schedule and budget summary. The project management members planned the project to meet the expected time frame and budget. RECORD OF CHANGES ok VERSION NUMBER DATE NUMBER OF FIGURE, TABLE OR PARAGRAPH *A M D TITLE OR BRIEF DESCRIPTION CHANGE REQUEST NUMBER V1 3/5 A Document creation V2 5/5 One paragraph A Adding preface V3 6/5 -Adding two paragraphs and one table + graph. -and review the whole document A & M Adding details to master schedule and budget summary V4 7/5 Adding to project summary and minor changes in other paragraphs A&M Adding to project summary *A - ADDED M - MODIFIED D – DELETED Table of Contents project management plan 1 for the 1 07/05/2014 1 1.SECTION: OVERVIEW 5 1.1.Project Summary bravo 5 1.1.1.Purpose, Scope, and Objectives 6 A.Goal / Objectives 6 i.The project objective is to develop a design for the system that will manage the fire extinguishers at Qatar Petroleum. The system will automate the current process which is manual. Every fire extinguisher currently is recorded on a spreadsheet. Managing the fire extinguishers in a large organization like Qatar Petroleum has proven a difficult challenge hence the need for the new application. 6 B.Purpose/ Need of this project 6 C.Scope 7 1.1.2 Assumptions and Constraints: 8 AAssumption: again here, related to the project and not the application 8 BConstraints: Those constraints should reflect as tasks (risk management tasks) in your WBS intended to overcome the constraints. 8 Existing Problems: 8 1.1.3 Project Deliverables Good all in all but you can always refer to the real deliverables from the document I sent you. 9 vii.Prototype with Windows Forms and/or Web Page 9 1.1.4 Master Schedule and Budget Summary: how much is the budget? 11 A. Master Schedule: 11 C.Budget Summary: 11 1. SECTION: OVERVIEW 1.1. Project Summary bravo This project involves analysis and design of a system that manages the fire extinguisher allocations and distribution within various zones, departments and locations at Qatar Petroleum. This need came about in order to increase the safety awareness within the entity. QP sits on a large land mass and activities that are held in its premises are highly inflammable. The number of people working in the institution is large in number. So, all these conditions increase the risk of fire within the entity especially if there is little awareness among the workers. Safety is a major concern for most Oil and Gas companies. Qatar Petroleum also takes great care for the safety of its staff and property. Installation of fire extinguishers in the company has been the custom since its existence. With the vastness of the area on which the company lies, managing and accounting for fire extinguishers, replacing expired extinguishers, monitoring the type of extinguishers in various locations and monitoring the numbers and types of extinguishers in various departments has been a great challenge. The purpose of this system is to ensure that higher management can from one point know which extinguishers are installed, the number and where. They also need to know which extinguishers need to be replaced, which are used and the ones that have expired. They need to know the departmental users in charge of the extinguishers and any reports that the company need on the make and usage of the extinguishers. 1.1.1. Purpose, Scope, and Objectives A. Goal / Objectives The goals of design of the system are: i. The project objective is to develop a design for the system that will manage the fire extinguishers at Qatar Petroleum. The system will automate the current process which is manual. Every fire extinguisher currently is recorded on a spreadsheet. Managing the fire extinguishers in a large organization like Qatar Petroleum has proven a difficult challenge hence the need for the new application. ii. Another objective is to provide documentation for the Fire Extinguisher Management system. This documentation is important to the design phase of the project and post-implementation phase. Changes in the code or functionality of the system in future will be aided by the documentation created here. Design of any application is important to be well documented. iii. The third objective is to ensure there is minimal data entry issues when capturing the data of new and existing fire extinguishers iv. To ensure easy retrieval of data of fire extinguishers, monitor distribution and of management team with a platform to monitor the existing fire extinguishers. v. Offer efficient communication between security teams, management teams and departments in case of fire. vi. To offer easy authorization for deployment of new fire extinguishers vii. To minimize the number of errors that occurs during the data capture process of the system. B. Purpose/ Need of this project The purpose of this project is to develop a system that will record, monitor, and manage fire extinguishers at Qatar Petroleum. The project will also include development of documentation of the entire application. The processes of design, development and deployment of the application will also be recorded. The design phase of the system will involve various tools such as use of UML tools, Microsoft Project and Visio for project management and various database tools and development IDEs. C. Scope The scope of this project is to provide a design analysis of the system, the functionality and documentation. System analysis will involve use of UML 2.0 tools such as class diagrams, sequence diagram, activity, state machine diagram and Entity Relationship Diagrams. Use cases are the basis of any UML 2.0 system analysis and will be part of the project. Use case diagram shows a relationship between the actors and use cases in the system. Actors are people, or objects that interact with the system. Some subsystems may act as actors in a system for example a legacy system that exports data into the system. Class diagram shows the structural design of the system. It is very useful to developers / implementers and other system users. It shows the classes and methods that will be incorporated in the system. Sequence Diagrams will be used to show various system entry processes and interactions. The process that users will encounter when certain actions are required or activated. Activity diagram will show an end-to-end flow of the system inputs from the beginning i.e. Login, to completion of a transaction in the system. ER Diagram shows the database structure of the system. The normalization table is important to help in normalizing the database. The entities of the database which are the tables of the database and the attributes that are the fields or columns in the table are well recorded. 1.1.2 Assumptions and Constraints: A Assumption: again here, related to the project and not the application The assumptions that have been taken into account include: i. Availability of budgetary provision to facilitate planning, analysis and and design of the system. ii. The design phase will elicit all the requirements of that the management demands for the new system. iii. The system to be developed will not need to offer in intelligent solutions or predictive solutions. The design is intended to provide an overview of the system that only capture various data. Constraints: Those constraints should reflect as tasks (risk management tasks) in your WBS intended to overcome the constraints. System constraints are i. Time for design the design is short because the requirements are extensive.. Why? ii. Availability of experts to help in the sign phase design of the application is not guaranteed. iii. Budgetary allocation to facilitate the requirement gathering, and system design is not sufficient. The number of persons required in this phase are more than the current budgetary provisions can provide. iv. Modelling and prototyping of the system is an expensive affair. 1.1.3 Project Deliverables Good all in all but you can always refer to the real deliverables from the document I sent you. The deliverables from this project are: i. Use-case Diagram. ii. Use-case Descriptions for each Use Case in your Use Case Diagram. iii. Sequence and/or Activity Diagrams for each Use Case in your Use Case Diagram. iv. A Class Diagram. v. State Machine/State Transition Diagrams. vi. An Entity Relationship Diagram (ERD) showing the 3rd Normal Form Database that will support the system you designed. vii. Prototype with Windows Forms and/or Web Page ID Name Duration Start Finish Predecessors Outline Level Cost 1 Fire Extinguisher Project (QP) 20 days 05 May 2014 25 May 2014 1 $7000 1 System Proposal 2 days 05 May 2014 07 May 2014 3 $1000 2 System Requirement Solution(SRS) Document 5 days 07 May 2014 12 May 2014 3 $1000 3 Modeling and Prototyping of system??? 3 days 13 May 2014 15 May 2014 3 $3000 4 Approval of Requirement Documentation 1 days 16 May 2014 17 May 2014 3 $200 5 Database Phase 8 days 17 May 2014 25 May 2014 4 2 6 Database Normalization Table 1 day 17 May 2014 18 May 2014 3 $100 7 Documentation of Database 2 day 19 May 2014 20 May 2014 3 $500 8 Graphical User interface Design 4 days 21 May 2014 24 May2014 3 $1000 9. Project Handover 1 days 25 May 2014 25 May 2014 8 2 $200 1.1.4 Master Schedule and Budget Summary: how much is the budget? A.  Master Schedule: B. Critical Path: C. Budget Summary:  The budget would include Employees working on this project weather technical or business, tools used to develop this system and integration with other systems, and other unexpected costs. The budgeted cost is as follow: 1- Salary: a. Programmers: 120 QR/ hour b. Project Planner: 150 QR/hour c. Programmers Assistant: 95 QR/hour d. System Analysis: 100 QR/hour e. System Designer: 100 QR/hour 2- Total number of employee required is equal to 8, a. with total cost of salaries: 565 QR/hour b. programmer: 1 i. Writing codes, supervise his or her assistants work. c. project Manager: 1 i. Overall supervising the project phases ii. Reviewing and approving documents d. Programmer assistant: 2 i. Help their programmer in coding and creating interface e. System analysis: 3 i. Analysis the existing system and the best available choices in the market and compare it with in-house developing f. System Designer: 1 i. Design databases and document the database to the project manger and programmer. 3- Total hours in project is 486 hours 4- Software tools: a. No additional cost. It already exists. 5- Integration Cost: a. Software Configuration: 25,000 QR b. Hardware Configuration: 35,000 QR i. This is estimated costs, because it’s hard to know what exactly is needed to make integration and that because of different systems they are using. Read More