1. Slide 11.1 CHAPTER 11 ANALYSIS AND DESIGN

2. Slide 11.2 Learning outcomes  Summarize approaches for analyzing requirements for e-business systems  Identify key elements of approaches to improve the interface design and security design of e-commerce systems.

3. Slide 11.3 Management issues  What are the critical success factors for analysis and design of e-business systems?  What is the balance between requirements for usable and secure systems and the costs of designing them in this manner?  What are the best approaches for incorporating new IS solutions with legacy systems into the architectural design of the e-business?

4. Slide 11.4 Analysis for e-business  Understanding processes and information flows to improve service delivery  Pant and Ravichandran (2001) say: ‘Information is an agent of coordination and control and serves as a glue that holds together organizations, franchises, supply chains and distribution channels. Along with material and other resource flows, information flows must also be handled effectively in any organization.’

5. Slide 11.5 Workflow management Workflow is ‘the automation of a business process, in whole or part during which documents, information or tasks are passed from one participant to another for action, according to a set of procedural rules.’

6. Slide 11.6  Workflow systems automate e-business process by providing a structured framework to support a process.  It helps manage business processes by ensuring that tasks are prioritized to be performed: as soon as possible by the right people in the right order

7. Slide 11.7 Process  Part of a system that has a clearly defined purpose or objective and clearly defined inputs and outputs.

8. Slide 11.8 Process modelling  Often use a hierarchical method of establishing  the processes and their constituent sub-processes  the dependencies between processes  the inputs (resources) needed by the processes and the outputs.

9. Slide 11.9 Task analysis and task decomposition  Before a process can be designed and implemented, a more detailed breakdown is required known as ‘task analysis’  Curtis et al. (1992) framework: Level 1 business process are decomposed into: Level 2 activities which are further divided to: Level 3 tasks and finally: Level 4 sub-tasks.

10. Figure 11.1 An example task decomposition for an estate agency Source: Adapted from Chaffey (1998)

11. Slide 11.11 Process Dependencies  PD summarize the order in which activity occur according to the business rules that govern the processes.  Data flow diagrams and flow charts are widely used as diagramming techniques  Flow process charts  Network diagrams  Event-driven process chain (EPC) model

12. Figure 11.2 Symbols used for flow process charts

13. Figure 11.3 Flow process chart showing the main operations performed by users when working using workflow software

14. Table 11.5 Elements of the event-driven process chain (EPC) model

15. Figure 11.4 General model for the EPC process definition model

16. Slide 11.16 Data modelling  Uses well established techniques used for relational database design  Stages: 1. Identify entities 2. Identify attributes of entities 3. Identify relationships.

17. Figure 11.5 Generic B2C ER diagram

18. Slide 11.18 Identify entities  Entities define the broad groupings of information such as information about different people, transactions or products. Examples include customer, employee, sales orders, purchase orders. When the design is implemented each design will form a database table.  Entity A grouping of related data, example customer entity. Implementation as table.  Database table Each database comprises several tables.

19. Slide 11.19 Identify attributes  Entities have different properties known as attributes that describe the characteristics of any single instance of an entity. For example, the customer entity has attributes such as name, phone number and e-mail address. When the design is implemented each attribute will form a field, and the collection of fields for one instance of the entity such as a particular customer will form a record.  Attribute A property or characteristic of an entity, implementation as field.  Field Attributes of products, example date of birth.  Record A collection of fields for one instance of an entity, example Customer Smith.

20. Slide 11.20 Identify relationships  The relationships between entities requires identification of which fields are used to link the tables. For example, for each order a customer places we need to know which customer has placed the order and which product they have ordered. The fields that are used to relate tables are referred to as key fields. A primary key is used to uniquely identify each instance of an entity and a secondary key is used to link to a primary key in another table.  Relationship Describes how different tables are linked.  Primary key The field that uniquely identifies each record in a table.  Secondary key A field that is used to link tables, by linking to a primary key in another table.

21. Design for e-business

22. Slide 11.22 Client/server architecture – separation of functions  Data storage. Predominantly on server. Client storage is ideally limited to cookies for identification of users and session tracking. Cookie identifiers for each system user are then related to the data for the user which is stored on a database server.  Query processing. Although some validation can be performed on the client.  Display. This is largely a client function.  Application logic. Traditionally, in early PC applications this has been a client function, but for e-business systems the design aim is to maximize the application logic processing including the business rules on the server.

23. Figure 11.6 Three-tier client server in an e-business environment

24. Slide 11.24 The three-tier client server  Require different servers to combine applications logic and database storage  Purpose of each server:  Web server. Manages http requests  Merchant server. Main location of app. Logic  Personalization server. Provides tailored content  Payment commerce server. Manages payment  Catalogue server. A document management server

25. Figure 11.7 E-business architecture for The B2C Company

26. Slide 11.26 Focus on User-centred design Unless a web site meets the needs of the intended users it will not meet the needs of the organization providing the web site. Web site development should be user-centred, evaluating the evolving design against user requirements. (Bevan, 1999a)

27. Slide 11.27 Analysis considerations (Bevan)  Who are the important users?  What is their purpose for accessing the site?  How frequently will they visit the site?  What experience and expertize do they have?  What nationality are they? Can they read English?  What type of information are they looking for?  How will they want to use the information: read it on the screen, print it or download it?  What type of browsers will they use? How fast will their communication links be?  How large a screen/window will they use, with how many colours?

28. Slide 11.28 Usability  An approach to web-site design intended to enable the completion of user tasks  Involves two key project activities:  Expert reviews  Usability testing

29. Slide 11.29 Use-case analysis  Use-case modelling A user-centred approach to modelling system requirements.  The use-case is part of a methodology known as Unified Modelling Language (UML).  Unified Modelling Language (UML) A language used to specify, visualize and document the artefacts of an object- oriented system.

30. Figure 11.9 Primary use-case scenario for an entire e-commerce purchase cycle

31. Slide 11.31 Primary scenario for the Register use-case Pre-condition: A user is active on the web site Scenario: Register Basic path: 1. Use-case starts when customer presses ‘register’ 2. Customer enters name, postal address and email 3. The post/zip code will be checked for validity 4. The customer will select ‘submit’ 5. The system will check all fields are present 6. A redirect page will be displayed to thank the customer.

32. Figure 11.10 Primary scenario for the Register use-cases for The B2C Company

33. Slide 11.33 Information Architecture  The combination of organization, labelling and navigation schemes comprising an information systems  Every information system has an information architecture

34. Slide 11.34 Designing the information architecture  Card sorting  The process of arranging a way of organizing objects on the web site  Blueprints  Shows the relationship between pages and other content components  Wireframes  A way of illustrating the layout of an individual page

35. Figure 11.12 Site structure diagram (blueprint) showing layout and relationship between pages

36. Figure 11.13 Example wireframe for a children’s toy site

37. Slide 11.37 Elements of Site design  Style and personality + design  Support the brand  Site organization  Fits audiences information needs  Site navigation  Clear, simple, consistent  Page design  Clear, simple, consistent  Content  Engaging and relevant.

38. Slide 11.38 Web accessibility  Number of visually impaired people  Number of users of less popular browsers or variation in screen display resolution  More visitors from natural listings of search engines  Legal requirements http://www.w3.org/TR/WCAG10/

39. Slide 11.39 Security requirements for e-commerce  Authentication – are parties to the transaction who they claim to be?  Privacy and confidentiality – is transaction data protected? The consumer may want to make an anonymous purchase.  Integrity – checks that the message sent is complete i.e. that it is not corrupted.  Non-repudiability – ensures sender cannot deny sending message.  Availability – how can threats to the continuity and performance of the system be eliminated?

40. Slide 11.40 Managing computer viruses  Boot-sector virus  Worms  Macro-viruses  E-mail attachment virus  Trojan viruses  Hoax e-mail viruses

41. Figure 11.18 The geographic spread of the ‘Slammer’ worm 30 minutes after release Source: Code Red (CRv2) Spread Animation. Copyright © 2001 The Regents of the University of California www-cse.ucsd.edu/~savage/ papers/IEEESP03.pdf

42. Slide 11.42 Monitoring of electronic communications  Employee communications monitoring  Acceptable-use policy  Scanning software  Filtering software

43. Slide 11.43 E-mail management  To minimize the volume  Spam  Internal business email  External business e-mail  Personal e-mail

44. Slide 11.44 Security Attacks  Hacking  Phishing  Denial-of-service attacks