Materi 4 Information System Engineering Sim 1223511116853894 8


Published on

Published in: Education, Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Materi 4 Information System Engineering Sim 1223511116853894 8

    1. 1. Sistem Informasi Manajemen Dr. Hary Budiarto Materi 4 Information System Engineering (1)
    2. 2. Menentukan Teknologi yang digunakan Orang yang membiayai
    3. 3. Information System Services Organization Sistem informasi
    4. 4. Information Systems Analysis <ul><ul><li>Information systems analysis merupakan salah satu kegiatan dari fase pengembangan implementasi sistem informasi yang berfokus pada penyelesaian permasalahan bisnis yang tidak tergantung pada jenis teknologi yang digunakan. </li></ul></ul>
    5. 5. System Owners <ul><li>System owners adalah lembaga yang menyediakan dana dalam implementasi proyek sistem informasi yang meliputi pengembangan, operasional dan perawatan sistem informasi. </li></ul>
    6. 6. System Users / Client <ul><li>System users adalah SDM yang terlibat langsung secara reguler implementasi sistem informasi yang terdiri dari capturing (memperoleh data), validating (mengecek), entering (memasukkan dan menyimpan), responding (), storing (perbaikan data), dan exchanging data & informasi. </li></ul><ul><li>Nama lain dari system user adalah klien (client) yang meliputi : </li></ul><ul><ul><li>Internal users </li></ul></ul><ul><ul><ul><li>Clerical and service workers </li></ul></ul></ul><ul><ul><ul><li>Technical and professional staff </li></ul></ul></ul><ul><ul><ul><li>Supervisors, middle managers, and executive managers </li></ul></ul></ul><ul><ul><ul><li>Remote and mobile users (internal but disconnected) </li></ul></ul></ul><ul><ul><li>External users </li></ul></ul><ul><ul><ul><li>customer </li></ul></ul></ul>
    7. 7. System Designers and System Builders <ul><li>System designers bertugas untuk menerjemahkan kebutuhan kegiatan bisnis system users ke suatu perancangan teknis sistem informasi yang meliputi perancangan computer files, databases, inputs, outputs, screens, networks, dan programs yang sesuai dengan keinginan system users. </li></ul><ul><li> hanya pada dokumentasi </li></ul><ul><li>System builders bertugas untuk membangun seluruh komponen sistem informasi berbasis pada spesifikasi teknis dari system designers. Dalam sejumlah kasus biasanya system designer dan builder merupakan satu institusi yang sama personilnya. </li></ul>
    8. 9. Information System Building Blocks
    9. 11. The Systems Analyst as a Facilitator
    10. 12. The DATA Focus
    11. 13. The DATA Focus <ul><li>System owners’ perspective </li></ul><ul><ul><li>Business knowledge is the insight that is gained from timely, accurate, and relevant information. (Recall that information is a product of raw data.) </li></ul></ul><ul><li>System users’ perspective </li></ul><ul><ul><li>Data requirements are a representation of users’ data in terms of entities, attributes, relationships, and rules. Data requirements should be expressed in a format that is independent of the technology that can or will be used to store the data. </li></ul></ul><ul><li>System designers’ perspective </li></ul><ul><ul><li>Database schema </li></ul></ul><ul><li>System builders’ perspective </li></ul><ul><ul><li>Database management system </li></ul></ul>
    12. 14. The PROCESS Focus
    13. 15. The PROCESS Focus <ul><li>System owners’ perspective </li></ul><ul><ul><li>Business functions are ongoing activities that support the business. Functions can be decomposed into other subfunctions and eventually into processes that do specific tasks. </li></ul></ul><ul><ul><li>A cross-functional information system supports relevant business processes from several business functions without regard to traditional organizational boundaries such as divisions, departments, centers, and offices. </li></ul></ul>
    14. 16. The PROCESS Focus <ul><li>System users’ perspectives </li></ul><ul><ul><li>Business processes are activities that respond to business events. Business processes are the “work” performed by the system. </li></ul></ul><ul><ul><li>Process requirements are a representation of the users’ business processes in terms of activities, data flows, or work flow. </li></ul></ul><ul><ul><li>A policy is a set of rules that govern a business process. </li></ul></ul><ul><ul><li>A procedure is a step-by-step set of instructions and logic for accomplishing a business process. </li></ul></ul>
    15. 17. The PROCESS Focus <ul><li>System designers’ perspectives </li></ul><ul><ul><li>An application schema is a model that communicates how selected business processes are, or will be, implemented using the software and hardware. </li></ul></ul><ul><ul><li>Software specifications represent the technical design of business processes to be automated or supported by computer programs to be written by system builders. </li></ul></ul><ul><li>System builders’ perspectives </li></ul><ul><ul><li>Application programs are language-based, machine-readable representations of what a software process is supposed to do, or how a software process is supposed to accomplish its task. </li></ul></ul><ul><ul><li>Prototyping is a technique for quickly building a functioning, but incomplete model of the information system using rapid application development tools. </li></ul></ul>
    16. 18. The INTERFACE Focus
    17. 19. The INTERFACE Focus <ul><li>System owners’ perspective </li></ul><ul><li>System users’ perspectives </li></ul><ul><ul><li>Interface requirements are a representation of the users’ inputs and outputs. </li></ul></ul><ul><li>System designers’ perspective </li></ul><ul><ul><li>User dialogues describe how the user moves from window-to-window, interacting with the application programs to perform useful work. </li></ul></ul><ul><li>System builders’ perspective </li></ul><ul><ul><li>Middleware is a layer of utility software that sits in between application software and systems software to transparently integrate differing technologies so that they can interoperate. </li></ul></ul>
    18. 20. The Role of the Network in IS
    19. 21. A COMMUNICATIONS Focus in IS
    20. 22. Information System Development Focus
    21. 23. Process of System Development <ul><li>A system development process is a set of activities, methods, best practices, deliverables, and automated tools that stakeholders use to develop and maintain information systems and software. </li></ul>A project is a [temporary] sequence of unique, complex, and connected activities having one goal or purpose and that must be completed by specific time, within budget, and according to specification.
    22. 24. Project versus Process Management <ul><li>Project management is the process of scoping, planning, staffing, organizing, directing, and controlling the development of an acceptable system at a minimum cost within a specified time frame. </li></ul><ul><li>Process management is an ongoing activity that documents, manages the use of, and improves an organization’s chosen methodology (the “process”) for system development. Process management is concerned with the activities, deliverables, and quality standards to be applied to all projects. </li></ul>
    23. 25. Measures of Project Success <ul><ul><li>The resulting information system is acceptable to the customer. </li></ul></ul><ul><ul><li>The system was delivered “on time.” </li></ul></ul><ul><ul><li>The system was delivered “within budget.” </li></ul></ul><ul><ul><li>The system development process had a minimal impact on ongoing business operations. </li></ul></ul><ul><ul><li>Project management Function : </li></ul></ul><ul><ul><li>Scoping, Planning, Estimating ,Scheduling </li></ul></ul><ul><ul><li>Organizing, Directing, Controlling </li></ul></ul><ul><ul><li>Closing </li></ul></ul>
    24. 26. Project Management Life Cycle
    25. 27. Project Management Tools & Techniques <ul><li>A PERT chart is a graphical network model that depicts a project’s tasks and the relationships between those tasks. </li></ul><ul><li>A Gantt chart is a simple horizontal bar chart that depicts project tasks against a calendar. Each bar represents a named project task. The tasks are listed vertically in the left-hand column. The horizontal axis is a calendar timeline. </li></ul>
    26. 28. PERT Chart 5-3-2008 5-12-2008 5-3-2008 5-11-2008 Preliminary Investigation 5-12-2008 6-12-2008 5-12-2008 6-14-2008 Problem Analysis 5-28-2008 7-15-2008 5-30-2008 7-18-2008 Requirements Analysis 6-13-2008 7-30-2008 6-13-2008 8-3-2008 Decision Analysis 9-10-2008 12-14-2008 TBD TBD Implementation 7-19-2008 11-13-2008 7-20-2008 In Progress Construction 7-3-2008 9-25-2008 7-5-2008 10-9-2008 Design 5-3-2008 N/A 5-3-2008 N/A Project Initiation Scheduled Start Scheduled Finish Actual Start Actual Finish Task Scheduled Start Scheduled Finish Actual Start Actual Finish Task intertask dependency Legend
    27. 29. Gantt Chart Incomplete Task Complete Task Legend ID 1 2 3 4 5 6 7 Preliminary investigation Problem analysis Requirements analysis Decision analysis Design Construction Implementation May Jun Jul Aug Sep Oct Nov Dec 2008 Task Name Today
    28. 30. Microsoft Project Gantt Chart
    29. 31. Microsoft Project PERT Chart