Академический Документы
Профессиональный Документы
Культура Документы
DR
PSI
Perancangan
Implementasi
Karakteristik Hardware
Infant mortality Wear out
Failure rate
Time
Karakteristik Software
Increased failure rate due to side effects
Failure rate
Change
Actual Curve
Keterlambatan penyampaian produk Tidak sesuai dengan spesifikasi , bahkan salah Menafikan aspek non teknis Software berukuran besar, dikembangkan oleh team dari berbagai disiplin, secara terus menerus produk dapat mengalami perubahan sepanjang pengembangan dan setelah instalasi
1970
1980
1990
Biaya perangkat lunak cenderung meningkat dan melebihi biaya perangkat keras
Code
Development Test
Acceptance Test
Operation
Perbaikan kesalahan pada tahap analisa memerlukan biaya 2 satuan. Perbaikan untuk kesalahan yang sama pada tahap operasi memelukan biaya 200 satuan
CAUSE Agency estimated its own state of progress when it let the contract Incorrect agency management action, such as using inapporapriate contract Agency failed to specify requirement adequtely Agency overcommited it selt agency failed to manage during execution, including executive changes Agency failed to adequately inspect and test 1 X 2 X 3 X X X X X X X X
Case Number 4 5 6 7 X X X X X X X X X X
8 X X X
X X X
49% 49
50% 21%
Sub karakteristik
Suitability, Accuracy, Interoperability,Security Maturity, Fault tolerance, Recoverability
MODEL
Code and Fix System Development Life Cycle (SDLC) Prototyping Spiral CASE (Computer Aided Software Engineering)
Proses pengembangan perangkat lunak pada awal era pengolahan data. Menggunakan 3GL atau lebih rendah. Biaya pemeliharaan yang besar.
KRITERIA TRANSISI :
Dokumentasi.
CATATAN :
Sering dikenal sebagai Document Driven Software Process Merupakan perbaikan dari code and fix, dan sampai saat ini merupakan salah satu proses perangkat lunak yang paling banyak digunakan.
Bernhard Boar has defined prototyping as A specific strategy for performing requirements definitions wherein user needs are extracted, presented, and successively refined by building a working model of the ultimate system quickly and in its working context.
Connell and Shafer: A software prototype is a dynamic visual model providing a communication tool for customer and developer that is far more effective than either narrative prose or static visual models for portraying functionality. It has been described as: functional after a minimal amount of effort a means for providing users of a proposed application with a physical representation of key parts of the system before system implementation flexible modifications require minimal effort not necessarily representative of a complete system.
KRITERIA TRANSISI :
CODE (PROGRAM) CATATAN :
Sering dikenal sebagai Code Driven Software Process Merupakan salah satu proses perangkat lunak yang mulai banyak digunakan saat ini. Banyak memanfaatkan 4GL dan Application Generator. Dibandingkan dengan SDLC :
* Produktivitas lebih baik * Kelengkapan fungsi dari sistem kurang baik * Keterpaduan (integrasi) sistem kurang baik
Alternatif
MEMBUAT SEBUAH PROTOTYPE REVISI PROTOTYPE CONTOH MODEL (PROTOTYPE) MENGGUNAKAN DAN MENGEVALUASI PROTOTYPE
Implementasi
Setuju
Tidak
PENGEMBANGAN PROTOTIPE SEBAGAI SUATU PROSES PENGEMBANGAN APLIKASI SECARA CEPAT (contoh produk NETSCAPE)
Start Specifications Complete Input from User Feedback Feature Design and Coding Integration Beta 0 Beta 2 Beta 1
Januari February March
Objectives
Full Release
Beta 4 Beta 5
May
Stabilize Beta 6
June July Agustus
Beta 3
April
7 User Approval
(Sumber : J.L. Connel, L.B. Shafer, Structured Rapid Prototyping, Prentice Hall, 1989)
Team. A few end users and IS developers form a team to develop a business Schematic. The initial prototype schematic design is developed. Prototype. The schematic is converted into a simple point-and-click
application
prototype using prototyping tools. Presentation. A few screens and routine linkages are presented to users. Feedback. After the team gets feedback from users, the prototype is retaired. Reiteration. Further presentations and reiteration are made. Consultation. consultation are held with central IT developers/consultants to identify potential improvements and conformance to existing standards of the organization. Completion. The prototype is converted into a finished application. Acceptance. Users review and sign off on their acceptance of the new system Installation. The new application software is installed on network servers
CATATAN :
Sering dikenal sebagai : Risk Driven Software Process Untuk pengembangan proyek yang berskala besar, dengan memperhatikan pengaruh resiko dilihat dari segi finansial maupun keamanan (jiwa manusia). Kombinasi SDLC, Prototyping dan Risk Analysis.
MODEL SPIRAL
tahap-tahapnya :
Determine Objectives Alternatives Constraints
Cumulative Cost Progress through steps Evaluate alternative Identity resolve risk Risk analysis
Risk analysis
Prototype
Prototype
Operasional Prototype
Requirements plan Concept of Simulation, model, bencmarks like cycle plan operation Software Detailed requirements design Requirements Software validation product Integration and Code design test plan Design validation & velitication Unit test Integra tion and Acceptance Implemen test test Plan next phases tation
Spiral Model
Case Workstation
The Analysis Toolset focuses on correctly capturing detailed business requirements early in development process Analysis Toolset
Case
Design Toolset
System Interface
The Information Integrator integrates system spscifications, check them for consistency and completeness, and records them in the repositories
The Database Generation Toolset generates information needed for data storage and access
The System Interface provides for file transfers and query resporting
Control What controls needed to protect against accidental loss or damage ? is there a needed to control access to data us by the application ?
Processing What operations on the inputs are needed to produce the desired output ? What software can most effectively support those operations ?
Output What information is needed by end users and in what form should the output be presented ?
Storage Does the application use previously stored data ? Does it create data that must be stored for future use by this or other applications ?
Define a problem or opportunity using systems thinking Develop and evaluate alternative system solutions Select the system solution that best meets your requirements
Design the selected system solution to meet your requirements Implement and evaluate the success of the designed system
IMPLEMENTASI SOLUSI
te tiga ves In
t Implemen
Desi gn
ze aly An
in inta Ma
(SDLC)
INVESTIGASI SISTEM
PRODUK: TUJUAN, RUANG LINGKUP DAN PERUMUSAN MASALAH TOOLS: MATRIK KOMPONEN SISTEM INFORMASI DLLNYA.
Interviews with employees, costumers, and managers. Questionnaires to appropriate end users in the organization. Personal observation, videotaping, or involvement in end user work activities. Examination of documents, reports, procedures manuals, and other documentation. Development, simulation, and observation of model of the work activities.
Organizational Feasibility
How well proposed system supports the strategic objectives of the organization
Economic Feasibility
Cost savings Increased revenue Decreased investment Increased profits
Technical Feasibility
Operational Feasibility
End user acceptance Management support Customer, supplier, and government requirements
TAHAPAN ANALISIS
PRODUK: FUNCTIONAL REQUIREMENTS
CONTOH SALAH SATU PENDEKATAN ANALISIS DAN DISAIN YANG MELIBATKAN TIM DAN PENGGUNAAN VIDEO
User videotape library and database video transcripts site maps mock-ups
Coview video with developers Understanding Identify key User Needs issues
Data Analysis
Codevelopment
Design solutions embodied in sketches, mock-ups, simulations Design workshops with users
Tahapan Disain
TAHAPAN IMPLEMENTASI
Implementation Activities
System Documentation
TAHAPAN IMPLEMENTASI
Evaluate and acquire new hardware and software. Hardware includes computer systems, POS terminals, and telecommunications processors and network facilities. Software includes network management programs and POS transaction processing packages. Develop computer programs or make any necessary modifications to software packages that are acquired. Prepare training materials and documentation on how to operate the new POS system for managers and salespeople. Educate and train managers, salespeople, and information systems personnel to operate the new system. Test the system and make corrections until it operates properly Convert to the new system on a phased store-by-store basis to minimize disruption. Use the first store converted as a pilot installation to help with testing and training. Perform a postimplementation audit within 30 days of each store's conversion to determine if the new POS systems are achieving their expected advantages.
KONVERSI SISTEM
DIRECT CUT OVER ( IMMEDIATE CUT OVER) PHASED IN CUT OVER PARALELL CUT OVER PILOT PROJECT