Concept Operational Description (OCD)
Data Mining of Digital Library Usage Data
Team #7
Hui-Hsien Chi FRD Shing-Cheung Chan OCD Maxim Krivokon SSRD Hsiao-Han Huang SSAD Fenny Muliawan LCP/Prototype Pei-Han Li -- UML
<October 25, 2004>
OCD_LCO_F04a_T07_V4.1.doc
Page i of 47
Version Date: 10/25/2004
Operational Concept Description (OCD)
Version no 4.1
Version History
"Early Section" releases: 1.x "LCO Core" releases: 2.x "LCO Draft on the Web" releases: 3.x "LCO after ARB" releases: 4.x
$ $ $ ' % % +, . & ( ( ! ! ! & & ! " # ! ! " " " # ) * ) * # #
OCD_LCO_F04a_T07_V4.1.doc
ii
Version Date 10/25/2004
Operational Concept Description (OCD)
Version no 4.1
Table of Contents
OPERATIONAL CONCEPT DESCRIPTION (OCD) ........................................................ I VERSION HISTORY ....................................................................................................... II TABLE OF CONTENTS................................................................................................. III TABLE OF TABLES .......................................................................................................V TABLE OF FIGURES ....................................................................................................VI
1. Introduction .......................................................................................................................................................7 1.1 1.2 1.3 2. Purpose of the OCD Document .................................................................................................................7 References .................................................................................................................................................8 Change Summary.......................................................................................................................................9
Shared Vision ..................................................................................................................................................10 2.1 2.2 2.3 2.4 2.5 2.6 2.7 System Capability Description ................................................................................................................10 Key Stakeholders .....................................................................................................................................11 System Boundary and Environment ........................................................................................................13 Major Project Constraints ........................................................................................................................13 Top-Level Business Case.........................................................................................................................14 Inception Phase Plan and Required Resources ........................................................................................14 Initial Spiral Objectives, Constraints, Alternatives, and Risks ................................................................15
3.
Domain/Organization Description ...................................................................................................................16 3.1 3.2 3.3 Organization Background ........................................................................................................................16 Organization Goals ..................................................................................................................................16 Current Organization Environment..........................................................................................................17
4.
Proposed System..............................................................................................................................................24 4.1 Statement of Purpose ...............................................................................................................................24 iii Version Date 10/25/2004
OCD_LCO_F04a_T07_V4.1.doc
Operational Concept Description (OCD) 4.2 4.3 4.4 4.5 4.6 5.
Version no 4.1
Project Goals and Constraints..................................................................................................................24 System Capabilities .................................................................................................................................25 Levels of Service (L.O.S.) Goals .............................................................................................................27 Changes in the Organization Environment Due to Proposed System ......................................................29 Effect on Organizations' Support Operation ...........................................................................................35
Prototyping ......................................................................................................................................................38 5.1 5.2 5.3 5.4 Objectives ................................................................................................................................................38 Approach .................................................................................................................................................39 Initial Results ...........................................................................................................................................40 Conclusions .............................................................................................................................................43
6.
Glossary for Domain Description ....................................................................................................................44
7. Appendices ..............................................................................................................................................................47
OCD_LCO_F04a_T07_V4.1.doc
iv
Version Date 10/25/2004
Operational Concept Description (OCD)
Table of Tables
Table 1: Operational Stakeholders Descriptions ..........................................................................................................7 Table 2: Change Summary ..........................................................................................................................................10 Table 3: Key Stakeholder Identifications.....................................................................................................................12 Table 4: Stakeholder Human Resources Involvements................................................................................................15 Table 5: Initial Spiral Objectives, Constraints, Alternatives, Risks ............................................................................16 Table 6: Organization Goal Form #1..........................................................................................................................17 Table 7: Organization Goal Form #2..........................................................................................................................18 Table 8: Organization Goal Form #3..........................................................................................................................18 Table 9: Business Use-Case Description (Current) #! ................................................................................................22 Table 10: Business Use-Case Description (Current) #2 .............................................................................................23 Table 11: Project Goals and Constraints #1 ...............................................................................................................25 Table 12: Project Goals and Constraints #2 ...............................................................................................................25 Table 13: Project Goals and Constraints #3 ...............................................................................................................26 Table 14: System Capability Form #1 .........................................................................................................................26 Table 15: System Capability Form #2 .........................................................................................................................27 Table 16: System Capability Form #3 .........................................................................................................................27 Table 17: Level of Services Specification Form #1 .....................................................................................................27 Table 18: Level of Services Specification Form #2 .....................................................................................................28 Table 19: Level of Services Specification Form #3 .....................................................................................................28 Table 20: Level of Services Specification Form #4 .....................................................................................................28 Table 21: Business Use-Case Description (New Process) #1 .....................................................................................32
OCD_LCO_F04a_T07_V4.1.doc
v
Version Date: 10/25/2004
Operational Concept Description (OCD)
Table of Figures
Figure 1: Benefits Realization Approach Results Chain .............................................................................................11 Figure 2: System Boundary and Environment.............................................................................................................13 Figure 3: Business-Structure Digram of Current Organization Structure ..................................................................18 Figure 4: Business-Collaboration Digram of Current Organization Structure ..........................................................18 Figure 5: Business-Artifacts Diagram of Current Organization Artifacts ..................................................................19 Figure 6: Business Use-Case Diagram of Current Organization Processes...............................................................20 Figure 7: Business Activity Diagram of Current Organization Processes #1.............................................................21 Figure 8: Business Activity Diagram of Current Organization Processes #2.............................................................22 Figure 9: Use-Case Model of System Capability ........................................................................................................26 Figure 10: Business Structure Diagram of Future Organization Structure ................................................................29 Figure 11: Business Collaboratin Diagram of Future Organization Structure ..........................................................30 Figure 12: Business-Artifacts Diagram of Future Organization Artifacts ..................................................................31 Figure 13: Business Activity Diagram of Future Organization Processes #1.............................................................33 Figure 14: Organization Chart #1...............................................................................................................................35 Figure 15: Organization Chart #2...............................................................................................................................36 Figure 16: Organization Chart #3...............................................................................................................................37 Figure 17: Prototype #1 ..............................................................................................................................................41 Figure 18: Prototype #2 ..............................................................................................................................................42 Figure 19: Prototype #3 ..............................................................................................................................................43
OCD_LCO_F04a_T07_V4.1.doc
vi
Version Date: 10/25/2004
Operational Concept Description(OCD)
Version 4.1
1. Introduction
1.1 Purpose of the OCD Document
The Operational Concept Description (OCD) for Data Mining of Digital Library Usage Data describes to the stakeholders how the new USC Digital Library Log Analysis System will function within their environment. This document is the Life Cycle Objectives (LCO) version of OCD. The OCD document consists of the scope of the proposed system. Some specific parts are described under different topic in this document. It not only covers the description of the new system, but also includes the primary benefits for client, and agreement on the high level structure of the project of the new system. The OCD will be served as reference and guidance for all stakeholders as to how the system will operate within its environment. Stakeholders can then make further recommendations on this system, and evolve it to a new operational concept from the current one. The development stakeholders will also have a better understanding of the system, and will make development decisions consistent with the operational objectives and constraints. The following are the names, organizations, titles, and roles of all operational stakeholders: Table 1: Operational Stakeholders Descriptions
Name Jewel Ward Johan Bollen Shing-Cheung Chan Fenny Muliawan Hsiao-Han Huang Hui-Hsien Chi Maxim Krivokon Pei Li Kristine Guevara
Organization USC Library Old Dominion University USC USC USC USC USC USC USC
Title Digital Resources Librarian Assistant Professor Student Student Student Student Student Student Student
Role Product Customer/User Product Customer/User Developer Developer Developer Developer Developer Developer Independent Verification & Validation (IV&V)
OCD_LCO_F04a_T07_V4.1.doc
Page 7 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
1.2 References
"Data Mining of Digital Library Usage Data" Project Description http://sunset.usc.edu/classes/cs577a_2004/projects/description/project7.htm Model-based Architecting and Software Engineering http://sunset.usc.edu/research/MBASE/mbase_main.html MBASE Guidelines version 2.4.1 http://sunset.usc.edu/classes/cs577a_2004/guidelines/MBASE_Guidelines_v2.4.1.pdf MBASE Version 2.4.1 Templates for OCD (version 1a) http://sunset.usc.edu/classes/cs577a_2004/guidelines/MBASEtemplates/OCD_Templatev1a.doc Visio template for the Results Chain http://sunset.usc.edu/classes/cs577a_2004/guidelines/MBASEtemplates/agile/ResultsChain_BRA_v2.vst MBASE Electronic Process Guide http://cse.usc.edu/research/MBASE/EPG Fall 2003 CS 577a Project #8 LCO portion of OCD http://ebase.usc.edu/eservices/cs577a_2003/team08a/LCO/OCD_LCO_F03a_T08.pdf USC Information Services Division http://www.usc.edu/isd/about/about.html USC Information Services Division--Policies Governing the Use of Computing Resources at USC http://www.usc.edu/isd/policies/computing/ Dr. Johan Bollen's Presentation http://www.cs.odu.edu~jbollen/presentations/facstaff_02_28_03.pdf http://www.cs.odu.edu/~jbollen/presentations/ecdl02.pdf http://www.cs.odu.edu/~jbollen/presentations/aisti04.pdf Digital Archive Visualization Engine
OCD_LCO_F04a_T07_V4.1.doc
Page 8 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
http://graphics.stanford.edu/~munzner/h3/ WinWin Spiral Model & Groupware Support System http://sunset.usc.edu/research/WINWIN/
H3Viewer library http://graphics.stanford.edu/~munzner/h3/
1.3 Change Summary
Table 2: Change Summary
Version 1.1 2.0 3.0 3.1 3.2 4.0 4.1
Changes Made Rewrite Introduction, Benefits Realized and Domain/Organization Description. Complete the rest of Operational Concept Descriptions (OCD) document Reflected suggested changes from the OCD Quality Report Reflected suggested changes from the OCD Early Sections Reflected suggested changes from team meetings Reflected suggested changes by the IV&V person and client. Reflected suggested changes from team meetings
OCD_LCO_F04a_T07_V4.1.doc
Page 9 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
2. Shared Vision
2.1 System Capability Description
The USC Digital Library staff has requested an archive usage analysis system as a supplement to standard web metrics such as hit counts. Our proposed usage analysis system will retrieve usage data from the digital library archive and will create relationship graphs for digital archive items. These graphs will give librarians a global structural view of the collections and will help them make decision on updating the collections. This system will be different from other systems because it automates creation of references/relations between digital library uses and documents, and can work with images and other items that do not have metadata or textual description. The system will be based on research by Dr. Johan Bollen, and will provide data for his future research.
2.1.1 Benefits Realized
The proposed USC Digital Archive Usage Analysis System has several key benefits. The librarians can use the results of the analysis to have better understandings of the digital archive collection and usage trends. Based on the information, they can make further improvements to the digital archive. The system will make it easier for library staff to make decisions on which items should be removed/added to the collection. These analyses include data usage, clustered image evaluations, user trend analysis, and shortterm image/document impact ranking versus long-term. The proposed system can also benefit Dr. Johan Bollen and other researchers who conduct their works on digital libraries and digital archives. Data and analysis reports produced by the system will be provided to researchers so that they can apply it to their research projects. In summary, the USC Digital Archive Usage Analysis System will benefit the USC Digital Library and digital archive researchers by: Better understandings of collection structure Better understandings of library usage Better understandings of usage trends over time References for archive improvements.
2.1.2 Results Chain
OCD_LCO_F04a_T07_V4.1.doc
Page 10 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
The results chain of implementing the digital archive usage analysis system is shown below. By analyzing logs and creating subsequent relationships, the system displays digital item characterizes, which will help digital library staff to gain a better understanding of the archive collection structure. The system also displays item accessibilities, so that the library staff can see the popularity of items, thus have a better understanding of library usage. The system also visualizes relationships between items, so that staff can see graphically the archive usage trend over time. Implementing the new system also means new ways of evaluation archive usage. Thus, digital library staff must be trained to learn to use the system to ensure effective use of the system. Give so, a set of training objectives to digital library staff will be formulated.
Figure 1: Benefits Realization Approach Results Chain
2.2 Key Stakeholders
The following identifies each stakeholder by their home organization, their authorized representative for project activities, and their relation to the Results Chain.
Table 3: Key Stakeholder Identifications
Stakeholder
Home
Authorized
Page 11 of 47
Relation to the Results
Version date 10/25/2004
OCD_LCO_F04a_T07_V4.1.doc
Operational Concept Description(OCD)
Version 4.1
Organization Customers (ISD Program Manager and Researchers) USC Information Services Division Old Dominion University USC
Representative Jewel Ward (ISD Program Manager) Johan Bollen (Researchers) Shing-Cheung Chan Hui-Hsien Chi Hsiao-Han Huang Maxim Krivokon Pei Li Fenny Muliawan
Chain Determine the initiative, intermediate outcome, and final outcomes. Experience final outcomes, provide assumptions. Execute the initiative to generate intermediate outcomes
Developers
Maintainers Database Suppliers IV&V Person Digital Library Staff Program Manager (System Administrator of future usage analysis system)
USC Information Services Division USC Information Services Division USC USC Information Services Division USC Information Services Division
ISD System Maintenance Team Jeff Pearson Kristine Guevara Jewel Ward Jewel Ward
Ensure intermediate and final outcomes Assist developers to achieve the intermediate outcomes Ensure developers correctly execute the initiative Experience final outcomes, provide assumptions. Determine the initiative
OCD_LCO_F04a_T07_V4.1.doc
Page 12 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
2.3 System Boundary and Environment
!
(/ &&
" 7
# .
#
#
11 # , 22
! 11 11 11
% 2 2 3, " 22 4 22 5 #
&! # 6 , ,
(/
0# # "# # "#
!
!
"
!
/ # ""
%
#
Figure 2: System Boundary and Environment
2.4 Major Project Constraints
There are constraints that are critical to the project's success: 1. 2. 3. Due to course constraints, the project must be completed by the end of spring semester 2005 (roughly 24 weeks). Due to course constraints, the system must be design and implement by six people, with addition of one IV&V person. Due to course constraints, the development of the system will receive no budgets.
OCD_LCO_F04a_T07_V4.1.doc
Page 13 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
4. 5. 6.
The system must be compatible with the existing digital archive system, so that data related to the digital archive system can be applied. The system will need to use existing open-source software (open source) to save implementation time. Must provide dynamic graphical user interfaces for data presentation.
2.4.1
Special focus: Further Shared Vision Elements for Large Systems
Special focus is not needed since this is a small development project.
2.5 Top-Level Business Case
The implementation of the Usage Analysis System for the USC Digital Library does not incur any costs since there is no budget for the development of this system. Even so, the quantitative and qualitative benefits realized in the Result Chain outcomes are tremendous. By analyzing digital items relationships and user trends, the Usage Analysis System can assist library staff to make improvements in the digital archive collections and assists researchers on their researches.
2.6 Inception Phase Plan and Required Resources
Since this project does not have any budgets, stakeholders do not need to have financial resources involved. As for human resources involvements, stakeholders have different commitments during the inception phase, depending on their role in the project.
Table 4: Stakeholder Human Resources Involvement
Stakeholder Type Software Users Customers
Human Resources Involvement None Attend project meetings Define project plans Participate in the WinWin negotiation Define project plans Participate in the WinWin negotiation Produce initial prototypes
Developers
OCD_LCO_F04a_T07_V4.1.doc
Page 14 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
Maintainers Data Suppliers IV&V Person Project Manager Digital Library Staff
None None Review project plans Review initial prototypes
None None
2.7 Initial Spiral Objectives, Constraints, Alternatives, and Risks
Table 5: Initial Spiral Objectives, Constraints, Alternatives, and Risks
Objectives
Gather negotiation system requirements from customers Negotiate requirements through WinWin negotiation Define initial system prototypes Project must be completed by spring semester of 2005 (roughly 24 weeks) New system must be compatible with existing digital archive system Develop portion of the system by using open-source packages Some developers may not participate in the implementation phrase Customers may not be reachable at times
Constraints Alternatives Risks
OCD_LCO_F04a_T07_V4.1.doc
Page 15 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
3. Domain/Organization Description
The USC Digital Library Usage Analysis System is being built to enhance the USC Digital Library service and to provide a user trend and digital item relationships analysis system. Currently, there exist usage analysis systems that have been built as part of the recommender services, such as the recommender services for the Los Alamos National Laboratory (LANL) Research Library (RL), the Open Video Project, and the NASA Technical Reports Archive, and our goal is to create a similar system for the USC Digital Library. The proposed usage analysis system will assist USC Digital Library employees and staff in evaluating image/document usage and impacts by providing a mechanism with which to cluster related images and analyzing archive user trends. The library staff can gain better understandings of item relationships, current archive usage, and user trends over periods of time. These analyses will contribute to the USC Digital Library's continual efforts to modify archive collections in order to satisfy user needs and improve library services.
3.1 Organization Background
The USC Library is part of the USC Information Services Division (USC-ISD), which is responsible for USC's networking, library services, academic computing, and telecommunications. The Resources and Services Group of the USC-ISD will manage the USC Digital Archive Usage Analysis System and its data collection, while the development of the system will be taken care of by USC graduate students. Researchers at the Old Dominion University will use the information and analyses provided by the USCISD for their on-going research.
3.2 Organization Goals
The broad, high-level objectives of the USC Library in relation to Data Mining of Digital Library Usage Data are summarized below:
Table 6: Organization Goal Form #1
Goal Identifier: Organization Goal: Description: Measurable: Relevant:
OG-1 New usage trends evaluation Use log data and item relationships analysis to monitor digital archive usage trends, etc. Compare the set of items relationships with previous period (OCD 2.1) Digital archive usage trend evaluation serves as a reference for assist library staff to improve digital archive over time (OCD 3.1)
OCD_LCO_F04a_T07_V4.1.doc
Page 16 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
Table 7: Organization Goal Form #2
Goal Identifier: Organization Goal: Description: Measurable: Relevant:
OG-2 Improved current usage evaluation Use log data and item relationship analysis to retrieve current archive usage. Compare the set of item collection with previous results (OCD 2.1) Improved current archive usage evaluation serves as a reference for assist library staff to have improve digital archive (OCD 3.1)
Table 8: Organization Goal Form #3
Goal Identifier: Organization Goal: Description: Measurable: Relevant:
OG-3 Better understandings of current archive collection structure Use archive items information to create an overall archive collection structure Compare current archive collection structure with previous results (OCD 2.1) Better understandings of current archive collection structure can help to move more relevant improvements on archive collection (OCD 3.1)
3.3 Current Organization Environment
The following describes the current organization environment of the USC Information Services Division (USC-ISD). These include the structure, artifacts, processes, rules, and shortcomings of USC-ISD.
3.3.1 Structure
The following describes the current workers of the organization and the outside actors that interact with the organization.
OCD_LCO_F04a_T07_V4.1.doc
Page 17 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
11
,,
22
7
8
% 7 , %
11
,,
22 11 ,, 22
11
# , 22
% ! ( / &&
(
)
##
# ,
Figure 3: Business-Structure Diagram of Current Organization Structure
9
97 8 %
:
#
#
97
, %
9
"
#
&
##
9%
# # , ; # ""
9% $94 9! (/ && # & ##
( ) # ,
##
OCD_LCO_F04a_T07_V4.1.doc
Page 18 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
Figure 4: Business-Collaboration Diagram of Current Organization Structure
3.3.1.1 Project Manager
Project managers work in the USC-ISD, and they are responsible for managing projects and systems that are currently under development or that have already been built. They also manage systems that were acquired from outside resources. For the digital library system, the project managers take charge of every aspects of the implementation of the digital library system, and they also request usage data from the system administrator.
3.3.1.2 Program Manager
The system administrator of the usage analysis system will be the USC-ISD program manager who oversees the Data Mining of Digital Library Usage Data project. The system administrator will manage the day-to-day operations of the digital library, once the system is in full operation.
3.3.1.3 Digital Library Staffs
Digital library faculty and staff contribute to the management of the USC Digital Library. They are responsible for maintaining and enhancing the digital library system, evaluating user logs and trends, and making enhancement proposals for discussion.
3.3.2 Artifacts
The following describes current artifacts inspected, manipulated, or produced by the organization.
11* #
##
22
0#
) #
##
22
11/ "
##
< <
(
!
Figure 5: Business-Artifacts Diagram of Current Organization Artifacts
OCD_LCO_F04a_T07_V4.1.doc
Page 19 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
3.3.2.1 Usage Analysis Report
The USC-ISD produces digital library usage reports regularly. Based on these reports, the digital library staff can make improvements to the digital archive. The reports will be distributed to all digital library staff members during regularly scheduled meetings, in which they will discuss potential improvements that can be made to the digital library.
3.3.2.2 Log Data
The USC-ISD updates log data regularly, which includes information such as user's IP, item id and time of retrieval. These log files will then be imported by the log analysis system to produce the usage analysis report. Based on these reports, the digital library staff can see all user activities in the digital archive. The set of log data will be distributed to all digital library staff members during regularly schedule meetings, in which they will discuss about potential improvements that can be made to the digital library.
3.3.3 Processes
The digital library staff holds meetings regularly to evaluate data usage and discuss improvements to the digital archive. For the most part, data usage evaluation is performed manually, and evaluations, for example, are based on the number of hits to the digital archive.
11/ #
## #
# ,
22
6
7
## #
!
(/
&&
11* # ## 0 # # 22
3 , 3, "
11/ #
## #
# 22
4
#
"
OCD_LCO_F04a_T07_V4.1.doc
Page 20 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
Figure 6: Business Use-Case Diagram of Current Organization Process
3.3.3.1 Evaluate Item Importance
(
!
7 !
(
#
Figure 7: Business Activity Diagram of Current Organization Process #1
Table 9: Business Use-Case Description #1 Identifier Use-Case Name Purpose Overview Organizational Goals Process-01 Evaluate item importance Evaluate item importance Digital Library staff get the number of hits for all items, and evaluate usage based on that information Better understandings of current archive collection structure
OCD_LCO_F04a_T07_V4.1.doc
Page 21 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
Priority Abstract Actors Pre-conditions Post-conditions Specializes Includes Extends Extension Points Priority
High No Digital Library Staff Digital Library staff can get the number of hits for all documents Digital Library staff make their evaluations on digital library usage No No No No High
3.3.3.2 Generate Usage Report
"
= # && ,
/ #
6 & ,
#
OCD_LCO_F04a_T07_V4.1.doc
Page 22 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
Figure 8: Business Activity Diagram of Current Organization Process #2 Table 10: Business Use-Case Description #2 Identifier Use-Case Name Purpose Overview Organizational Goals Priority Abstract Actors Pre-conditions Post-conditions Specializes Includes Extends Extension Points Priority Process-02 Generate Usage Report Evaluate log data to access digital archive usage trend Digital Library staff get the number of hits to the digital library, and observe usage pattern Better understandings of current archive collection structure High No Digital Library Staff Digital Library staff can get the number of hits to the digital library by library users Digital Library staff make their evaluations on digital library usage No No No No High
3.3.4 Rules
The organization must satisfy copyright law, which prohibits distribution or reproduction, in any digital form, of copyrighted music, video, or other multimedia contents without the express written permission of the material's rightful owner.
3.3.5 Shortcomings
The currently usage analysis only uses hit counts as the basis of evaluation. This does not provide library staff with meaningful information about library usage trends, and thus is not very helpful in enhancing library services. Digital library users at times are frustrated by the search results when they look for relevant information. To strive for service improvements, the current method of usage analysis should include more information and in-depth analysis about usage trends, document clustering, and impact rankings. Then the digital library staff can read these analyses and make improvements based on the digital library's usage patterns.
OCD_LCO_F04a_T07_V4.1.doc
Page 23 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
4. Proposed System
This section depicts the proposed system for Data Mining of Digital Library Usage Data and explains what the system is, what it performs and how well it performs.
4.1 Statement of Purpose
The USC library staff needs a digital archive usage analysis system which can provide a more detailed analysis than a simple web metrics system. Our proposed system can retrieve necessary data from the digital library archive and perform suitable analysis on user trends, impact ranking, and image/document clustering. These analyses will have digital library staff to gain in-depth knowledge about digital archive usage trends, archive collection structure, and item relationships. These will help digital library staff to make further improvements to the USC Digital Library's services.
4.2 Project Goals and Constraints
The main goals and constraints that are critical to the project's success are described below:
4.2.1 Limited Schedule
Table 11: Project Goals and Constraints Form #1
Project Goal: Description: Measurable: Relevant: Specific:
PG-1: Limited Schedule The system must be completed within 24 weeks Successful completion of the system by week 24 Compatible with rapid completion constraint (OCD 2.4) The system must be completed within 24 weeks (OCD 2.4)
4.2.2 Service Compatibility
Table 12: Project Goals and Constraints Form #2
Project Goal: Description:
PG-2: Service Compatibility The new system must be compatible with the current USC Digital Library
Page 24 of 47 Version date 10/25/2004
OCD_LCO_F04a_T07_V4.1.doc
Operational Concept Description(OCD)
Version 4.1
service. Measurable: Relevant: Specific: Information displays in the new system is consistent with the current service Compatible with existing system (OCD 2.4) Compatible with existing system (OCD 2.4)
4.2.3Package Compatibility
Table 13: Project Goals and Constraints Form #3
Project Goal: Description: Measurable: Relevant: Specific:
PG-3: Package Compatibility The system must be compatible with open-source packages Successful establishment of connections between open-source packages and new modules Compatible with open-source constraint (OCD 2.4) Use of open-source package for development (OCD 2.4)
4.3 System Capabilities
The new USC Digital Library Usage Analysis System will provide a brand-new usage analysis system to all digital library employees and staff, and they can study the views and perspectives of a given digital library user community using the data collected by the system. The capabilities listed below are broad categories of the analysis system, and these should realize the high-level services described in the System Boundary and Environment (OCD 2.3).
OCD_LCO_F04a_T07_V4.1.doc
Page 25 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
<<capability>> Generate item relationships <<capability>> Import usage data 11 6 " / , 22 # "#
5 #
Digitial Library Staff
Figure 9: Use-Case Model of System Capability
4.3.1 Import Usage Data
Table 14: System Capability Form #1
Identifier Name Description Importance Use In Priority
SC-01 Import Usage Data Import archive usage data from the ISD database server Primary TBD High. This is the essential component of the archive usage analysis.
OCD_LCO_F04a_T07_V4.1.doc
Page 26 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
4.3.2 Generate Item Relationships
Table 15: System Capability Form #2
Identifier Name Description Importance Use In Priority
SC-02 Generate item relationships Use algorithm proposed by Dr. Johan Bollen to analyze digital item relationships Primary TBD High. This is the essential component of the archive usage analysis.
4.3.3 Visualize Item Relationships
Table 16: System Capability Form #3
Identifier Name Description Importance Use In Priority
SC-03 Visualize item relationships Generate graphical views of item relationships and collection structure Primary TBD High. This is the essential component of the archive usage analysis.
4.4 Levels of Service (L.O.S.) Goals
The following describes the levels of service goals for the usage analysis system. Table 17: Level of Service Specification Form #1 Level of Service: Description: Measurable: Relevant: Specific: Stable database connection The system should maintain connection with database at all times. Connectivity can achieve 99.9% up-time Stable and reliable connection between database and host System regularly retrieve usage log data from the database
OCD_LCO_F04a_T07_V4.1.doc
Page 27 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
Priority:
High
Table 18: Level of Service Specification Form #2 Level of Service: Description: Measurable: Relevant: Specific: Priority: System maintenance System should not crash or restart unexpectedly System can achieve 99.9% up-time Build an usage analysis system that is robust System regularly perform usage log analyses High
Table 19: Level of Service Specification Form #3 Level of Service: Description: Measurable: Relevant: Specific: Priority: Usable data for library staff Data should be organized in a way that is meaningful to both library staff and researchers. Library staff will provide usability feedback Provide meaningful datasets Data must be presented in a meaningful way so that it can be used as a basis for researches High
Table 20: Level of Service Specification Form #4 Level of Service: Description: Measurable: Relevant: Specific: Priority: Provide user-friendly interfaces for viewing item relationships and updating data Provide user-friendly interfaces for viewing item relationships and updating data User will provide usability feedback Import usage data View results of usage analyses Bad interfaces mislead users high
OCD_LCO_F04a_T07_V4.1.doc
Page 28 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
4.5 Changes in the Organization Environment Due to Proposed System
The following sections describe how the new usage analysis system changes the environment of the organization. This includes the structure, artifacts, processes, rules, and how the new system remedies the shortcomings of the organization's current environment and system.
4.5.1 Structure
The following sections describe how the new usage analysis system will change organization's architecture.
11
,,
22
7
11 ,,
8
% 11
22
. 22 ) , #
11 11 ,, 22
&( 11
,,
) ## # # , . 22
22
0#
11 # , 22
0#
(
)
##
# ,
! 11
( / . 22
&&
# 11 22
Figure 10: Business-Structure Diagram of Future Organization Structure
OCD_LCO_F04a_T07_V4.1.doc
Page 29 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
9 97 8 % 11 9 " # & . 22 ##
:
#
#
##
9) ,
#
&(
)
### # , 11 . 22
9%
# # , ; # ""
90 #
$94
#
&
##
90 # ( ) ## # , 11# # , 22
Figure 11: Business-Collaboration Diagram of Future Organization Structure
4.5.1.1 New Workers and Outside actors
4.5.1.1.1
Researchers
Researchers who conduct researches in digital archives can acquire analyses and reports on archive usage analysis from the USC-ISD. They will interact with digital library staffs when they need information for their researches.
4.5.1.2 Changed Workers and Outside actors
4.5.1.2.1
Administrator of Log Analysis System
The Log Analysis System Administrator for the new system is essentially the ISD program manager of current organization. However, system administrator will have more control of the analysis process, such as logging onto the new system, importing log data and running usage analysis.
OCD_LCO_F04a_T07_V4.1.doc
Page 30 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
4.5.1.3 Deleted Workers and Outside actors
There are no deleted workers or outside actors
4.5.2 Artifacts
The following sections describe how the new usage analysis system will change the organization's artifacts.
11/ #
##
22
)
,
0#
)
<
##
"
< <
11/ #
##
22
(
!
< 11/ # ## 22
#
!
,
#
Figure 12: Business-Artifacts Diagram of Future Organization Artifacts
4.5.2.1 New Artifacts
4.5.2.1.1
Research Documents
Digital archive researchers (especially Dr. Johan Bollen of Old Dominion University), will be using analyses generated by the new system for their researches. Future research documents on digital archive may contain information from the USC digital library.
4.5.2.2 Changed Artifacts
The following describes the changed artifacts that appear because of the new usage analysis system.
OCD_LCO_F04a_T07_V4.1.doc
Page 31 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
4.5.2.2.1
Automated Usage Analysis Report
The USC-ISD will automate digital library usage reports by using the proposed usage analysis system. The system will produce reports based on log data and document rankings. Then digital library staff can make improvements to the digital archive, and they will discuss potential improvements that can be made to the digital library.
4.5.2.3 Deleted Artifacts
There are no deleted artifacts.
4.5.3 Processes
The following sections describe how the new usage analysis system will change the organization's processes. A new process has been added because of the system.
4.5.3.1 New Processes
The following describes organization processes that have been added because of the new usage analysis systems
4.5.3.1.1
Usage Log Analysis and Report Generation
Table 21: Business Use-Case Description (New Process) #1 Identifier Use-Case Name Purpose Overview Organizational Goals Process-10 Usage Log Analysis and Report Generation Generate usage data analysis reports between a specific timeframe Report the analyses conducted and displayed by the usage analysis system New usage trend evaluation Improved current usage evaluation Better understandings of current archive collection structure Priority Abstract Actors Pre-conditions High No Administrator of Log Analysis System System administrator asks for analysis reports on system usage between specific times
OCD_LCO_F04a_T07_V4.1.doc
Page 32 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
Post-conditions Specializes Includes Extends Extension Points Priority
System administrator selects the timeframe. No No No No High
; ## "
) (
## & !
4 ) ## "
Figure 13: Business Activity Diagram of Future Organization Process #1
OCD_LCO_F04a_T07_V4.1.doc
Page 33 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
4.5.3.2 Changed Processes
There are no changed processes.
4.5.3.3 Deleted Processes
The following describes organization processes that have been deleted because of the new usage analysis systems.
4.5.3.3.1
Evaluate Item Importance
The new process "Usage Log Analysis Report Generation" automates the evaluation of item relevancy and thus the current process of manual evaluate is unnecessary.
4.5.3.3.2
Generate Usage Report
The new process "Usage Log Analysis and Report Generation" automates the generation of usage report and thus the current process of manual report generation is unnecessary.
4.5.4 Rules
The following sections discuss any changes to the policies or constraints that must be satisfied by the organization.
4.5.4.1 New Rules
No new rules need to be carried out.
4.5.4.2 Changed Rules
No rules need to be changed.
4.5.4.3 Deleted Rules
No rules need to be deleted.
OCD_LCO_F04a_T07_V4.1.doc
Page 34 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
4.5.5 How New System Cures Current Shortcomings
Successful development and installation of the proposed system will address the shortcoming by providing a justification as to which documents are more relevant than others and which documents have been accessed by most digital archive users. This helps digital library staff to accurately evaluate digital archive usage and enhance services.
4.6 Effect on Organizations' Support Operation
4.6.1 Operational Stakeholders
The figure below shows the responsibility relations between the various organizations involved in the software life cycle process, and identifies the key responsible personnel within each organization.
Figure 14: Organization Chart #1
OCD_LCO_F04a_T07_V4.1.doc
Page 35 of 47
Version date 10/25/2004
Operational Concept Description(OCD)
Version 4.1
4.6.2 Organizational Relationships
The USC-ISD is responsible for providing computing support and electronic services to the USC community. Specifically, the Information Data Management Department (IDM) under the USC-ISD is responsible for managing projects and systems, which include the digital library and the digital archive. Within IDM, there are project sponsors, project managers, program managers, directors, and implementation teams. They are responsible for funding, managing, overseeing, directing, and implementing projects, respectively. The USC-ISD is committed to bringing the USC community high quality technological services, and IDM realizes such commitment by building and maintaining computer systems that satisfy the needs of the USC community. An example of this is to provide and enhance digital library services.
Figure 15: Organization Chart #2
...