Slide 11.1 Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Chapter 11 Analysis and design.

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

09/04/2015Unit 2 (b) Back-Office processes Unit 2 Assessment Criteria (b) 10 marks.
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Introduction To System Analysis and Design
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 5: Restaurant.
Building an information architecture
Chapter 3 Database Management
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Info1409 De Montfort University1 Requirements Modelling Systems Analysis & Design Academic Year 2008/9 Info 1409 Lecture 7.
Chapter 4: Database Management. Databases Before the Use of Computers Data kept in books, ledgers, card files, folders, and file cabinets Long response.
“DOK 322 DBMS” Y.T. Database Design Hacettepe University Department of Information Management DOK 322: Database Management Systems.
Sharif University of Technology Session # 7.  Contents  Systems Analysis and Design  Planning the approach  Asking questions and collecting data 
Chapter 13: Designing the User Interface
Where Do I Start REFERENCE: LEARNING WEB DESIGN (4 TH EDITION) BY ROBBINS 2012 – CHAPTER 1 (PP. 3 – 14)
Web 2.0 Testing and Marketing E-engagement capacity enhancement for NGOs HKU ExCEL3.
Object Oriented Analysis and Design Using the UML
Part 3 Digital marketing: implementation and practice Chapter 7 Delivering the online customer experience.
_______________________________________________________________________________________________________________ E-Commerce: Fundamentals and Applications1.
]. Website Must-Haves Know your audience Good design Clear navigation Clear messaging Web friendly content Good marketing strategy.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Chapter 7: The Object-Oriented Approach to Requirements
1. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “Usability Engineering” –Describe the various steps involved.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Paper Prototyping Source:
Chapter 11 Analysis and Design
User Interface Theory & Design
Systems Analysis and Design in a Changing World, Fifth Edition
Introduction To System Analysis and design
Chapter 12 Implementation
Chapter 6 The Traditional Approach to Requirements
Chapter 10 Architectural Design
Chapter 11 Analysis and Design
CHAPTER 9 DATABASE MANAGEMENT © Prepared By: Razif Razali.
Systems Analysis and Design in a Changing World, Fifth Edition
OHT 11.1 © Marketing Insights Limited 2004 Chapter 11 Analysis and Design.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
1 Chapter 11 Implementation. 2 System implementation issues Acquisition techniques Site implementation tools Content management and updating System changeover.
Copyright © 2009 Pearson Education, Inc. Slide 6-1 Chapter 6 E-commerce Marketing Concepts.
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
ITEC224 Database Programming
Chapter 6: Foundations of Business Intelligence - Databases and Information Management Dr. Andrew P. Ciganek, Ph.D.
OHT 11.1 © Marketing Insights Limited 2004 Chapter 9 Analysis and Design EC Security.
Chaffey: Internet Marketing, 2nd edition © Pearson Education Limited 2003 OHT 7.1 Learning objectives Describe the different stages involved in creating.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Chapter 6: NavigationCopyright © 2004 by Prentice Hall 6. Navigation Design Site-level navigation: making it easy for the user to get around the site Page-level.
Designing & Testing Information Systems Notes Information Systems Design & Development: Purpose, features functionality, users & Testing.
6 Systems Analysis and Design in a Changing World, Fifth Edition.
Slide 12.1 Chapter 12 Implementation. Slide 12.2 Learning outcomes Produce a plan to minimize the risks involved with the launch phase of an e-business.
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
UML - Development Process 1 Software Development Process Using UML.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 7 Storing Organizational Information - Databases.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Slide 11.1 CHAPTER 11 ANALYSIS AND DESIGN. Slide 11.2 Learning outcomes  Summarize approaches for analyzing requirements for e-business systems  Identify.
Systems Development Lifecycle
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
E- Tour VIII : Analysis & design E. Widodo. 2 e- Objectives Understand some approaches to analyze requirements of e-Business solution.Understand some.
E-Business Infrastructure PRESENTED BY IKA NOVITA DEWI, MCS.
Course Outcomes of Object Oriented Modeling Design (17630,C604)
System Design Ashima Wadhwa.
Part 3 Digital marketing: implementation and practice Chapter 7 Delivering the online customer experience.
Chapter 11 Analysis and design
Database Design Hacettepe University
Lecture 23 CS 507.
UML Design for an Automated Registration System
Presentation transcript:

Slide 11.1 Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Chapter 11 Analysis and design

Slide 11.2 Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Learning outcomes Summarize approaches for analysing requirements for e-business systems Identify key elements of approaches to improve the interface design and security design of e-commerce systems.

Slide 11.3 Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 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?

Slide 11.4 Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 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

Slide 11.5 Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 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 Examples: Booking a holiday Handling a customer complaint Receiving a customer order

Slide 11.6 Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 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

Slide 11.7 Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure 11.1 An example task decomposition for an estate agency Source: Adapted from Chaffey (1998)

Slide 11.8 Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure 11.1 An example task decomposition for an estate agency (Continued) Source: Adapted from Chaffey (1998)

Slide 11.9 Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure 11.2 Symbols used for flow process charts

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure 11.3 Flow process chart showing the main operations performed by users when working using workflow software

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Process modelling Complete activity using Figure 11.2 and Table 11.2 on pp for how to improve processes What observation do you have for te process of table 11.2? How to improve it? What’s difference between table 11.3 and 11.2? Can it be further improved?

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure 11.4 General model for the Event-driven process chain (EPC) definition model

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Validating Process Models Talk through—Use business scenarios Walk through—role play the service and more details Run through—focus on object interaction

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Data modelling Uses well-established techniques used for relational database design Stages: 1.Identify entities 2.Identify attributes of entities 3.Identify relationships

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 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

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 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 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

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited Identify attributes (Continued) 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

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 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. As is evident from Figure 11.5, the fields customer id and product id are used to relate the order information between the three tables. The fields that are used to relate tables are referred to as key fields. A primary 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

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited Identify relationships (Continued) 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

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure 11.5 Generic B2C ER diagram

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Data Modelling-Normalization Data Normalization is a process to reduce unnecessary redundancy on an existing data model P. 620, Activity 11.3 Exam the Fig E-R diagram to create a normalized E-R Diagram

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Design for E-Business The text covers several aspects in terms of e- Business design –Overall architecture –Security –Interface

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure 11.6 Three-tier client server in an e-business environment

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 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. Predominantly on the server, although some validation can be performed on the client

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 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 Client / server architecture – separation of functions (Continued)

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure 11.7 E-business architecture for a B2C company

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 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)

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 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 expertise 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?

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited stages of Rosenfeld and Morville (2002) 1.Identify different audiences 2.Rank importance of each to business 3.List the three most important information needs of audience 4.Ask representatives of each audience type to develop their own wish lists

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Web Usability An engineering approach to website design to ensure the user interface of the site is learnable, memorable, error free, efficient ad give user satisfaction Expert review Usability testing

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Site design issues 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 Covered by the ten principles that follow

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Principle 1 standards Users spend most of their time on other sites. This means that users prefer your site to work the same way as all the other sites they already know… Think Yahoo and Amazon. Think ‘shopping cart’ and the silly little icon. Think blue text links’ Jakob Nielsen -

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Principle 2 support marketing objectives Support customer lifecycle –Acquisition – of new or existing customers –Retention – gain repeat visitors –Extension – cross- and up-selling Support communications objectives 3 key tactics 1.Communicate the online value proposition 2.Establish credibility 3.Convert customer to action

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Principle 3 support communications objectives 3 key tactics 1.Communicate the online value proposition 2.Establish credibility 3.Convert customer to action

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Principle 4 customer orientation Content + services support a range of audiences and… Different segments 4 familiarities 1.With Internet 2.With company 3.With products 4.With web site

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Principle 6 lowest common denominator Access speed Screen resolution and colour depth Web browser type Browser configuration –Text size –Plug-ins

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Principle 7 aesthetics fit the brand Site personality –How would you describe the site if it were a person? for example, Formal, Fun, Engaging, Entertaining, Professional Site style –Information vs graphics intensive –Cluttered vs Clean Are personality and style consistent with brand and customer orientation? Aesthetics = Graphics + Colour + Style + Layout + Typography

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Principle 9 make navigation easy According to Nielsen, we need to establish: 1.Where am I? 2.Where have I been? 3.Where do I want to go? Context. Consistency. Simplicity.

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Principle 10 support user psychology Hofacker’s 5 stages of information processing 1.Exposure – can it be seen? 2.Attention – does it grab? 3.Comprehension and perception – is message understood? 4.Yielding and acceptance – It is credible and believable? 5.Retention – is the message and experience remembered?

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure 11.8 Different elements of the online customer experience

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure 11.9 Dulux.co.uk web site

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Use-case analysis The use-case method of process analysis and modelling was developed in the early 1990s as part of the development of object-oriented techniques. It is part of a methodology known as Unified Modelling Language (UML) that attempts to unify the approaches that preceded it such as the Booch, OMT and Objectory notations Use-case modelling. A user-centred approach to modelling system requirements Unified Modelling Language (UML). A language used to specify, visualize and document the artefacts of an object-oriented system

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Use-case analysis Persona—summary of characteristics, needs, motivations and environment of typical website users A primary persona must be identified. Sometimes you may also identify a secondary persona Customer scenario—a set of tasks a particular customer want to needs to do to accomplish the desired outcomes.

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Use-case analysis Mini Case Study 11.1 on pp Do you think the website does a good job in supporting the targeted personas?

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Schneider and Winters (1998) stages in Use-Case 1.Identify actors. Actors are typically application users such as customers and employers also other systems 2.Identify use-cases. The sequence of transactions between an actor and a system that support the activities of the actor. 3.Relate actors to use-cases. See Figure on p Develop use-case scenarios. See Figure on p.633 for a detailed scenario

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Customer scenarios and service quality A customer scenario is a set of tasks that a particular customer wants or needs to do in order to accomplish his or her desired outcome. Customer I want to... Successful Outcome: Patricia Seybold, The Customer Revolution Example: New customer – open online account Existing customer – transfer account online Existing customer – find additional product

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure Relationship between actors and use-cases for a B2C company, sell-side e-commerce site

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure Primary scenario for the Register use-cases for a B2C company

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure Clear user scenario options at the RS Components site (

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Design Information Architecture Web IA is the combination of organization, labelling and navigation for a website Common tools for designing the IA of a website: Blueprint/Sitemap*—for the whole website Wireframes—for the page layout

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure Site structure diagram (blueprint) showing layout and relationship between pages. It’s often called sitemap as well.

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure Site structure diagram (blueprint) showing layout and relationship between pages (Continued)

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Wireframe is a graphic representation of the page layout Figure Example wireframe for a children’s toy site

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Customer orientation Depending on the site nature and the available resources, a web site could be designed for different customer segment Ref. Dell.com to see how they target different customers

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Customer orientation Web users are notoriously fickle: They take one look at a home page and leave after a few seconds if they can't figure it out. The abundance of choice and the ease of going elsewhere puts a huge premium on making it extremely easy to enter a site Nielsen

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure Different types of audience for a typical B2B web site

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Elements of the Site Design Much of these have been covered in other courses or earlier in the chapter Site design & structure –Style –Personality –Organization –Navigation schemes Page Design Content Design

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure (a) Narrow and deep and (b) broad and shallow organization schemes

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Web Accessibility This was covered in IMG110. Here is a review checklist.htmlhttp:// checklist.html / /

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Case Study Read the dabs.com case on pp Answer questions on p For question 2, you may compare dabs.com with a store that you are familiar with such as staples.ca or futureshop.ca

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Figure HSBC Global home page (

Slide Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Security Design for e-Business –Read the Box 11.3 on pp and be prepared to discuss the security threat to e- commerce systems.