PgmReport - Software Development Report Replacing Pre–...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Software Development Report Replacing Pre– and Post–lab Exercises 1. Problem Summary. This is a short paragraph that briefly describes the problem that your software solves. This provides the context and scope for the reader. 2. Specifications. This is a list of things that any solution to the problem is required to do. This section answers the question “What?”, not “How?”. Include a list of required inputs and outputs, along with their types and ranges. If files are involved, describe the required or produced field formats. 3. System Design and Detailed Design. This is where “How?” is answered. Initially, this is your first design for the system. This section might go through a number of iterations. it might also change as the code is debugged. The final design must correspond with the developed code and should aid the reader in understanding and maintaining the code if necessary. This section should provide a roadmap for the software. The format of this section should use pseudocode to describe a general algorithm (break–down of your...
View Full Document

This note was uploaded on 02/02/2010 for the course COMPUTER math2170 taught by Professor Vc during the Spring '10 term at University of Illinois at Urbana–Champaign.

Page1 / 2

PgmReport - Software Development Report Replacing Pre–...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online