7. 2. SOFTWARE DEVELOPMENT LIFE CYCLE
In software engineering, the software life cycle describes the activities that take place
from the initial concept formation for a software system up until its eventual phasing
out and replacement.
Core activities:!
- Requirements specification
- Architectural design
- Detailed design
- Coding and unit testing
- Integration and testing
- Maintenance
8. 2. SOFTWARE DEVELOPMENT LIFE CYCLE
Waterfall model
Requirements Specification
Architectural Design
Detailed Design
Coding and UnitTesting
Integration andTesting
Operation and
Maintenance
9. 2. SOFTWARE DEVELOPMENT LIFE CYCLE
Issues
Missing the user perspective!
The traditional software life cycle does not
promote the use of techniques which
support the user’s perspective of the
interactive system.
10. 2. SOFTWARE DEVELOPMENT LIFE CYCLE
Issues
Validation and verification!
Formality gap: refers to a gap between the
real world and structured design.As a
consequence, there’s always a certain
subjectivity in validation.
11. 2. SOFTWARE DEVELOPMENT LIFE CYCLE
Involve all parties!
USERS CUSTOMERS DEVELOPMENTTEAM
Needs
12. 2. SOFTWARE DEVELOPMENT LIFE CYCLE
Implement a workload scheduling!
Needs
ACTIVITIES RESPONSIBLES ARTIFACTS
14. 3. IMPROVINGTECHNOLOGY DESIGN
“The need for the future is not so much
computer oriented people as for people
oriented computers”
Nickerson, 1969
15. 3. IMPROVINGTECHNOLOGY DESIGN
Research areas that explore how people interact with
computers
• Interaction Design (IxD)
• User Experience (UX)
• Human-Computer Interaction (HCI)
• User-centered Systems Design (UCSD)/ Human-Centered Systems
Design (HCSD)
• User-Centered Design (UCD)
16. 3.1. INTERACTION DESIGN
Interac)on
Design
Ergonomics
Psychology/ cognitive
Science
Informatics
Engineering
Computer Science /
Software Engineering
Social Sciences
Graphic Design
Product Design
Artist-Design
Industrial Design
Film Industry
DESIGN PRACTICESACADEMIC DISCIPLINES
Information Systems
Computer Supported Cooperative Work
Cognitive Ergonomics
Human Factors
Cognitive Engineering
Human-Computer Interaction
INTERDISCIPLINARY FIELDS
Preece, Sharp and Rogers, 2007
17. 3.2. USER EXPERIENCE
“a person’s perceptions and responses that result
from the use or anticipated use of a product,
system, or service”
ISO 9241- 210
18. 3.3. HUMAN COMPUTER INTERACTION
HCI covers major threads of research in 4 disciplines:
• Human Factors
• Information Systems
• Computer Science
• Library and Information Science
A discipline concerned with the design, evaluation and implementation of
interactive computing systems for human use and with the study of major
phenomena surrounding them
Hewett et al. 1996
19. “User-centered design’ (UCD) is a broad term to
describe design processes in which end-users
influence how a design takes shape. It is both a
broad philosophy and variety of methods.”
Abras, Maloney-Krichmar, Preece, 2004
3.4. USER-CENTERED DESIGN
20. 4. LEVELS OF USER INVOLVEMENT
Overview of methods for stakeholder involvement in relation to the level of involvement and the phase of application (De Bont et al., 2014)
25. Understand and
Specify context of use
Specify user
requirements
Produce design
solutions
Evaluate
Design solution
satisfies the
requirements
Plan the human-
centered activities
Iterate where
appropriate
ISO 9241-210
5.3. UCD STANDARD
26. • More usable products
• Cost savings
• Safer systems
5.4. UCD ADVANTAGES
28. FURTHER READINGS
This material uses Creative Commons License
Recognition – Share alike.
Abras, C., Maloney-Krichmar, D., Preece, J. (2004). User-centered design.Bainbridge,W. Encyclopedia of
Human-Computer Interaction.Thousand Oaks: Sage Publications, 37(4), 445-456.
Dis, I. (2009). 9241-210: 2010. Ergonomics of human system interaction-Part 210: Human-centred design for
interactive systems. International Standardization Organization (ISO). Switzerland.
Goodman, E., Kuniavsky, M., Moed,A. (2012). Observing the user experience:A practitioner’s guide to user
research. San Francisco, CA: Morgan Kaufman
Gould, J. D., Lewis, C. (1985). Designing for usability: key principles and what designers
think. Communications of the ACM, 28(3), 300-311.
Norman, D.A. (1988).The psychology of everyday things. Basic books.
Norman, D.A., Draper, S.W. (1986). User centered system design. New Perspectives on Human-Computer
Interaction, L. Erlbaum Associates Inc., Hillsdale, NJ.
Sharp, H., Rogers,Y., Preece, J. (2011). Interaction design: Beyond human–computer interaction (3rd ed.).
Chichester, UK: John Wiley and Sons Ltd.
29. FURTHER READINGS
This material uses Creative Commons License
Recognition – Share alike.
Ritter, F. E., Baxter, G. D., Churchill, E. F. (2014). User-centered systems design: a brief history. In Foundations
for designing user-centered systems(pp. 33-54). Springer London.
Wallach, D., Scholz, S. C. (2012). User-centered design: why and how to put users first in software
development. In Software for people (pp. 11-38). Springer Berlin Heidelberg.