SFWR ENG 3KO4 / 3MO4
Software Development For Computer / Electrical Engineering
Fall 2007 Lab 4 - (Week of Oct 8)

• Due date
  • Monday October 15 at 4:00 pm. Submit your deliverables (see below) in your lab's drop-in box in ITB building.
  
  
• Goals
  • To review the first draft of an "Architectural Design Document" to enhance its (maintainability and understandability) qualities.
  
  
• Instructions
  In Lab3 report, the students produced the first draft of the ABM architectural design document.
  
  In Lab4:
  • The TAs will collect the "component diagram" and "statecharts" from each group, as the requirment for Lab 3. These diagrams worth %10 of the Lab 4's mark, and will be assessed as part of Lab 4 deliverables. Therefore the deliverables for Lab 4 (see below) worth %90 of Lab 4's mark.
    
    
  • The TAs will present two examples on decomposition of system SRS into architectural design, i.e., Restaurant System and Ticket Selling Kiosk (from UML book page 33 indicated below). Also, you have two other examples, i.e., Thermostat and ABM systems from Lab 3. These examples will provide the seeds for discussion on how to improve the high-level design of both Restaurant System and ABM system, as part of your deliverables for Lab 4.
    
    
  • Then, the groups of students will be given another chance to work on their architectural designs (only Component Diagram and Statechart) to enhance the maintainability (i.e., less interaction among the components) and understandability (i.e., clear and simple interfaces) qualities of the components. In this enhancement we concern about the proper allocation of the system's functionalities into the components and the provided interfaces and their meaningful naming.

  • The student groups can consult with the TAs about their design decisions at the architectural level.
  
  
• Full SRS of ABM
  The complete SRS of the ABM system is provided for you such that all the groups access to the same set of requirements for their revised Component Diagram and Statechart. Click HERE to get the PDF slides.

• Brief guideline
  A brief guideline on how to design Component Diagram and Statechart at the architectural level of a system is provided. Click HERE.

• Example
  An example of Ticket Selling Kiosk design from UML book. Click HERE on page 33.

• Deliverables
  1. Hard copy of the revised Component Diagram and Statechart with their descriptions for ABM System, according to the Software Design Specification (SDS) document modified version of the IEEE SDS template.
  2. Hard copy of the Component Diagram & Statechart for the Restaurant system.
  3. Draw your diagrams using a tool such as Rational Rose (see annuncement) or NetBeans.

  
  Back to main page