Mixed-Mode Sample i d d l Management System: An Management System: An Early Glance Gina Cheung The 11th International Blaise Conference Annapolis, Maryland September 2007
Four Powerful Social and Economic Forces 1 1. From homogeneity to heterogeneity From homogeneity to heterogeneity 2. From batch to flow 3 3. From fixed to adaptive F fi d t d ti 4. From centralized to decentralized to… a third way? Dr. Bob Groves, IBUC 2007 Keynote Speaker
Challenges from these Forces Challenges from these Forces • The customized survey design needs new The customized survey design needs new paradata to customize designs to sample units • Software functionality must be designed with y g responsive design in mind – real-time analysis of paradata – integrated statistical analyses to direct question flow or recruitment step actions • This requires centralization of information Thi i t li ti f i f ti resources, but dispersed use of the resources Dr. Bob Groves, IBUC 2007 Keynote Speaker
What is Paradata? What is Paradata? • Information that can be used for sample/case Information that can be used for sample/case management, such as: – Call records (result codes, call notes, time of contact, etc…) – Respondent information (address, phone numbers, respondent profile, etc…) respondent profile etc ) – Sample information (PSU, segment, sampling unit, etc) – Contact, Interview and household observation data Contact, Interview and household observation data – Interview key attributes (length of IW, break off variables, answers for some analysis variables, etc…) Survey Research Center • Institute for Social Research • University of Michigan
Vision for Mixed Mode Vision for Mixed Mode • A fully integrated mixed-mode sample (case) A fully integrated mixed mode sample (case) management system that allows sample movement, management, and reporting between collection modes, both prior to and during data collection. • Build on our success - capture the best features and functions of our existing sample management and other systems management and other systems . Survey Research Center • Institute for Social Research • University of Michigan
Current Situation Current Situation Survey Research Center • Institute for Social Research • University of Michigan
Proposed Solution Proposed Solution Survey Research Center • Institute for Social Research • University of Michigan
High-Level Concepts High-Level Concepts • Mixed-mode sample management system Mixed mode sample management system – Integrated system utilizing paradata – Paradata stored in a mode-neutral format Paradata stored in a mode neutral format – System will manage paradata Survey Research Center • Institute for Social Research • University of Michigan
High-Level Functional Requirements High-Level Functional Requirements • One logical system presenting a universal point of entry for the user for the user • Allow for different modes within same study • Flexibility for survey collection design • Real time paradata and survey data movement between • Real-time paradata and survey data movement between samples and interviewers • Track the status and life history of individual cases • Allow for transfer of cases between interviewers and All f t f f b t i t i d across modes and surveys • Allow for capture and management of metadata and paradata paradata • Centralized allocation, scheduling, and planning of resources based on skills, location, language, shift, etc. Survey Research Center • Institute for Social Research • University of Michigan
Development Process Development Process • Phase I – Requirements and Analysis q y • Phase II – Design, Develop, Test/Implement and Stabilize Stabilize – This phase will refine the requirements of the system and the system architecture and database structures, and will build and test a prototype in a pilot/production setting. p yp p p g • Phase III – Design, Develop, Test/Implement, Stabilize Stabilize – This will be a second round of activities, similar to that in Phase II, and will end with a stable production system with system documentation and training modules. Survey Research Center • Institute for Social Research • University of Michigan
Phase I Deliveries � Business Requirements Business Requirements � Features List � User Interface Prototype � User Interface Prototype � Flow Diagrams � Architectural Considerations � A hit t l C id ti � Architectural Design � Data Model � Technical Recommendation Survey Research Center • Institute for Social Research • University of Michigan
Business Requirements and Features (1) • 650 major requirements aggregated to 220 Features Features • Need to include more non-functional requirements i t • Focuses on the operational requirements of the entire mixed mode data collection Survey Research Center • Institute for Social Research • University of Michigan
Business Requirements and Features (2) • Grouped into 12 categories: G d i t 12 t i � Database and Device Management � I t � Interfacing with Other Systems f i ith Oth S t � Interviewing � Online Help � Production Management � Production Management � Production Support � Sample Delivery (Scheduler) � Sample Line Generation and Management p g � Security � Study Setup � Survey Support Services � U � User Interface I t f Survey Research Center • Institute for Social Research • University of Michigan
User Interface Prototype User Interface Prototype • Evolved from the business requirements, E l d f th b i i t SME (Subject Matter Experts) interaction ( j p ) and iterations • “Prototype, prototype…” Survey Research Center • Institute for Social Research • University of Michigan
Flow Diagrams – Use Cases Flow Diagrams Use Cases Survey Research Center • Institute for Social Research • University of Michigan
Industry Practices SRC Required Architectural Considerations Architectural Considerations Survey Research Center • Institute for Social Research • University of Michigan
Architecture Design Architecture Design • Services Oriented Architecture (SOA) Services Oriented Architecture (SOA) –A collection of services –Services communicate with each other Services communicate with each other –The communication can involve either simple data exchange or it could involve two or more services coordinating some activity • Web Services XML, UDDI, HTTP, SOAP Survey Research Center • Institute for Social Research • University of Michigan
SRC MMSMS Blaise Blaise Service
Thick Mobile Internet Other Client Client Client Client LAN Access Gateway
Categorical Relationship Diagram System Configuration Study/Project Study/Project User User Security Security Search Sample L User Interface Sample Line* N Help Scheduler Interview Reports
Technical Recommendations • Software development environment: Software development environment: Microsoft .NET Framework 3.x • Programming Language: C# • Programming Language: C# • SOA with Web Services for communication • Database: Microsoft SQL Server 2005 (2008?) • Replication Survey Research Center • Institute for Social Research • University of Michigan
Next Step Next Step • System design System design – Describes desired features and operations in detail including screen layouts business detail, including screen layouts, business rules, process diagrams, pseudo-code, and other documentation. • Implementation Survey Research Center • Institute for Social Research • University of Michigan
Thank You Thank You Gina Cheung qianyang@umich.edu i @ i h d Survey Research Center • Institute for Social Research • University of Michigan
Recommend
More recommend
