Back Room Front Room 2

More documents

Recommendations

Info

192 ENTERPRISE INFORMATION SYSTEMS VI Gamma, E., Helm, R., Johnson, R., and Vlissides, J. (1995). Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley Professional Computing Series. Addison-Wesley Publishing Company, New York, NY. Gnatz, M., Marschall, F., Popp, G., Rausch, A., and Schwerin, W. (2001). Modular process patterns supporting an evolutionary software development process. Lecture Notes in Computer Science, 2188. Henderson-Sellers, B. and Edwards, J. (1990). The objectoriented systems life cycle. Communications of the ACM, 33(9):142–159. Mirbel, I. and de Rivieres, V. (2002a). Adapting Analysis and Design to Software Context: the JECKO Approach. In 8th International Conference on Object- Oriented Information S ystems. Mirbel, I. and de Rivieres, V. (2002b). Introducing Flexibility in the Heart of Analysis and Design. In 6th world multiconference on systemics, cybernetics and informatics (SCI). Mirbel, I. and de Rivieres, V. (2003). UML and the Unified Process, chapter Towards a UML profile for building on top of running software. IRM Press. Object Management Group (2001). Uml specification. Potts, C. (1989). A generic model for representing design methods. In 11th International Conference on Software Engineering. Ralyte, J. (2001). Ingenierie des methodes a base de composants. PhD thesis, Universite Paris I - Sorbonne. Rolland, C. and Souveyet, C. (1995). An approach for defining ways-of-working. Information Systems Journal. Royce, W. (1970). Managing the development of large software systems: Concepts and techniques. In WESCON. Saeki, M. (2003). Toward automated method engineering: Supporting method assembly in came. In First International Workshop on Engineering methods to support information systems evolution, Geneva, Switzerland. si Said, S. and Rolland, C. (1998). Formalising guidance for the CREWS goal-scenario approach to requirements engineering. In Eight European-Japanese Conference on Information Modelling and Knowledge Bases. van Slooten, K. and Hodes, B. (1996). Characterizing IS development projects. In S. Brinkkemper, K. Lyytinen, R. W., editor, IFIP TC8, WG 8.1/8.2, pages 29–44.
FEATURE MATCHING IN MODEL-BASED SOFTWARE ENGINEERING Alar Raabe Department of Computer Engineering, Tallinn Technical University, Ehitajate tee 5, 19086 Tallinn, Estonia Email: alar.raabe@profitsoftware.ee Keywords: Model-based development, model-driven architecture (MDA), domain modeling, feature models, software engineering Abstract: There is a growing need to reduce the cycle of business information systems development and make it independent of underlying technologies. Model-driven synthesis of software offers solutions to these problems. This article describes a method for synthesizing business software implementations from technology independent business models. The synthesis of business software implementation performed in two steps, is based on establishing a common feature space for problem and solution domains. In the first step, a solution domain and a software architecture style are selected by matching the explicitly required features of a given software system, and implicitly required features of a given problem domain to the features provided by the solution domain and the architectural style. In the second step, all the elements of a given business analysis model are transformed into elements or configurations in the selected solution domain according to the selected architectural style, by matching their required features to the features provided by the elements and configurations of the selected solution domain. In both steps it is possible to define cost functions for selecting between different alternatives which provide the same features. The differences of our method are the separate step of solution domain analysis during the software process, which produces the feature model of the solution domain, and usage of common feature space to select the solution domain, the architectural style and specific implementations. 1 INTRODUCTION Today business processes become increasingly dependent on the software, and must change rapidly in response to market changes. Initial results from software development should be delivered with a very short delay and have to be deployable with minimal costs. When the business volume grows, or the business processes change, supporting software systems must be able to grow and change along, without impeding the business process and without a major reimplementation effort. To achieve different non-functional requirements (e.g. quality of service) needed for business information systems, different implementation technologies, which themselves are rapidly evolving, are to be used and combined. As a result, there is a growing need to shorten the development cycle of business information systems, and to achieve its independence of underlying technologies, which often evolve without offering backward compatibility. Therefore the main body of reusable software assets of an enterprise should be independent of implementation technologies. I. Seruca et al. (eds.), Enterprise Information Systems VI, © 2006 Springer. Printed in the Netherlands. 193 193–202. These problems are addressed by model-based approaches to software development, e.g. modelbased software synthesis (Abbott et al., 1993), model-based development (Mellor, 1995), and model driven architecture (MDA) (OMG, 2001a). In the model-based software development, the primary artifact is a model of the required software system, which becomes the source of the specific implementation of a given software system created through synthesis or generation. We treat the development of business information systems as similar to domain-oriented application development technologies (SEI, 2002 and Honeywell, 1996), where business, in general, is treated as a large general domain containing several more specific domains (business areas), which refer to common elements from the general business domain. In this article we describe a method that is applicable to synthesizing business software implementations from technology independent business models. Our method is based on establishing a common
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:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152: 140 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 and 194: BALANCING STAKEHOLDER'S PREFERENCES
Page 195 and 196: A POLYMORPHIC CONTEXT FRAME TO SUPP
Page 197 and 198: A POLYMORPHIC CONTE XT FRAME TO SUP
Page 199 and 200: A POLYMORPHIC CONTE XT FRAME TO SUP
Page 201: A POLYMORPHIC CONTE XT FRAME TO SUP
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 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

Create successful ePaper yourself

Delete template?

Save as template?