Systems Project & Quality Management - Example

Project Plan - Course Name: Systems Project & Quality Management Name; Number: Course: Lecturer: Date: Table of Contents Project Plan - Course Name: Systems Project & Quality Management 1 Goals and objectives 3 1.1. Project Goals 3 1.2.Project objectives 3 1.3.Acceptance criteria 4 2.0. Task sheet 4 3.0. Solution Design with Quality Measurements 7 3.1. Hardware 7 3.2. Software 7 3.3. Quality measurements 8 4.0. Team’s activity plan 9 References 10 Goals and objectives 2 1.1. Project Goals 2 1.2. Project objectives 3 1.3. Acceptance criteria 3 2.0. Task sheet 4 3.0. Solution Design with Quality Measurements 6 3.1. Hardware 6 3.2. Software 6 3.3. Quality measurements 6 4.0. Team’s activity plan 8 Goals and objectives 1.1. Project Goals The main goal of JJ-IT Ltd logistics IT department management System is to offer the right thing, at the right place, at the right occasion, at the superlative cost. This new logistical management system is set to achieve the below goals[And06]. Fasten the warehouse activities and better services provision at the same time automating the normal manual tasks. Minimize the number of errors witnessed within the warehouse especially during information processing. Do away with data duplication which in turn leads to a lot of redundancies. Offer a consistent material and supplies flows that are vital to the warehouse operations. Avail up to date data to clients and stakeholders not forgetting that the data must also be accurate. Reduce the high warehouse dependency on humans on most of its task hence it should economize on time by offering less human dependent management responses. 1.2. Project objectives To build a new effective logistics management system for Bulk Breakfasts warehousing company. This software will improve and expand warehouse operation. This project will achieve the following objectives. Accurate& effective inventory control Elimination of errors in warehouse operation Time saving in warehouse operation Simplify warehouse operation Automate warehouse operation Reduce the losses of theft, obsolescence & wastage 1.3. Acceptance criteria No Item No of Clients in Favor 1 More expedient information access 2 Better expenses efficiency of provision of information 3 Economical use of time 4 Larger scope of relevant data and technology types 5 Easier system usability 7 Better system security 8 Quicker information availability 2.0. Task sheet WBS Task Name Duration Start Finish WBS Predecessors 1 Bulk Breakfasts Project 71 days Tue 14/08/12 Tue 20/11/12 1.1 Planning Phase 21 days Tue 14/08/12 Tue 11/09/12 1.1.1 Project Proposal 2 days Tue 14/08/12 Wed 15/08/12 1.1.2 Staff Requirement Estimation 1 day Thu 16/08/12 Thu 16/08/12 1.1.1 1.1.3 Roles Assignment 1 day Fri 17/08/12 Fri 17/08/12 1.1.1 1.1.3.1 Project Manager Responsibilities 1 day Fri 17/08/12 Fri 17/08/12 1.1.2 1.1.3.2 Business Analyst Responsibilities 1 day Fri 17/08/12 Fri 17/08/12 1.1.2 1.1.3.3 Software Engineer Responsibilities 1 day Fri 17/08/12 Fri 17/08/12 1.1.2 1.1.3.4 Portfolio Manager Responsibilities 1 day Fri 17/08/12 Fri 17/08/12 1.1.2 1.1.3.5 Hardware Engineer 1 day Fri 17/08/12 Fri 17/08/12 1.1.2 1.1.3.6 Team Charter 1 day Fri 17/08/12 Fri 17/08/12 1.1.2 1.1.4 Management Plan 8 days Mon 20/08/12 Wed 29/08/12 1.1.3 1.1.4.1 Scope Document 1 day Mon 20/08/12 Mon 20/08/12 1.1.3.5 1.1.4.2 Risk Management Plan 1 day Wed 22/08/12 Wed 22/08/12 1.1.4.1 1.1.4.3 Quality Management Plan 3 days Tue 21/08/12 Thu 23/08/12 1.1.3 1.1.4.3.1 Document Review 1 day Tue 21/08/12 Tue 21/08/12 1.1.4.1 1.1.4.3.2 Version Control Check 1 day Wed 22/08/12 Wed 22/08/12 1.1.4.3.1 1.1.4.3.3 Quality Management Plan Review 1 day Thu 23/08/12 Thu 23/08/12 1.1.4.3.2 1.1.4.4 Cost Estimation 1 day Fri 24/08/12 Fri 24/08/12 1.1.4.3 1.1.4.5 Change Request Plan 2 days Mon 27/08/12 Tue 28/08/12 1.1.4.4 1.1.4.6 Communication Plan 1 day Wed 29/08/12 Wed 29/08/12 1.1.4.5 1.1.5 Stakeholder Analysis 3 days Wed 5/09/12 Fri 7/09/12 1.1.4 1.1.5.1 External Stakeholders Analysis 1 day Wed 5/09/12 Wed 5/09/12 1.1.4.6 1.1.5.2 Internal Stakeholders Analysis 2 days Thu 6/09/12 Fri 7/09/12 1.1.5.1 1.1.6 Work Breakdown Structure 1 day Mon 10/09/12 Mon 10/09/12 1.1.5.2 1.1.7 Hardware Requirements 1 day Tue 11/09/12 Tue 11/09/12 1.1.6 1.2 Software Requirements Engineering Phase 7 days Wed 12/09/12 Thu 20/09/12 1.1 1.2.1 SRS 3 days Wed 12/09/12 Fri 14/09/12 1.1.6 1.2.2 RTM 2 days Mon 17/09/12 Tue 18/09/12 1.2.1 1.2.3 RSI 1 day Wed 19/09/12 Wed 19/09/12 1.2.2 1.2.4 Gap Analysis Documents 1 day Thu 20/09/12 Thu 20/09/12 1.2.3 1.3 Software Design Phase 21 days Fri 21/09/12 Fri 19/10/12 1.2 1.3.1 Use Case 2 days Fri 21/09/12 Mon 24/09/12 1.2.4 1.3.2 Class Diagram 3 days Tue 25/09/12 Thu 27/09/12 1.3.1 1.3.3 ERD 4 days Fri 28/09/12 Wed 3/10/12 1.3.2 1.3.4 Sequential Diagram 2 days Thu 4/10/12 Fri 5/10/12 1.3.3 1.3.5 Actual Code 10 days Mon 8/10/12 Fri 19/10/12 1.3.4 1.4 Implementation Phase 6 days Mon 22/10/12 Mon 29/10/12 1.3 1.4.1 DTM 4 days Mon 22/10/12 Thu 25/10/12 1.3.5 1.4.2 Release Notes 2 days Fri 26/10/12 Mon 29/10/12 1.4.1 1.5 Software Testing Phase 8 days Tue 30/10/12 Thu 8/11/12 1.4 1.5.1 Test Cases 4 days Tue 30/10/12 Fri 2/11/12 1.4.2 1.5.2 Test Report 2 days Mon 5/11/12 Tue 6/11/12 1.5.1 1.5.3 Sanity Testing Documents 1 day Wed 7/11/12 Wed 7/11/12 1.5.2 1.5.4 Test Traceability 1 day Thu 8/11/12 Thu 8/11/12 1.5.3 1.6 Maintenance Phase 3 days Fri 9/11/12 Tue 13/11/12 1.5 1.6.1 Change Request 1 day Fri 9/11/12 Fri 9/11/12 1.5.4 1.6.2 New Requirements 2 days Mon 12/11/12 Tue 13/11/12 1.6.1 1.7 Closure 5 days Wed 14/11/12 Tue 20/11/12 1.6 1.7.1 Final Project Report 3 days Wed 14/11/12 Fri 16/11/12 1.6.2 1.7.1.1 Document Submission 2 days Wed 14/11/12 Thu 15/11/12 1.6.2 1.7.1.2 Reflections 1 day Fri 16/11/12 Fri 16/11/12 1.7.1.1 1.7.2 Final Project Presentation 2 days Mon 19/11/12 Tue 20/11/12 1.7.1.2 3.0. Solution Design with Quality Measurements Since the software solution will serve clients from different points the solution design will incorporate a web based management system that shall be hosted by the company such that all clients can have a common point of service provision. From this the system access points shall me networked via use of effective networking equipment to a central data store where all clients will access up to date information. There will also be a security mechanism where by all points will have restricted user levels and customized accounts as per the kind of user[Wal98]. Requirements 3.1. Hardware For effective project completion this project will require the following hardware materials Super computer that will act as a database server Personal computer that will act as client computer Server rack to store the server 3.2. Software Operating system preferably Linux for the server and windows for client computers Database management system (SQL) Word processing software preferably Microsoft word (2007) Web programming languages (Html, PHP, Java script) and structured query language Antivirus software for security of database records preferably kaspersky 2012 3.3. Quality measurements Standards Since this is a vital project quality measurement, we recommend the standards below. ISO-9000-9001: The main basis for recommending these standards is because they operate globally and are used for quality measurements. It is also applicable to a wider range of products ranging from industrial to organizational. These particular standards are applied in areas that develop and maintain products the body might certify that the quality of an organization conforms to the standard. These standards will also ensure effective quality measurement through its 8 principles. 1. Customer focus- it requires adequate understanding of the needs of the clients at the moment and in future. 2. Leadership-since these calls for unity of purpose and the way an organization leads to. The project ought to establish and regulate and internal setting where people can participate entirely in achieving the warehouses objectives. 3. Client’s involvement- the clients should be involved at all stages of the solution design thus ensuring that a mutual product is produced. 4. Process approach- to obtain a good product, inter related resources and activities shall be treated and managed as one process. 5. System draw near to management- locating and governing related system process will lead to the warehouses management system efficiency and effectiveness 6. Consistent improvement- persistent improvement during the solution design stage shall lead to a better version quality of the final product 7. Sober approach to making of decisions- within the development team effective decision making shall go along way towards producing a quality measure. The above principles shall be used to test whether the final product met the required quality. 4.0. Team’s activity plan References And06: , (Stellman & Greene 2006), Wal98: , (Royce 1998), Read More