Back Room Front Room 2

More documents

Recommendations

Info

184 ENTERPRISE INFORMATION SYSTEMS VI ACKNOWLEDGMENTS This work was partially supported by the CyTED (Ciencia y Tecnología para el Desarrollo) project VII-J-RITOS2, by the UNComa project 04/E048, and by the MAS project supported by the Dirección General de Investigación of the Ministerio de Ciencia y Tecnología (TIC 2003-02737- C02-02). REFERENCES Alexander R. and Blackburn M., 1999. Component Assessment Using Specification-Based Analysis and Testing. Technical Report SPC-98095-CMC, Software Productivity Consortium. Allen P. and Frost S., 2001. Planning Team Roles for CBD. In Component-Based Software Engineering - Putting the Pieces Together, Addison-Wesley. Edited by G. Heineman and W. Council. Alves C., 2003. COTS-Based Requirements Engineering. In Component-Based Software Quality: Methods and Techniques, Springer-Verlag LNCS 2693. Alves C. and Filkenstein A., 2002. Challenges in COTS- Decision Making: A Goal-Driven Requirements Engineering Perspective. In Proceedings of the Fourteenth International Conference on Software Engineering and Knowledge Engineering, SEKE’02. Ballurio K., Scalzo B., and Rose L, 2002. Risk Reduction in COTS Software Selection with BASIS. In Proceedings of the First International Conference on COTS-Based Software Systems, ICCBSS 2002, Springer-Verlag LNCS 2255 , pp. 31-43. Boehm B., Bose P., Horowitz E., and Lee M., 1995. Software Requirements Negotiation Aids: A Theory- W Based Spiral Approach. In Proceedings of the 17 th International Conference on Software Engineering, pp. 243-253. Cechich A., Piattini M., and Vallecillo A., (eds.) 2003. Component-Based Software Quality: Methods and Techniques, Springer-Verlag LNCS 2693. Cechich A. and Piattini M., 2003. Defining Stability for Component Integration Assessment. In Proceedings of the 5th International Conference on Enterprise Information Systems, ICEIS 2003, pp. 251-256. Cechich A. and Piattini M., 2004. On the Measurement of COTS Functional Suitability. In Proceedings of the 3 rd International Conference on COTS-based Software Systems, ICCBSS 2004, Springer-Verlag LNCS. Chung L., Nixon B., Yu E., and Mylopoulos J., 2000. Non-Functional Requirements in Software Engineering. Kluwer Academic Publisher. Dardenne A., van Lamsweerde A., and Fickas S, 1993. Goal-directed Requirements Acquisition. Science of Computer Programming, Vol. 20, pp. 3-50. GRL homepage, http://www.cs.toronto.edu/k-m/GRL/ Hui B., Lisakos S., and Mylopoulos J., 2003. Requirements Analysis for Customizable Software: A Goals-Skills-Preferences Framework, In Proceedings of the 11 th IEEE International Requirements Engineering Conference, pp. 117-126. I* homepage, http://www.cs.toronto.edu/km/istar Kaiya H., Horai H., and Saeki M., 2002. AGORA: Attributed Goal-Oriented Requirements Analysis Method. In Proceedings of the IEEE International Conference on Requirements Engineering, pp. 13-22. KAOS homepage, http://www.info.ucl.ac.be/research/ projects/AVL/ReqEng.html Maiden N. and Ncube C., 1998. Acquiring COTS Software Selection Requirements. In IEEE Software, Vol. 15(2), pp. 46-56. Mylopoulos J., Chung L., and Yu E., 1999. From Object- Oriented to Goal-Requirements Analysis, Communications of the ACM, 42(1), pp. 31-37. Saaty T.L., 1990. The Analytic Hierarchy Process. McGraw-Hill. Sedigh-Ali S., Ghafoor A., and Paul R., 2001. Software Engineering Metrics for COTS-Based Systems. IEEE Computer Magazine, pp. 44–50.
A POLYMORPHIC CONTEXT FRAME TO SUPPORT SCALABILITY AND EVOLVABILITY OF INFORMATION SYSTEM DEVELOPMENT PROCESSES Isabelle Mirbel I3S Laboratory Les Algorithmes Route des Lucioles BP 121 06903 Sophia Antipolis Cedex FRANCE isabelle.mirbel@unice.fr Keywords: Information System, Method Engineering, Fragment, Reuse, Evolution Abstract: Nowadays, there is an increasing need for flexible approaches, adaptable to different kinds of Information System Development (ISD). But customization of ISD processes have mainly be thought of for the person in charge of building processes, i.e. the methodologists, in order to allow him/her to adapt the process to the need of its company or projects. But there is also a need for customizations dedicated to project team members (application engineers), to provide them with customized guidelines (or heuristics) which are to be followed while performing their daily task. The knowledge capitalization framework we propose supports evolvability and customization of ISD processes. Reuse and customization are handled through process fragments stored in a dedicated repository. Our purpose is not to propose a new way to built processes, as several approaches already exist on this topic, but to ease the use of existing ones by making them less rigid and allowing their adaptation to the need of the company, the project and most of all, the project team member. Therefore, in addition to a repository of process fragments, we propose a scalable and polymorphic structure allowing methodologists to define a working space through a context made of criterias. Thanks to this context the project team members better qualify their ISD problem in order to find a suitable solution. A solution is made of process fragments organized into a route-map specially built to answer the project team member need and directly usable by him/her. The context-frame we focus on in this paper is a scalable structure which supports evolution and tailoring by the methodologists for the project team member’s need with regards to project and process features. 1 INTRODUCTION Information System Development (ISD) is different each time, depending on the situation and context. A given technique, notation or mechanism may be used in a different way depending on the development under consideration. A process (or method) that has proved its power for certain kinds of development may be quite unsuitable for others. There is no universal applicability of processes (Ralyte, 2001). Therefore, there is a need for flexible approaches, adaptable to different kinds of development. The need for situation-specific processes, to better satisfy particular situation requirements, has already been emphasized (van Slooten and Hodes, 1996; Brinkkemper et al., 1998). Moreover, there is an increasing need for lightweight processes by opposition to heavyweight ones. Lightweight processes increase project team members (or application engineers) involvement on I. Seruca et al. (eds.), Enterprise Information Systems VI, © 2006 Springer. Printed in the Netherlands. 185 185–192. the contrary of heavyweight processes where the only significant choice is made by methodologists who chose the development process. Lightweight processes focus on finding the best way for the current situation. Project team members choose from as many alternative paths as possible. Indeed customization of ISD processes (Ralyte, 2001; Brinkkemper et al., 1998) have mainly be thought of for the person in charge of building a new process, i.e. the methodologists, in order to allow him/her to adapt the process to the need of its company or projects. But there is also a need for customizations dedicated to project team members, to provide them with guidelines (or heuristics) which are to be followed while performing their daily task (Gnatz et al., 2001; Mirbel and de Rivieres, 2002b). The adaptation is handled through the breaking down of guidelines (heuristics) into fragments, which may then be selected if they answer to the project team member need.
Page 1 and 2:
www.dbeBooks.com - An Ebook Library
Page 3 and 4:
A C.I.P. Catalogue record for this
Page 5 and 6:
vi TABLE OF CONTENTS PART 1 - DATAB
Page 7 and 8:
viii TABLE OF CONTENTS A WIRELESS A
Page 9 and 10:
CONFERENCE COMMITTEE Honorary Presi
Page 11 and 12:
Hung, P. (AUSTRALIA) Jahankhani, H.
Page 13 and 14:
Invited Papers
Page 15 and 16:
2 ENTERPRISE INFORMATION SYSTEMS VI
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
10 ENTERPRISE INFORMATION SYSTEMS V
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
EVOLUTIONARY PROJECT MANAGEMENT: MU
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
MANAGING COMPLEXITY OF ENTERPRISE I
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
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:
ASSESSING EFFORT PREDICTION MODELS
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
ORGANIZATIONAL AND TECHNOLOGICAL CR
Page 77 and 78:
Page 79 and 80:
ASAP Processes W Project Kickoff A
Page 81 and 82:
Page 83 and 84:
since it means changing the relevan
Page 85 and 86:
ACME-DB: AN ADAPTIVE CACHING MECHAN
Page 87 and 88:
ACME-DB: AN ADAPTIVE CACHING MECHAN
Page 89 and 90:
Hit Rate (%) ACME-DB: AN ADAPTIVE C
Page 91 and 92:
5.3.6 Effect on all Policies by Int
Page 93 and 94:
ACKNOWLEDGEMENTS We would like to t
Page 95 and 96:
This paper describes the data sampl
Page 97 and 98:
The major limit A of the operation
Page 99 and 100:
RELATIONAL SAMPLING FOR DATA QUALIT
Page 101 and 102:
TOWARDS DESIGN RATIONALES OF SOFTWA
Page 103 and 104:
((Brown et al., 1998), pp. 159-190,
Page 105 and 106:
sive data filtering, presentation (
Page 107 and 108:
• implementation changes in servi
Page 109 and 110:
MEMORY MANAGEMENT FOR LARGE SCALE D
Page 111 and 112:
Data Rate [bytes/sec] 1600000 14000
Page 113 and 114:
E.g., DV Camcorder Camera Packets (
Page 115 and 116:
Procedure CheckOptimal (n rs 1 ...n
Page 117 and 118:
MEMORY MANAGEMENT FOR LARGE SCALE D
Page 119 and 120:
PART 2 Artificial Intelligence and
Page 121 and 122:
110 ENTERPRISE INFORMATION SYSTEMS
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
DYNAMIC MULTI-AGENT BASED VARIETY F
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: 132 ENTERPRISE INFORMATION SYSTEMS
Page 169 and 170: AN EXPERIENCE IN MANAGEMENT OF IMPR
Page 179 and 180: ANALYSIS AND RE-ENGINEERING OF WEB
Page 181 and 182: Module p0 Customer Itinerary Send I
Page 183 and 184: departments: the marketing dept. se
Page 185 and 186: • An acyclic module M is usable,
Page 187 and 188: BALANCING STAKEHOLDER’S PREFERENC
Page 189 and 190: The scenarios will provide an abstr
Page 191 and 192: BALANCING STAKEHOLDER'S PREFERENCES
Page 193: BALANCING STAKEHOLDER'S PREFERENCES
Page 197 and 198: A POLYMORPHIC CONTE XT FRAME TO SUP
Page 203 and 204: FEATURE MATCHING IN MODEL-BASED SOF
Page 205 and 206: combination of solution domains - a
Page 207 and 208: • features for all the concepts:
Page 209 and 210: Existence In both steps it is possi
Page 211 and 212: matching strategies are maximal, mi
Page 213 and 214: TOWARDS A META MODEL FOR DESCRIBING
Page 215 and 216: elementary message (ae-message) can
Page 217 and 218: problems on a pragmatic level, whic
Page 219 and 220: TOWARDS A META MODEL FOR DESCRIBING
Page 221 and 222: INTRUSION DETECTION SYSTEMS USING A
Page 223 and 224: INTRUSION DETECTION SYSTEMS USING A
Page 225 and 226: (k� 1) (k) (k�1) (k) p � w
Page 227 and 228: Table 5: Performance Comparison of
Page 229 and 230: A USER-CENTERED METHODOLOGY TO GENE
Page 231 and 232: carries out the second phase of the
Page 233 and 234: 1 1 1 1 2 PROCESS STORE ENTITY EDGE
Page 235 and 236: constraints rules. KOGGE (Ebert et
Page 237 and 238: PART 4 Software Agents and Internet
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
CABA 2 L A BLISS PREDICTIVE COMPOSI
Page 287 and 288:
y disables evidencing severe mental
Page 289 and 290:
Figure 4: Symbols emission in DAR-H
Page 291 and 292:
they evidence a generalization erro
Page 293 and 294:
A METHODOLOGY FOR INTERFACE DESIGN
Page 295 and 296:
and mobility loss coupled with redu
Page 297 and 298:
Tradeoff: The default input is poss
Page 299 and 300:
Sessions on the VABS which are held
Page 301 and 302:
A CONTACT RECOMMENDER SYSTEM FOR A
Page 303 and 304:
A CONTACT RECOMMENDER SYSTEM FOR A
Page 305 and 306:
- "Going to the sources". The user
Page 307 and 308:
Here are the matrix W and P for our
Page 309 and 310:
EMOTION SYNTHESIS IN VIRTUAL ENVIRO
Page 311 and 312:
theme turns out to be surprisingly
Page 313 and 314:
6 FROM FEATURES TO SYMBOLS 6.1 Face
Page 315 and 316:
sions are described by different em
Page 317 and 318:
Electronic Imaging 2000 Conference
Page 319 and 320:
to the accessibility problem for th
Page 321 and 322:
Figure 3: Hierarchical View of the
Page 323 and 324:
4 CONCLUSIONS AND FUTURE WORK On th
Page 325 and 326:
PERSONALISED RESOURCE DISCOVERY SEA
Page 327 and 328:
Page 329 and 330:
profile, the user defines his curre
Page 331 and 332:
Page 333 and 334:
Abdelkafi, N. .....................
show all

Back Room Front Room 2

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?