Title: Plan for Architectural Analysis for Identifying Query
1Plan for Architectural Analysis for Identifying
Query Retrieval Components
2Component types needed to support Query
Retrieval
Query Retrieval Architecture
3Online Data Viewing Components
- Purpose
- For viewing details of the selected or retrieved
(hit list) record - Examples
- Grant Update Module (GUM) screens read only
- Application block Review details block
- Admin. review block Edit PI
- Budget block Addresses
- CAN SBIR/STTR BAD codes
- QuickView screens
- Overview PI/Staff Organization
- Budget Budget detail Award detail
4QV Overview Screen
GUM Applic. Admin. Review Blocks
5Output Method Components
- Purpose
- Methods for receiving output results
- Examples
- Print Central
- Merge Zip
- Export hit list to Excel
- Generate report print
- Export report to Excel
- View document print
- View and Print from Grant Folder
- Burn CD
6(No Transcript)
7Output Format Components
- Purpose
- Formats for receiving output after identifying
desired query results - Examples
- Fixed report
- Manipulable/exportable report (Discoverer)
- Labels report
- Form template report w/pre-printed info.
- PDF Document
- ASCII file
- Data for spreadsheet
- CD
8(No Transcript)
9Query Components
- Purpose
- For facilitating user query
- Examples
- Individual query fields
- Lists of Values (LOVs)
- Special Selects (active grant, animal concern,
etc.) - Default query blocks (QuickView, Grant Mgmt.)
- Customizable query (ICSTORe Adv.Query)
- Special Views (PowerViews)
10(No Transcript)
11Hit List Components
- Purpose
- For viewing query results to identify desired
records and for viewing retrieved information - Examples
- Default Hit Lists (ICSTORe, Review, CRISP)
- Customizable Hit List (ICSTORe)
- Sort buttons as column headers
- Select checkbox with Select all/Deselect all
- Order number column with resequencing
- Book Definition
- Nested sorts
- Sections with different sorts
- Sort by value
- Ascending/descending sort option
-
12(No Transcript)
13Requirements for Universal Query Tool
Architecture
- Different categories of users have different
requirements for query and retrieval, - making a single user interface impractical.
- The purpose of this analysis is to identify
requirements for different query retrieval
interfaces and their common components.
14Types of Users
- Scientific Query Users
- Regular
- Power
- Advanced Query Users (ICSTORe)
- Business Area Specific Users
15Types of Users, cont.
- Document Tracking Users
- Program/IC Portfolio Users
- Peer Review Users
- Finance Budget Users
- Program Analysis Users
16Query Tools Access Methods
- ICSTORe- Tack Order
- ICSTORe Book Definition
- ICSTORe Advanced Query
- QuickView
- CRISP Plus
- IQR
- CRISP on the Web
- QVR
- ECB
- Ad Hoc Query
- Commons Status
- IRDB TechView
- IMPP TechView
- Business Area Specific Screens
17Query Tools Methods
Categories of Users
- QuickView Status Users
- Scientific Query Users
- Regular
- Power
- Advanced Query Users
- Business Area Specific Users
- Document Tracking Users
- Program/IC Portfolio Users
- Peer Review Users
- Finance Budget Users
- Program Analysis Users
- ICSTORe- Tack Order,
- ICSTORe Book Definition
- ICSTORe Advanced Query
- QuickView
- CRISP Plus
- IQR
- CRISP on the Web
- QVR
- ECB
- Ad Hoc Reporting
- Commons Status Reporting
- IRDB TechView
- IMPP TechView
- Business Area Query Screens
18Query Tools Methods
Categories of Users
- QuickView Status Users
- Scientific Query Users
- Advanced Query Users
- Business Area Specific Users
- Document Tracking Users
- Program/IC Portfolio Users
- Peer Review Users
- Finance Budget Users
- Program Analysis Users
- ICSTORe- Tack Order,
- ICSTORe Book Definition
- ICSTORe Advanced Query
- QuickView
- CRISP Plus
- IQR
- CRISP on the Web
- QVR
- ECB
- Ad Hoc Reporting
- Commons Status Reporting
- IRDB TechView
- IMPP TechView
- Business Area Query Screens
19Categories of Users
Query Tools Methods
- QuickView Status Users
- Scientific Query Users
- Advanced Query Users
- Business Area Specific Users
- Document Tracking Users
- Program/IC Portfolio Users
- Peer Review Users
- Finance Budget Users
- Program Analysis Users
- ICSTORe- Tack Order,
- ICSTORe Book Definition
- ICSTORe Advanced Query
- QuickView
- CRISP Plus
- IQR
- CRISP on the Web
- QVR
- ECB
- Ad Hoc Reporting
- Commons Status Reporting
- IRDB TechView
- IMPP TechView
- Business Area Query Screens
20Categories of Users
Query Tools Methods
- QuickView Status Users
- Scientific Query Users
- Advanced Query Users
- Business Area Specific Users
- Document Tracking Users
- Program/IC Portfolio Users
- Peer Review Users
- Finance Budget Users
- Program Analysis Users
- ICSTORe- Tack Order,
- ICSTORe Book Definition
- ICSTORe Advanced Query
- QuickView
- CRISP Plus
- IQR
- CRISP on the Web
- QVR
- ECB
- Ad Hoc Reporting
- Commons Status Reporting
- IRDB TechView
- IMPP TechView
- Business Area Query Screens ICO
21Categories of Users
Query Tools Methods
- QuickView Status Users
- Scientific Query Users
- Advanced Query Users
- Business Area Specific Users
- Document Tracking Users
- Program/IC Portfolio Users
- Peer Review Users
- Finance Budget Users
- Program Analysis Users
- ICSTORe- Tack Order,
- ICSTORe Book Definition
- ICSTORe Advanced Query
- QuickView
- CRISP Plus
- IQR
- CRISP on the Web
- QVR
- ECB
- Ad Hoc Reporting
- Commons Status Reporting
- IRDB TechView
- IMPP TechView
- Business Area Query Screens
22Categories of Users
Query Tools Methods
- QuickView Status Users
- Scientific Query Users
- Advanced Query Users
- Business Area Specific Users
- Document Tracking Users
- Program/IC Portfolio Users
- Peer Review Users
- Finance Budget Users
- Program Analysis Users
- ICSTORe- Tack Order,
- ICSTORe Book Definition
- ICSTORe Advanced Query
- QuickView
- CRISP Plus
- IQR
- CRISP on the Web
- QVR
- ECB
- Ad Hoc Reporting
- Commons Status Reporting
- IRDB TechView
- IMPP TechView
- Business Area Query Screens (ICO)
23Categories of Users
Query Tools Methods
- QuickView Status Users
- Scientific Query Users
- Advanced Query Users
- Business Area Specific Users
- Document Tracking Users
- Program/IC Portfolio Users
- Peer Review Users
- Finance Budget Users
- Program Analysis Users
- ICSTORe- Tack Order,
- ICSTORe Book Definition
- ICSTORe Advanced Query
- QuickView
- CRISP Plus
- IQR
- CRISP on the Web
- QVR
- ECB
- Ad Hoc Reporting
- Commons Status Reporting
- IRDB TechView
- IMPP TechView
- Business Area Query Screens REV
24Categories of Users
Query Tools Methods
- QuickView Status Users
- Scientific Query Users
- Advanced Query Users
- Business Area Specific Users
- Document Tracking Users
- Program/IC Portfolio Users
- Peer Review Users
- Finance Budget Users
- Program Analysis Users
- ICSTORe- Tack Order,
- ICSTORe Book Definition
- ICSTORe Advanced Query
- QuickView
- CRISP Plus
- IQR
- CRISP on the Web
- QVR
- ECB
- Ad Hoc Reporting
- Commons Status Reporting
- IRDB TechView
- IMPP TechView
- Business Area Query Screens ICO
25Categories of Users
Query Tools Methods
- QuickView Status Users
- Scientific Query Users
- Advanced Query Users
- Business Area Specific Users
- Document Tracking Users
- Program/IC Portfolio Users
- Peer Review Users
- Finance Budget Users
- Program Analysis Users
- ICSTORe- Tack Order,
- ICSTORe Book Definition
- ICSTORe Advanced Query
- QuickView
- CRISP Plus
- IQR
- CRISP on the Web
- QVR
- ECB
- Ad Hoc Reporting
- Commons Status Reporting
- IRDB TechView
- IMPP TechView
- Business Area Query Screens ICO
26To retain the unique requirements of each
interface/access method while eliminating
unnecessary duplication
The Challenge
27Plan for Analysis
28Task 1 For each eRA Query tool and access
methods listed, complete a fact sheet that
describes the following
- Target community
- Primary objectives
- Unique or special features
- Other similar or overlapping tools
- Early recommendations on how to improve
- Components used for the following
- Online viewing
- Output methods
- Output format options
- Query parameter objects
- Query fields
- Hitlist options
- Sample for ICSTORe included
29Based on data collectedin Task 1, develop a
matrix that lists every component available and
show which tools/access methods use which
component.
Task 2
30Sample Task 2 MatrixComponent to Query Tool
Adv.Q
ICO
QV
QVR
Custom HL
custom hitlist
Custom Query
Dual PO
save Query
31Develop a matrix of query fields showing all
query fields availablein eRA query retrieval
tools, and show which tools use which query
fields. This will help identify duplicative
user interfaces and tools
Task 3
32Sample Task 3 MatrixQuery Field to Query Tool
PI
PO
PCC
IC
ICO
QV
CRISP
Adv.Q
QVR
33Task 4 Recommend
- Requirements for eRA Query Retrieval
- Components needed for new environment
- Duplicate and unnecessary objects to eliminate
- User Interfaces needed to satisfy unique
requirements for different categories of users - User Interfaces that can be
- merged to minimize
- duplication
- User Interfaces that should
- be eliminated
34What this analysis doesnt do
- Doesnt recommend design of needed components or
objects - It recommends only WHAT, not HOW!
Caution
- Analyses is limited to what already exists in eRA
- Must add to this new ideas!
35Mapping of needed components to needed user
interfaces
Task 5
36RAE Tool Analysis
37Sample Task 1 Fact Sheet for ICSTORe Track
Order Screen
- DEA office that tracks and files
Summary Statements within a Council
Round for IC - IC office that prepares
Council Books - Program Directors that track and file
Summary Statements within a Council Round for
portfolio
38Sample Task 1 Fact Sheet for ICSTORe Track
Order Screen, cont.
- Primary objectives
- Query
- Quick easy way for tracking Summary Statements
and other documents released within a Council
Round for the users primary duals applications - Hitlist
- Provides default hitlist for Track Order users
- Provides customizable hitlist for more advanced
users - Output format selection
- Provides Central Print at CIT for bulk printing
- Provides Merge and Zip PDF files for local
printing - Provides ability to export customized hitlist to
Excel
39Sample Task 1 Fact Sheet for ICSTORe Track
Order Screen, cont.
- Query on POs PCCs for users primary dual
applications - Queries by User ICs council date which may be
different from primary ICs council date - Tracking to easily identify docs released since
last check - Selection of desired document from drop-down list
(Sum.Stmnt.,Resume, Abstract) - Customizable Hitlist
- Central Print at CIT for bulk printing
- Merge and Zip PDF files for local printing
- Export customized hitlist to Excel
- Save and share named queries
40Sample Task 1 Fact Sheet for ICSTORe Track
Order Screen, cont.
- Other similar tool(s)
- QVR for output format options
- ICO for query by dual PO, PCC, and Council Date
- Early Recommendations
- Separate the query, hit list, and output format
selection - Separate selection of desired document from query
- Separate ordering from tracking
- Provide ability to save customized hit list with
a named query
41Sample Task 1 Fact Sheet for ICSTORe Track
Order Screen, cont.
- Components used
- Online viewing
- GUM
- Grant Folder
- Output methods
- View doc
- Merge/Zip doc
- Export hitlist to Excel
- Grant Folder
- Output format options
- Documents
- No reports
42Sample Task 1 Fact Sheet for ICSTORe Track
Order Screen, cont.
- Components used, cont.
- Query Parameter Objects
- Query parameters TBD
- Pull down lists
- Special selects (incl. Duals)
- Save/retrieve query
- Share queries (private vs. IC-specific)
- Query on POs and PCCs for users for primary
dual applications - Queries by Users ICs council date which may be
different from primary ICs council date - Tracking option to easily identify docs released
since last check
43Sample Task 1 Fact Sheet for ICSTORe Track
Order Screen, cont.
- Components used, cont.
- Hitlist
- Default hitlist for tracking Summary Statements
- Select desired document (Sum.Stmnt., Abstract,
Resume) - Customizable hitlist
- Sorting by column header buttons
- Select checkbox w/Select all/deselect all
- Order number
- Resequence by Order number
- Book Definition
- Divide hitlist in 2 sections with different sorts
- Nested sorting
- Ascending/Descending sorting by column
- Sort by value
- Save Book Definition