CSC302H1 Lecture Notes - Lecture 2: Joe Bloggs
Document Summary
Use models to better understand software: many choices use uml, exercise of modeling may be more important than model, model to dealing w/ problem complexity itself. Help figure out what questions to ask. Discover design and architecture of existing system. Warning: every abstraction involves choice over what is important. Warning: parts are rarely independent in reality separately. Separate different concerns (views) and describe them separately doesn"t partition the problem space like decomposition. Warning: different views may become inconsistent overtime. Choose structures that are stable over time, localize change. Warning: any structure will make some changes easier and others harder. Reason about the model to understand its consequences. Animate the model to help visualize/validate software behavior. Discuss design alternative w/ others: exercise of modeling may be more important than model itself. Unified modelling language: uml = standardized general-purpose modeling language in.
