Arch tecture of an Informat on System for Personal F nanc al Plann ng
Copyright ?© 2007, Idea Group Inc. Copying or distributing in print or electronic forms without written permission
of Idea Group Inc. is prohibited.
System.Architecture
Architecture influences just about everything in the process of developing software. Architecture
gives the rules and regulations by which the software has to be constructed. Figure
2 shows the general architecture of our prototype FiXplan (IT-based Personal Financial
Planning), and the data flow between the User Interfaces, the Application Layer, and the
Sources (Braun & Schmidt, 2005).
Basically, the system contains the following components:
??? Clients: Used by Personal Financial Planners or clients to access our main financial
planning system and our Web Services; User Interfaces may be Web browsers such
as the Internet Explorer or Mozilla, or applications such as Microsoft Excel.
??? Server: As described in detail in the analysis model; the Web Services Toolbox provides
useful tools for personal financial planning.
??? Sources: Used as a repository for the tools of the personal finance framework.
The three-tier architecture of FiXplan supports modular deployment of both device-specific
user interfaces through multi-channel delivery of services and new or adapted operational
processes and strategies.
Pages:
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254