Hci in software process
-
Upload
raina-malik -
Category
Software
-
view
216 -
download
0
Transcript of Hci in software process
![Page 1: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/1.jpg)
HCI IN SOFTWARE PROCESS
SUBMITTED TO MAM SUMERA KOUSAR
SUBMITTED BY RIDA MARIAM
![Page 2: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/2.jpg)
HCI in Software process
Software engineering and the design process for interactive systems
Usability engineering Iterative design and prototyping Design rationale
![Page 3: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/3.jpg)
Software lifecycle
![Page 4: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/4.jpg)
Software engineering is the discipline for understanding the software design process, or life cycle
Designing for usability occurs at all stages of the life cycle, not as a single isolated activity
![Page 5: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/5.jpg)
The waterfall modelRequirementsspecification
Architecture design
Detail design
coding and unit testing
Integration and testing
Operation andmaintenance
![Page 6: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/6.jpg)
Activity in lifecycle
![Page 7: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/7.jpg)
Requirements specification Designer and customer try capture what the
system is expected to provide Expressed in natural language or more
precise languages, such as a task analysis would provide
Architectural design High-level description of how the system will
provide the services required Factor system into major components and
how they are interrelated Must satisfy both functional and
nonfunctional requirements
![Page 8: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/8.jpg)
Detailed design Refinement of architectural components
and interrelations to identify modules to be implemented separately
Coding and unit testing Implementing and testing the individual
modules in some executable programming language
![Page 9: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/9.jpg)
Integration and testing Combining modules to produce
components from the architectural description
Operation and maintenance
Product is delivered to customer and any problems/enhancements are provided by designer while product is still live
The largest share of the life cycle
![Page 10: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/10.jpg)
Verification and Validation
Verification Designing the product right Validation Designing the right product The formality gap Validation will always rely to some extent on
subjective means of proof Management and contractual
issues Design in commercial and legal contexts
Real-worldrequirementsand constraints
The formality gap
![Page 11: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/11.jpg)
The life cycle for interactive systems
![Page 12: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/12.jpg)
Usability engineering
![Page 13: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/13.jpg)
The ultimate test of usability based on measurement of user experience
Demands specific usability measures be made explicit in requirements
Usability specification Usability attribute/principle Measuring concept Measuring method Now level/ worst case/ planned
level/ best case
![Page 14: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/14.jpg)
Problems Usability specification requires
level of detail that may not be possible early in design
Satisfying a usability specification does not necessarily satisfy usability
![Page 15: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/15.jpg)
Itera
tive
desig
n
and
Prot
otyp
ing
![Page 16: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/16.jpg)
Iterative design overcomes inherent problems of incomplete requirements
Prototypes Simulate or animate some features of
intended system different types of prototypes
Different models Throw-away Incremental Evolutionary
![Page 17: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/17.jpg)
Management issues Time Planning Non-functional features Contracts
![Page 18: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/18.jpg)
Techniques of Prototype
Storyboards Need not be computer-based can be
animated Limited functionality simulations Some part of system functionality
provided by designers Tools like hypercard are common for
these Wizard of oz technique
![Page 19: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/19.jpg)
Techniques of Prototype
Warning about iterative design Design inertia – early bad decisions
stay bad Diagnosing real usability problems
in prototypes…. and not just the symptoms
![Page 20: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/20.jpg)
Why Prototype??? Team members can communicate
effectively You can test out ideas for yourself It encourages reflection: very
important aspect of design Prototypes answer questions, and
support designers in choosing between alternatives
![Page 21: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/21.jpg)
Design Rationale
![Page 22: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/22.jpg)
Design rationale is information that explains why a computer system is the way it is.
Rationale has to do with logical explanations and reasons
Discussions, debates, negotiations
Reasons for features Reasons against features
![Page 23: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/23.jpg)
![Page 24: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/24.jpg)
Benefits of design rationaleCommunication throughout life cycle
Reuse of design knowledge across products
Enforces design disciplinePresents arguments for design trade-offs
Capturing contextual information
![Page 25: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/25.jpg)
Types of DR: Process-oriented
Preserves order of deliberation and decision-making
Structure-orientedEmphasizes post hoc structuring
of considered design alternatives
Two examples:Issue-based information system
(IBIS)Design space analysis
![Page 26: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/26.jpg)
Any Question
![Page 27: Hci in software process](https://reader035.fdocuments.us/reader035/viewer/2022062900/58ec8d9c1a28ab4e788b4649/html5/thumbnails/27.jpg)