Example Requirements Document - Converged Altitude Calculation Program (CACP) - Updated July 12, 2025

Sep 12, 2026

Upload by Aladdin

This example requirements document outlines a converged altitude calculation program (CACP) designed to help users determine a rocket’s height using multiple tracking stations rather than a single station. The document explains the motivation and problem with inconsistent readings caused by wind and non-vertical flight at apogee. It defines the intended Android app experience: entering measurements from several stations, calculating in moments, reviewing prior history, and correcting errors before subsequent launches to produce more accurate altitudes and faster results.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages11

Reading Time4 min

AccessFree to download

Overview

CACP Application Overview

Why program CACP?

If I don’t build CACP, what will happen?

Who will benefit from this App?

Previous Process

Process with CACP

Functional Project Requirements

Example Requirements Document for Converged Altitude Calculation Program (CACP) Prepared by: Your Name Here Updated: July 12, 2025 Overview: This document provides an example requirements document for Kansas 4-Hersin the Computer Science division. It is based on plans for a converged altitude calculation program (CACP) that allows users to calculate the height of their rockets when using multiple tracking stations. This provides users with a more accurate altitude for their rocket than using a single tracking station. Note: Material in brackets [] and italicized is to provide information about the section and is not typically included in a requirements document. Note: This is one example of a requirements document, other requirements document formats are ﬁne and can be used. Note: This is a moderately complex requirements document. No matter how simple or complex, requirements documents should have a requirements section. They can be simpler or much more complex than this one. The goal is to share with anyone reading it, why your project matters, why you want to create it, and what needs to be done to create it. A good requirements document will allow a developer (you) to look at it and check oƯthings as you go. It also makes sure you don’t forget something important, whether it’s a reason forgetting a cellphone or to make sure a button turns green when data is entered. Overview When someone launches a rocket, they want to know how high it went. This can be determined by using an altimeter placed in the rocket or with tracking stations placed at various distances from the rocket. The tracking stations are what interests me. A single tracking station is okay, but if the wind blows the rocket so it doesn’t ﬂy straight up, or the tracker is on a hill the altitude may not be correct. To ﬁx this, I want to use multiple tracking stations which will provide a more accurate altitude when I launch my rocket or anyone else who uses it. As you can see in the diagram above each of the tracking stations have diƯerent results because the rocket wasn’t straight up and down at apogee. Which of the readings is correct 333 feet, 218 feet, or 270 feet? There is more than 100 feet of diƯerence between the tracking stations. With multiple tracking stations ﬁguring this out can be done manually with pencil and paper and some really hard math, but I want to make it easier and faster by turning it into an application I can use on my dad’s cell phone and maybe later share it with my friends. My objective is to build an Android app that will tell me how high my rocket went accurately using measurements from multiple tracking stations. 2 | P a g e E x a m p l e R e q u i r e m e n t s D o c u m e n t CACP Application Overview [This section provides information about who the document is for, why, and how it will be used. The ‘big picture.’] CACP will be an application where you can enter tracking data from multiple tracking stations to determine how high a rocket went. The app will be able to run on my dad’s Android cell phone. The app will consist of a few screens that allow the user to input calculations, see the results, and view the previous history of calculations. [􀃅 This is your objective statement in a single paragraph.] My app provides the following beneﬁts: 􀁸 More accurate altitudes at rocket launches 􀁸 Faster results than doing it on paper 􀁸 Better results than just using a single tracking station 􀁸 Helps younger kids ﬁgure out how high their rockets went 􀁸 Easy to use, because it’s on a cell phone Why program CACP? 􀁸 I’ve never built an Android app before 􀁸 I need a project for the fair 􀁸 I don’t like having to do math to ﬁnd out how high my rocket went 􀁸 No one likes doing math 􀁸 Be a reason for me to get my own cell phone If I don’t build CACP, what will happen? 􀁸 I’ll have to do hard math over and over again to ﬁgure out how high my rocket went 􀁸 I might not have accurate alti

FAQs

What problem does CACP solve compared with using a single tracking station?

CACP addresses inaccurate altitude readings that occur when the rocket is not perfectly vertical or when tracking is affected by conditions like wind or terrain. Multiple tracking stations provide more accurate altitude results.

What is the main objective of the CACP project?

Build an Android app that calculates a rocket’s altitude accurately using measurements from multiple tracking stations.

How does the process with CACP differ from the previous manual process?

Previously, users wrote station measurements down and then performed calculations manually, which could be slow and lead to mixed-up inputs. With CACP, users enter measurements into the app and press calculate for faster results, with an option to correct measurement errors before the next launch.

Sep 12, 2026

Upload by Aladdin