Design Project I
Nine topics that take a team from an idea to a fully designed software system: planning, a LaTeX report, an IEEE SRS, an SDLC choice, data flow diagrams, UML use case, sequence, communication and class diagrams, and Figma wireframes. Each topic is a slide deck with diagrams you can explore, interactive tools, worked examples, practice, a quiz and links for further learning.
Inside a topic: ← → or Space to move, F for full screen, M for the slide list. The pen button lets you draw on any slide.
- 1Lab ITeam Formation, Project Assignment & PlanningForming a team, choosing a project, writing the proposal, and planning it: feasibility study, work plan, Gantt chart, budget, risk analysis and roles.37 slides · Gantt, budget, feasibility and risk tools
- 2Labs II–IIITechnical Report Writing with LaTeXTypesetting reports in LaTeX with Overleaf: text and special characters, errors, mathematics, lists, packages, sections, cross-references, figures, tables, algorithms and BibTeX citations.59 slides · Live LaTeX previewer, table and BibTeX builders
- 3Lab IV · open-endedIEEE Software Requirements Specification (SRS)Functional and non-functional requirements, what makes a requirement good, how requirements are gathered, and how to write an SRS with the IEEE template, priorities and traceability.31 slides · Requirement sorter and quality checker
- 4Lab VSDLC Model SelectionThe six stages of the software development life cycle, the waterfall, iterative, V, spiral, agile and prototyping models, and how to choose one with a weighted comparison matrix.32 slides · Weighted selection matrix and model advisor
- 5Lab VIData Flow Diagrams (DFD): Level 0 and Level 1What a DFD shows, the four symbols in Gane–Sarson and Yourdon notation, the rules of valid data flows, and how to draw and balance Level 0 (context) and Level 1 diagrams, using the ATM system.27 slides · Flow checker and level explorer
- 6Lab VIIUML Use Case DiagramsActors, use cases and system boundaries; association, include, extend and generalization; use case descriptions with main and alternative scenarios, using the ATM system.28 slides · Scenario walk-through and include/extend game
- 7Lab VIIIUML Sequence & Communication DiagramsLifelines, activations and the eight message types; guards and combined fragments (alt, opt, loop); turning a use case into a sequence diagram; and the equivalent communication diagram.30 slides · Message-by-message sequence stepper
- 8Labs IX–XUML Class DiagramsClasses, attributes, operations and visibility; association, multiplicity, aggregation, composition and dependency; generalization, abstract classes, interfaces and realization, with the telephone and ATM examples.37 slides · UML decoder, relationship game, ATM explorer
- 9Lab: UI/UXUI/UX Foundations & Figma WireframingUsability, user-centred design, Nielsen’s heuristics, visual design and the laws of UX, accessibility with WCAG, fidelity levels, and designing and prototyping wireframes in Figma from your use cases.32 slides · Contrast checker, heuristics game, fidelity viewer
A real project, start to finish
Follow team Pulse as they design CampusCare, an appointment system for the university medical centre, through all nine steps of the course.
- Team & planning: problem (40-minute queues), SMART objectives, feasibility, 11-week Gantt, 80,300 Tk budget, risks
- LaTeX reports: one Overleaf report, one chapter file per member
- IEEE SRS: four user classes, FR-2.1–2.4, six measurable NFRs
- SDLC models: iterative model, 22 of 30 in the weighted matrix
- DFD levels 0–1: Level 0 with four entities; Level 1 with five processes and three stores, balanced
- Use case diagrams: eight use cases, «include» Log in, «extend» Join waiting list
- Sequence & communication: Book appointment with an alt fragment, and the matching communication diagram
- Class diagrams: abstract User, Schedule ◆ Slot, Appointment ◆ VisitNote
- UI/UX & Figma: three Figma screens, traced to UC-01 and tested with five users
How the course fits together
Every topic produces one part of your team’s final report. The running example is the ATM banking system from the lab manual; your team applies each step to its own project.
Academic integrity. These notes teach the method with the ATM example. Your lab tasks (the Library Management System, the Student Registration System and your team’s own project) must be your own work: the practice slides give hints and checklists, not finished diagrams to copy.
