WinWin
Taxonomy for Digital Library Projects
Model 1
1 Operational Modes
1.1 Operational States (e.g., pre-operation, on-operation, post-operation)
1.2 Classes of Service (e.g., system administrator, privileged user, general public)
1.3 Other Modes (e.g., management, training, test)
1.4 Graceful Degradation and Recovery
2 Application Capabilities
2.1 Media Handled
2.1.1 Static (text, images, graphics, etc.)
2.1.2 Dynamic (audio, video, animation, etc.)
2.2 Media Operations
2.2.1 Query, Browse
2.2.2 Access
2.2.3 Text Operations (find, reformat, etc.)
2.2.4 Image Operations (zoom in/out, translate/rotate, etc.)
2.2.5 Adaptation (cut, copy, paste, superimpose, etc.)
2.2.6 File Operations (save, recall, print, record, etc.)
2.2.7 User Control
2.3 Support Capabilities
2.3.1 Help
2.3.2 Administration
2.3.2.1 User Account Management
2.3.2.2 Usage Monitoring and Analysis
2.3.3 Maintenance and Diagnostics
3 Interfaces
3.1 User Interfaces
3.1.1 Graphical User Interface(s)
3.1.2 Command-Line Interface(s)
3.1.3 Application Programming Interface(s)
3.1.4 Diagnostics
3.2 Hardware Interfaces
3.3 Communications Interfaces
3.4 Other Software Interfaces (SIRSI, BRS, etc.)
4 Environment and Data
4.1 Operating Assumptions
4.1.1 Workload Characterization
4.1.2 Data Storage Characteristics
4.2 Design and Construction Constraints
4.2.1 Tools
4.2.2 Programming Languages
4.2.3 Computer Resources
4.2.4 Standards Compliance
4.3 Packaging
4.4 Implementation
4.5 Software Support Environment
5 Quality Attributes
5.1 Dependability
5.1.1 Reliability/Availability
5.1.2 Security/Privacy
5.2 Inter-operability
5.3 Usability
5.4 Performance
5.5 Adaptability
5.5.1 Evolvability
5.5.2 Portability
5.6 Affordability
5.6.1 Cost
5.6.2 Schedule
5.7 Reusability
6 Evolution
6.1 Capability Evolution
6.2 Interface Evolution
6.3 Technology Evolution
6.4 Environment and Workload Evolution
Win Conditions
Allow several reports to be merged
Can
create new subject
Users
can sign up to subscribe new book lists.
Users
can stop receiving new books lists.
Web-based
System.
There
are two ways to get new books lists
(Web and email)
Multi
browsers support
The
system should provide basic statistics.
Development
and transition to user in limited time (12 weeks)
Capability
to expand users
Reliable
and stable alerting service
Multiple
Subscriptions for same account
Editable
Search Form
Ease
use Application
User's
privacy
Confirmation
of subscription
Issues
Personalized searching strategy and limited time
Hard
to find test users
Model 2
1 Operational Modes
1.1 Operational States (e.q., pre-operation, on-operation, post-operation)
1.2 Classes of Services (e.q., system administrator, privileged user, general public)
1.3 Other Modes (e.q., training, test)
1.4 Maintenance Mode
2 Application Capabilities
2.1 Input Operation
2.1.1 Cursor Operation (e.q., move forward/backward )
2.1.2 Edit Operation (e.q., dictate or type data )
2.1.3 Field Operation
2.2 User Operations
2.2.1 Search
2.2.2 Select Collection
2.2.3 Enter Data in Form
2.2.4 User Control
2.4 Support Operations
2.4.1 On-line Help System
3 Interfaces
3.1 User Interfaces
3.1.1 Graphical User Interface
3.1.2 Web Browser Interface
3.2 Database Interface
3.3 Hardware Interface
4 Quality Attributes
4.1 Dependability/Fault-Tolerance
4.1.1 Reliability
4.1.2 Availability
4.1.3 Accessibility
4.2 Usability
4.3 Performance
4.4 Adaptability
4.4.1 Evolvability
4.4.2 Portability
4.5 Inter-operability
4.6 Affordability
4.6.1 Cost
4.6.2 Schedule
5 Environment and Data
5.1 Operating Assumptions
5.1.1 Workload Characterization
5.1.2 Data Storage Characteristics
5.2 Design Constraints
5.2.1 Tools
5.2.2 Programming Languages
5.2.3 Computer Resources
5.3 Implementation
5.4 Software Support Environment
5.5 Conditions for External Environment
6 Maintenance
7 Evolution
7.1 Interface Evolution
7.2 Capability Evolution
Win Conditions
A new Login screen is needed
Multi-Platform
Support.
On-line
data entry in Database
Data
type checking to ensure data validity
Multi
search capability
Scalability
of the new system
Extensibility
of the system
On-line
help facility
Zoom
in & zoom out capabilities
Local
and remote access
The
system should be based on Triangular architecture
Thumb
nail & sample images will be provided
Completion
of project in one semester
Voice
training required for catalogers
Accuracy
of dictation
Issues
Security of the system
Model 3
1 Operational Modes
1.1 Operational States (e.q., pre-operation, on-operation, post-operation)
1.2 Classes of Services (e.q., system administrator, privileged user, general public)
1.3 Other Modes (e.q., training, test)
2 Application Capabilities
2.1 Input Operation
2.1.1 Cursor Operation (e.q., move forward/backward )
2.1.2 Edit Operation (e.q., dictate or type data )
2.1.3 Field Operation
2.1.3.1 Radio Field Operation ( exclusive selection field )
2.1.3.2 Combo Field Operation ( multi selection field )
2.1.3.3 Check Field Operation ( check/uncheck field)
2.1.3.4 Button Field Operation
2.2 Support Capabilities
2.2 Help
2.3 Administration
2.3.1 User Account Management
2.3.2 Usage Monitoring and Count (user location and count)
2.4 Maintenance and Diagnostics
2.4.1 Tools of database operations
3 Interfaces
3.1 User Interfaces
3.1.1 Graphical User Interfaces
3.1.2 Application Programming Interfaces
3.2 Hardware Interfaces
3.3 Communications Interfaces
3.4 Other Software Interfaces (SIRSI, BRS, etc.)
4 Quality Attributes
4.1 Dependability
4.1.1 Reliability / Availability
4.1.2 Privacy/Security
4.2 Inter-Operability
4.3 Usability
4.4 Performance
4.4.1 User Response Time
4.5 Adaptability
4.5.1 Evolvability
4.5.2 Portability
4.6 Affordability
4.6.1 Cost
4.6.2 Schedule
5 Environment and Data
5.1 Operating Assumptions
5.1.1 Workload Characterization
5.1.2 Data Storage Characteristics
5.2 Design and Construction Constraints
5.2.1 Tools
5.2.2 Programming Languages
5.2.3 Computer Resources
5.3 Implementation
5.4 Software Support Environment
6 Evolution
6.1 Capability Evolution
6.2 Interface Evolution
6.3 Technology Evolution
6.4 Environment and Workload Evolution
Win Conditions
Portable
Ease
of use of application
Storage
of media assets
Security
of application
12
weeks development time
Uploading
of files should be easy
System
should present default values for applicable fields
The
cases should have time stamps.
Reusable Data
System
should keep track of completed/incomplete sections.
Add/delete Search Engine
Provision
for submitting detailed questions by email
Site
Statistics
Issues
Short development time
Natural
Language Processing will be difficult to implement
Exhaustive
documentation needed
Uploading
multi-media assets
Large
numbers of choices = slow performance
Model 4
1 Operational Modes
1.1 Operational States - Post Operation
1.2 Classes of Service - Privileged User
1.3 Testing / Training
2 Application Capabilities
2.1 Media Handled
2.1.1 Static - Text report generated by Unicorn
2.2 Media Operations
2.2.1 Text Operations
2.2.1.1 Reformat
2.2.1.2 Sort
2.2.2 Report Operations
2.2.2.1 Open
2.2.2.2 Save
2.2.2.3 Print
2.2.2.3.1 Printer
2.2.2.3.2 File
2.2.3 User Control
2.2.3.1 Select Options
2.2.3.2 View Results
2.3 Support Capabilities
2.3.1 On-line Help
3 Interfaces
3.1 User Interfaces
3.1.1 Graphical User Interface
3.1.2 Command Line Interface
4 Environment and Data
4.1 Operating Assumptions
4.1.1 Workload Characterization
4.1.2 Data Storage Characteristics
4.2 Design and Construction Constraints
4.2.1 Tools
4.2.2 Programming Languages
4.2.3 Computer Resources
4.2.4 Standards Compliance
4.3 Packaging
4.3.1 User's Manual
4.4 Implementation
4.4.1 Development Platform
5 Quality Attributes
5.1 Dependability
5.1.1 Reliability
5.1.2 Privacy / Security
5.2 Inter-operability
5.3 Usability
5.4 Performance
5.5 Adaptability
5.6 Affordability
5.6.1 Cost
5.6.2 Schedule
6 Evolution
6.1 Interface Evolution
6.2 Capability Evolution
Win Conditions
Security Issues
Existing
RDBMS as back-end
Time
taken by new system less than or equal to that of current system
Should incorporate OPEN,SAVE and PRINT operations
SELECT
and FORMAT capabilities
SURG
should flag duplicate records
On-line
HELP
Issues
Flagging of duplicate records only once
Model 5
1 Operational Modes
1.1 Operational States (e.q., pre-operation, on-operation, post-operation)
1.2 Classes of Services (e.q., system administrator, privileged user, general public)
1.3 Other Modes (e.q., training, test)
1.4 Maintenance Mode
2 Application Capabilities
2.1 Input Operation
2.1.1 Cursor Operation (e.q., move forward/backward )
2.1.2 Edit Operation (e.q., dictate or type data )
2.1.3 Field Operation
2.2 User Operations
2.2.1 Search
2.2.2 Select Collection
2.2.3 Enter Data in Form
2.2.4 User Control
2.4 Support Operations
2.4.1 Help System
3 Interfaces
3.1 User Interfaces
3.1.1 Graphical User Interface
3.1.2 Web Browser Interface
3.2 Database Interface
3.3 Hardware Interface
4 Quality Attributes
4.1 Dependability/Fault-Tolerance
4.1.1 Reliability
4.1.2 Availability
4.1.3 Accessibility
4.2 Usability
4.3 Performance
4.4 Adaptability
4.4.1 Evolvability
4.4.2 Portability
4.5 Inter-operability
4.6 Affordability
4.6.1 Cost
4.6.2 Schedule
5 Environment and Data
5.1 Operating Assumptions
5.1.1 Workload Characterization
5.1.2 Data Storage Characteristics
5.2 Design Constraints
5.2.1 Tools
5.2.2 Programming Languages
5.2.3 Computer Resources
5.3 Implementation
5.4 Software Support Environment
5.5 Conditions for External Environment
6 Evolution
6.1 Interface Evolution
6.2 Capability Evolution
Win Conditions
Security
Multiplatform
Ease
of use
Compatible
with current systems
Archived
Log
of migration
Issues
Corruption of data
Concurrency
Interleaving
Model 6
1 Operational Modes
1.1 Operational States (e.g., pre-operation, on-operation, post-operation)
1.2 Classes of Service (e.g., system administrator, privileged user, general public)
1.3 Other Modes (e.g., training, test)
2 Application Capabilities
2.1 Media Handled
2.1.1 Static (text, images, graphics, etc.)
2.2 Media Operations
2.2.1 Query, Browse
2.2.2 Access
2.2.3 Text Operations (find, reformat, etc.)
2.2.4 File Operations (save, recall, print, record, etc.)
2.2.5 User Control
2.2.6 E-mail conformation.
2.3 Support Capabilities
2.3.1 Help
2.3.2 Administration
2.3.2.1 User Account Management
2.3.2.2 Usage Monitoring and Analysis
2.3.3 Maintenance and Diagnostics
3 Interfaces
3.1 User Interfaces
3.1.1 Graphical User Interface(s)
3.1.2 Application Programming Interface(s)
3.2 Hardware Interfaces
4 Environment and Data
4.1 Operating Assumptions
4.1.1 Workload Characterization
4.1.2 Data Storage Characteristics
4.2 Design and Construction Constraints
4.2.1 Tools
4.2.2 Programming Languages
4.2.3 Computer Resources
4.3 Implementation
5 Quality Attributes
5.1 Dependability
5.1.1 Reliablity/Availability
5.1.2 Privacy/Security
5.2 Usability
5.3 Affordability
5.3.1 Schedule
6 Performance
7 Prototype
Win Conditions
Web based system for all interactions
Password
protection
Domain
name access control
Fast
Access
Swapping
function
E-mail
confirmation
Administrator
privileges
Users
can edit their request
Easy
to use interface
Requirements
must not change
Issues
What programming language will be used
Users
may forget password
User
privacy concerns
Y2k
Calendar compliance
Model 7
1 Operational Modes
1.1 Management Mode
1.2 User Mode
1.3 Graceful Degradation and Recovery
2 Application Capabilities
2.1 User Operations
2.1.1 Map Display
2.1.2 Path Generation
2.1.3 Tip Display
2.1.4 Printing
2.2 Management Operations
2.2.1 Tip Management
2.2.2 Guide Card Management
2.2.3 Map Management
3 Interface
3.1 Graphical User Interface(s)
3.2 Printer Interface
3.3 Database Interface
4 Environment and Data
4.1 Operating Assumptions
4.1.1 Workload Characterization
4.1.2 Data Storage Characteristics
4.2 Design and Construction Constraints
4.2.1 Tools
4.2.2 Programming Languages
4.2.3 Computer Resources
4.2.4 Standards Compliance
5 Quality Attributes
5.1 Dependability
5.1.1 Reliability/Availability
5.1.2 Privacy/Security
5.2 Usability
5.3 Performance
5.4 Adaptability
5.4.1 Evolvability
5.4.2 Portability
5.5 Affordability
5.5.1 Cost
5.5.2 Schedule
5.6 Reusability
6 Evolution
6.1 Capability Evolution
6.2 Interface Evolution
6.3 Technology Evolution
6.4 Environment and Workload Evolution
Win Conditions
Ease of Use
Guide
Card Generation
Floor
Plans Generation
Tools
for Project Delivery
Stability
of requirements
Code
Reuse
System
robustness and scalability
Issues
Link to existing database
Model 8
1 Operational Modes
1.1 Operational States
1.1.1 Automatic
1.1.2 Manual
1.2 Classes of Service
1.3 Training
2 Application Capabilities
2.1 Media Handled
2.1.1 Static
2.1.1.1 Text
2.1.1.2 Image, graphic
2.2 Media Operations
2.2.1 Query, Browse
2.2.2 Access
2.2.3 Notification
2.2.4 Text Operations
2.2.5 Image Operations (view)
2.2.6 File Operations (download, print, forward)
2.2.7 User Control
2.3 Support Capabilities
2.3.1 Help
2.3.2 Administration
2.3.2.1 User Account Management
2.3.2.2 Usage Monitoring and Analysis
2.3.3 Maintenance
2.3.4 Hardware/Software Requirement
3 Interfaces
3.1 User Interfaces
3.1.1 Graphical User Interface(s)
3.1.2 On-line Access Interfaces
3.1.3 Application programming Interfaces
3.2 Hardware Interfaces
3.3 Communications Interfaces
3.4 Other Software Interfaces
4 Environment and Data
4.1 Operating Assumptions
4.1.1 Workload Characterization
4.1.2 Data Storage Characteristics
4.1.3 Data Entry
4.1.4 Data Consistency
4.2 Design and Construction Constraints
4.2.1 Tools
4.2.2 Programming Languages
4.2.3 Computer Resources
4.2.4 Standards Compliance
4.3 Implementation
4.4 Software Support Environment
4.5 System Configuration
5 Quality Attributes
5.1 Dependability
5.1.1 Reliability/Availability
5.1.2 Privacy/Security
5.2 Inter-operability
5.3 Usability
5.4 Performance
5.5 Adaptability
5.5.1 Evolvability
5.5.2 Portability
5.6 Schedule
5.7 Reusability
6 Evolution
6.1 Capability Evolution
6.2 Interface Evolution
Win Conditions
Automatic transfer of documents to patrons
Use
of a Web browser for patron's interface to application program
Security
mechanism
Activity
monitoring capability
E-mail
notification and update of records
Capability
of processing multiple requests from a single user
Network
reliability
User
friendly interface
Manual
operation capability
Viewing
and printing the downloaded (received) file
Issues
Viewing
documents using a browser and authorizing only the owner of documents
Processing
documents submitted from different libraries
Model 9
1 Operational modes
1.1 Class of service
1.2 Authentication
1.3 Basic requirements
1.4 Training
2 Application Capabilities
2.1 Media handled
2.1.1 Static
2.1.2 Dynamic
2.2 Media operation
2.2.1 Access
2.2.2 Text operation
2.2.3 File operation
2.3 Administrative
3 Interfaces
3.1 Infrastructure
3.2 Media providers
3.3 Operators
3.3.1 Students
3.3.2 Instructors
4 Quality attributes
4.1 Assurance
4.1.1 Reliability/Available
4.2 Performance
4.3 Portability
4.4 Cost
4.5 Schedule
4.6 Reusability
4.7 Usability
4.8 Readability
5 Environment and Data
5.1 Operating Assumptions
5.1.1 Workload Characterization
5.1.2 Data Storage Characteristics
5.2 Design Constraints
5.2.1 Tools
5.2.2 Programming Languages
5.2.3 Computer Resources
5.3 Implementation
5.4 Software Support Environment
5.5 Conditions for External Environment
6 Evolution
6.1 Capability evolution
6.2 Interface and technology evolution
6.3 Environment and workload evolution
Win Conditions
12
weeks to complete project
Authentication
of users
Live
communications
Interdepartmental
usage
Collaborative
component
Link
to multiple pages
Language
translation
Ability
to fetch files and documents
Archiving
of material
Multi-platform
Customized
view for user
Search
engine
Simple
GUI
Issues
Feasibility of live communication
Image
search
Concurrency
On-line
translators
For
all models, stakeholders include developers, customers, prototypists, project
managers and testers.