http:^^cs.fit.edu^~ellis^cse5450.html

This data set contains WWW-pages collected from computer science departments of various universities

<!-------------------ROLES-------------------------->
<center><!WA30><img src="http://cs.fit.edu/~ellis/redwhblu.gif"></center><br>
<a name="Roles"><Center><h2>Project Roles</h2></center></a>
<center><table border>
    <th align=center>Role</th>
    <th align=center>Assigned to:</th>
    <th align=center>Job Description Summary</th>
  <tr>
    <td align=left>Task Leader</td>
    <td align=center>Parivash<br>(Pari)<br>Jamnia<br>
         [e-mail]</td>
    <td align=left>Responsible for the creation of the software
         product. Primary responsibilities include: 1) cost and
         schedule performance of the team; 2) authoring the
         requirements and specification document; 3) advising on
         overall design; and 4) supervising implementation and
         testing.</td>
  <tr>
    <td align=left>Project<br>Administrator</td>
    <td align=center>Hung Ju<br>(Henry)<br>Cho<br>
         [e-mail]</td>
    <td align=left>Responsible for resource allocation and
         tracking. Primary responsiblities are cost analysis and 
         control, computer and human resource acquisition and
         supervision. Collects data and issues bi-weekly 
         cost/manpower consumption reports and the final report.</td>
  <tr>
    <td align=left>Configuration/<br>Data Manager</td>
    <td align=center>Hsin-Chi<br>(Dillon)<br>Chen<br>
         [e-mail]</td>
    <td align=left>Responsible for change control. Primary
         responsibilities include the configuration management plan,
         tracking change requests and discrepancy reports, calling
         and conducting change control board meetings, archiving, and
         preparing product releases. Also responsible for final
         preparation of all documentation prior to delivery to 
         the "customer". Ensures documents are delivered in
         accordance with program milestones. Establishes the program
         documentation standard and ensures all documents conform.</td>
  <tr>
    <td align=left>Test and<br>Evaluation<br>Engineer</td>
    <td align=center>Yuh-Sheue<br>(Rosa)<br>Chen<br>
         [e-mail]</td>
    <td align=left>Responsible for testing and evaluating individual
         modules and subsystems and for preparing the appropriate
         test plans and test documentation.</td>
  <tr>
    <td align=left>Designer</td>
    <td align=center>Somrak<br>Bhakdisuparit<br>
         [e-mail]</td>
    <td align=left>Primary responsibility for developing aspects of
         the design as specified by the Task Leader; includes
         assessing the impact of alternative implementations
         for proposed changes.</td>
  <tr>
    <td align=left>Implementor</td>
    <td align=center>Paul<br>Bryer<br>
         [e-mail]</td>
    <td align=left>Primary responsibility is to implement the 
         individual modules of the design and serve as the technical
         specialist for the programming language and operating
         system. During the requirements specification and design
         stages, the implementor could develop tools and experiment
         with unfamiliar language features needed for the project.</td>
</table></center>
<hr>

-- Return to <!WA31><a href="#top">top</a>, or:<br>
1. <!WA32><a href="#Fact Sheet">Fact Sheet</a>; 2. <!WA33><a href="#Syllabus">
  Syllabus</a>; 3. <!WA34><a href="#Roles">Roles</a>; 4. <!WA35><a href="#PDRL">
  PDRL</a>; 5. <!WA36><a href="#Assmt 1"> Assignment #1</a>; 
  6. <!WA37><a href="#Assmt 2">Assignment #2</a>; 
  7. <!WA38><a href="#Assmt 3">Assignment #3</a>; 
  8. <!WA39><a href="#Assmt 4">Assignment #4</a>.</p>

<!-------------------PROJECT DELIVERABLES-------------------------->
<center><!WA40><img src="http://cs.fit.edu/~ellis/redwhblu.gif"></center><br>
<a name="PDRL">
<center><h2>Project Deliverable Requirements List</h2></center>
<center><table border>
    <th align=center>Item Num.</th>
    <th align=center>Document Name</th>
    <th aligh=center>Responsibility</th>
  <tr>
    <td align=center>A001</td>
    <td align=left>Software Development Plan</td>
    <td align=left>Task Leader</td>
  <tr>
    <td align=center>A002</td>
    <td align=left>Software Configuration Management Plan</td>
    <td align=left>Configuration/Data Manager</td>
  <tr>
    <td align=center>A004</td>
    <td align=left>Program Documentation Standards</td>
    <td align=left>Configuration/Data Manager</td>
  <tr>
    <td align=center>A005</td>
    <td align=left>Coding Standard / Maintenance Manual</td>
    <td align=left>Configuration/Data Manager</td>
  <tr>
    <td align=center>A006</td>
    <td align=left>Cost / Schedule Status Report (bi-weekly)</td>
    <td align=left>Project Administrator</td>
  <tr>
    <td align=center>A007</td>
    <td align=left>Software Requirements Specification</td>
    <td align=left>Task Leader</td>
  <tr>
    <td align=center>A008</td>
    <td align=left>Interface Requirements Specification</td>
    <td align=left>Task Leader</td>
  <tr>
    <td align=center>A009</td>
    <td align=left>Software Design Document</td>
    <td align=left>Designer</td>
  <tr>
    <td align=center>A010</td>
    <td align=left>Test Plan</td>
    <td align=left>Test and Evaluation Engineer</td>
  <tr>
    <td align=center>A011</td>
    <td align=left>User Manuals
    <td align=left>Task Leader</td>
  <tr>
    <td align=center>A012</td>
    <td align=left>Code</td>
    <td align=left>Implementor</td>
  <tr>
    <td align=center>A013</td>
    <td align=left>Test Report</td>
    <td align=left>Test and Evaluation Engineer</td>
</table></center>
<hr>

-- Return to <!WA41><a href="#top">top</a>, or:<br>
1. <!WA42><a href="#Fact Sheet">Fact Sheet</a>; 2. <!WA43><a href="#Syllabus">
  Syllabus</a>; 3. <!WA44><a href="#Roles">Roles</a>; 4. <!WA45><a href="#PDRL">
  PDRL</a>; 5. <!WA46><a href="#Assmt 1"> Assignment #1</a>; 
  6. <!WA47><a href="#Assmt 2">Assignment #2</a>; 
  7. <!WA48><a href="#Assmt 3">Assignment #3</a>; 
  8. <!WA49><a href="#Assmt 4">Assignment #4</a>.</p>

<!-------------------ASSIGNMENT #1-------------------------->
<center><!WA50><img src="http://cs.fit.edu/~ellis/redwhblu.gif"></center><br>
<a name="Assmt 1"><Center><h2>Assignment #1</h2></center></a>
<p><strong>NOTE:</strong> <em>Everyone MUST keep track of the 
hours spent on project activities. Turn in weekly activity report
forms to the Project Administrator.</em>
<h3>Task Leader:</h3>
<ul>
  <li> Familiarize yourself with the present design of the Low Cost
       Flight Simulator (LCFS) program. Write a report on your general
       impressions of the design and utility of this product. Include
       a description of the major deficiencies you have found.
  <li> Review the Requirements Document to ensure that it reflects the
       present configuration of the product. Identify any requirements
       that the baselined software fails to satisfy or code features
       not explicitly required.
  <li> Establish key project objectives. Specify major project activites
       (both development and support) and identify key project 
       milestones. Establish an initial project schedule.
  <li> Provide the Project Administrator with salary figures for all
       personnel.
  <li> Locate at least two references on "cleanroom software development".
       Provide a short summary of the salient features of this approach,
       including a projection of its applicability to your project.
</ul>
<h3>Project Administrator:</h3>
<ul>
  <li> Create Weekly Activity Report (WAR) forms to allow all team
       members to report their hours expended for specific individual
       tasks. Coordinate the design of this form with the Task Leader
       to ensure it captures all costs.
  <li> Working with the project schedule and salary figures developed
       by the Task Leader, assign preliminary earned values to each
       milestone. Plot the planned value of the scheduled milestones
       against time for the duration of the project (i.e., the 
       "Budgeted Cost of Work Scheduled" - BCWS line). This becones
       the baseline program plan.
  <li> Collect actual costs for the project start-up activities through
       25 Jan 96 by interviewing each of the team members. Include
       this initial cost in all project status reports.
  <li> Prepare an initial Cost-Schedule Status Report (CSSR) that
       shows the BCWS for the entire project and the initial cost
       (i.e., initial "Actual Cost of Work Performed" - ACWP).
  <li> For the duration of the project, collect the Weekly Activity
       Reports from each team member and prepare CSSRs (updating
       the ACWP and "Budgeted Cost of Work Performed" - BCWP) every
       other week. Present the bi-weekly CSSR to the team with hard
       copies to the Task Leader and the "customer".
</ul>
<h3>Configuration/Data Manager:</h3>
<ul>
  <li> Investigate and write a short report on the availability of
       Software Configuration Management (SCM) tools that run on the
       PC. Make a recommendation to the Task Leader as to whether a
       SCM tool should be used during the project. If the recommendation
       is to use a SCM tool, recommend which one.
  <li> Collect all existing project documents and establish a project
       library for the other team members. Establish a log to track
       who has copies of controlled documents. Establish procedures
       for the distribution and authorization to make changes to the
       documents.
  <li> Establish criteria for placing all new documents and code
       under configuration control.
  <li> Design the format (hard copy and/or soft copy) for discrepancy
       reports and change requests.
  <li> Write a Configuration Management Plan that defines how SCM will
       be applied to this program. Be sure the plan is complete and
       covers such topics as baseline definition, change management,
       etc.
  <li> Coordinate all SCM plans with the Task Leader. With Task Leader
       approval, report to the team how SCM will be accomplished during
       the project, including tools and their use, procedures, use of
       forms, make-up of the Software Configuration Control Board
       (SCCB), etc.
  <li> Evaluate existing program documentation for consistency of 
       format. Identify common deficiencies and those of individual
       documents. Prepare a report that documents your findings.
  <li> Generate a Documentation Standard that defines the required
       format for all program documents. Consider the effects on
       current documents.
  <li> Generate a Coding Standard / Maintenance Manual that describes
       how all program source code should be formatted to enhance
       product maintainability. Besides issues relating to readability,
       be sure to include module identification with program header
       and logic description with embedded comments, and traceability
       of implementation back to design documentation.
</ul>
<h3>Test and Evaluation Engineer:</h3>
<ul>
  <li> Locate papers on testing object-oriented programs. Determine
       the unique characteristics, if any, of testing OO programs.
       Coordinate with the Task Leader to establish the target
       platform configuration for the project product. Determine what
       testing aids are available for C++ programs on the target
       platform. Prepare a written report evaluating what you have
       learned.
  <li> Generate a Test Plan document that fully describes how software
       testing will be conducted and documented for the program.
</ul> 
<h3>Designer:</h3>
<ul>
  <li> Locate papers on software design approaches. Write a brief
       report that summarizes the differences between Object-Oriented
       Design and Structured Design.
  <li> Review any existing program design material. Compare the
       documented design against the actual code to identify any
       inconsistencies.
  <li> Structure the existing design data into a design document that
       identifies the top-level (architecture) design and detailed
       design. Update to reflect any inconsistencies you found
       between the design documentation and the implemented code.
  <li> As necessary, assist the Team Leader and Implementor in
       evaluating proposed product changes by suggesting designs
       (consistent with the current design) to implement those
       changes.
</ul>
<h3>Implementor:</h3>
<ul>
  <li> Locate and study references on the Object-Oriented Programming
       in the C++ programming language. Concentrate on the concepts
       of the classes and inheritance.
  <li> Write a short report that summarizes how OO structures are
       implemented in the C++ language, and make the report available
       to the Designer and Task Leader.
  <li> Coordinate the preparation of the Coding Standard / Maintenance
       Manual with the Configuration/Data Manager.
  <li> As necessary, assist the Task Leader and Designer in evaluating
       the implementation impact of suggested designs. Be aware of
       Commercial-Off-The-Shelf (COTS) and/or public domain/shareware
       software that is available to the team to assist in the
       implementation.
</ul>
<hr>
-- Return to <!WA51><a href="#top">top</a>, or:<br>
1. <!WA52><a href="#Fact Sheet">Fact Sheet</a>; 2. <!WA53><a href="#Syllabus">
  Syllabus</a>; 3. <!WA54><a href="#Roles">Roles</a>; 4. <!WA55><a href="#PDRL">
  PDRL</a>; 5. <!WA56><a href="#Assmt 1"> Assignment #1</a>; 
  6. <!WA57><a href="#Assmt 2">Assignment #2</a>; 
  7. <!WA58><a href="#Assmt 3">Assignment #3</a>; 
  8. <!WA59><a href="#Assmt 4">Assignment #4</a>.</p> 

<!-------------------ASSIGNMENT #2-------------------------->
<center><!WA60><img src="http://cs.fit.edu/~ellis/redwhblu.gif"></center><br>
<a name="Assmt 2"><Center><h2>Assignment #2</h2></center></a>
<p><strong>NOTE:</strong> <em>Everyone MUST keep track of the 
hours spent on project activities. Turn in weekly activity report
forms to the Project Administrator.</em>
<p><em>Although individual assignments are due on 27 Feb, most 
work will have to be done well in advance of this date in order 
for the project to remain on schedule.</em>

<h3>Task Leader:</h3>
<ul>
  <li>Write Change Requests/Discrepancy Report(s) [CR/DRs] against 
      the Requirements Document and/or source code to reflect 
      inconsistencies between them. Turn CR/DR in to the 
      Configuration Manager.
  <li>Support your CR/DRs at the Software Configuration Control 
      Board (SCCB) meeting at which they are presented.
  <li>If the SCCB authorizes changes to the Requirements Document, 
      log out the document with the Configuration Manager and make 
      all authorized changes. Return the updated document to the 
      Configuration Manager.
  <li>If changes to the code are authorized by the SCCB as the result 
      of your CR/DRs, coordinate changes with the designer and 
      implementor, as required.
  <li>Recommend at least one significant change (not associated with 
      a discrepancy) for the LCFS product. Turn CR(s) in to the 
      Configuration Manager.
</ul>

<h3>Project Administrator:</h3>
<ul>
  <li>Collect Weekly Activity Reports (WARs) weekly and prepare 
      bi-weekly Cost/Schedule Status Reports (C/SSRs) for presentation 
      to the team & customer with hard copies to the Task Leader and 
      customer.
  <li>Discuss the expected 揺ffort remaining