IT Course of e-professional Training for ADOC in Peru

Transcription

1 IT Course of e-professional Training for ADOC in Peru System Architecture Design in Enterprise Robert C. Wu, DBA/PsyD

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

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 3

4 IT in Enterprise Desktop Environment Infrastructures Security Real-time Performance Management Collaboration Accomplishment Customer Satisfaction and Success 4

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 5

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 6

7 7 Classic Planning Cycle

8 8 Real-time Planning Cycle

9 Collaboration Accomplishment Quick & Correct Order Responding Planning Collaboration Simulation Commitment 9

10 Collaboration Accomplishment 2. Collaboration 4. Commitment 1. Planning 3. Simulation 2. Collaboration 4. Commitment Order-Driven New, Change 10

11 Collaboration Accomplishment Profitability Analysis Planning Results Suppliers Collaboration Feedback Order-Driven Change Commitment to Customer Simulation 11 Metric-1 Metric-2 Metric-n Base Plan 4,134, ,987 Scenario 1-355, Scenario 2 Scenario n -232,347-29, , ,000-68,954

12 Collaboration Accomplishment Executing Officer BPM process Data Collecting Object buyer product supplier JIT Delivery Corrective procurement Actions B2Bi Material Supplying manufac account 12 ERP Inventory module, eprocurement Module

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 13

14 Grow-up Enterprise Value Disciplines and the Life Cycle Product Leadership + Operational Excellence Main Street Operational Excellence + Customer Intimacy Product Leadership Only Tornado Bowling Alley 14 Product Leadership + Customer Intimacy?? Geoffrey Moore 1995 Inside the Tornado «????»? 176?

15 SW Implementation in Enterprise Transaction System Networking System Planning and Analyzing System Collaboration System 15

16 Systems Stack Sales Processes Enterprise IT Structure Real-Time Performance Management Planning Processes Procurement Processes BPM / Portal Service Processes B2Bi EAI 16 ERP

17 Transaction System Keep Business Operation in Record 4 Purposes to Record Administration Calculation Audit Analysis Foundation of e-business 17

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

19 Process Through Network Real-Time Performance Management Business Rules Buyers Sale s BPP (Business Process Platform) 19 OM MRP IV GL

20 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 21

22 Enhancing Process (As Is) Define Negotiate Perform Assess Customer ODM/OEM Supplier Tier 1 Supplier Tier 2 Place Order Order materials Commit to delivery Order materials Commit to delivery Commit to delivery Send invoice Send invoice Pay invoice Send invoice Pay invoice Pay invoice 22 Deliver ordered Materials Internal Processes

23 Enhancing Process (To Be) Define Negotiate Perform Assess Customer ODM/OEM Place Order Commit to delivery Send invoice Pay invoice Supplier Tier 1 Supplier Tier 2 Negotiate order commitment Negotiate order commitment Commit to delivery Commit to delivery Time Saved Send invoice Send invoice Pay invoice Pay invoice 23 Deliver ordered Materials Internal Processes

24 Enhancing Process (To Be) Define Negotiate Perform Assess Customer ODM/OEM Place Order Commit to delivery Send invoice Pay invoice Supplier Tier 1 Supplier Tier 2 Negotiate order commitment Negotiate order commitment Commit to delivery Commit to delivery Send invoice Send invoice Pay invoice Pay invoice 24 Deliver ordered Materials Internal Processes

25 Flow of Standardize Processing Customer Role Define Notify Assess Type of Communication Offer/ Request Agree Report Accept/ Reject Yes Withdraw? No Supplier Role Negotiate Perform 25 Time

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 26

27 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 28

29 Model of Chain Operating Planning Order Collaborative Integration Receiving AP Tracking Delivering cplanning KPI collection Process Integration csupply 29 eprocess

30 Well-engineered SW Key Attributes The Software Process Management Process Models 30

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 31

32 Key Attributes of Well-engineered SW The SW should be maintainable. As longlifetime 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. 32

33 Key Attributes of Well-engineered SW 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. 33

34 Key Attributes of Well-engineered SW 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. 34

35 Waterfall Model of SW Development Requirements analysis and definition System and SW design Implementation and unit testing Integration and system testing 35

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 36

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 37

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. 38

39 Documents for Activity Requirements analysis? Feasibility study, Outline requirements Requirements definition? Requirements specification System specification? Functional specification, Acceptance test specification, Draft user manual 39

40 Documents for Activity 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 40

41 Documents for Activity 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 41

42 Documents for Activity 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 42

43 SW Spec and Design Requirements Definition System Modeling Software Prototyping Software Design Real-Time Systems Design User Interface Design 43

44 Q & A Thank You All, and Hope Being Helpful Welcome to Reach Me by wu.chibin@msa.hinet.net ADOC Office Locally 44