1. Requirements Analysis Document Presentation
Brian Woo
User Interface Subsystem
PAID Project
Fall 1998

2. General Goals
Provide set of interfaces for scenarios presented in problem statement
Provide standards for communication between end-users and external subsystems

3. Current System WIS EPC (Electronic Parts Catalog) VISTA
Reynolds-Reynolds

4. Proposed System
Graphical interface for end-user interaction with PAID system
Style guide for all interfaces within PAID

5. Functional Requirements
User-friendly interface
display data
handle processing/requesting of data
Ability to work efficiently
disconnected mode (info from local db)
connected mode (info from MBNet)
Ability for users to set preferences

6. User Interface/Human Factors
Wide range of users
Multiple languages/cultures
Different platforms to be run on
desktop PC
portable device

7. Documentation Extensive online help system
Multimedia or paper tutorials
Reference manuals

8. Hardware Consideration
Use of Java Virtual Machine
Storage capacity
Connectivity

9. Performance Characteristics
Speed
download
display
Storage Space

10. Error Handling/Extreme Conditions
Detection
Display

11. System Interfacing Input Output user input devices visual display
audio signal

12. Quality Issues
Reliability
Portability

13. System Modifications New/improved input devices New languages/cultures
Change according to user feedback
Change according to change in PAID

14. Physical Environment Location Environmental factors office garage
off-site repair location
Environmental factors
noise
dirt
physical shock

15. Security Issues
Level of access per individual
Two forms of access

16. Resource Issues
Installation

17. System Model Use case : local database update
Actors : use case initiated by Bratt, who communicates with the server
Description : PAID prompts Bratt to update the local database. Bratt delays download. Later, Bratt downloads and receives message confirming update.

18. Local Database Update Server Download_Control Bratt
Get network load
high
low
start download
download finished
Bratt
PAIDSystem_Interface
Communication
DelayedDownload_Control
initiates
starts
login panel
log in
yes, download now
creates
server ready
prompt for download
N bytes
finished
download status
Display status
Local Database Update
See screen sequence for details of the login process
Bratt can access the local database anytime
no, not now

19. System Model (cont’d) Login process : Terminate program
Successfully connected
Network error
Authentication error
Ok pressed
Login name: __________
Password : __________ OK
Login dialog
Connecting…
Since it takes a long time to connect to the server, display some message describing what’s happening.
Display the error and propose to try again or close the program.
The user chooses to close the program.

20. System Model (cont’d) Download process : Level 1: Gauge
Level 2: Window
A small gauge is displayed at the bottom. The percentage of data downloaded is written on it.
Displayed:
Percentage
Time left
Displayed:
Percentage
Time left
Check list
Cancel
More >
Close
Close pressed/Close Window
< Less
Download over
Package one – ok
Package two – ok
Package three – in progress
Package four –
Package five – …
Presses Cancel/stop downloading
Presses Less/resize window
Download over
Cancel

21. Issues Push vs. pull information Accomodation of languages/cultures
Windows widgets vs. custom interface
Hardware for mobile garage scenario
Etc., etc...