1. 1. Requirement
    1. 1.1. Context, stakeholders and their needs
    2. 1.2. Functional, non-functional and general use-case diagram
    3. 1.3. Task assignment module's use-case diagram and the use-case using a table format.
  2. 2. System modeling
    1. 2.1. Activity diagram
    2. 2.2. Sequence diagram for "a back officer to assign vehicles to janitors and collectors" process
    3. 2.3. Class diagram of Task Assignment module
    4. 2.4. MVP 1: Task Management for back-officer
  3. 3. ArchitecturalDesign
    1. 3.1. Layered architecture
    2. 3.2. Component diagram
  4. 4. Test report

UWC Documentation

Architectural Design

  • Layered architecture
  • Component diagram