4th International Conference on Principles and Practices ... - MADOC

More documents

Recommendations

Info

final contract to be printed contracts with no need for a postproduction CD grey stored contracts without a CD yet stored contracts with a CD CD green or grey final contract to be printed contracts to be postproducted CD red CD red Legend: B.1: stored applications, for which no credit decision (CD) was made yet. B.2: stored applications, for which a credit decision was made already. B.3: applications, for which the last credit decision was red. B.4: applications, with CD green, which don’t have to go into reviewing. B.5: applications, with CD green, which don’t have to go into reviewing, the contract of which is ready for printing. B.6: applications, with CD green, which are being reviewed, for which however there hasn’t been done any CD in the reviewing yet. B.7: applications with CD grey in the reviewing. B.8: applications with CD red in the reviewing. B.9: agreed applications, the contract for which is ready for printing. Figure 1: Simplified shown life cycle model of the application way “Internet guest” • Finding the amounts in the single pipeline sections, • Monitoring, whether the applications are moving forward in the pipeline, • Checking, whether all applications/contracts within a certain time frame have reached a final status. For this the following monitoring variants are used in detail: Pipeline-snapshot: Establishing the absolute amount of applications within the single pipeline sections at defined times (e.g. each hour). Pipeline-progress: Establishing, which application objects have newly reached the corresponding pipeline section within a defined time interval (e.g. each 15 minutes). The absolute amount of applications is established. Application specific finalising: Here it is checked, whether all applications within a certain time interval have reached the defined final status (e.g. one working day per each application). Defined final states are the sections B.3, B.5, B.8, B.9. Wait time-monitoring: Establishing, how much time it takes for an application from one pipeline section to the next respectively whether an application stays for too long in a certain pipeline section. Critical pipeline sections are: B.2, B.5, B.6, B.7, B.9. The monitoring of the single application states is done by cyclical database requests. Hereby the time stamp of the corresponding status entry in the database serves as a reference. E.g. if the Schufa credit agency is not available, it is easily possible to recognize through evaluating the pipeline progress that the amount of applications with status CD grey have been raised significantly. 5. FURTHER DEVELOPMENT OF THE MONITORING PROCEDURE WITH CEP/ESP The so far described approach assumes that each credit application with its total life cycle runs through several processing steps, like in a production line or within a pipeline. Precondition for a corresponding technical monitoring is however that each 239
status change of an application is recorded with a corresponding time stamp in a database. Only in this way a simple database request can establish, how many contracts are located in which place within the pipeline. The advantage of this procedure is the simple realization. The disadvantage of this approach however is that only a frozen state of an existing constellation at time point t of the data base request can be seen. A real time monitoring of the economical states of the application is only possible, if status changes of applications are requested in the data base permanently. This means: if the answer for a request is wanted each second, the request has to be entered each second as well. This solution cannot be realized for hundreds of different requests. Therefore the database is a bottleneck in the case of complex status changes, which shall be monitored in real time. Also the triggers, which were integrated later in traditional databases, don’t solve the problem, as these don’t scale. Event Stream Processing (ESP) or Complex Event Processing (CEP) are paradigms, which are helpful to react in real time to changes of states by corresponding informations [9]. With CEP/ESP messages, informations or data are correlated, aggregated, analyzed and evaluated in real time. These newly generated informations then provide the base for further decisions. Thus a CEP/ESP-platform becomes an intelligent BAM-tool, which also offers the possibility of dynamic visualization. In a next step this pipeline model shall be realized with methods of CEP/ESP. 5.1 Redesign as SOA and Use of a BPELbased Workflow Engine For the new approach of easyCredit it is necessary to redesign the architecture of the system in the sense of a SOA [3][16]. As a principal difference to EAI [12] a SOA is based on the business processes (see fig. 2). At each process step another enterprise internal or external process or a service respectively a software component can be called and eventually a change in a database or in a legacy system, e.g. in an ERP-system like R/3 or in a CRMsystem like Siebel, can be caused. Fig. 2 shows the example of an online-credit-system that this architecture could arbitrarily cascade [1]. All software-components respectively services are defined e.g. by the Web-Service-Definition-Language (WSDL) and are bound as web-service to a process step. However hereby it has to be guaranteed that for the aim of a real time BAM no performance problems will be caused by still relatively heavy and slow XML-based protocols like SOAP [15] because of longer latency times. This also goes for the use of a BPEL-based workflow engine [13]. Though the business process can be standardized and flexibly implemented in this way and even be modified at run time of the system on a high level, i.e. by the means of workflow design tools by non-IT-experts, if applicable even directly by a business department, for the realization of new business and marketing strategies. On the other hand numerous, concurrent business process instances could cause performance and scalability problems of the BPEL-engine. This has to be considered in time towards the required real time performance of the BAM at the dimensioning of the system and the resource planning (sizingproject). 5.2 Events for the Workflow Engine Versus Events for CEP/ESP The business process is controlled e.g. in the sense of an eEPCnotation [5] of events, like “credit application received”, “credit application checked for completeness”, “Schufa-information Service Consumer Loan Consulting Credit Investigation Loan Awarded Credit Processing In an SOA, the process is controlled by the service consumer. Service Provider Consultation System Credit Reporting Agency Costing System Value Date / Payment Securities Management Reporting Service providers can implement processes and also call services. Service Provider Accouting System ... Reporting Data is accessed via the service provider. Figure 2: The SOA Challenge - design horizontal and vertical coupling of services 240
Page 1 and 2:
Edited by: Ralf Gitzel, Markus Alek
Page 3 and 4:
Message from the Chairs Dear confer
Page 5 and 6:
Sam Midkiff, Purdue University (USA
Page 7 and 8:
Session F: Novel Uses of Java______
Page 10 and 11:
The Project Maxwell Assembler Syste
Page 12 and 13:
tomated assembler and disassembler
Page 14 and 15:
memory address offset mnemonic argu
Page 16 and 17:
5.2 Instruction Templates The assem
Page 18 and 19:
ange for a very short restart/debug
Page 20 and 21:
Tatoo: an innovative parser generat
Page 22 and 23:
In the grammar file an error termin
Page 24 and 25:
Figure 3: Push parsers and lexers L
Page 26 and 27:
eturn visit((Expr)p1, param); } R v
Page 28:
Session B Program and Performance A
Page 31 and 32:
Table 1: Use of interfaces and deco
Page 33 and 34:
Table 3: Comparison of the situatio
Page 35 and 36:
will trigger the creation of many n
Page 37 and 38:
Appendix A 10 9 8 7 6 5 4 3 2 1 0 1
Page 39 and 40:
Throughout this paper, we make no a
Page 41 and 42:
instrumented program and obtained t
Page 43 and 44:
Figure 5: Investigation of garbage
Page 45 and 46:
to the same category—again, this
Page 47 and 48:
Investigating Throughput Degradatio
Page 49 and 50:
Figure 1: Apache. Throughput degrad
Page 51 and 52:
Minor GC Full GC Workload # of Avg.
Page 53 and 54:
Figure 6: Comparing memory and pagi
Page 55 and 56:
GenRC on the other hand, allows the
Page 58:
Session C Mobile and Distributed Sy
Page 61 and 62:
ing a continuous buffer for raw dat
Page 63 and 64:
the data arrival speed is more impo
Page 65 and 66:
public class StreamingClient { publ
Page 67 and 68:
importance of β in our aggregation
Page 69 and 70:
Enabling Java Mobile Computing on t
Page 71 and 72:
A strongly mobile thread has the ab
Page 73 and 74:
a context switch occur. The invoked
Page 75 and 76:
above phases. Now, the new stack ha
Page 77 and 78:
5 frames 15 frames 25 frames Pure d
Page 79 and 80:
Juxta-Cat: A JXTA-based platform fo
Page 81 and 82:
Figure 1: JXTA Architecture. 3. JUX
Page 83 and 84:
• Send a discovery query to the p
Page 85 and 86:
The best candidate is then the one
Page 87 and 88:
Local Hosts=2 Hosts=4 Hosts=8 Hosts
Page 90:
Session D Resource and Object Manag
Page 93 and 94:
Enterprise Edition (J2EE). It enabl
Page 95 and 96:
As pictured in Figure 4, JDOSecure
Page 97 and 98:
Methods of a PersistenceManager, th
Page 99 and 100:
Datenmodell abstrahiert user role,
Page 101 and 102:
An Extensible Mechanism for Long-Te
Page 103 and 104:
missing object references in the de
Page 105 and 106:
4.2 Mapping the name spaces of the
Page 107 and 108:
(a) (b) ColorSliderPanel0 color
Page 109 and 110:
8. REFERENCES [1] Abu-Ghazaleh, N.,
Page 111 and 112:
permission by process. In other wor
Page 113 and 114:
The processor then refers to the en
Page 115 and 116:
1: // Protection domain 2: struct p
Page 117 and 118:
Table 3: Frequency of JNI calls tha
Page 119 and 120:
[13] Intel Corporation. IA-32 Intel
Page 121 and 122:
01 try { 02 ... 03 } finally { 04 t
Page 123 and 124:
2. FRAMEWORK The Framework for Unif
Page 125 and 126:
ManagedInputStream ResourceGroup Ma
Page 127 and 128:
18. throw ‡ 1. release 17. cleanu
Page 129 and 130:
3. FUTURE WORK The ability to split
Page 131 and 132:
124
Page 133 and 134:
UML sequence diagrams are among the
Page 135 and 136:
diagrams, and behavioral (dynamic)
Page 137 and 138:
the official scripting language for
Page 139 and 140:
Apache's XML Graphics Project. A cu
Page 141 and 142:
Java Debug Interface (JDI). In Revi
Page 143 and 144:
1.3 JML 1.3.1 Overview JML, the Jav
Page 145 and 146:
The Usage of CANAPA is fairly strai
Page 147 and 148:
*@non_null@*/ String str = attribut
Page 149 and 150:
142
Page 151 and 152:
parallel and distributed versions o
Page 153 and 154:
RingElem CextendsRingElem GenPolyno
Page 155 and 156:
RingElem +isZERO():bolean CextendsR
Page 157 and 158:
class constructors with the actual
Page 159 and 160:
plemented via a distributed hash ta
Page 161 and 162:
which are common nowadays. The reus
Page 163 and 164:
Derivative Contract Component Repos
Page 165 and 166:
stepwise execution create Derivativ
Page 167 and 168:
5.4.1 Structural Constraints Struct
Page 169 and 170:
into the conceptual foundation of n
Page 171 and 172:
different implementation and is mor
Page 173 and 174:
the service from the root. It allow
Page 175 and 176:
model: 1. Servlet [6] adapter compo
Page 177 and 178:
y possibly different service, where
Page 179 and 180:
or the fact that widgets extend ser
Page 181 and 182:
174
Page 183 and 184:
The idea of Java 5.0 type inference
Page 185 and 186:
Source := (class | interface)∗ cl
Page 187 and 188:
5. IMPLEMENTATION In order to prese
Page 189 and 190:
Infinite Streams in Java Dominik Gr
Page 191 and 192:
} private static LinkedStream fibon
Page 193 and 194:
of the f stream in order to compute
Page 195 and 196: Interaction among Objects via Roles
Page 197 and 198: (a) (b) (c) (d) (e) Figure 1: The p
Page 199 and 200: class Printer { private int totalPr
Page 201 and 202: Experiences of using the Dagstuhl M
Page 203 and 204: Metric Definition Java .class files
Page 205 and 206: scription of the metric values. Non
Page 207 and 208: Figure 1: Results from the J-vestig
Page 209 and 210: an error is subsequently generated
Page 211 and 212: 3. BASIC TERMINOLOGY As object-orie
Page 213 and 214: • subtyping • (implementation)
Page 215 and 216: Improving the Quality of Programmin
Page 217 and 218: Results of online checks (shortened
Page 219 and 220: 212
Page 221 and 222: 214
Page 223 and 224: Experiences With Hierarchy-Based Co
Page 225 and 226: Sub View Child DataField 0..n Ke
Page 227 and 228: Figure 8 - Actual State Charts elem
Page 229 and 230: associations, which may result in r
Page 231 and 232: M3PS: A Multi-Platform P2P System B
Page 233 and 234: In following, we will explain in de
Page 235 and 236: Figure 10. JDP in Windows XP. Figur
Page 237 and 238: Mapping Clouds of SOA- and Business
Page 239 and 240: the technical SOA events (from the
Page 241 and 242: component and the business process
Page 243 and 244: Figure 13. “Business Value of Dat
Page 245: Solaris of SUN. This platform provi
Page 249 and 250: coming up, is presently discussing
Page 251: ISBN: 3-939352-05-5 ISBN: 978-3-939
show all

4th International Conference on Principles and Practices ... - MADOC

Create successful ePaper yourself

Delete template?

Save as template?