Journal of Software - Academy Publisher

More documents

Recommendations

Info

An Improved Fuzzy C-means Clustering Algorithm based on PSO Qiang Niu and Xinjian Huang Classification of Bio-potential Surface Electrode based on FKCM and SVM Hao Liu, Xiaoming Tao, Pengjun Xu, and Guanxiong Qiu Consonant Recognition of Dysarthria Based on Wavelet Transform and Fuzzy Support Vector Machines Zhuo-ming Chen, Wei-xin Ling, Jian-hui Zhao, and Tao-tao Yao ELECTRE I Decision Model of Reliability Design Scheme for Computer Numerical Control Machine Jihong Pang, Genbao Zhang, and Guohua Chen Fractional Modeling Method Research on Education Evaluation Chunna Zhao, Yu Zhao, Liming Luo, and Yingshun Li Immune Genetic Evolutionary Algorithm of Wavelet Neural Network to Predict the Performance in the Centrifugal Compressor and Research Shengzhong Huang Development of Optimization Design Software for Bevel Gear Based on Integer Serial Number Encoding Genetic Algorithm Xiaoqin Zhang, Yu Rong, Jingjing Yu, Liling Zhang, and Lina Cui Study on Operating Mechanisms and Dynamics Behavior of Agile Supply Chain Guohua Chen, Genbao Zhang, and Jihong Pang Unified Service Platform for Accessing Grid Resources Shaochong Feng, Yuanchang Zhu, and Yanqiang Di Research on an Improved Terrain Aided Positioning Model Shidan Li, Liguo Sun, Xin Li, and Desheng Wang Research on Integrated Information Platform of Agricultural Supply Chain Management Based on Internet of Things Yan-e Duan 873 880 887 894 901 908 915 923 930 937 944
JOURNAL OF SOFTWARE, VOL. 6, NO. 5, MAY 2011 747 User Requirements Notation: The First Ten Years, The Next Ten Years Abstract—The User Requirements Notation (URN), standardized by the International Telecommunication Union in 2008, is used to model and analyze requirements with goals and scenarios. This paper describes the first ten years of development of URN, and discusses ongoing efforts targeting the next ten years. We did a study inspired by the systematic literature review approach, querying five major search engines and using the existing URN Virtual Library. Based on the 281 scientific publications related to URN we collected and analyzed, we observe a shift from a more conventional use of URN for telecommunications and reactive systems to business process management and aspect-oriented modeling, with relevant extensions to the language being proposed. URN also benefits from a global and active research community, although industrial contributions are still sparse. URN is now a leading language for goal-driven and scenario-oriented modeling with a promising future for many application domains. Index Terms—Goals, Goal-oriented Requirement Language (GRL), modeling, review, scenarios, tools, Use Case Maps (UCM), User Requirements Notation (URN) I. INTRODUCTION The User Requirements Notation (URN) is a modeling language that aims to support the elicitation, analysis, specification, and validation of requirements. URN is the first international standard to address explicitly, in a graphical way and in one unified language, goals and scenarios, and the links between them [106]. URN models can be used to specify and analyze various types of reactive systems as well as telecommunications standards and business processes. URN allows software and requirements engineers as well as business analysts to discover and specify requirements for a proposed system or process (or evolving ones), and analyze such requirements for correctness and completeness. The kind of modeling supported by URN is different from the detailed specification of “how” functionalities are to be supported, as described with languages such as UML [146]. Here the modeler is primarily concerned with exposing “why” certain choices for behavior and/or structure were introduced, combined with an abstract view of “what” capabilities and architecture are required. The modeler is not yet interested in the operational details of internal component behavior or component interactions. Omitting these kinds of details during early development allows working at a higher level of abstraction when modeling a current or future software © 2011 ACADEMY PUBLISHER doi:10.4304/jsw.6.5.747-768 (Invited Paper) Daniel Amyot and Gunter Mussbacher University of Ottawa, Canada Email: {damyot, gunterm}@site.uottawa.ca system, business process, or standard, and its embedding environment. Modeling and answering “why” questions leads us to consider the opportunities stakeholders seek out and vulnerabilities they try to avoid within their environment, whereas modeling and answering “what” questions helps identify capabilities, services, and architectures required to satisfy stakeholder goals. Based on a systematic literature review, this paper provides a historical perspective on the development of URN together with trends related to future constructs and application domains for this notation. Such study is important at this point not only to appreciate the richness of URN and the substantial body of work that already exists, but also to step back, understand current trends, and anticipate future needs for evolving the notation in the right direction. Section II introduces URN’s basic concepts and notational elements, together with its standard analysis techniques. As it is important to understand why URN was created, a historical description of the origins of the notation is presented in Section III. Then, Section IV summarizes the main results of our literature survey, especially with regards to the sources of contributions to URN. In Section V, some of the main research contributions that have shaped URN in the past decade are categorized and reviewed, whereas section VI identifies current and future development activities and research areas related to URN for the next decade. Finally, section VII provides our conclusions. II. OVERVIEW OF URN The User Requirements Notation standard combines two sub-languages [106]: the Goal-oriented Requirement Language for modeling actors and their intentions, and the Use Case Maps notation for describing scenarios and architectures. In this section, we give a brief overview of each of these sub-languages, supported by a simple URN model example that targets the evaluation of an architectural decision about where to put the data and the logic of the authorization service of a wireless system. A. Goal-oriented Requirement Language (GRL) GRL is a visual modeling notation for intentions, business goals, and non-functional requirements (NFR) of many stakeholders, for alternatives that have to be considered, for decisions that were made, and for rationales that helped make these decisions.
Page 1: Journal of Software ISSN 1796-217X
Page 5 and 6: JOURNAL OF SOFTWARE, VOL. 6, NO. 5,
Page 53 and 54:
JOURNAL OF SOFTWARE, VOL. 6, NO. 5,
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 82 and 83:
826 JOURNAL OF SOFTWARE, VOL. 6, NO
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Aims and Scope. Call for Papers and
show all

Journal of Software - Academy Publisher

Create successful ePaper yourself

Delete template?

Save as template?