System Prospectus- IE

Project: {Project Name}

{Manager Name}

CSE 5325 – SP 2017 Module: Project Plan

Deliverable: Project Plan Document

Version: [1.0] Date: [mm/dd/yyyy]

1 Prepared by:

{Contributors list}

Revision History Versi Date Originat Reason for High level on or change description of numb changes er 1.0 mm/dd/yyy Name(s) Initial draft y

Approval Information Approver Name Approver Approval Date Signature

{your name}

Dr. Khalili

Mr. Rodrigo

2 TABLE OF CONTENTS

3 1. Executive Summary

{Provide a high-level overview of the project that includes the following:  Project high-level description  Project deliverables  Client information  In-scope  Out-of-scope  High-level cost and schedule }

4 2. Project Acronyms and Glossary of Terms

{A list of terms and acronyms used in this project, if any, some examples below} Customer/Client – The term “Customer” or “Client” are used interchangeably throughout this document to refer to our client Cost – Cost is in US $

5 3. Project Organization

3.1 ORGANIZATIONAL STRUCTURE {Provide a brief history of the organization and why you are qualified to handle this project. Include all relevant information such as development philosophy, e.g. conventional development or agile, if agile what type (XP or Scrum), management style (i.e. hierarchical, matrix, etc.), if the company is public (if so, provide ticker symbol under which the company trades on the stock market) or private, plus any other relevant information. i.e. this is your company, make reasonable assumptions/statements, be consistent}

3.2 ROLES AND RESPONSIBILITIES {List all team members, for each member; list their qualifications, the years working for your organization, technical skills and other relevant qualifications}

3.3 STAFFING PLAN {Specify any additional personnel that you need to complement your current staff, listed above, to conduct the project.}

3.4 COMMUNICATION PLAN {What is the primary means for communication in this project? For information passing, error reporting, etc.}

6 4. Management Process

4.1 PROJECT PHASES {Is project delivered in one phase or multiple phases? If multiple phases, what is included in each phase.}

4.2 PROJECT ASSUMPTIONS {Includes all assumptions}

4.3 PROJECT DEPENDENCIES {Includes all project dependencies}

4.4 PROJECT CONSTRAINTS {Includes all constraints}

7 5. Risk Management

5.1 PROJECT MONITORING AND CONTROL {What monitoring measures do you have in place to monitor and control all risks to the project?}

5.2 PROJECT RISKS {Identify and assess all risks associated with the project}

5.3 RISKS CONTINGENCY AND MITIGATION {For each risk identified, what is the mitigation? i.e. what do you do to remedy the risk if it happens?}

5.4 ESCALATION PROCEDURE {What is the escalation procedure to report problems and risk concerns?}

8 6. Technical Process

6.1 ARCHITECTURE PLAN {Description of the high-level architectural plan, e.g. agile vs. conventional development methodology: waterfall, incremental, etc.}

6.2 REQUIRED SOFTWARE AND DEVELOPMENT TOOLS {Required external software and CASE packages, e.g. databases, data dictionary, query generator, configuration management tools; etc.}

6.3 REQUIRED HARDWARE {The list of required hardware}

6.4 REQUIRED SECURITY TOOLS AND ALGORITHMS {Required Security and related software purchases}

6.5 TECHNOLOGY UTILIZATION {What technologies/versions are you planning to utilize, e.g. Web, Android, etc. Provide details of your approach, e.g. if web was selected, what web technologies, web development environment such as ASP, PHP, web hosting, etc. are you planning to use}

9 7. Project Success Criteria

7.1 PROJECT MILESTONES {List of Milestones from customer’s point of view}

7.2 ACCEPTANCE CRITERIA {Customer acceptance criteria for the project}

7.3 SUCCESS METRICS {List of success metrics}

7.4 CLIENT APPROVAL PROCESS {Identify management process for obtaining client approval, i.e. what takes to start the project. Also include any external approvals if required, e.g. government, etc.}

10 8. Project Schedule

{Detailed delivery schedule from start to the end when product is delivered to your customer, provide cross reference with Microsoft Project Professional 2016}

11 9. Project Cost Planning

9.1 HARDWARE COST {Hardware cost, a detailed list including price competition from different vendors, provide references}

9.2 COMMERCIAL OFF-THE-SHELF (COTS) COMPONENT COST {Cost of buying support software, a detailed list including price competition from different vendors}

9.3 COCOMO SOFTWARE COST ESTIMATION {Use COCOMO to estimate software development cost using your resources, refer to http://ranger.uta.edu/~khalili/Overview%20of%20COCOMO.htm;}

9.4 OVERHEAD COST {Consultants, Rents, utility bills, phone cost, etc., you may want to abstract some of the details from your client and just show a certain percentage, say 25%, overhead as an example}

9.5 TOTAL COST {Sum of 7.1, 7.2, 7.3 & 7.4; make sure to reflect overhead cost}

12 10. Project Procurement Plan

{THIS SECTION WILL DESCRIBE HOW HARDWARE, SOFTWARE, LICENSE, OR ANY COMPONENTS WILL BE PROCURED FOR THE PROJECT. THE ITEMS MAY BE PROCURED BY PURCHASE, LEASED, OR BORROWED}

13 11. Project Development Plan

11.1 DEVELOPMENT ENVIRONMENT {What is the Programming language and development environment….}

11.2 TASKS AND DELIVERABLES {List all high-level deliverables; Provide reference/link to Microsoft Project Professional 2010 for task details. E.g. defining requirements, designing web screens, database tables and queries, coding, creating test cases and test data}

11.3 CONFIGURATION MANAGEMENT {Where & how to store code and other project artifacts}

14 12. Project Test Strategy

12.1 UNIT TESTING {Testing strategy by developers at the module level, e.g. uses test cases, JUnit, etc.}

12.2 SYSTEM INTEGRATION TESTING {System level testing strategy}

12.3 STRESS TESTING {Test strategy for stressing the system by overloading}

12.4 PERFORMANCE TESTING {Test strategy to measure performance}

12.5 DATA VALIDATION TESTING {Validate all fields for accuracy}

12.6 USER ACCEPTANCE TESTING {Test plan by clients}

15 13. Project Deployment and Rollout Plan

13.1 DELIVERY DATE {Expected delivery date}

13.2 DELIVERY METHOD {How is it delivered to the client? What is included?}

13.3 PENALTY FOR LATE DELIVERY {What is penalty for late delivery, typically certain $ amount for each business day that is it delivered late}

16 14. Project Training Plan

14.1 USER MANUAL {Prepare user manual}

14.2 CLIENT ONSITE TRAINING {Training plans to train clients if applicable}

17 15. Project Maintenance and Support Plan

15.1 DATA MAINTENANCE {Include contractual details for maintaining data, e.g. normalizing, routing backups, securing access, etc.}

15.2 FIXING BUGS AFTER RELEASE {Include error reporting mechanism}

15.3 CHANGE OPERATING ENVIRONMENT {Include contractual details and charge structure for changing operating environments such as updating new OS, changing hardware, changing web hosting, etc.}

15.4 ADDING NEW FUNCTIONALITY {Include contractual details and charge structure for adding new functionality}

18 16. Post Project Issues

16.1 PROJECT ARTIFACT OWNERSHIP {Does client own project artifacts, e.g. requirements, source code, etc., or the client. What arrangements has been made with client about this}

16.2 QUALITY ASSURANCE {Agreements that product will meet client’s expectation after delivery. What are the criteria if it does or does not}?

16.3 FUTURE RELEASES {Contractual details for future commitments of (how long) to support this customer}

19 17. Glossary of Terms

Acceptance Test – Formal test performed by the client prior to accepting the system

Activity - A project task that requires resources and time to complete Web Hosting – ….

20 Appendices

{Additional documents, web links, and references which are not included in the sections above}