Pengembangan Sistem Informasi Pertemuan 23

advertisement
Matakuliah
Tahun
Versi
: T0604-Pengantar Teknologi Informasi
: 2008
: 2.0/0.0
Pertemuan 23
Pengembangan Sistem
Informasi
Sumber:
Chapter 10. System Analysis &
Programming: S/W Development,
Programming, & Languages, p.463
Williams, B.K, Stacy C. Sawyer (2007).
Using Information Technology: A
Practical Introduction to Computers &
Communications. Seventh Edition,
McGraw-Hill, New York. ISBN-13: 978-007-110768-6
1
Learning Outcomes
Pada akhir pertemuan ini, diharapkan mahasiswa
akan mampu :
• menjelaskan enam langkah dalam
pengembangan sistem informasi (C2)
2
Outline Materi
• The purpose of a system
• Starting the project
• Six phases of systems analysis & design
3
Systems Development
• Organizations can make mistakes, and big organizations can
make really big mistakes
• Murphy’s Law: Whatever can go wrong, will go wrong,
and at the worst possible time
• A system
Warning!
Road Out!
– A collection of related components that interact to
perform a task in order to accomplish a goal
• Systems Development
– 6-phase process of gathering information about
system requirements and using that to develop a
new system that improves productivity
10-4
Systems Development
• The three kinds of users of a project are:
– Users
• The new system must ALWAYS be developed in
consultation with the people who will be using the
completed system
– Management
• Managers within an organization should be consulted
about the system, as they control the budget and
resources
– Technical staff
• The Information Systems or IT staff must be involved
so they can make sure the technology is there
10-5
Systems Development
• Systems Analyst
– An information specialist who performs systems
analysis, design, and implementation
– His or her job is to study the information and
communications needs of an organization and
determine what changes are needed to deliver
better information to the people who need it
10-6
Systems Development
• The 6 phases of systems analysis &
design are:
1.
2.
3.
4.
5.
6.
Preliminary investigation
Systems analysis
Systems design
Systems development
Systems implementation
Systems maintenance
• Information systems are frequently
revised and upgraded
• Steps in the cycle often overlap
10-7
Systems Development
• Phase 1: Conduct a preliminary investigation
– Conduct a preliminary analysis
– Propose alternative solutions
• Interview people within the organization
• Study what competitors are doing
• Decide to leave the system as is, improve it, or develop a
new system
– Describe costs and benefits
– Submit a preliminary plan with recommendations
• This should be a written report
• Get management approvals for next phase
10-8
Systems Development
• Phase 2: Analyze the system
– Gather data
•
•
•
•
Interview employees and managers
Develop, distribute, analyze questionnaires
Review current written documents
Observe people and processes at work
– Analyze the data
• Use system modeling tools, such as CASE tools
• Create a data flow diagram to show how data flows through
the system
– Write a report and get approvals for next phase
• Document how the current system works
• Document problems with the current system
• Describe the requirements for the new system
10-9
Systems Development
• Phase 3: Design the system
– Notice that you don’t design the new system until you
have done phase 2 since that establishes the
requirements it must meet!
– Do a preliminary design
• Often involves prototyping
– Do a detail design, showing:
•
•
•
•
•
•
Input requirements
Output requirements
Storage requirements
Processing requirements
System controls
Backup
– Write a report and get approvals for next phase
10-10
Systems Development
• Phase 4: Develop the system
– Develop or acquire the software
– Acquire and integrate the hardware
– Test the system
• Unit testing
• Systems testing with both analysts and end-users
• End-user testing is critical, as they don’t know the
software and will show the developers where they
forgot something
10-11
Systems Development
• Phase 5: Implement the system
– Choose a strategy to convert to the new
system
•
•
•
•
Direct implementation
Parallel implementation
Phased implementation
Pilot implementation
– Train the users
• Document the system
• Give classes or train the trainers
10-12
Systems Development
• Phase 6: Maintain the system
– Perform periodic evaluations
– Make changes to the system based on new
conditions
– Document those changes
10-13
Kesimpulan
14
Download