Prototyping and GUI Design

Lecture 10 focuses on software prototyping and Graphical User Interface (GUI) design principles. Prototyping provides an interactive physical representation of system interfaces, enabling early stakeholder validation. The lecture contrasts Throwaway Prototyping (rapidly constructing paper sketches or throwaway screen mockups purely to clarify uncertain requirements before discarding them) with Evolutionary Prototyping (gradually building a working system core that evolves into the final production software). Students explore core GUI design guidelines: visual consistency across screens, meaningful error feedback, intuitive navigation hierarchies, accessibility, minimizing user memory load, and providing undo capabilities. Heuristic evaluation techniques that uncover usability flaws before code implementation are detailed. Software design principles emphasize high cohesion and low coupling to minimize ripple effects and enhance long-term system maintainability. Coupling classifications, spanning content, common, control, stamp, and data coupling, are critically evaluated to eliminate structural dependencies. Cohesion levels, from coincidental and logical to communicational and functional cohesion, provide objective criteria for evaluating module quality. Object-oriented analysis using the Coad and Yourdon methodology illustrates identifying classes, responsibilities, attributes, and services. Structural relationships, including Generalization-Specialization inheritance hierarchies and Whole-Part aggregation assemblies, are modeled with precision. Dynamic interaction modeling demonstrates sequence diagrams, object lifelines, activation bars, and synchronous versus asynchronous message exchanges. Software architecture frameworks explore Kruchten's 4+1 view model, connecting logical, process, development, and physical architectural perspectives. Architectural styles, including layered hierarchies, repository patterns, client-server structures, and pipe-and-filter pipelines, are contrasted. Design pattern principles demonstrate how Gang of Four solutions, such as the Observer pattern, decouple subjects from observers to handle state changes. Professional coding style standards detail clear identifier naming, consistent indentation, layout structure, and self-documenting code conventions. Defensive programming practices illustrate safe file handling, resource leak prevention, and robust input validation in C++ and Java environments. Exception handling mechanisms demonstrate try-catch-finally blocks, structured error propagation, and eliminating silent runtime failures. Software portability guidelines detail isolating hardware-dependent logic, handling endianness, and standardizing primitive data type representations. Verification and validation activities contrast static software inspections and walkthroughs with dynamic code execution testing techniques.