1 / 33

Software Process for Electronic Commerce Portal Systems

Software Process for Electronic Commerce Portal Systems. Volker Gruhn 1 , Lothar Schöpe 2. 1 Department of Computer Science, University of Dortmund 2 Informatik Centrum Dortmund, e.V. Hypothesis.

odina
Download Presentation

Software Process for Electronic Commerce Portal Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Process for Electronic Commerce Portal Systems Volker Gruhn1, Lothar Schöpe2 1 Department of Computer Science, University of Dortmund 2 Informatik Centrum Dortmund, e.V. 8th EWSPT

  2. Hypothesis Software processes for e-Business / e-Commerce applications differ from traditional software processes (for information systems) V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  3. Experience: A Portal for Insurance Agents • combines and integrates • content and applicationsto support the agents' work • to increase • productivity, company loyalty • built using an adaptedsoftware development process V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  4. V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  5. Basis for experience is • the development of • an EC portal system • Application Domain: • B2E • Extranet provided by insurance company to support agents in daily work • Technical Features: • Integrates heterogeneous applications • Built on distributed OO Architecture • Idiosyncrasies of EC • software development • not covered by most • software development • processes • Idiosyncrasies: • System integration crucial • User interfaces play important role • Performance considerations pivotal • Systematic content management needed • Time pressure high • Very distributed process • An adapted EC software • development process is • needed • Needed changes: • New roles, activities, tools- Content Managers- GUI Specialists- Performance Planner- Security Expert- Integration Expert • New approaches- Technical (OO, CBD)- Communication • New strategies for dealing with shorter time to market- e.g. bifocal approach V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  6. Adaptation Idiosyncrasies Causes System Integration • Many heterogeneous new systems • Potentially short lifetime of systems • Many new technologies • Early integration plan • Cut-through-prototypes for system selection • Incremental testing User Interface Design • Few standards • Guides users • Influences performance • Outsourcing factor • Cooperate with experts • Plan for easy changes • Horizontal prototypes Content Management • “Up-to-date” factor • Rapidly changing content • Outsourcing / customer factor • Appoint Content Mgr. • Start selection early • Plan for easy changes V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  7. Adaptation Idiosyncrasies Causes Performance • 8 second rule • Peculiarities in customer behaviour(burstiness / heavy tails) • Workload forecasting • Performance modelling • Perform ongoing tests Time To Market Paradox • First mover advantage • Early estimates difficult but needed • Long runner advantage • Quality requirement unchanged • Cut-through prototypes again • Bifocal approach • Keep QM in mind Distributed Process • Many roles with highly diverse and specialized qualifications • Qualifications not found in one firm • Take partner selection into account • Distributed collaboration V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  8. Deliverable Subprocess Model Software Process Model V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  9. Software Process Model V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  10. Requirements Specification • cooperation with insurance companies • comprehensive tasks singular actions • prioritized and documented: V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  11. Software Process Model V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  12. Subsystem Identification Electronic Procurement Legacy Applications Admin Office Content Management Comm e-Mail Folders Address Book Calendar To-Do List Product Portfolio Company Handbook Marketing Information Law Documents Office Material (Toner, ...) Promotional Material (Flyers, ...) Company Services (Courses, ...) Partner Database Contracts Database Tariff Computer Sending Reminders, Messages, etc. by Fax SMS e-Mail User Management Monitoring Search Portal-wide Full Text Searches M a k e o r B u y ? V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  13. Outlook pirobase SmartStore Partner DB sendfax, yaps, JavaMail Subsystem Identification Electronic Procurement Legacy Applications Admin Office Content Management Comm e-Mail Folders Address Book Calendar To-Do List Product Portfolio Company Handbook Marketing Information Law Documents Office Material (Toner, ...) Promotional Material (Flyers, ...) Company Services (Courses, ...) Partner Database Contracts Database Tariff Computer Sending Reminders, Messages, etc. by Fax SMS e-Mail User Management Monitoring Search Portal-wide Full Text Searches M a k e o r B u y ? V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  14. Software Process Model V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  15. Cut-Through Prototypes V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  16. Internet Portal System for Insurances (IPSI) Core System Cut-Through Prototypes Electronic Procurement Legacy Applications External Subsystems Office Content Management Communi- cation V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  17. ? ? ? ? ? Internet Portal System for Insurances (IPSI) Core System Cut-Through Prototypes Electronic Procurement Legacy Applications External Subsystems Office Content Management Communi- cation Adaptors V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  18. ? ? ? ? ? Adaptors Internet Portal System for Insurances (IPSI) Core System • Q: Subsystem integration feasible? • A: Adaptor prototypes implementing key features Cut-Through Prototypes Electronic Procurement Legacy Applications External Subsystems Office Content Management Communi- cation Is it connectable? How is it connectable? What implications are there? V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  19. Software Process Model V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  20. GUI Development V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  21. HTML Page / WML Deck Controller Formatter Controller Formatter Controller Formatter Subsystem Subsystem Subsystem IPSI-specific Elements Basic Elements Basic Elements Basic GUI Elements GUI Design • Extensible layout • Formatters for different media • Customized libraries of GUI elements • Control flow charts • Identification of controller/formatter classes Dispatcher V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  22. Software Process Model V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  23. GUI Dispatcher HTML Page/ WML Deck Formatter Controllers Workflow Search Admin System Architecture Office Content Management Electronic Procurement Legacy Application Comm V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  24. Software Process Model V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  25. Realiziation • Distributed implementation • Subsystems on different machines • Middleware: CORBA • Code distribution: CVS • Languages • Java • Visual C++ V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  26. Object-Oriented Design • UML use cases, class diagrams • Goal: simple subsystem integration • Business objects • transported between subsystems • Boundary classes • encapsulate subsystem functionality V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  27. Software Process Model V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  28. Integration and System Test V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  29. XML Stream Query Decoder Query Encoder Legacy Boundary XML Stream Result Encoder Result Decoder Example: Legacy Integration Partner DB DBMS Search Controller V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  30. Testing • Class Test • Class functionality ok? • Subsystem Test • Code review; subsystem boundary ok? • Integration Test • Subsystems' interfaces ok? • System Test • Workflow and GUI ok? V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  31. Conclusion: Experiences • EC software development process can differ from conventional process in: • types of tasks • order in which tasks are performed • roles that perform tasks • software tools used • especially notable: • high effort for subsystem integration V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  32. Conclusion: Software Quality • Problem: • quality-assuring methods can fall prey to time-to-market philosophy • Partial solution: • incremental, iterative prototyping to estimate feasibility, effort and dev. time • Goal: Model software development process ensuring consistent high quality despite more challenging conditions V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

  33. Thank you!Any questions? V. Gruhn, L. Schöpe; Software Process for Electronic Commerce Portal Systems

More Related