1 / 8

Comprehensive Top-Level Design Document for Software Project

This Top-Level Design (TLD) Document outlines the design goals, architecture, and planning for a software project as envisioned by Dr. Ron Rymon at IDC in January 2004. It includes links to the project proposal, Software Requirements Specification (SRS), architecture details, testing strategies, and a project management framework. Key components such as module specifics, integration tasks, and performance metrics are discussed, ensuring clarity in project responsibilities and timelines. The document serves as a vital resource for development and testing teams.

sacha-cotton
Télécharger la présentation

Comprehensive Top-Level Design Document for Software Project

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. CS Field ProjectThe Top-Level Design (TLD) Document Dr. Ron Rymon IDC, Herzliya January 2004

  2. Goals • Link from Proposal: Overview the project • Link from SRS: The Requirements and constraints that the design must satisfy • “Solution Architecture” to the level of specific development and integration tasks • “Project Planning” designating schedule and responsibilities • Link to QA: module and system tests (mostly communication and performance) • Link to Programmer Manual: specific APIs, and components

  3. Document Parts • Overview of the Project • Main Requirements and Constraints (SRS) • Product and Software Architecture • Description of Specific Modules • Development and Target Environments • Expected Performance • Testing • Project Plans for Development and Testing

  4. Architecture • Decomposition of the product based on functional, development, and flow considerations • Consider components that are available off-the-shelf • Data flow diagrams • Extensibility and limitations • Merits vs. alternative architectures

  5. Modules and Components • Functionality and interfaces • Main classes, APIs • Implementation details and challenges • Available components and wrapping

  6. Testing • Module tests, based on specified functionality and intended performance • System tests • Tests against SRS use cases and requirements

  7. Project Plans • Use a project management tool • Outline all development / testing tasks • Granularity of 1-2 weeks max • Assign to specific team members • Indicate dependencies and interfaces • Estimate time frames and fit to schedule

  8. Schedule • First Submission – January 25, 2004 • Second Submission and Presentation – one week after receiving comments • For faster progress, or to consult on any issue, feel free to contact me to coordinate a meeting at ANY TIME. • Grading Policy: • Late submissions will receive a penalty of 10 points for every week • Both submissions are graded into the final grade

More Related