1 / 54

Lecture 10: Analysis, Design and Implementation

Lecture 10: Analysis, Design and Implementation. B1 – Strategic and tactical tools for e-business Philip Holst Center for applied ICT Copenhagen Business School. Analysis. Learning outcomes. Summarize approaches for analysing requirements for e-business systems. Management issues.

lerato
Télécharger la présentation

Lecture 10: Analysis, Design and Implementation

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. Lecture 10:Analysis, Design and Implementation B1 – Strategic and tactical tools for e-business Philip Holst Center for applied ICT Copenhagen Business School

  2. Analysis

  3. Learning outcomes • Summarize approaches for analysing requirements for e-business systems

  4. Management issues • Understanding processes and information flows to improve service delivery • 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?

  5. Workflow management • “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” • WfMC (1996) • Administrative workflow • Production workflows

  6. Typicalfunctions in workflow management • Assigning tasks to people • Reminding people of their tasks and the sequence they should be performed in • Allowing collaboration between people sharing tasks • Retrieve information needed for performing tasks • Providing managers with an overview of the status of each task

  7. Processmodeling • the processes and their constituent sub-processes • the dependencies between processes • the inputs (resources) needed by the processes and the outputs

  8. Examples of processmodelling

  9. Examples of processmodeling

  10. Event-driven modelling

  11. Ressource, events, agents (REA) model • Proposed by William E. McCarthy in 1982 as an accounting system for the computer age • goods, services or money, i.e., RESOURCES • business transactions or agreements that affect resources, i.e., EVENTS • people or other human agencies (other companies, etc.), i.e., AGENTS

  12. Richpictures

  13. Use-casemodeling • Analysis from the useperspective. • Identifying the actorswhointeractwith the system • Describing scenarios of use and linkingactors to use-cases

  14. The Microsoft Customer Model – people and departments

  15. The Microsoft Customer Model – departments and work

  16. The Microsoft Customer Model – personas (roles)

  17. Data modeling • Identifying: • Entities – the groupings in the domain • Attributes – the characteristics of the entities • Relationships – the connection between entities

  18. Data modeling

  19. Design

  20. Learningoutcomes Identify key elements of approaches to improve the interface design and security design of e-commerce systems.

  21. The online customerexperience Your competitors website is just one click away!

  22. Approches to design • Participatory Design • Contextual design • Human-centered design processes for interactive systems (ISO 13407 Model, 1999)

  23. Usability ”An engineering approach to web design to ensure the user interface of the site is learnable, memorable, error free, efficient, and gives user satisfaction. It incorporates testing and evaluation to ensure the best use of navigation and links to access information in the shortest possible time. A companion process to information architecture.” (Jakob Nielsen, 2000)

  24. Goals for usability (Sharp et al. 2007) • Effective to use • Efficient to use • Safe to use • Easy to learn • Easy to remember • Good utility

  25. Someusability design principles (Nielsen 2001) • Visibility of system status • Match between system and the real world • User control and freedom • Consistency and standards • Help users recognize, diagnose and recover from errors • Error prevention • Recognition rather than recall • Flexibility and efficiency of use • Aesthetic and minimalist design • Help and documentation

  26. Information architecture - Cardsorting

  27. Information architecture - sitemaps

  28. Accessibility • Size of display • Type of browser • Resolution • Mobile acces

  29. Different elements of online customerexperience

  30. Security – types of ”attacks” • Malware • Phishing • Denial-of-service (DoS) attack • Virus • Hacking

  31. Security - countermeasures • Information security management systems • Antivirus • Firewall • Encryption • Information security policy • Security standards (e.g.ISO 17799) • Ethical hacker (White hat hackers)

  32. Security - Securetransactions • SecureSocketLayer (SSL) • Virtual Private Network (VPN) • Digital signatures • Certificates (e.g. Verisign)

  33. Example rules triggered by e-mail

  34. Implementation

  35. Learningoutcomes • Produce a plan to minimize the risks involved with the launch phase of an e-business application • Define a process for the effective maintenance of an e-business system • Create a plan to measure the effectiveness of an e-business application

  36. Management issues • What actions can we take to minimize the risks during implementation? • What are the critical success factors? • How do we transition from previous systems to a new e-business system? • What techniques are available to measure the success of our implementation?

  37. Technicalimplementationissues • Acquisition techniques • Site implementation tools • Content management and updating • Localization • System changeover • Evaluation and monitoring

  38. Implementation approaches - The Waterfall model

  39. Implementationapproaches - The iterative approach

  40. Microsoft SureStepimplementationmethodology

  41. Acquisitionmethods • In-housedevelopment (Bespokedevelopment) • Highlytailored solution • Customized standard packaged solution (Off-the-shelf) • Hosted • E-commerce servers

  42. Common web developmentapplications and frameworks A survey of the application frameworks used by Fortune 1000 companies in 2007Source: Port80 software (www.port80software.com/surveys/top1000appservers)

  43. Testing

  44. Usabilityevaluation • Examples of usability evaluation methods • Expert reviews • Heuristics • Usability evaluation • Examples of dimensions of usability evaluation • Effectiveness – can the users complete their tasks correctly and completely? • Productivity (Efficiency) – are tasks completed in an acceptable time? • Satisfaction – are the users satisfied with the interaction

  45. Go-livemethods

  46. Content management system (CMS) • Helpseasyauthoring • Publicationworkflow • Versioning • Tracking and monitoring

  47. Example of a (lenghty) contentupdatereviewprocess

  48. Performance measurement ”the process of quantifying the efficiency and effectiveness of past actions throughacquisition, collation, sorting, analysis, interpretation and dissemination of appropriate data” Neely et al. (2002)

  49. Performance measurementprocess

  50. Commonmeasurements • Uniquevisitors • Visits • Page impression • Ad impressions • Ad clicks

More Related