 |
||
|
Advanced Search |
||
|
|||||
|
Design Analysis < Verification & Validation < Results Home
|
|
Click here to complete a short survey. The results of this survey will be used to help us improve the research program and this website.
Click here to view research projects that had new research results added in the last 90 days.
|
| Transitioning from Software Requirements Models to Design Models | |
| Point of Contact |
Jon Whittle jonathw@email.arc.nasa.gov |
| Dates | October 2002 - November 2005 |
| Problem | Many large NASA software projects give software modeling top priority and use state of the art modeling languages, such as UML, to capture requirements and designs. However, current tools offer no support for maintaining the consistency of software model s across the software lifecycle. This leads to discontinuities that make it difficult to trace the linkages between requirements and implementation and can also lead to design and coding errors. |
| Objective | Often, the artifacts or models produced during one phase of the development process get thrown away or remain as mere (and sometimes obsolete) documentation when the transition to the next development phase happens. Methodologies and tools for building m odels in one phase constructively from those in the previous phase will lead to increased traceability and fewer design and coding errors. This will be accomplished by developing refinement patters for UML sequence diagrams. |
| Results | No results are available at this time. Please check back again. |
| Keywords | UML, software models, software lifecycle |
| Categories |
Design Analysis Domain-Specific Analysis Requirements Analysis |
|
| |
|
Curator: Josh Stonestreet NASA Official: Lisa Montgomery |
|
NASA Privacy, Security, Notices |