Internet-speed development: Difference between revisions

Content deleted Content added
m Development phase: convert html to wikicode
m WP:CHECKWIKI error fix for #40. Convert depreciated font tag. Do general fixes and cleanup if needed - using AWB (8855)
Line 171:
</TD>
<TD WIDTH=342>
<P STYLE="margin-bottom: 0&nbsp;cm"><span style="color:black;">“<SPAN LANG="en-US"><span style="font-size:100%;"><FONT FACE="Arial, sans-serif">Early
in the planning phase, the team analyzes and documents
requirements in a list or tool. Requirements fall into four broad
categories: business requirements, user requirements, operational
requirements, and system requirements (those of the solution
itself).”</span></span></span></SPAN>
 
 
(MSF Process model )<ref name="ReferenceA"/>
 
</TD>
Line 195:
</TD>
<TD WIDTH=342>
<P STYLE="margin-bottom: 0&nbsp;cm"><span style="color:black;">“<SPAN LANG="en-US"><span style="font-size:100%;"><FONT FACE="Arial, sans-serif">As“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.”</span></span></span></SPAN>
 
 
(MSF Process model <ref name="ReferenceA"/>
 
Line 214 ⟶ 213:
</TD>
<TD WIDTH=342>
<P STYLE="margin-bottom: 0&nbsp;cm"><span style="color:black;">“<SPAN LANG="en-US"><span style="font-size:100%;"><FONT FACE="Arial, sans-serif">The“The
team prepares the functional specification.”</span></span></span></SPAN>
 
Line 338 ⟶ 337:
</TD>
<TD WIDTH=342>
<P STYLE="margin-bottom: 0&nbsp;cm"><span style="color:black;">“<SPAN LANG="en-US"><span style="font-size:100%;"><FONT FACE="Arial, sans-serif">This“This
begins with a systematic analysis of ''user profiles''</span></span></span></SPAN>
 
<P STYLE="margin-bottom: 0&nbsp;cm"><SPAN LANG="en-US"><span style="font-size:100%;"><FONT FACE="Arial, sans-serif"><span style="color:black;">(also
called “personas”) which describe various types of
users and their job functions (operations staff are users too).
Line 351 ⟶ 350:
into a specific sequence of tasks, known as ''use cases'',
which the user performs to complete that activity. This is called
“story-boarding.””</span></span></span></SPAN>
 
Line 443 ⟶ 442:
</TD>
<TD WIDTH=356>
<P STYLE="margin-bottom: 0&nbsp;cm"><span style="color:black;">“<SPAN LANG="en-US"><FONT SIZE=2 STYLE="font-size: 10pt"><FONT FACE="Arial, sans-serif">Documentation
of requirements in a list or tool.”</span></span></span></SPAN>
 
 
Line 460 ⟶ 458:
</TD>
<TD WIDTH=356>
<P STYLE="margin-bottom: 0&nbsp;cm"><span style="color:black;">“<SPAN LANG="en-US"><FONT SIZE=2 STYLE="font-size: 10pt"><FONT FACE="Arial, sans-serif">Document
on how the team plans to implement the risk management process
within the context of the project.”</span></span></span></SPAN>
 
Line 478 ⟶ 476:
</TD>
<TD WIDTH=356>
<P STYLE="margin-bottom: 0&nbsp;cm"><span style="color:black;">“<SPAN LANG="en-US"><FONT SIZE=2 STYLE="font-size: 10pt"><FONT FACE="Arial, sans-serif">All
plans are synchronized and presented together as the master
project plan.”</span></span></span></SPAN>
 
Line 496 ⟶ 494:
</TD>
<TD WIDTH=356>
<P STYLE="margin-bottom: 0&nbsp;cm"><span style="color:black;">“<SPAN LANG="en-US"><FONT SIZE=2 STYLE="font-size: 10pt"><FONT FACE="Arial, sans-serif">A
plan or plans for the deliverables that pertain to the role and
participates in team planning sessions.”</span></span></span></SPAN>
 
 
Line 528 ⟶ 525:
</TD>
<TD WIDTH=356>
<P STYLE="margin-bottom: 0&nbsp;cm"><span style="color:black;">“<SPAN LANG="en-US"><FONT SIZE=2 STYLE="font-size: 10pt"><FONT FACE="Arial, sans-serif">Time
estimates and schedules for Deliverables.”</span></span></span></SPAN>
 
 
Line 545 ⟶ 541:
</TD>
<TD WIDTH=356>
<P STYLE="margin-bottom: 0&nbsp;cm"><span style="color:black;">“<SPAN LANG="en-US"><FONT SIZE=2 STYLE="font-size: 10pt"><FONT FACE="Arial, sans-serif">The
various schedules are then synchronized and integrated into a
master project schedule.”</span></span></span></SPAN>
 
Line 563 ⟶ 559:
</TD>
<TD WIDTH=356>
<P STYLE="margin-bottom: 0&nbsp;cm"><span style="color:black;">“<SPAN LANG="en-US"><FONT SIZE=2 STYLE="font-size: 10pt"><FONT FACE="Arial, sans-serif">The
functional specification describes in detail how each feature is
to look and behave. It also describes the architecture and the
design for all the features.”</span></span></span></SPAN>