A key consideration when setting out to build and implement a system is to determine the scope and identify the activities for the project (these should map to the SDLC or another analysis and design process like Agile, DevOps, etc.). The purpose of this deliverable is to define the project as completely as possible, early in the semester so that you, your client, and I understand what you are expected to do. There is no substitute for clarifying expectations early in the life of a project. Because a thorough analysis of the organization has not been performed at this point, the project plan will not be written at a very detailed level. The main goal is to clarify the scope and the direction of the project, and to outline a project schedule that shows you have thought about how to manage the project. Your concern should be that you understand the setting and the requirements for the project (network, database, VoIP system, security policy, etc.).

The contents of the deliverable should correspond to the project initiation and planning process in the SDLC (or other) process. This deliverable must contain, but should not be limited to, the following information (put in report format, not a bulleted list):

- Table of Contents (with appropriate page numbering and formatting) - Executive Overview Include a brief description of the client, sponsor (industry partner), and potential user(s) to be served by the proposed system. An overview of the company, the problem, and potential solution should be the main focus of this document.. Make assumptions as needed but include them on an assumptions page (probably as an appendix). Make sure to put this on a separate page.

Project Scope

Problem/Opportunity Statement - A description of the specific purpose for analysis of this business function and why the organization wants the system(s). In other words, what are the problems and/or what opportunities would such a system provide.

Project Objectives - These are the goals or critical success factors of the system (what must happen for the system to be a success). They can be expressed as a series of statements that are either qualitative or quantitative but that typically do not contain details likely to change substantially over time - again, put in paragraph/report format, not solely a bulleted list.

Project Description - This is a narrative of the general functionality of the system and how it will work. It includes how it will help people to solve their problems or take advantage of new opportunities. Copies of all existing reports, forms, summaries, etc. currently used by your client should also be included.

Logical Context-Level Data Flow Diagram - An overview of the system showing the boundaries, external entities that interact with the system, and the major information flows between the entities and the system (at this point the Context Level diagram is all that is needed, you need to describe what the DFD represents.)

Project Deliverables - List the major deliverables and dates for this project. This is not a list of all tasks (as in the Gantt chart), but the major items within each deliverable and the date they are to be delivered (not the task end-date). You may use the course schedule to determine deliverable dates (baseline project, analysis & design, etc.). Project Proposal

System Justification - At this point, you will likely not be able to quantify all the costs and benefits of the system. However, you should be able to list some tangible and intangible costs and benefits that will lay the groundwork for a more precise business case in later stages of the project. Specify your consulting costs as if you were a real consultant (you may use $115/hr for programmers, $125/hr for analysts, $100/hr for network technicians and $110/hr for database designers.) The hours estimated should be how many hours you think it will take you during the semester to complete the project. Include hardware and software estimates as appropriate. List the possible risks as well for both the customer and your group. Assume a total cost for the entire project of about $200,000 (could be more or less, but make sure that you can justify later in the project).

Resource Requirements - List what you will need to complete the project. For example, you may need access to certain people, equipment, and software. You will need to specify the number and type of people from your consulting firm who need to be involved (your team members, of course, play all of these roles). This could include such things as programming languages, database package, Microsoft Project, Visio, etc.

Project Plan - Show the detailed steps you intend to follow to complete the project in order to meet the due dates for various deliverables in the form of a Gantt chart. The chart and any accompanying description should be clearly shown for each detailed project step including the following items: task name, estimated work time, start and completion dates, sequence and parallel nature of project steps, and personnel assignments for each step. The schedule might follow the systems development life cycle, but it likely will be customized and modified to suit the nature of this project. You can think of this item as a time budget for the project. The project schedule should be very detailed for the Baseline Project Plan (BPP) and Analysis phase of the project but may be less specific for later steps in the project. Conclusion

Conclusion - Design a short conclusion/summary statement that summarized the work done to date, and the main reasons for moving forward with the project.