IT Course of e-Professional Training for ADOC in Peru · IT Course of e-Professional Training for...

IT Course of e-Professional Training for ADOC in

Peru

System Architecture Design

in Enterprise

Robert C. Wu, DBA/[email protected]

2

Agenda

? Overview? Information Technology in Enterprise? Software Implementation in Enterprise? Well-engineered Software? Software Specification and Design

3

Background of Instructor

? 8 Years Solid Working Experience in Enterprise Resource Planning and Supply Chain Management

? Familiar with Both SAP N1 and Oracle eBS Top Worldwide Enterprise SW System

? Chief Designer of WinsERP which Is A Package Developed for SME in Oriental

4

IT in Enterprise

? Desktop Environment? Infrastructures? Security? Real-time Performance Management? Collaboration Accomplishment? Customer Satisfaction and Success

5

Challenge of Administrating IT

? Mixed Desktop and Platform Environment? Multi-Sites? Both Wire and Wireless Streaming? Avoiding Attack and Spam? Secure Information? Deploy Difficult Without Thin-UI

6

Real-time Performance Management

? Best Description of e-Business? On-time Is Only Standard? Synchronization of? Operation Scale? Execution Speed? Location Spread

? En-powering the Real-Time Manufacturer

7

Classic Planning Cycle

8

Real-time Planning Cycle

9

Collaboration Accomplishment

? Quick & Correct Order Responding? Planning? Collaboration? Simulation? Commitment

10


Order-DrivenNew, Change

1. Planning

3. Simulation4. Commitment

4. Commitment2. Collaboration

2. Collaboration

11


1 3 4 , 9 8 7Metric-n3 4 5Metric-2

- 3 5 5 , 1 4 5

4 , 1 3 4 , 9 8 7Metric-1Scenario

nScenar io

2Scenar io

1Base P lan

+23-232 ,347 -29 ,100+ 3 5

22,992 +11 ,000 - 68 ,954- 1 7

Order-Driven Change

P lann ingResults

Suppl iers Col laborat ionFeedback

Simulat ion

Profitability Analysis

Commitment to Customer

12


J IT De l ive ry C o r r e c t i v e

A c t i o n s

D a t a C o l l e c t i n g

Objec t B 2 B i

E R P I n v e n t o r y m o d u l e , e P r o c u r e m e n t M o d u l e

b u y e r

account

p r o d u c tp rocurement

B P M p r o c e s s

E x e c u t i n g O f f i c e r

M a t e r i a lSupp ly ing

suppl ier

manufac

13

Customer Satisfaction and Success

? Win Business Opportunity? Quick to Market? Better Customer Service? Accurate Order Confirmation? Inventory Reduction? On-Time Delivery Improved? Visibility of Information Flow Improved

14

Grow-up Enterprise

Value Disciplines and the Life Cycle

Tornado

Main Street

Operational Excellence+

Customer IntimacyProduct Leadership

+Operational Excellence

Bowling Alley

Product Leadership+

Customer Intimacy

? ? Geoffrey Moore 1995 Inside the Tornado« ? ? ? ? » ? 176?

Product Leadership

Only

15

SW Implementation in Enterprise

? Transaction System? Networking System? Planning and Analyzing System? Collaboration System

16

Systems Stack

ERP

B2Bi EAI

BPM / Portal

Sales Processes

Planning Processes

Procurement Processes

Service Processes

Real-Time Performance Management

Enterprise IT Structure

17

Transaction System

? Keep Business Operation in Record? 4 Purposes to Record? Administration? Calculation? Audit? Analysis

? Foundation of e-Business

18

Networking System

? Provide Information Super Highway? Link All Stand Alone Computers Into Web? Administrate Different Types or Size? LAN?WAN? VPN

19

Process Through Network

B u y e r s S a le s

B P P ( B u s i n e s s P r o c e s s P l a t f o r m )

O M M R P I V G L

R e a l - T i m e P e r f o r m a n c e M a n a g e m e n t

B u s i n e s s R u l e s

20

Networking Business Transactions

21

Process Is Soul of SW

? Process Is The Enterprise Know-how? Solid Process Makes Create Key

Performance Index (KPI) Possible? SW Operated by Computing Logic that is

Business Process in Enterprise? Data (Transaction) Analyses by Business

Logic that is Effect of Process

22

Enhancing Process (As Is)

Define Negotiate Perform Assess

Customer

ODM/OEM

SupplierTier 1

SupplierTier 2

Place Order

Commit to delivery

Sendinvoice

Payinvoice

Ordermaterials

Commit to delivery

Ordermaterials

Commit to delivery

Deliver ordered Materials

Internal Processes

Sendinvoice

Sendinvoice

Payinvoice

Payinvoice

23

Enhancing Process (To Be)


Customer

ODM/OEM

SupplierTier 1

SupplierTier 2

Place Order

Commit to delivery

Sendinvoice

Payinvoice

Negotiate order

commitment

Commit to delivery

Negotiate order

commitment

Commit to delivery


Internal Processes

Sendinvoice

Sendinvoice

Payinvoice

Payinvoice

TimeSaved

24

Enhancing Process (To Be)


Customer

ODM/OEM

SupplierTier 1

SupplierTier 2

Place Order

Commit to

delivery

Sendinvoice

Payinvoice

Negotiate order

commitment

Commit to delivery

Negotiate order

commitment

Commit to delivery


Internal Processes

Sendinvoice

Sendinvoice

Payinvoice

Payinvoice

25

Flow of Standardize Processing

CustomerRole

Type of Communication

SupplierRole

Define

Negotiate Perform

Assess

Offer/ Request

Agree Report Accept/ Reject

Time

Withdraw?No

Notify

Yes

26

Advancing to Collaboration

? Processes Between Companies that is Basic Meaning of Collaboration

? Co-working Like A Virtual Team? Platform Provided Needed for Communicate

for Business Issues

27

Collaboration Processing Structure

28

Collaborations Cause Chain

? To The Side of Some Tiers Suppliers that is Supply Chain

? To The Side of Some Tiers Customers that is Demand Chain

? Enhancing Performance of Chain that is Basically Process Re-engine

29

Model of Chain Operating

eProcess

ProcessIntegration

KPIcollection

cSupply

PlanningIntegration

Tracking

Receiving

AP

Delivering

cPlanning

OrderCollaborative

30

Well-engineered SW

? Key Attributes? The Software Process? Management Process Models

31

Advantages of Well-engineered SW

? Stable in Perform Production of Enterprise? Reducing Cost in Re-design or Spec

Changing? Correction Assure, Avoiding Garbage-in

Garbage-out

32

Key Attributes of Well-engineered SW

? The SW should be maintainable. As long-lifetime SW is subject to regular change, it should be written and documented so that changes can be made with undue costs.

? The SW should be reliable. This means that it should perform as expected by users and should not fail more often than is allowed for in its specification.

33


? The SW should be efficient. This does not necessarily mean that the last ounce of performance is squeezed out of the system HW; maximizing efficiency may make the SW more difficult to change. Efficiency means that a system should not make wasteful use of system resources such as memory and processor cycles.

34


? The SW should offer an appropriate user interface. Much SW is not used to its full potential because its interface makes it difficult to use. The user interface design must be tailored to the capabilities and background of the system users.

35

Waterfall Model of SW Development

? Requirements analysis and definition? System and SW design? Implementation and unit testing? Integration and system testing

36

Waterfall Model of SW Development

? Make up of a number of stages then defined it is “signed-off” and development proceeds to the following stage (Waterfall Model)

? Exploratory programming? Prototyping? Formal transformation? System assembly from reusable components

37

Managing by Document

? The timing of management requirements may not necessarily correspond with the time required to complete an activity so artificial documents may by produced

? The need to approve documents tends to constrain process integration as the costs of going back and adapting a completed deliverable are high

38

Managing by Document

? The notion that document from one stage should act as the defining input to the next stage is flawed

? The time required to review and approve a document is significant and there is rarely a smooth transition from one phase of the process to the next.

39

Documents for Activity

? Requirements analysis ? Feasibility study, Outline requirements

? Requirements definition ? Requirements specification

? System specification ? Functional specification, Acceptance test specification, Draft user manual

40


? Architectural design ? Design architecture specification, System test specification

? Interface design ? Interface specification, Integration test specification

? Detailed design ? Design specification, Unit test specification

? Coding ? Program code

41


? Unit testing ? Unit test result report? Module testing ? Module test result report? Integration testing ? Integration test report,

Final user manual? System testing ? System test report? Acceptance testing ? Final system

42


? Suitable: Waterfall model, Formal transformations

? Not Suitable: Exploratory programming, Reuse-oriented model

? Prototyping: Uneconomic to generate documents during initial phase of fast integration; later phases OK if waterfall model followed

43

SW Spec and Design

? Requirements Definition? System Modeling? Software Prototyping? Software Design? Real-Time Systems Design? User Interface Design

44

Q & A

? Thank You All, and Hope Being Helpful? Welcome to Reach Me by e-mail? [email protected]

? ADOC Office Locally

IT Course of e-Professional Training for ADOC in Peru · IT Course of e-Professional Training for...

Documents

Transcript of IT Course of e-Professional Training for ADOC in Peru · IT Course of e-Professional Training for...