informatics 121 software design i
DESCRIPTION
Informatics 121 Software Design I. Lecture 6 Duplication of course material for any commercial purpose without the explicit written permission of the professor is prohibited. Today’s lecture. Design methods Practice. Design cycle. synthesize. goals constraints assumptions decisions - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/1.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 1
Informatics 121Software Design I
Lecture 6
Duplication of course material for any commercial purpose without the explicit written permission of the professor is prohibited.
![Page 2: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/2.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 2
Today’s lecture
• Design methods
• Practice
![Page 3: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/3.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 3
Design cycle
analyze evaluate
synthesize
goalsconstraints
assumptionsdecisions
ideas
![Page 4: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/4.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 4
Backtracking
current decisionexplored idea
unexplored idea previous decision
![Page 5: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/5.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 5
Backtracking
satisfactory experience
plan for realization
change in the world
what is it to accomplish?
how does one interact with it?
what is its conceptual core?
what are its implementation details?
![Page 6: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/6.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 6
Realistic design process
satisfactory experience
plan for realization
change in the world
what is it to accomplish?
how does one interact with it?
what is its conceptual core?
what are its implementation details?
![Page 7: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/7.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 7
Realistic design process
satisfactory experience
plan for realization
change in the world
what is it to accomplish?
how does one interact with it?
what is its conceptual core?
what are its implementation details?
What happens here?
![Page 8: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/8.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 8
Realistic design process
satisfactory experience
plan for realization
change in the world
what is it to accomplish?
how does one interact with it?
what is its conceptual core?
what are its implementation details?
Or here?
![Page 9: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/9.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 9
Design process
• A design process represents a planned course of action as to how to tackle a design problem to arrive at a design solution– where to focus effort– what methods to use– whom to involve
• A design process may be defined up-front in its entirety, or defined in increments as the design project unfolds
![Page 10: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/10.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 10
Design method
• A self-contained, structured technique that guides a designer in advancing some aspect of the design project at hand
• Serves as a bridge from the overall process of design to actual individual and collaborative design work
![Page 11: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/11.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 11
Origin
![Page 12: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/12.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 12
Today
![Page 13: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/13.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 13
Example
![Page 14: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/14.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 14
Example
![Page 15: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/15.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 15
Example
![Page 16: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/16.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 16
Example
![Page 17: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/17.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 17
Characteristics of design methods
• Each design method suits a specific purpose with respect to the design cycle and overall design project
• Each design method expects a certain context for it to lead to optimal results
• Applying just one design method rarely suffices (but still may help)
![Page 18: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/18.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 18
Example – decision making
![Page 19: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/19.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 19
Example – unearthing assumptions
![Page 20: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/20.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 20
Example – generating ideas
![Page 21: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/21.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 21
Example – identifying goals
![Page 22: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/22.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 22
Software design methods
Applicationdesign
Interactiondesign
Architecturedesign
Implementationdesign
Analysis • competitive testing• contextual inquiry• feature comparison• stakeholder analysis• task analysis
• critical incident technique• interaction logging• personas• scenarios
• framework assessment• model-driven
engineering• quality-function-
deployment• reverse engineering• world modeling
• release planning• summarization• test-driven design• visualization
Synthesis • affinity diagramming• concept mapping• mind mapping• morphological chart
• design/making• participatory design• prototyping• storyboarding
• architectural styles• generative programming• component reuse• decomposition
• pair programming• refactoring• search• software patterns
Evaluation • requirements review• role playing• wizard of oz
• cognitive walkthrough• evaluative research• heuristic evaluation• think-aloud protocol
• formal verification• simulation• weighted objectives
• correctness proofs• inspections/reviews• parallel deployment• testing
![Page 23: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/23.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 23
Choosing design methods to apply
• Focus on essence
• Focus on the unknown
• Focus on making progress
![Page 24: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/24.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 24
Focus on essence
• Every design problem has an essence, the key – and often most difficult – part that must be understood and addressed ‘right’ for the design solution (plan for change in the world) to satisfy the stakeholders
• Postponing understanding and addressing the essence of a design problem incurs a significant risk of rework at a later time
![Page 25: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/25.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 25
Focus on the unknown
• Every design problem involves knowledge deficiencies – gaps in the understanding of the design problem and its possible solutions – that must be addressed for the design solution (plan for change in the world) to satisfy the stakeholders
• Postponing understanding and addressing knowledge deficiencies incurs a significant risk of rework at a later time
![Page 26: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/26.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 26
Focus on making progress
• Every design problem involves times during which the design project gets stuck; focusing effort elsewhere and continuing to make progress is often the right approach in response
• Continuing to focus on a stuck issue for extended periods of time tends to be effort that is wasted
![Page 27: Informatics 121 Software Design I](https://reader035.vdocuments.mx/reader035/viewer/2022062719/568130f8550346895d972049/html5/thumbnails/27.jpg)
Department of Informatics, UC IrvineSDCL Collaboration LaboratorySoftware Design and
sdcl.ics.uci.edu 27
Practice
• Virtual campus visit
• Disney electronic queue management system
• Mountain climbing 3D guide system
• Social restaurant table