Skip to main content
College of Engineering
Capstone

Requirements Analysis Executive Summary

Requirements Analysis Executive Summary

Project Title: [Your Project Title]
Team Number: [Your Team Number]
Date: [Submission Date]

1. Project Overview

  • Project context/background
  • An explanation of what your project is
  • Project value proposition, including the financial/business impact of the project for the sponsor. What is the overarching goal for the sponsor?

2. Sponsor/Market Requirements

Summarize the critical requirements your project must meet. This is not a copy and paste of the requirements documents but rather an explanation and discussion of why these requirements are the ones you need to ensure the project meets the sponsor’s needs.

Specific artifacts (that may contain both functional and non-functional requirements as well as measurable values, user stories, etc.) should be referenced by name in this section to support the summaries.

Artifacts should be attached in the order in which they are referenced.

3. Key Success Measures (KSM)

The top-level functional requirements determined in coordination with the sponsor and appropriate to your specific project.

  • KSMs can be related to performance, security, and/or cost. Some examples of engineering KSMs include:
  • Product metrics - These metrics measure attributes of a product, such as its size, features, design, quality, and reliability.
  • Process metrics - These metrics analyze the procedures, tools, methods, and deployment cycles of software engineering.
  • People effort - These metrics include the total number of people contributing to the project in each iteration, and users contributing to the project over a relevant timespan.
  • Business impact - These metrics include project ROI (return on investment), time-to-market, feature adoption rate, project status alignment, etc.

The KSMs for your project might include items from one or two of these categories, or they might include metrics from all of the categories. The team must determine the KSMs specific to your project and in consultation with your sponsor, who must approve your KSMs.

WE RECOMMEND HAVING YOUR SPONSOR APPROVE YOUR REQUIREMENTS IN WRITING (EMAIL CONFIRMATION) TO ENSURE THAT THERE HAVE NOT BEEN ANY MISUNDERSTANDINGS. INCLUDING THAT AS AN ARTIFACT WOULD MAKE SENSE.

Your team should determine the best format for presenting your KSMs. It could be in paragraph form, a table, a wireframe, or some other form appropriate to your project.

4. Project Plan

  • Plan for how the project will be managed (roles & responsibilities, pm systems, assignment and report back structure, team meeting plan, etc.
  • How/when sponsor communications will happen
  • Summary of sponsor expectations for desired project documentation and delivery with reference to the specific artifact that addresses this
  • Schedule for specific team activities between now and the next design review