Project Planning is an important part of the Software Development Life Cycle (SDLC). Some of the planning phase activities include defining the problem, creating the project schedule, confirming project feasibility, and staffing the project.

For your group project, please complete the following planning activities:

1. Prepare a Systems Proposal that includes:

   1. Executive Summary

   2. Problem Statement

   3. Business Justification

   4. Scope

   5. Functional and Nonfunctional requirements

   6. Expected Value

   7. Constraints

2. Create a project schedule that includes a list of all the major project activities, allocation of activities to team members, and a planned timeline.

3. Meeting Minutes: All project meetings and other related events associated with this project to date (date, time, team members present, topics discussed, and action items. These meeting minutes will grow over time and will be part of your final submission.

4. Use Case Diagram & Description: Create a Use Case Diagram, as well as use case descriptions for your project as covered in class. Both the diagram as well as the descriptions should be sufficiently complex to cover the project.

Note:

• Refer to the guidelines, sample term project, and recommended format for the systems proposal for examples of any of the items above.

• The following pages describe the recommended format and guidelines.

Systems Proposal

A high level description of the proposed system which highlights the business need, scope, and value. The systems proposal should include the following sections:

• Project Name: The name of the project

• Background and Justification: Briefly discuss the business need for the system. This may include

  symptoms of the problem or imposed benefits of a new system.

• Functionality (objectives): A concise description of the major functions to be included in the

  system. This is not a functional requirements document, but a high level outline discussion of

  some of the major features.

• Project Scope: A brief description explaining what is in scope and what is out of scope. Similar to a

  project scope statement.

• Functional and Non-functional requirements: Detailed list and description of requirements.

• Expected Value: A short discussion of the expected value or the project outcomes that will be

  realized by the proposed system.

• Constraints: What potential issues have you identified. What may get in the way of the project.

  What limitations may exist.

  Project Schedule

  The project schedule should be in the form of a work break down structure (WBS). A WBS is a division of a project into tasks and subtasks. The tasks are numbered to indicate their relationship to each other. WBSs are critical for project planning particularly when estimating time and resource requirements. The WBS should include the assigned resource names and estimated completion date. Major project activities should include the following planning, analysis, design, and implementation activities:

Analysis:

• Functional Requirements

• Class Diagram

• Process Model: Use Case Diagrams and

Design:

Interface Design Software Design Controls Test Cases

Descriptions Object Behavior Model: A Sequence

Diagram for the major Use Cases

Implementation

Although you will not be implementing your system, please include the necessary implementation activities in your overall project schedule. These activities may not be assigned to anyone and may not have a due date, but should be listed in the document for planning purposes.

please help me this partUse Case Diagram & Description: Create a Use Case Diagram, as well as use case descriptions for your project as covered in class. Both the diagram as well as the descriptions should be sufficiently complex to cover the project.