Objective: This assignment will require you to demonstrate your understanding of collecting, outlining and evaluating project requirements in the Software Development Lifecycle (SDLC).

Objective: This assignment will require you to demonstrate your understanding of collecting, outlining and evaluating project requirements in the Software Development Lifecycle (SDLC).

 

Using practical applications and analysis, you will begin to develop a planning document for your capstone project. Depending on where you are at in the development of your capstone project, these tasks may be retrospective (thinking back on past actions), in progress or prospective. The key is that you demonstrate your understanding of the component in a best-case scenario.

 

Each assignment component outlined below represents a key component of your planning documentation, which will lay the foundation for an effective and successful SDLC.

 

Assignment Components:

 

 

Section 1: Project Description and Stakeholder Identification

 

Using your capstone project as the scenario for this assignment, provide a brief description of the project (e.g., an online shopping platform, a student management system).

Identify and list potential and/or known stakeholders for this project. Please include a minimum of 5, with at least one internal and one external example.

Explain the importance of each stakeholders involvement in the lifecycle of the project.

Outline your planned method(s) for stakeholder communication and why you have chosen this method

Brainstorm 1-2 questions per stakeholder that you would ask to initiate the planning process & indicate how they will support the success of your project management plan

Section 2: Project Scope

 

Build the project scope including (but not limited to) the following:

 

Project deliverables

Definition of the boundaries of the project.

Inclusions and exclusions.

Constraints and assumptions.

 

Associated Learning Outcomes:

 

1.1 Explain a project charter and the ramifications of a stakeholder communications plan.

 

1.2 Critique project charter for a proposed system.

 

1.3 Identify the most suitable methods of gathering system requirements.

 

1.4 Evaluate a plan for gathering system requirements.

 

 

Submission Guidelines:

 

Submit all assignment components in one PDF document, professionally formatted with clear headings and annotations for each component.

Formatting and style of the final product is the student’s choice. It should be clean, professional and make sense for the project.

No min/max word count or page length of the final product. These numbers will vary between each unique project. Instead, ensure that the critical information is communicated clearly and concisely in the final product.