Internet-speed development: Difference between revisions

Content deleted Content added
Undid revision 466672272 by 117.212.79.8 (talk) Undid vandalism or something...
m WP:CHECKWIKI error fix #36. Convert HTML to wikicode. Do general fixes and cleanup if needed using AWB (8512)
Line 96:
 
(MSF Process model )<ref name="ReferenceA"/>
 
</TD>
Line 195:
</TD>
<TD WIDTH=329>
<P STYLE="margin-bottom: 0&nbsp;cm"><FONT COLOR="#000000">“<SPAN LANG="en-US"><FONT SIZE=2><FONT FACE="Arial, sans-serif">''Vision''is an unbounded view of what a solution may be.“<I/FONT></FONT></FONT></SPAN>Vision
</I>is an unbounded view of what a solution may be.“</FONT></FONT></FONT></SPAN>
 
Line 212 ⟶ 211:
</TD>
<TD WIDTH=329>
<P STYLE="margin-bottom: 0&nbsp;cm"><FONT COLOR="#000000">“<SPAN LANG="en-US"><FONT SIZE=2><FONT FACE="Arial, sans-serif">''Scope'' identifies the part(s) of the vision can be<I/FONT></FONT></FONT></SPAN>Scope
</I>identifies the part(s) of the vision can be</FONT></FONT></FONT></SPAN>
 
<P STYLE="margin-bottom: 0&nbsp;cm">accomplished within the project
Line 414 ⟶ 412:
</TD>
<TD WIDTH=342>
<P STYLE="margin-bottom: 0&nbsp;cm"><FONT COLOR="#000000">“<SPAN LANG="en-US"><FONT SIZE=2><FONT FACE="Arial, sans-serif">As the team moves on to design the solution and create the functional specifications, it is important to maintain ''traceability'' between requirements and features. Traceability does not have to be on a one to one basis. Maintaining traceability serves as one way to check the correctness of design and to verify that the design meets the goals and requirements of the solution.”</FONT></FONT></FONT></SPAN>
the team moves on to design the solution and create the functional
specifications, it is important to maintain <I>traceability
</I>between requirements and features. Traceability does not have
to be on a one to one basis. Maintaining traceability serves as
one way to check the correctness of design and to verify that the
design meets the goals and requirements of the solution.”</FONT></FONT></FONT></SPAN>
 
Line 1,681 ⟶ 1,673:
* Database and database management tools (examples: MS SQL Server, [[MySQL]], Oracle, [[PostgreSQL]]) For making knowledge bases.
* Automated testing tools (examples: Test scripts) For executing tests after each daily build.
 
==Notes==
<references/>
 
==See also==
Line 1,691 ⟶ 1,680:
* [[DSDM]]
* [[MoSCoW Method]]
 
==Notes==
<references/>
 
==References==