Software Project Plan For the Try n Save Incorporated ERP System

Chelsea Raymond August 21 2011

1

Table of Contents
1.0 Overview 1.1 Project Summary 1.1.1 Purpose, Scope and Objectives 1.1.2 Assumptions and Dependencies 1.1.3 Project Deliverables References Definitions Project Organization 4.1 External Interfaces 4.2 Internal Structure 4.3 Roles and Responsibilities Managerial Process Plans 5.1 Work Plan 5.1.1 Work Activities 5.1.2 Schedule Allocation 5.1.3 Resource Allocation Technical Process Plan 6.2 Methods, Tools, and Techniques

3 3 3 3 3 4 4 4 5 5 5 5

2.0 3.0 4.0

5.0

6.0

1.
1.1

Overview
Project Summary
1.1.1 Purpose, Scope and Objectives
The purpose of the Software Project Plan is to identify the scope of the project, establish a schedule for the implementation of the project and to estimate the amount of work involved. According to the problem statement, the scope of our project, the ERP system for Try 'n Save Incorporated includes improving their inventory system to have to ability to automatically send store orders, restock orders and transfer orders to efficiently manage the inventory system. The project will involve around 375,000 lines of code and will also have the ability to generate management reports for headquarters as will as data-mining features.

1.1.2 Assumptions and Constraints

It is assumed that the design team will meet all requirements. It is also assumed that this product will be purchased by TSI. The design team is constrained by a schedule, resources and capital as well as specified requirements.

1.1.3 Project Deliverables

Upon project completion, Try 'n Save Inc will be provided with a complete system for inventory management, as well as the ability to automatically restock all inventory. Management of TSI will receive an administrative interface complete with corporate wide views of all stores and warehouses and data-mining capabilities.

2.

References
IEEE Std. 1058 - 1998 IEEE Standards for Software Project Management Plans CMIS 330 Problem Statement Try 'n Save Incorporated

3.

Definitions
TSI: Try n Save Incorporated ERP: enterprise resource planning POS: point of sale 3

SO: store order TO: Transfer order RO: Resupply order LOC: lines of code

4.
4.1

Project Organization
External Interface

As a consulting and contracting software company, our external interface is one between company and client. The project is led and maintained by a project manager who communicates with the client to establish and verify all requirements.

4.2

Internal Structure

The internal structure of our company is an integrated team made up of a project manager, software engineers and a number of other positions dedicated to make sure the product produced is of the highest quality.

4.3

Roles and Responsibilities

Project Manager: The main role of the Project Manager is to make sure that the software development process is working as intended. He/she is in charge of making sure all project requirements are fulfilled Software Engineers: The main role of the software engineers is to design, implement and modify the software program. The software engineers must make sure the program is affordable, high quality, and durable. They must meet all project requirements. Testers/QA: The role of the testers is to make sure, once completed, the program runs as it should and fulfills all requirements. The testers must make sure all inputs return the correct outputs and there are no errors. CM: The role of CM, or Configuration Management is to track and control all changes made to the software. V&V: The role of V&V, or Verification and Validation is to make sure the finished project fulfills all requirements and meets its intended purpose. This process is high-level checking. Client: The role of the client is to specify exactly what they are looking for in a software program and to make realistic requests and specifications. They must also take care of all financial matters in a timely manner.

5.
5.1

Managerial Process Plans

Work Plan
5.1.1 Schedule Allocation

5.1.2 Resource Allocation

The project will be implemented using state-of-the-art CASE tools and will include about 325,000 lines of code. Half of the lines will use off the shelf software products and the other half will be custom. All lines must still be analyzed, designed and tested. The program will be written in Java and all database actions written in SQL. The project will cost about $400,000

6.

Technical Process Plans

5

6.1

Methods, Tools, and Techniques

o Team member desktop foundation o Microsoft Windows 2000 desktop operating system o Microsoft Office 2003 productivity application suite o Adobe Acrobat 6.0 [creating/viewing PDF files] o Project management o Microsoft Project 2003 [WBS, schedule/cost estimates, resource planning, project control] o Microsoft Word 2003 [document preparation and revision] o Quality o Requirements o IBM Rational RequisitePro [requirements tracking] o Design o IBM Rational Rose Data Modeler o IBM Rational Rose Technical Developer o Implementation o Microsoft Visual C++ [programming language, development tools and object code generation] o Windows Software Development Kit (SDK) [programming support] o Testing o IBM Rational Robot [automated functional and regression testing] o Training o Microsoft PowerPoint 2003 [training presentations] o Online Performance Reporting o Microsoft Windows 2000 Server Standard [server operating system]

Problem Statement:
Try 'n Save Incorporated (TSI) The Try 'n Save Inc. is a discount pet food store that caters to bargain-hunting pet owners. The management of Try 'n Save wishes to implement an enterprise resource planning (ERP) system that links the local stores, regional warehouses, participating suppliers, and headquarters. Management requires that each sale at a store's cash registers (i.e., the pointof-sale (POS) transaction) be tracked by the store's inventory system and the inventory system at the store's regional warehouse. The regional warehouses will exchange inventory and sales data with each other, with their suppliers, and with headquarters. Some suppliers will service all warehouses, while others will service only one regional warehouse. The ERP system component at the local Try 'n Save store will automatically determine when to submit a store order (SO) to the regional warehouse to replenish the store's inventory for the product in question. The regional warehouse automatically will determine when to submit a Resupply Order (RO) to the supplier, versus handling the SO with onhand supply. Regional warehouses alternatively may submit a Transfer Order (TO) to a peer regional warehouse if a peer regional warehouse has more than a 90-day supply of the item(s) requested by the SO. In addition to processing the order, the recipient will acknowledge all types of orders. The response time between an order and its acknowledgement will be one (1) minute or less 90 percent of the time. The suppliers of Try 'n Save will be encouraged to automatically process Try 'n Save's ERP system ROs. During the period suppliers transition to fully automated links, the ERP system will tolerate a mix of automated and non-automated links to suppliers. Assume that the link to the non-automated suppliers will be by means of faxed transmission of ROs over commercial telephone lines. There will be no acknowledgement of faxed ROs. The headquarters component of the ERP system will maintain a corporate-wide view of sales and inventory levels. Monthly and quarterly management reports will be generated that will summarize the following for the respective time period: sales by store sales by region total sales inventory by store inventory by region and total inventory

Ad hoc report capability will also be supported by the ERP system. In addition, the headquarters ERP system component will provide "data-mining" features to determine trends in the corporate-wide data by region, by time-of-year, by holiday, and by other pet demographic parameters to be defined by management. Assume you are the lead software engineer and project manager for a software development contractor that builds custom computing systems for public and private organizations. You run an expert shop utilizing state-of-the-art CASE tools and are selfrated #4 on Software Engineering Institute's (SEI's) Capability Maturity Model (CMM). A 7

recently completed project similar to this one involved 325,000 lines of code (LOC) written in a 3rd generation programming language. Approximately 175,000 LOC of the total 325,000 LOC consisted of commercial-off-the-shelf (COTS) software products that did not have to be coded but still required analysis, design, and testing. State all assumptions when estimating size, effort, staffing, and project duration for the Try 'n Save ERP system. You will be graded on your rationale, documentation of assumptions, technical thoroughness, and fulfillment of the conference topic's minimum requirements for each document, rather than exact right or wrong answers.