ANALYSIS CONCEPTS & PRINCIPLES
What Are the Real Problems? the customer has only a vague idea of what is required the developer is willing to proceed with the "vague idea" on the assumption that "we'll fill in the details as we go" the customer keeps changing requirements the developer is "racheted" by these changes, making errors in specifications and development and so it goes...
Software Requirements Analysis identify the “customer” and work together to negotiate “product-level” requirements identify the “customer” and work together to negotiate “product-level” requirements build an analysis model build an analysis model focus on data define function represent behavior prototype areas of uncertainty prototype areas of uncertainty develop a specification that will guide design develop a specification that will guide design conduct formal technical reviews conduct formal technical reviews
Analisis Kebutuhan
Identifikasi Kebutuhan
Workers
SRS (Software Requirement Specification) SRS adalah hasil akhir dari proses analisis. Fungsi dan kinerja yang harus dipenuhi sebagai bagian dari rekayasa sistem ditetapkan dengan deskripsi yang lengkap, baik deskripsi fungsional dan behavioral. Format/kerangka SRS, adalah sebagai berikut : Kerangka SRS.pdf Kerangka SRS.pdf
Tugas 2 1.Analisis kasus proyek perangkat lunak pada pertemuan sebelumnya ! 2. Dokumentasikan hasil analisis tersebut dalam dokumen SRS (Bab Idan Bab II)!