Requirements Concepts

<body topmargin=0 leftmargin=0 marginheight=0 marginwidth=0> <table cellpadding=0 cellspacing=0 border=0><tr> <td valign="top" rowspan="3" width=170 BGCOLOR="#000099" TEXT="#F7F7FF" background="02ebbc00erkqpg.jpg"> <div> <A HREF="req_hier.htm" TARGET="_top" TITLE="Requirements Hierarchy"><IMG BORDER="0" SRC="Wing0a73007700c8cccccc00.png" HEIGHT="13" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Requirements Hierarchy</A></div> <div> <A HREF="test_req.htm" TARGET="_top" TITLE="Testable Requirements"><IMG BORDER="0" SRC="Wing0a73007700c8cccccc00.png" HEIGHT="13" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Testable Requirements</A></div> <div> ------------------------------</div> <div> <A HREF="soft_size_meas.htm" TARGET="_top" TITLE="Software Sizing Measures"><IMG BORDER="0" SRC="Symb075c00b700c8cccccc00.png" HEIGHT="13" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Software Sizing Measures</A></div> <div> <B><IMG BORDER="0" SRC="Symb075c00b700c8cccccc00.png" HEIGHT="13" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Requirements Concepts</B></div> <div> <A HREF="tr_as_size_meas.htm" TARGET="_top" TITLE="Testable Requirements as a Sizing Measur"><IMG BORDER="0" SRC="Symb075c00b700c8cccccc00.png" HEIGHT="13" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Testable Requirements as a Sizing Measure</A></div> <div> <A HREF="tr_appl.htm" TARGET="_top" TITLE="Applications of Testable Requirements"><IMG BORDER="0" SRC="Symb075c00b700c8cccccc00.png" HEIGHT="13" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Applications of Testable Requirements</A></div> <div> <A HREF="tr_exper.htm" TARGET="_top" TITLE="Experience With Testable Requirements"><IMG BORDER="0" SRC="Symb075c00b700c8cccccc00.png" HEIGHT="13" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Experience With Testable Requirements</A></div> <div> <A HREF="ref.htm" TARGET="_top" TITLE="References"><IMG BORDER="0" SRC="Symb075c00b700c8cccccc00.png" HEIGHT="13" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">References</A></div> <div> <A HREF="glossry.htm" TARGET="_top" TITLE="Glossary"><IMG BORDER="0" SRC="Symb075c00b700c8cccccc00.png" HEIGHT="13" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Glossary</A></div> </td> <td valign="top" colspan=2 height=60 BGCOLOR="#FFFFFF" TEXT="#080000"> <div> <B>Requirements Concepts</B></div> <bR> <bR> <div> </div> </td> </tr><tr> <td valign="top" height=396 width="100%" colspan=2 BGCOLOR="#FFFFFF" TEXT="#080000"> <div> A requirement can be defined as a condition or capability that is necessary for a system to meet its objectives.  This definition is purposely broader than some definitions of a requirement.  Many software designers use the term "requirements" to mean the "user requirements."  The above definition is intended to include not only the traditional user requirements, but also other categories of requirements such as technical design and operational requirements.  The IEEE Standard Glossary of Software Engineering Terminology <FONT SIZE="1" COLOR="#000000" FACE="Arial" ><A HREF="ref_4_ieee_standards_collection_1994.htm" TARGET="_top" TITLE="References">[</A><A HREF="ref_4_ieee_standards_collection_1994.htm" TARGET="_top" TITLE="References">Ref 4</A><A HREF="ref_4_ieee_standards_collection_1994.htm" TARGET="_top" TITLE="References">]</A></FONT> includes definitions of six different types of requirements -- functional, design, implementation, interface, performance, and physical.</div> <bR> <div> It should be emphasized that there are frequently important differences between different types of requirements.  Many problems occur, for example, when developers do not properly distinguish between user requirements and technical design requirements.  For purposes of sizing, however, there is value in being able to size each type of requirement with the same measure.  The above definition of requirements thus includes all types of requirements.  </div> <bR> <div> Most methodologies analyze requirements in a top-down fashion through a <A HREF="req_hier.htm" TARGET="_top" TITLE="Requirements Hierarchy">Requirements Hierarchy</A>.  Requirements at the lowest level of the hierarchy are called <A HREF="test_req.htm" TARGET="_top" TITLE="Testable Requirements">Testable Requirements</A>.</div> </td> </tr><tr> <td valign="top" colspan=2 height=24 BGCOLOR="#FFFFFF" TEXT="#080000"> <div> <A HREF="soft_size_meas.htm" TARGET="_top" TITLE="Software Sizing Measures"><B><IMG SRC="02711110.png" border=0 width="17" height="17" ALT="prev" ALIGN="BOTTOM" HSPACE="0" VSPACE="0"></B></A><B> </B><A HREF="tr_as_size_meas.htm" TARGET="_top" TITLE="Testable Requirements as a Sizing Measur"><B><IMG SRC="02811110.png" border=0 width="17" height="17" ALT="next" ALIGN="BOTTOM" HSPACE="0" VSPACE="0"></B></A><B>     </B><A HREF="index.htm" TARGET="_top" TITLE="Sizing Software Using Testable Requireme"><B><IMG SRC="02611110.png" border=0 width="17" height="17" ALT="up" ALIGN="BOTTOM" HSPACE="0" VSPACE="0"></B></A><B> </B><A HREF="req_hier.htm" TARGET="_top" TITLE="Requirements Hierarchy"><B><IMG SRC="02c11110.png" border=0 width="17" height="17" ALT="down" ALIGN="BOTTOM" HSPACE="0" VSPACE="0"></B></A><B>          </B><B>               </B><A HREF="http://www.mosaicinc.com" TARGET="_top" TITLE="http://www.mosaicinc.com"><B>Mosaic Home</B></A></div> <bR> </td> </tr></table></body>