1 / 4

Deliverable 10

Deliverable 10. Deliverable #10 Class Design and Implementation #1 due 9 April. Executive Summary and Statement of Work Iteration Plan (Updated) for remaining iterations based on your assessment of the previous iterations.

hashim-dotson
Download Presentation

Deliverable 10

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Deliverable 10

  2. Deliverable #10Class Design and Implementation #1 due 9 April • Executive Summary and Statement of Work • Iteration Plan (Updated) for remaining iterations based on your assessment of the previous iterations. • Iteration Plan Assessments - Present your assessment of each of your iterations to date • Class diagrams - Ensure all methods in your Use Case Realizations have full signatures in their calling sequences. • Traceability - Extend your Traceability to cover your current detail design • Testing: Document your test suites: catalog these via number, purpose, scope, results, and assessment of each test. • This is the major component of this deliverable

  3. Deliverable #10Class Design and Implementation #1 • Source Code: Your deliverable is to include your source-level components. • organized ‘by design unit’ (that is, package, subsystem), ‘by component’ (within these higher level components). • Please note: Your source code absolutely must be internally documented with meaningful, guiding comments. These will be reviewed very carefully!!! • So, your organization should be Component View, Implementation Model, Package or Subsystem, and specific component within the owning package or subsystem.

  4. Deliverable #10Class Design and Implementation #1Presentation 11 April during class • Demonstrate, discuss, and show your applicationcode level concerns. • In detail, show some code snippets (fully documented, of course), starting with an organizational perspective (top down) • Present your test suites to include test case design, projected inputs, outputs, issues, expectations, and results. Talk about the ‘good, bad, and ugly’ of your development, tests, etc. • Map these back to your use cases for traceability.

More Related