Home > Papers > APAQS 2001
Introduction | The IPSI EC portal | Process decription | Requirements analysis | Subsystem selection | Prototype development | GUI development | Integration and system test | Conclusion | References | Slides
A Specific Software Development Process for an Electronic Commerce Portal
3.2. Subsystem selection
In most cases, EC/EB systems are not developed independently of an existing hardware and software infrastructure. Usually, the EC/EB systems have to be integrated into that infrastructure by exchanging data with it. However, the exchange of data between the EC/EB system and existing software systems may not always be sufficient - sometimes, the use of existing functionality is necessary. Thus, the IPSI electronic commerce portal exchanges data with its subsystems as well as with the database systems of the client (e.g. UDS, BS2000). This way, the portal can supply the data of insured persons and their contracts to the insurance agent. Furthermore, the portal needs the functionality of a complex tariff computation module, e.g. for a life insurance. Existing software systems like the latter one are termed legacy systems. In order to realize each subsystem, it must be decided if existing software systems fulfill the client's requirements, and if an existing software system can be integrated or if it is necessary to develop new software.
For the IPSI electronic commerce portal, it was decided to integrate existing software systems for most subsystems. This decision was followed by a market analysis to determine which existing systems should be used. The analysis took into account non-functional criteria such as price, availability, support and platform and led to the selection of MS Outlook 2000, Pirobase 4.0, SmartStore 2.0 and JavaMail 1.1 for the subsystems office, content management, procurement and communications (see Figure 3).
|Authors: Volker Gruhn, Lothar Schöpe, Matthias Book -- Paper © 2001 The Institute of Electrical and Electronics Engineers, Inc. (IEEE)|