0% found this document useful (0 votes)
60 views

Jim Diamond: Software Design & Evaluation

The document discusses software design and evaluation. It outlines the software life cycle from requirements analysis through deployment and maintenance. It also discusses evaluating software based on functionality, reliability, usability, efficiency, maintainability, and portability as defined by the ISO 9126 standard. Finally, it discusses pathological interface design and the need for interfaces to be simple, appropriate, and functional.

Uploaded by

Yogendra Rajavat
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
60 views

Jim Diamond: Software Design & Evaluation

The document discusses software design and evaluation. It outlines the software life cycle from requirements analysis through deployment and maintenance. It also discusses evaluating software based on functionality, reliability, usability, efficiency, maintainability, and portability as defined by the ISO 9126 standard. Finally, it discusses pathological interface design and the need for interfaces to be simple, appropriate, and functional.

Uploaded by

Yogendra Rajavat
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 24

Software Design & Evaluation

Jim Diamond
Medical Informatics 28th February 2001

Who is Afraid of the System?

Knowledge

Communication!
The sponsor (Client) has a general idea of what he or she wants the program to do, but may not really understand how computers work or what is involved in programming.

The Developer (Systems Analyst), on the other hand, knows a lot about computers and programming, but typically does not know very much about the task from the sponsors point of view.

Software Design/Evaluation Environment

Design

Evaluation

Design

Evaluation

Feedback

Software Life Cycle

Requirements Analysis

Requirements are a description of what you actually want


Background information for the non-specialist

Who will use it, how experienced? Will the product be used often by experts? Computers type? Functionality? Compatibility policy?

Specification

A description of what the program does

The specification describes one particular way of solving the problem

Not how it does it

Formal document for project specification

Development

Structure
Division of the program into modules and procedures Design of the data structures and algorithms Plans for producing documentation and test cases Configuration management

Produce the actual code for the program

Evaluation

How do we know when a program is correct?


Ensure confidence

Black box testing White box testing Module test Integration testing

Deployment

Maintenance

Bug reporting Fixing

Distribution
Version control

Retirement

The period of time in the software lifecycle during which support for a software product is terminated De-commission

Software Evaluation
Functionality Reliability

ISO 9126
ISO 9126 is the software product evaluation standard from the International Organisation for Standardisation. This international standard defines six characteristics that describe, with minimal overlap, software quality.

Usability Efficiency Maintainability Portability

Functionality

Suitability Accurateness

Inter-operability
Compliance Security

Reliability

Maturity Fault tolerance Recoverability

Usability

Understandable Learnable

Operability

Efficiency

Time behaviour Resource behaviour

Maintainability

Analysable Changeable

Stability
Testable

Portability

Adaptability Installable

Replaceable
Conformance

Pathological Interface Design (1)

Pathological Interface Design (2)


Breast Fine Needle Aspiration Cytology

Pathological Interface Design (3)

EXPERT SYSTEMS

Pathological Interface Design (4)

What should be the characteristic features of the interface design?


Users don't have the manual, and if they did, they wouldn't read it. In fact, users can't read anything, and if they could, they wouldn't want to.

Pathological Interface Design (5)

Simple

Appropriate
Functional

You might also like