Temperature Conversion Application

a Worked Example

This process has been tailored to fit the needs of this simple application and the limited resources used to produce the new product. Development of substantial projects will take a lot more resources. The processes that are necessary to ensure a quality product will be incorporated into the software engineering process. Where large diverse groups are used to develop software, an overarching process capture method is necessary to ensure repeatability.

For the sake of this example, the rudimentary process events are listed along with the a narrative of methods used to satisfy the requirements of the system development. This example provides a template for using various tools in the software engineering process.

Phase I Requirements

There are several types of requirements that can be gathered during this phase. The table below contains a sample of the type of requirements that can be collected. Beside each type of requirement, an indication as to whether they are included in this example is indicated.

During this phase, developing problem statements that describe specific problems that the requirements are satisfying, augment the requirements while the subject mater experts are available and engaged in the process of defining the system is highly encouraged. When they will be reviewed and analyzed during the analysis phase

The tool that was used during this example was an evaluation copy of the RMTRAK program. It is a low cost document driven tool that captures requirements into an authoritative database. Keeps track of changes and provides many reporting tools to develop other products for inclusion in other phases of the project.