ICO Nyanya

Project Charter

< New Software Development >

Joseph Moore

1 November 2015

Project Charter

< New Software Development >

Project Manager: Joseph Moore

Anticipated Start Date: November 1 2015

Anticipated End Date: October 16, 2016

Project Summary

This project is primarily designed to promote the significance of new software development to the companies. The purchasing business should possess’ long-term management preparation used for choosing, approving and upgrading software programs such as commercial off-the-shelf (COTS) and other software products which are reusable. If a mixture of these constituents is increased in the new systems, the demand continues to grow. The new software management plan and COTS usually help to facilitate the purchasing of new programs management of COTS and some of the reusable software. The project addresses how new COTS and reusable software will provide the strategy that outline data management about monitoring interdependency of software, tracking, choosing specific features and documenting those choices. The reusable software and COTS presented in this project functions as a guide for how to accomplish new software components and COTS in a complex system (Anderso, Smith and Ward, 2007). The purpose of this project is help in identifying the techniques and collaborative processes in handling the new software components, and to address the risks and other issues. Some of the actions that must be taken to address the risk and issues include identification of the components that can be shared across the software system and encourage their use (Anderso, Smith and Ward, 2007).

Project Scope

This project seeks to justify the new development on the application of COTS solution. It also provides introductory information about COTS and new software programs and describes its relationship to other program plans (Anderso, Smith and Ward, 2007). The anticipated deliveries include: to eliminate the baseless production of similar but different software components which are reusable across the organization and support the quantity discounts if possible. Secondly is to describe strategies for the program and approaches to managing and developing software components and COTS, which provide an origin for supporting roles and possesses (Anderso, Smith and Ward, 2007). Thirdly is to provide a summary of roles of the program that are affected by development plan and includes an overview of the operation that supports the software plan strategies. Additionally, to ensure software development plan is implemented by describing the programs processes. Finally, to describe the activities that exceeds the development of the systems and employs reusable software components. However, the project is not going to cover how the system will be maintained and the procedure of installation, therefore it is upon the company to recruit experts.

Project Assumptions

The initial conditions of the project include the schedule for working hours occurs between9:00am-4:00 pm. At least six staffs will be working at 20% dedicated time. Failover setups are based on the timeframe of 5:30 am to 6:30 pm. The availability of staff vendor and partner needed. The final conditions are the staff who will be dedicated will remain in their current roles. The choice of the research will not be modified. The staffs who are dedicated will cross-train one another. New hardware is functional. The testing of the database will utilize mercury load runner and will require a professional team. Finally, there is availability of facilities staffs and ESD Networking

Summary milestone schedule

November 1, 2015 – Project Plan Complete and Approved

December 31, 2015 –Design Completed

February 31, 2016 – Coding Completed

April 30, 2016 – Testing Completed

June 31, 2016 – Beta Testing Completed

July 30, 2016 – Execution Completed

Oct 15, 2016 - One Performance Cycle Complete and Project Completion

Project Budget

Expenses	Total cost (p.m.)$
Staffs	2000
Consultancy	2490
Guest speakers	1432
lodging	500
Train	1000
Per Diem	436
Material	234
catering	655
Total	8747

References

Anderso, W., Smith, D., & Ward, M. C. (2007, October). COTS and Reusable SoftwareManagement Planning: A Template forLife-Cycle Management. Retrieved October 2015, from software engineering institute: https://resources.sei.cmu.edu/asset_files/TechnicalReport/2007_005_001_14882.pdf

http://www.projectmanagementwatch.co.uk/wp-content/uploads/2015/03/project-budget-template-excel.jpg

Kerzner, H. R. (2013). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.

�I’m having a hard time determining what this project is supposed to so, exactly. In plain English, what are the deliverables? What are the users expecting to receive?

�Is this software replacing existing software? If so, are their boundaries with other systems that need to be preserved or altered?