Matthias Book: Realizing an Integrated Electronic Commerce Portal - PDF document

Matthias Book: Realizing an Integrated Electronic Commerce Portal System August 11, 2000 A Portal for Insurance A Portal for Insurance Agents Agents Realizing an an Integrated Integrated Realizing • combines and integrates Electronic Commerce Portal System Electronic Commerce Portal System • information and applications • which the agents need for their work Matthias Book, Volker Gruhn, Lothar Schöpe • on a mobile platform • to increase Chair of Software Technology Department of Computer Science • productivity University of Dortmund, Germany • company loyalty 1/15 Matthias Book: Realizing an Integrated Electronic Commerce Portal System 2/15 Americas Conference on Information Systems - August 11, 2000 Software Process Software Process Requirement Analysis Requirement Analysis • Requirement Analysis • cooperation with insurance companies • Subsystem Identification • comprehensive tasks � singular actions • High-Level Architecture • prioritized and documented • Cut-Through Prototypes Req ID Requirement Priority Type Rationale • GUI Design EP-F/1.2.3 All shop items must be 1 MUST Users are familiar with accessible via a the concept of a • Object-Oriented Design product hierarchy. hierarchy and can find items there easily. EP-F/1.2.4 A full text search may 3 MAY The search facility • Implementation be provided to find serves as a backup in products. case the user can't find • System Test an item in the hierachy. Matthias Book: Realizing an Integrated Electronic Commerce Portal System 3/15 Matthias Book: Realizing an Integrated Electronic Commerce Portal System 4/15 Subsystem Identification Subsystem Identification High- High -Level Architecture Level Architecture Content Electronic Legacy Office Comm Admin Management Procurement Applications GUI Product Office Office Dispatcher User e-Mail Portfolio Material Sending HTML Page/ Management Folders Partner WML Deck (Toner, ...) Reminders, Content Database Formatter Company Messages, Monitoring Management Address Handbook Promotional etc. Book Contracts Material Controllers Electronic Database Workflow Search Marketing (Flyers, ...) by Procurement Calendar Information Fax Premium Company SMS Portal-wide Legacy Search To-Do Computer Full Text Application Best Practice Services e-Mail List Solutions (Courses, ...) Searches Comm Admin Outlook pirobase SmartStore Partner DB sendfax, yaps, JavaMail Matthias Book: Realizing an Integrated Electronic Commerce Portal System 5/15 Matthias Book: Realizing an Integrated Electronic Commerce Portal System 6/15 Americas Conference on Information Systems - AMCIS 2000 1

Matthias Book: Realizing an Integrated Electronic Commerce Portal System August 11, 2000 Cut- Cut -Through Prototypes Through Prototypes GUI Design GUI Design • Question: HTML Page / • Extensible layout Dispatcher WML Deck ? Subsystem integration Office • Formatters for feasible? different media Content ? Controller Formatter Management Controller Formatter • Custom libraries of • Requirement: Controller Formatter Electronic GUI elements ? Key features accessible Procurement IPSI-specific • Control flow charts via adaptors Subsystem Subsystem Elements Legacy Subsystem ? Application • "Proof": • Identification of controller/formatter "Quick & dirty" adaptor ? Comm Basic GUI Basic Basic Elements classes Elements implementations Elements Matthias Book: Realizing an Integrated Electronic Commerce Portal System 7/15 Matthias Book: Realizing an Integrated Electronic Commerce Portal System 8/15 Object- Object -Oriented Oriented Design Design Legacy Integration Legacy Integration • Goal: Simple subsystem integration Partner DB XML Stream • UML use cases, class diagrams Query Query Decoder Encoder Controller Search Legacy • Boundary classes DBMS Boundary XML Stream • encapsulate subsystem functionality Result Result Encoder Decoder • Business objects (e.g. User, Task) • transported between subsystems Matthias Book: Realizing an Integrated Electronic Commerce Portal System 9/15 Matthias Book: Realizing an Integrated Electronic Commerce Portal System 10/15 Implementation Implementation System Test System Test • Class Test • Distributed implementation • Class functionality ok? • Subsystems on separate machines • Subsystem Test • Middleware: CORBA • Code review; subsystem boundary ok? • Code distribution: CVS • Integration Test • Languages • Subsystems‘ interfaces ok? • System Test • Java • Workflow and GUI ok? • Visual C++ Matthias Book: Realizing an Integrated Electronic Commerce Portal System 11/15 Matthias Book: Realizing an Integrated Electronic Commerce Portal System 12/15 Americas Conference on Information Systems - AMCIS 2000 2

Matthias Book: Realizing an Integrated Electronic Commerce Portal System August 11, 2000 Conclusion Conclusion » Portal implementation = integration task • „Glue“ code connecting subsystems • requires detailed design, careful testing • Adaptor prototypes crucial • basis for feasibility/time/effort prognosis • Open architecture pays off • allows simple modification of subsystems Matthias Book: Realizing an Integrated Electronic Commerce Portal System 13/15 Matthias Book: Realizing an Integrated Electronic Commerce Portal System 14/15 T h a n k y o u ! T h a n k y o u ! Matthias Book: Realizing an Integrated Electronic Commerce Portal System 15/15 Americas Conference on Information Systems - AMCIS 2000 3