@phdthesis{oai:sucra.repo.nii.ac.jp:00018911, author = {ZHOU, Yuan}, month = {}, note = {xii, 207 p., Over two decades, many kinds of questionnaires, testing, and voting are performed in some completely electronic ways to do questions and answers on the Internet as Web applications, i.e. e-questionnaire systems, e-testing systems, and e-voting systems. E-questionnaire, e-testing, and e-voting systems are indispensable in society. On the one hand, the mutual collaboration of the stakeholders is the foundation for the development and operation of e-questionnaire, e-testing, and e-voting systems. There are many stakeholders involved in a variety of e-questionnaire, e-testing, and e-voting systems around the world. To address this situation, it is necessary to promote the effective communications among those stakeholders by a communication tool to easily link each stakeholder's requirements for systems and services of e-questionnaire, e-testing, and e-voting. However, until now there is no communication tool shared among the stakeholders of systems and services of e-questionnaire, e-testing, and e-voting. All the e-questionnaire, e-testing, and e-voting systems are designed, developed, used, and maintained in various ad hoc ways. As a result, the stakeholders are diffcult to communicate to implement the systems, because there is neither an exhaustive requirement list to have a grasp of the overall e-questionnaire, e-testing, and e-voting systems nor a standardized terminology for e-questionnaire, e-testing, and e-voting systems to avoid ambiguity. A specification language is a formal language used during systems analysis, requirement analysis, and system design to describe a system. Requirements specification is the first and main step of developing software, and the specification language is the most direct way to specify requirement specifications. In addition, owing to the demands for the requirement list and the terminology, a specification language is a better communication tool to solve communication problems. On the other hand, because e-questionnaire, e-testing, and e-voting have common processes, that is, from preparing questions, following by authenticating respondents, through submitting answers, and ending to analyzing, tallying, and declaring results, systems that provide e-questionnaire, e-testing, and e-voting services have common functions to do the processes. E-questionnaire, e-testing, and e-voting systems have lots in common. Thus, it is necessary to provide a specification language as a communication tool to provide exhaustive requirement list and standardized terminology for systems and services of e-questionnaire, e-testing, and e-voting so that the stakeholders can communicate easily and unambiguously, and deal with and describe the requirement specifications for three kinds of systems and services. When the stake-holders are using and working with an updating system, they are looking forward to a clever and automatic way to easily deal with the changes. The ideal state is that a tool as a generator automatically converting the formalized specifications to generate the e-questionnaire, e-testing, and e-voting systems. However, until now, there is no general-purpose specification language for specifying various e-questionnaire, e-testing, and e-voting systems in a unified format such that the stakeholders can communicate, understand and accept each other to create the requirement specifications. The existing specification languages Simple Survey System (SSS), IMS Question and Test Interoperability Specification (QTI), and OASIS Election Markup Language (EML) cannot solve the above problems, because based on their own motivations, they can neither cover e-questionnaire, e-testing, and e-voting systems nor specify exhaustive requirements of e-questionnaire, e-testing, and e-voting systems. This thesis proposes the first specification language, named “QSL,” with a standardized, consistent, and exhaustive list of requirements for specifying various e-questionnaire, e-testing, and e-voting systems. QSL can be used to provide a desirably exhaustive requirement list to the corresponding stakeholders, so that they can easily choose requirements and complete the requirement specifications. To propose QSL, firstly, we collected, analyzed, and summarized exhaustive requirements for systems and services of e-questionnaire, e-testing, and e-voting, which are extremely similar. There are 181 requirements for e-questionnaire systems, 169 requirements for e-testing systems, and 168 requirements for e-voting systems. We summarized 121 common requirements for e-questionnaire, e-testing, and e-voting systems. The exhaustive requirements are the fundament of QSL and based on the requirements, the stakeholders can choose requirements and complete the requirement specifications easily. Secondly, according to the investigations, we proposed QSL as a unified method to provide terminology and specifications of e-questionnaire, e-testing, and e-voting systems with a standardized, consistent, and exhaustive requirement list to solve the communication problems among the stakeholders. Thirdly, we evaluated the proposed QSL about description power to ensure its completeness manifesting in specifying various e-questionnaire, e-testing, and e-voting systems. Current QSL can cover more than 95% system requirements and 95.4% service requirements, and provides enough notations to describe the requirements for data portability, and can cover the existing specifications compared with the related works. The reasons of the rest requirements QSL cannot cover, on the one hand, they are not necessary requirements for QSL according to the motivation, and on the other hand, they are easy to extend QSL to cover them. Lastly, we proposed an alternative usage of QSL for data portability and implemented two real applications for QSL. QSL is used as a data format for data portability for a general-purpose e-questionnaire server to help conduct an e-questionnaire on different e-questionnaire systems, and for an offine e-testing environment to provide users with offine e-testing service to execute various offline e-testing. The applications can prove QSL is practical and available to be used to provide data format for data portability., Abstract i Acknowledgments iii List of figures xi List of tables xii 1 Introduction 1 1.1 Background and Motivation . . . . . . . . . . . . . . . . . . . . . . 1 1.2 Purpose and Objectives . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 Structure of This Thesis . . . . . . . . . . . . . . . . . . . . . . . . 4 2 Exhaustive Requirements of E-Questionnaire, E-Testing, and E-Voting Systems 5 2.1 Collecting Requirements of E-Questionnaire, E-Testing, and E-Voting Systems . . . . . . . . . . . . . . . . . . . 5 2.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3 QSL: A Specification Language for E-questionnaire, E-testing, and E-voting Systems 11 3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.2 QSL Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.3 QSL Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.4 An Example of QSL . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4 Evaluation about Description Power of QSL 20 4.1 Specifications for E-Questionnaire, E-Testing, and E-Voting Systems 20 4.2 Specifications for E-Questionnaire, E-Testing, and E-Voting on the Systems . . . . . . . . . . . . . . . . . . . 22 4.3 Specifications for Portable Data . . . . . . . . . . . . . . . . . . . . 23 4.4 Comparison with Related Works . . . . . . . . . . . . . . . . . . . . 24 4.5 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5 Applications for QSL 27 5.1 A Format of Data Portability . . . . . . . . . . . . . . . . . . . . . 27 5.1.1 ENQUETE-BAISE: a General-Purpose E-Questionnaire Server for Ubiquitous Questionnaire . . . . . . . . . . . . . . . . . . . . . . . 28 5.1.2 A General-Purpose Offline E-Testing Environment . . . . . . 29 5.2 Expectable Applications for QSL . . . . . . . . . . . . . . . . . . . 30 5.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 6 Conclusions 32 6.1 Contributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.2 Future works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Publications 34 References 36 Appendix 40 A QSL Specification (Version 3.1) 41 A.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 A.1.1 QSL Documentations . . . . . . . . . . . . . . . . . . . . . . 42 A.1.2 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 A.1.3 Overview of the Document . . . . . . . . . . . . . . . . . . . 43 A.1.4 Changes in this Version . . . . . . . . . . . . . . . . . . . . 43 A.1.5 Advantages of using QSL . . . . . . . . . . . . . . . . . . . . 44 A.1.6 How to use QSL . . . . . . . . . . . . . . . . . . . . . . . . . 45 A.2 QSL Grammar Outline . . . . . . . . . . . . . . . . . . . . . . . . . 45 A.2.1 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 A.2.2 Viewing Schemas . . . . . . . . . . . . . . . . . . . . . . . . 45 A.2.3 Schema Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 46 A.2.4 Namespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 A.2.5 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 A.3 QSL Core Component . . . . . . . . . . . . . . . . . . . . . . . . . 47 A.3.1 Terminology of QSL . . . . . . . . . . . . . . . . . . . . . . 47 A.3.2 Simple Types . . . . . . . . . . . . . . . . . . . . . . . . . . 51 A.4 QSL Schema Descriptions . . . . . . . . . . . . . . . . . . . . . . . 57 A.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 A.4.2 100-QSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 A.4.3 110-System . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 A.4.4 120-Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 A.4.5 210-Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 A.4.6 220-Security . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 A.4.7 230-Paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 A.4.8 240-Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 A.4.9 250-Environment . . . . . . . . . . . . . . . . . . . . . . . . 66 A.4.10 260-Participant . . . . . . . . . . . . . . . . . . . . . . . . . 67 A.4.11 270-Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 A.4.12 280-Function . . . . . . . . . . . . . . . . . . . . . . . . . . 69 A.4.13 310-SettingUp . . . . . . . . . . . . . . . . . . . . . . . . . . 70 A.4.14 311-Distributing . . . . . . . . . . . . . . . . . . . . . . . . . 75 A.4.15 312-Registering . . . . . . . . . . . . . . . . . . . . . . . . . 77 A.4.16 313-Submitting . . . . . . . . . . . . . . . . . . . . . . . . . 79 A.4.17 314-Collecting . . . . . . . . . . . . . . . . . . . . . . . . . . 83 A.4.18 315-Analyzing . . . . . . . . . . . . . . . . . . . . . . . . . . 84 A.4.19 316-Counting . . . . . . . . . . . . . . . . . . . . . . . . . . 85 A.4.20 320-Sponsor . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 A.4.21 321-Questioner . . . . . . . . . . . . . . . . . . . . . . . . . 88 A.4.22 322-Respondent . . . . . . . . . . . . . . . . . . . . . . . . . 89 A.4.23 323-Analyst . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 A.4.24 324-Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 A.4.25 330-Export . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 A.4.26 331-Import . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 A.4.27 332-Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 A.4.28 333-Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 A.4.29 334-Generate . . . . . . . . . . . . . . . . . . . . . . . . . . 96 A.4.30 335-Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 A.4.31 336-Integrate . . . . . . . . . . . . . . . . . . . . . . . . . . 98 A.4.32 337-Remind . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 A.4.33 340-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 A.4.34 341-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 A.4.35 342-Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . 108 A.4.36 343-Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 109 A.4.37 344-Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 A.4.38 345-Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 A.4.39 350-Anonymity . . . . . . . . . . . . . . . . . . . . . . . . . 113 A.4.40 351-Authentication . . . . . . . . . . . . . . . . . . . . . . . 115 A.4.41 352-Authority . . . . . . . . . . . . . . . . . . . . . . . . . . 118 A.4.42 353-Seal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 A.4.43 354-Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 A.4.44 360-Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 A.4.45 361-Question . . . . . . . . . . . . . . . . . . . . . . . . . . 121 A.4.46 362-Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 A.4.47 363-Description . . . . . . . . . . . . . . . . . . . . . . . . . 125 A.4.48 364-Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 A.4.49 365-Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . 127 A.4.50 366-Limitation . . . . . . . . . . . . . . . . . . . . . . . . . 128 A.4.51 370-Language . . . . . . . . . . . . . . . . . . . . . . . . . . 129 A.4.52 371-Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 A.4.53 372-Number . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 A.4.54 373-Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 A.4.55 374-Response . . . . . . . . . . . . . . . . . . . . . . . . . . 133 A.4.56 375-Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 A.4.57 410-Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 A.4.58 510-Marking . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 A.4.59 520-Score . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 A.4.60 530-Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 A.4.61 540-Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 A.4.62 550-Marker . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 A.4.63 610-Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . 144 A.4.64 620-Candidate . . . . . . . . . . . . . . . . . . . . . . . . . . 146 A.4.65 630-Proposer . . . . . . . . . . . . . . . . . . . . . . . . . . 147 A.4.66 640-Auditor . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 A.5 Question Types Reference Guide . . . . . . . . . . . . . . . . . . . 149 A.5.1 Basic Question Types . . . . . . . . . . . . . . . . . . . . . . 149 A.5.2 Possible Combinations of Question Types . . . . . . . . . . . 160 A.6 Logic Types Reference Guide . . . . . . . . . . . . . . . . . . . . . 169 A.6.1 Basic Logic Types . . . . . . . . . . . . . . . . . . . . . . . 169 A.6.2 Possible Combinations of Logic Types . . . . . . . . . . . . 177 B Requirements for Systems and Services of E-Questionnaire, E-Testing, and E-Voting 186 B.1 Requirements for Common Systems . . . . . . . . . . . . . . . . . . 186 B.2 Requirements for E-Questionnaire Systems . . . . . . . . . . . . . . 191 B.3 Requirements for E-Testing Systems . . . . . . . . . . . . . . . . . 192 B.4 Requirements for E-Voting Systems . . . . . . . . . . . . . . . . . . 194 B.5 Requirements for Common Services . . . . . . . . . . . . . . . . . . 197 B.6 Requirements for E-Questionnaire Services . . . . . . . . . . . . . . 201 B.7 Requirements for E-Testing Services . . . . . . . . . . . . . . . . . . 204 B.8 Requirements for E-Voting Services . . . . . . . . . . . . . . . . . . 206, 指導教官 : 後藤祐一, text, application/pdf}, school = {埼玉大学}, title = {QSL: A Specification Language for E-Questionnaire, E-Testing, and E-Voting Systems}, year = {2019}, yomi = {シュウ, ゲン} }