1 / 14

Comprehensive Project Plan for Software Development

Detailed plan outlining risks, schedule, language decision, quality plan, testing, documentation, and program architecture. Includes project phases, major features, and key milestones. Risks addressed include hardware, XML files, and language decisions such as J2EE or .NET. Follows a structured timeline for design, testing, and completion. Quality plan highlights change control, defect tracking, and versioning. Testing covers unit, system-level, and acceptance testing with documentation requirements. Stay tuned for insights on program architecture by Greg.

ednaajohnson
Download Presentation

Comprehensive Project Plan for Software Development

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. The project plan. December 16, 2004

  2. Agenda • The project plan • Risks • Language decision • Schedule • Quality plan • Testing • Documentation • Program architecture

  3. Risks • Assumptions • Adequate hardware • XML files • Major features disclosed

  4. Risks

  5. Language decision • Rich client or web application? • J2EE or .NET?

  6. Schedule • R1 – The Framework (January) • Design doc • Test plan • Stubbed implementation of framework • Prototype for each major user type

  7. Schedule • R2 – Submit and grade (February) • Professors may create labs • Students may submit answers • Graders may grade submissions • Test suite

  8. Schedule • R3 – Compile and test (March) • Professors may define tests • Students receive immediate compile and test results • Graders may review test results • Administrators may add / remove privileges • Test suite

  9. Schedule • R4 – Code complete (April) • All remaining functionality • Sandbox • UI • Configure for distributed environment • Graders may view standard metrics on submissions

  10. Schedule • R5 – Gold (May) • All acceptance tests must pass • Documentation finalized

  11. Quality plan • Change control • Versioned & log changes • Vote • Configuration management • Suffixed by build number • Defect tracking • Bugzilla

  12. Testing • Unit • System-level • Performance • Acceptance

  13. Documentation • SRS • Design • Javadocs • Test plan • User’s manual / help • Developers manual • Administrators manual

  14. Any questions?Up next…Program architecture…as presented by Greg

More Related