Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition

1. Systems Analysis and Design With UML 2.0An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc.

2. INTRODUCTION Chapter 1

3. Key Ideas 1996 Survei by The Standish Group 46% of all corporate IS project were abandoned before completion • Analysts tried to build wonderful systems without understanding the organization • The primarily goal is to create value for the organization 1996 Survei by General Accounting Office 53% of all U.S. Government IS were abandoned

4. Key Ideas • Systems analystadalah orang utama yang menganalisa proses business, mengidentifikasikan kesempatan perbaikan, dan pendesainan sisteminformasiuntuk menerapkan konsep ini. • Merupakan hal yang penting untuk memahami dan mengembangkan melalui melatih skill yang diperlukan untuk mendesain dan mengimplementasikan sistem informasi baru yang sukses

5. THE SYSTEMS DEVELOPMENT LIFE CYCLE

6. Major Attributes of the Lifecycle • The project • Bergerak sistematis pada fase – fase dimana setiap fase memiliki output • Menghasilkan project deliverables • Menggunakan deliverables pada implementasi • Hasil pada actual information system • menggunakangradual refinement

7. Project Phase – Planning(1) • Kenapa sistem informasi harus di bangun? • Bagaimana project team menanganinya? ?

8. Project Phase – Planning(2) • Step #1 (Project initiation) System request Project sponsor Generate the request IS Approval Commitee (Steering commitee) IS Department Feasibility analysis Technical feasibility Can we build it? Economic feasibility Will it provide business value? Organization feasibility If we build, will it be used?

9. Project Phase – Planning(2) • Step #2 (Enters project management) Project manager Workplan Staff the project Techniques Help the project team control and direct the project

10. Project Phase – Analysis(1) • Siapa yang menggunakan sistem tersebut? • Apa yang dilakukan sistem tersebut? • Dimana sistem tersebut digunakan? ?

11. Project Phase – Analysis(2) Project team Investigate any current system(s) Identifies improvement opportunities Develops a concept for the new system

12. Project Phase – Analysis(3) • Analysis strategy • Developed to guide the project team’s effort • Analysis of the current system (as-is system) & it’s problems • Ways to design a new system (to be system) Requirement gathering System proposal = analysis + system concept + models Presented to teh project sponsor and other key decision makers Decide whether the project sholud be continue to move forward

13. Project Phase – Design(1) • Bagaimana sistem akan beroperasi • Hardware, software, network infrastructure, user interface .... ?

14. Project Phase – Design(2) Design strategy Whether the system will be operate by the company’s own programmer Whether the system will be outsourced to another firm Whether the company will buy an existing software package Basic Architecture Design Database and file specifications Program design

15. Project Phase - Implementation Construction System is built and tested to ensure it performs as designed Installation Direct customer approach Parallel convertion approach Phase conversion strategy Support plan Forma and informal post-implementation review

16. A “Simple” Process for Making Lunch

17. Process Product Project Plan System Proposal System Specification New System and Maintenance Plan Planning Analysis Design Implementation Processes and Deliverables

18. SYSTEM DEVELOPMENT Methodologies

19. What Is a Methodology? • Pendekatan formal pada rangkaian tahap • Menulis code tanpa kejelasanmungkin berhasil untuk program yang kecil, tapi apakahberhasil pada sistem yang besar?

20. Structured Design • Berpindah secara metodis dari satu langkah ke yang lain • Secara umum, sebuah langkah selesai sebelum masuk ke langkah berikutnya

21. Waterfall Development Method

22. Pros and Cons of the Waterfall Method Pros Cons Identifies systems requirements long before programming begins Design must be specified on paper before programming begins Long time between system proposal and delivery of new system

23. Parallel Development

24. Alternatives to the SDLC • Rapid Application Development (RAD) • Phased Development • Prototyping • Throw-Away Prototyping

25. Critical elements CASE tools JAD (Join Application Design) sessions Fourth generation/visualization programming languages Code generators Rapid Application Development

26. Phased development A series of versions Prototyping System prototyping Throw-away prototyping Design prototyping Agile Development Extreme Development Rapid Application Development Categories

27. How Prototyping Works

28. Throwaway Prototyping

29. Selecting the Appropriate Methodology • Clarity of User Requirements • Familiarity with Technology • System Complexity • System Reliability • Short Time Schedules • Schedule Visibility

30. Criteria for Selecting a Methodology

31. Project Team Roles and Skills

32. Information Systems Roles • Business analyst • System analyst • Infrastructure analyst • Change management analyst • Project manager

33. Project Team Roles

34. Summary -- Part 1 • The Systems Development Lifecycleberisi 4 tahapan: Planning, Analysis, Design, and Implementation • The major developmentmethodologies: • Structured design • the waterfall method • Parallel development • RAD development • Prototyping (regular and throwaway) • Agile development • XP streamline SDLC

35. Summary -- Part 2 • Ada 5 peran penting dalam team: business analyst, systems analyst, infrastructure analyst, change management analyst dan project manager.