Project Phase II Assignment for CS 499 – due November 7

(during class, not after!)

Phase II of the project is to perform the design, implementation, and testing for the project and to present the results to your peers. Here are the things you must prepare by November 7.

1.(13 points)High Level Design

  1. Architecture diagram (figure 5.19 Pfleeger) or Package Diagram (figure 6.22 Pfleeger)
  2. Describe any architectural styles or patterns that you used
  3. Hold Formal Technical Review (FTR) of the architecture and show results
  1. (16 points) Detailed Design

a.Detailed design of each method (in PDL (sidebar 6.3 Pfleeger) or other detailed design notation - suggest that you use a low-level sequence diagram (figure 6.23 Pfleeger) over PDL where multiple classes are involved, there you will list the method names

b.a.Detailed class diagram (Figure 6.21 Pfleeger)Utilize some method of showing your detailed design for important scenarios or methods (must do so for at least one scenario or method)

c.b.User interface design (figures 6.37, 6.38 Pfleeger)

d.c.Describe any design patterns that you used

e.d.Hold a FTR of the design and show results

  1. (26 points) Implementation
  2. Source code listing with in-line comments
  3. Hold a FTR of the code and show results
  4. User’s manual – format of your choosing
  5. Administrator’s manual (configuration) along with System requirements and Installation – format of your choosing – note that this may be one paragraph of text
  1. (17 points) Testing
  2. Test plan, test cases, test results for unit testing (lowest level)one level of testing in addition to acceptance testing (unit or integration or system) – you must perform all these levls but must only provide deliverables for one level

b.Test plan, test cases, test results for integration testing

c.Test plan, test cases, test results for system testing (highest level)

  1. Hold a FTR (of the test plans and cases prior to testing) and show results
  1. (13 points) Technical Metric Collection (seek “waiver” for metrics that do not apply)
  2. Estimated lines of code (function points) – from Phase I
  3. Actual lines of code (or function points) – as implemented in Phase II

c.Lack of Cohesion of methods (LCOM)

d.Weighted methods per class (WMC) (for each class)

e.Depth of inheritance tree (DIT)

f.Coupling between object classes (CBO) provide at least 2 metrics on your code (of your choosing)

  1. Product size (by phase – that is: 1) design (number of use cases or number of sequence diagrams or number of objects), 2) code (number of lines of code), 3) test (number of test cases))
  2. Product effort (number of person hours) (by phase - that is: 1) design (hours spent on design), 2) code (hours spent coding), and 3) test (hours spent testing))
  3. Defects (by phase - that is: 1) design (number of defects found during FTR of design), 2) code (number of defects found during FTR of code), and 3) test (number of defects caught during testing))
  1. Keep the Engineering Notebook up to date – separate grade
  1. (15 points) Demonstration of the project to customer/professor
  1. Give your project to another team for peer review/evaluation (10/31) and perform a peer review/evaluation of the project of another team (they give to you 10/31, you give back your report by 11/9)– separate grade

9. Presentation of Results to Class (11/5 and 11/7) – separate grade

Each team will have 10 minutes to present their results

You may use viewfoils (transparency slides), PowerPoint slides, or posters

Your presentation must present the major aspects of Phase II (you will not have enough time to show all the items developed, so some results may be combined or skipped)

The project may be handwritten (neatly), typed (word processor, graphics package), in spreadsheet format, or a combination of these. You may turn in hardcopy and/or email project and/or send URL.

All assignments must have the names of your team members, course number, semester, project phase number, and date