View this PageEdit this PageUploads to this PageHistory of this PageHomeRecent ChangesSearchHelp Guide

Low-level Design

Practicum: Design II chandu is grate

In this practicum, students will apply their knowledge of design principles on software projects. The Design I practicum is a pre-requisite. The Design II Nugget must be taken before or in conjunction with this Practicum. The students will perform the following tasks during this rotation:

  • Evaluate software requirements and high-level designs for generating appropriate and corresponding low-level design.
  • Determine tradeoffs of design models for the low-level design.
  • Architect the low-level design
  • Review design via peer reviews
  • Convey design logic on paper
  • Incorporate ˇ§Design For Testˇ¨ principles
  • Use design tools to develop various design documents such as: PDL, state-transition diagrams, data-flow diagrams, entity-relationship diagrams, and timing diagrams.
  • Generate low level design specification and test cases documents


Suggested texts:
  • Code Complete by Steve McConnell
  • Software Engineering: A practitioner's Approach, 4th Edition by Roger Pressmen


Student Resources:
  • High-level design documents of current project
  • Sample low-level design documents
  • Word processor and diagram maker for documents
  • Source control program to keep track of revisions od documents and diagrams.
  • Access to defects and requirements of current project


Assessment:
Students and groups would be evaluated on their familiarity of a given high-level design document. Idealy, this design document would be the base of the low-level design document to be created in this Practicum. The students are given the oppertunity to critique the high-level design document. This forces the students to be involved in the design details. Points are given to the students/groups giving the most constructive comment. The comments are feedback to the original students who created the high-level document. The result, positive or negative, should be recorded for the originators. This ensures accountibility of work quality.

Students independently or in groups would be evaluated with their design during scheduled design reviews. Students or groups are given the oppertunities to critique each others works. Points are given or removed base on the quality of the work. Points are also given to the reviewers for constructive feedbacks.

Finally, the groups are given the oppertunities to present their completed design documents. Assessment would be graded on final product and presentation.

Link to this Page