e-Business Development: Implementing Business Processes with Technology

1. Rational Unified Process Fundamentals Module 7: Process for e-Business Development

2. Objectives: Process for e-Business Development • Understand the use of e-Business applications to implement business processes • Understand concepts and technologies for e-Business solutions • Examine process customization for e-Business development

3. Definition: e-Business Building systems (business tools) that automate business processes

4. Generations of e-Business systems 1st 2nd 3rd • Reengineer a process to provide highly personalized, adaptive solutions. • Automate the complete business process, often integrating with legacy systems and internet devices. • Implement e-commerce and simple transactional models • Use the web to publish information

5. Categories of e-Business Development • Customer to business (C2B) • Business to business (B2B) • Business to customer (B2C) • Customer to customer (C2C)

6. Characteristics of e-Business Development • Externally imposed rules and regulations, often of high complexity (business rules) • Interface with legacy data structures • Customer focus • Compressed time schedules • Concern for performance and reliability of the final system

7. Contrast with Traditional Development • More emphasis on business modeling • More emphasis on user-interface • graphic design • anonymous users • Use of e-Business enabling technologies to define the architecture • inherently distributed architecture • Greater focus on performance testing • unpredictable loads

8. The Role of Enabling Technologies in e-Business Changed Business Practices Technological Advances New Business Opportunities

9. RUP Content for e-Business Development • Roadmap: Developing e-Business Solutions • Extends the process based on technology issues • Emphasizes related parts of workflow • Provides more specific information for activities • Suggests appropriate artifacts • Introduces related concepts

10. Process Variation Based on Phases Roadmap: Developing e-Business Solutions

11. E-business Process Variation: Phases • Business Modeling • Requirements • Analysis & Design • Implementation • Test • Environment

12. Process Variation in Business Modeling • Compared to system modeling... • Increased prominence of business modeling • Greater variety of stakeholders • For e-Business modeling ... • Limit scope to area of influence • Identify automated and non-automated parts of the business • Consider role of legacy systems

13. Six Scenarios for Business Modeling (review) • Organization chart • Domain modeling • One business, many systems • Generic business model • New business • Revamp

14. Business Processes? Business Process • A set of internal activities performed to serve a customer • The purpose is to offer each customer the right product or service • Cuts right through functional organization structures;requires changes in organizational structures Branch office Credit department Loan committee New loan: from Loan application to Loan disbursement

15. The Fundamental Business Goal? Perceived Value The Company Business process A Business process B Business process C A Customer is a “User of the Company”

16. Business actor - represents a role played in relation to the business by someone or something. Business use case - a sequence of actions performed in a business that produces a result of observable value to an individual actor of the business. Example Business Use-Case Model Core business processes for a generic software solution vendor

17. E-business Process Variation: Phases • Business Modeling • Requirements • Analysis & Design • Implementation • Test • Environment

18. Process Variation in Requirements • Rely on the business assessment and organization description from Business Modeling. • Rely on stakeholder input obtained during Business Modeling. • Let the system boundaries reflect the business boundaries (the system is the business).

19. Business Model Input to Requirements

20. User-Centered Design • Business success depends on accommodating users • Varying legislation around the globe • Standards organizations • Involve and observe users • Integrate interface development with design • Iterative design

21. Focus on user interface usability Create a storyboard Find boundary classes as preparation for an object-oriented interface Prepare user-interface prototype Model the User Interface

22. Multiple Dimensions to User-Centered Design

23. Concept Overlap for Functional Requirements

24. E-business Process Variation: Phases • Business Modeling • Requirements • Analysis & Design • Implementation • Test • Environment

25. Process Variation in Analysis & Design • Web architecture is well-defined. • Focus on GUI and business logic. • Use UML Extension for Web Applications • Map non-functional system requirements to web development framework. • Focus on web server, application server (processes and threads). • Describe distribution for scalability and fault tolerance.

26. Business Model Input to Analysis and Design

27. Using UML for Web Application Architectures • UML designed to allow formal extensions • stereotypes (icons), tagged values, constraints • Distinction between business logic and presentation logic • Allows modeling of web page behavior on client and server

28. Three Common Web Architecture Patterns • Thin web client • Minimal client configuration • Minimal computing power • Business logic on the server • Thick web client • Client-side scripting and custom objects • Some business logic • Web delivery • Web as delivery mechanism for a distributed client/server system

29. E-business Process Variation: Phases • Business Modeling • Requirements • Analysis & Design • Implementation • Test • Environment

30. Process Variation in Implementation • Architectural prototypes • Component implementation • browser environment • server-side • legacy enhancements • database enhancements • Subsystem integration • System integration

31. E-business Process Variation: Phases • Business Modeling • Requirements • Analysis & Design • Implementation • Test • Environment

32. Process Variation in Test • Test for a scalable and Reliable Architecture • Benchmark testing • Contention testing • Performance profiling • Load testing • Stress testing • Appropriateness of web site structure • Browser compatibility

33. E-business Process Variation: Phases • Business Modeling • Requirements • Analysis & Design • Implementation • Test • Environment

34. Process Variation in Environment • Develop user-interface guidelines • e.g. ‘Design Brief’ • Web-site consistency • Develop web UI prototype

35. Summary: Process for e-Business Development • What is an “e-Business”? • How is e-Business development different from traditional development? • What role do business models play in e-development? • Give examples of the process variant for e-Business development.