HCI in Software process Flashcards

1
Q

What is software engineering?

A

Software engineering is the discipline for understanding the software design process, or life cycle.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Outline 3 activities in the life cycle

A
  1. Requirements specification
  2. Architectural design
  3. Detailed design
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Explain 3 activities in the life cycle

A
  1. Requirements specification - designer and customer try capture what the system is expected to provide can be expressed in natural language or more precise languages, such as a task analysis would provide
  2. Architectural design - high-level description of how the system will provide the services required factor system into major components of the system and how they are interrelated needs to satisfy both functional and nonfunctional requirements
  3. Detailed design - refinement of architectural components and interrelations to identify modules to be implemented separately the refinement is governed by the nonfunctional requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Differentiate verification and validation

A

Verification means designing the product right and validation means designing the right product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Describe the formality gap

A

validation will always rely to some extent on subjective means of proof

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What’s the ultimate test of usability based on measurement of user experience

A

Usability engineering demands that specific usability measures be made explicit as requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Problem associated with Usability engineering

A

usability specification requires level of detail that may not be possible early in design

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Outline 4 usability specifications

A
  1. usability attribute/principle
  2. measuring concept
  3. measuring method
  4. now level/ worst case/ planned level/ best case
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Briefly describe 3 traditional usability categories

A
1. effectiveness
can you achieve what you want to?
2. efficiency
can you do it without wasting effort?
3. satisfaction
do you enjoy the process?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are prototypes?

A

These are temporary systems that simulate or animate some features of intended system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

List down three types of prototypes

A
  1. throw-away
  2. incremental
  3. evolutionary
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Briefly describe any 2 prototyping techniques

A
  1. Storyboards
    need not be computer-based
    can be animated
  2. Limited functionality simulations
    some part of system functionality provided by designers, tools like HyperCard are common for these
    Wizard of Oz technique
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is design Rationale?

A

Design rationale is information that explains why a computer system is the way it is

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

List down 4 Benefits of design rationale

A

1 . communication throughout life cycle

  1. reuse of design knowledge across products
  2. enforces design discipline
  3. presents arguments for design trade-offs
  4. organizes potentially large design space
  5. capturing contextual information
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

explain two types of design Rationale

A

1 . Process-oriented
preserves order of deliberation and decision-making
e.g Issue based information system

  1. Structure-oriented
    emphasizes post hoc structuring of considered design alternatives
    e.g design space analysis
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What about psychological design Rationale?

A
  • aims to make explicit consequences of design for users
  • users are observed on system
  • psychological claims of system made explicit
  • negative aspects of design can be used to improve next iteration of design