E- Tour VIII : Analysis & design E. Widodo. 2 e- Objectives Understand some approaches to analyze requirements of e-Business solution.Understand some.

Slides:



Advertisements
Similar presentations
Logical and Physical Design of an Information System
Advertisements

Information Technology IMS5024 Information Systems Modelling Event-driven modelling.
Information Systems Analysis and Design
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
All Rights Reserved: JusticeExperts.com Enterprise? What Enterprise? Enterprise Development.
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.
Chapter 2 Database Environment.
E. Wainright Martin Carol V. Brown Daniel W. DeHayes Jeffrey A. Hoffer William C. Perkins MANAGINGINFORMATIONTECHNOLOGY FIFTH EDITION CHAPTER 9 (part a)
Architecture, Deployment Diagrams, Web Modeling Elizabeth Bigelow CS-15499C October 6, 2000.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
C++ Training Datascope Lawrence D’Antonio Lecture 11 UML.
Chapter 9 Database Design
System Analysis and Design
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Lecture Two Database Environment Based on Chapter Two of this book:
The chapter will address the following questions:
TIBCO Designer TIBCO BusinessWorks is a scalable, extensible, and easy to use integration platform that allows you to develop, deploy, and run integration.
© 2003 McGraw-Hill Australia Pty Ltd, PPTs t/a Accounting Information & Reporting Systems by A. Aseervatham and D. Anandarajah. Slides prepared by Kaye.
PHASE 3: SYSTEMS DESIGN Chapter 7 Data Design.
WORKFLOW IN MOBILE ENVIRONMENT. WHAT IS WORKFLOW ?  WORKFLOW IS A COLLECTION OF TASKS ORGANIZED TO ACCOMPLISH SOME BUSINESS PROCESS.  EXAMPLE: Patient.
Enterprise Systems & Architectures. Enterprise systems are mainly composed of information systems. Business process management mainly deals with information.
Chapter 10 Architectural Design
Chapter Seven Process Modeling, Process Improvement, and ERP Implementation.
The Design Discipline.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Overview of the Database Development Process
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
ITEC224 Database Programming
Changing Perspective From Structured to Object-oriented.
CST203-2 Database Management Systems Lecture 2. One Tier Architecture Eg: In this scenario, a workgroup database is stored in a shared location on a single.
ITEC 3220M Using and Designing Database Systems
CSCI 3140 Module 2 – Conceptual Database Design Theodore Chiasson Dalhousie University.
OHT 11.1 © Marketing Insights Limited 2004 Chapter 9 Analysis and Design EC Security.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
CSC 480 Software Engineering OOAD Process. Topics Overview: OOAD Process The object model Identifying classes Responsibilities and collaborations Hierarchy:
1 Welcome to CSC 301 Web Programming Charles Frank.
Systems Analysis and Design in a Changing World, 3rd Edition
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
GRASP: Designing Objects with Responsibilities
UHD::3320::CH121 DESIGN PHASE Chapter 12. UHD::3320::CH122 Design Phase Two Aspects –Actions which operate on data –Data on which actions operate Two.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
© 2005 Prentice Hall1-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Slide 11.1 Dave Chaffey, E-Business and E-Commerce Management, 4 th Edition, © Marketing Insights Limited 2009 Chapter 11 Analysis and design.
Feb. 9, 2004CS WPI1 CS 509 Design of Software Systems Lecture #4 Monday, Feb. 9, 2004.
E-commerce COM380 E-commerce Lecture 10 Analysis and maintenance.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
IBM Global Services © 2005 IBM Corporation SAP Legacy System Migration Workbench| March-2005 ALE (Application Link Enabling)
UML - Development Process 1 Software Development Process Using UML.
1 Database Environment. 2 Objectives of Three-Level Architecture u All users should be able to access same data. u A user’s view is immune to changes.
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
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 4: Analysis and Design Overview.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
ENTITY RELATIONSHIP DIAGRAM. Objectives Define terms related to entity relationship modeling, including entity, entity instances, attribute, relationship.
Basic Concepts of Software Architecture. What is Software Architecture? Definition: – A software system’s architecture is the set of principal design.
Review Business Analyst vs. Systems Analyst – A Business Analyst identifies a problem and states – in business terms -- what the solution is. They define.
ITEC 3220A Using and Designing Database Systems
Object-Oriented Analysis and Design
Unified Modeling Language
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
CHAPTER 9 (part a) BASIC INFORMATION SYSTEMS CONCEPTS
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Lecture 23 CS 507.
Presentation transcript:

e- Tour VIII : Analysis & design E. Widodo

2 e- Objectives Understand some approaches to analyze requirements of e-Business solution.Understand some approaches to analyze requirements of e-Business solution. Know some key elements of techniques to provide “blueprint” design for the e-Business solution.Know some key elements of techniques to provide “blueprint” design for the e-Business solution.

3 e- Contents IntroIntro Analysis for e-BusinessAnalysis for e-Business Process modelingProcess modeling Data modelingData modeling Design for e-BusinessDesign for e-Business

4 e- Intro General understanding of analysis & design:General understanding of analysis & design: –Analysis: platform-independent approach to elicit “what” are the requirements of system’s business- process or users. –Design: platform-dependent models as guidance to develop final system solution. –Analysis & design: identifying and structuring of system requirements to be able to create the plan/blueprint of e-business solution effectively & efficiently. –Role: to convert strategic planning into final implementation of system solution. StrategicPlanningSystemSolution Analysis Design

5 e- Analysis for e-business Analysis for e-business: understanding the business and user requirements for e-business system by:Analysis for e-business: understanding the business and user requirements for e-business system by: –Understanding the current business process –Reviewing possible alternatives for implementing e- business solution Role: used as a tool to optimize the flow of information both inside and outside organization.Role: used as a tool to optimize the flow of information both inside and outside organization. Commonly used tools:Commonly used tools: –Workflow management (WFM) –Process modeling (PM) –Data modeling (DM)

6 e- Workflow management WFM: the automation of a business process, in a whole or part during which documents, information or task are passed from one participant to another for action, according to a set of procedural rules.WFM: the automation of a business process, in a whole or part during which documents, information or task are passed from one participant to another for action, according to a set of procedural rules. Criteria in performing WFM:Criteria in performing WFM: –As soon as possible –By the right entity –In the right order Purpose:Purpose: –Assign task to people/entity –Remind people about their tasks –Allow collaboration between people/entity –Retrieve information needed to perform task –Provide report to management about task status & organization performance

7 e- Process modeling Using hierarchical method of:Using hierarchical method of: –The processes and its constituent sub-processes –The dependencies between processes –The inputs and outputs of processes Activity-based process definition: analysis tools used to identify the relationship between tasks within business process.Activity-based process definition: analysis tools used to identify the relationship between tasks within business process. Process: part of a system that has a clearly defined purpose or objective as well as clearly defined inputs & outputs.Process: part of a system that has a clearly defined purpose or objective as well as clearly defined inputs & outputs. Process mapping: identification of location and responsibility of process within organizationProcess mapping: identification of location and responsibility of process within organization –Purpose: to eliminate the overlapping of functional area

8 e- Example of process mapping

9 e- Task analysis & decomposition Task Analysis: identification of a group of task, their sequence and how they are broken down.Task Analysis: identification of a group of task, their sequence and how they are broken down. Curtis 1995 provides a useful framework of task analysis & decomposition as follow:Curtis 1995 provides a useful framework of task analysis & decomposition as follow: –Level 1 Business Process Level 2 ActivitiesLevel 2 Activities –Level 3 Task »Level 4 Sub-task Business process: a set of one or more linked procedure or activities which collectively realize a business objective.Business process: a set of one or more linked procedure or activities which collectively realize a business objective. Activity: a collection of work that forms one logical step within a process.Activity: a collection of work that forms one logical step within a process. Task (Work item) : representation of the work to be processed in the context of an activity within a process instance.Task (Work item) : representation of the work to be processed in the context of an activity within a process instance.

10 e- Example of task analysis

11 e- Flow process chart FPC: tools for describing the sequence of activities of a workflow that is a part of a business processFPC: tools for describing the sequence of activities of a workflow that is a part of a business process Symbols used:Symbols used:

12 e- Example of Flow Process Chart

13 e- Using FPC for efficiency (1/2) Original situationOriginal situation

14 e- Using FPC for efficiency (2/2) After re-engineering processAfter re-engineering process

15 e- Network diagram (Generalized Activity Network = GAN)

16 e- Event-driven Process Chain (EPC)  Model for SAP R/3 ERP

17 e- General model of EPC

18 e- Use-case analysis

19 e- Use-case scenario

20 e- Data modeling Data modeling for e-Business & e-Commerce system solution is referred to relational database analysis in information system management:Data modeling for e-Business & e-Commerce system solution is referred to relational database analysis in information system management: –Entity Relationship Diagram –Normalization Critical step in developing them:Critical step in developing them: –Identifying entities –Identifying attributes for entities –Identifying relationships & its properties among them Things to be remembered:Things to be remembered: –Entity –Attribute (primary key, secondary key) –Record –Relationship

21 e- Example of data modeling

22 e- Design for e-Business Architectural design of e-Business system:Architectural design of e-Business system: –Client/server model: system architecture in which end-user machine is known as client run application while accessing data and program from server –Typical function in client/server model: Data storageData storage Query processingQuery processing Display/Interface  the most prominentDisplay/Interface  the most prominent Application logicApplication logic –Three-tier client/server model: the first tier is the client that handles display, the second is application logic & business rules, the third is database storage.

23 e- Display/interface Display/interface is the front-line of e-business & e-commerce system solution to the users.Display/interface is the front-line of e-business & e-commerce system solution to the users. It varies in term of:It varies in term of: –Structure –Presentation –Behavior Display/interface implements hypertext scheme.Display/interface implements hypertext scheme. Navigation refers to paging structure and process flow among system display. It also reflects system solution functionality derived from its business use-cases.Navigation refers to paging structure and process flow among system display. It also reflects system solution functionality derived from its business use-cases.

24 e- Display: structure, presentation & behavior

25 e- Three-tier client/server model

26 e- e-Business architecture

27 e- 8 th week souvenir Task 1: Base on your previously agreed topic arrange its analysis and design phases prior to its implementation. Note: at least it consists of: 1. Process mapping 2. Task analysis 3. Use-case model 4. Flow process chart 5. Data modeling 6. Interface navigation