Professional Documents
Culture Documents
Aries Saifudin - RPL - 07. SDLC
Aries Saifudin - RPL - 07. SDLC
Implementation Analysis
Design
Software Development Life Cycle
(SDLC)
1. Planning: Why build the system?
– System request, feasibility analysis, project size estimation
2. Analysis: Who, what, when, where will the system be?
– Requirement gathering, business process modeling
3. Design: How will the system work?
– Program design, user interface design, data design
4. Implementation: System construction and delivery
– System construction, testing, documentation and
installation
Planning
1. Identifying business value (System Request)
– Lower costs
– Increase profits
2. Analyze feasibility
– Technical Feasibility
– Economic Feasibility
– Organizational Feasibility
3. Estimating the size of project
Analysis
1. Requirement gathering by answering the
questions:
– Who will use the system?
– What will the system do?
– When will it be used?
2. Investigate the current system
3. Identify possible improvements
4. Develop a concept for new system
Design
1. Program Design (UML Diagrams)
– What programs need to be written
– Exactly what each program will do
2. User Interface Design
– How users interact with system
– Forms / reports used by the system
3. Data Design (ER Diagrams)
– What data is to be stored
– What format the data will be in
– Where the data will be stored
Data Design Example
Data Design Example
Unnormal Form
Data Design Example
1NF (1st Nomal Form)
Data Design Example
2NF (2nd Nomal Form)
Data Design Example
3NF (3rd Nomal Form)
Data Design Example
ERD (Entity Relationship Diagram)
* KodeParts
Kendaraan Punya Parts NamaParts
1 M
Harga
* NoPolisi 1 Discount
Warna
Merek
Tahun
* NoFaktur
Mengerjakan Faktur Gunakan
M TglFaktur
JamFaktur
1 ** NoPolisi
** Mekanik
1 M
* NoFaktur **
*Mekanik
Mekanik Terdiri Detil Faktur * KodeParts **
NamaPetugas M Kuantum
Data Design Example
Tranformation ERD to LRS
* KodeParts
Parts NamaParts
Harga
Kendaraan Punya
1 1 Discount
* NoPolisi
Warna
Merek
Tahun * NoFaktur
TglFaktur
JamFaktur Gunakan
M ** NoPolisi
** Mekanik
Faktur
1
M
M
Detil Faktur
*Mekanik
NamaPetugas
M * NoFaktur **
* KodeParts **
1 Kuantum
Mekanik Mengerjakan
Terdiri
Data Design Example
LRS (Logical Record Structured)
Kendaraan
Faktur Parts
PK NoPolisi 1
1
PK NoFaktur PK KodeParts 1
Warna
TglFaktur NamaParts
Merek
JamFaktur Harga
Tahun M
NoPolisi Discount
Mekanik
1 M
Detil Faktur
Mekanik
PK NoFaktur
M
PK Mekanik
PK KodeParts
M
NamaPetugas
Kuantum
Implementation
• Construction
– New system is built and tested
– Often testing is the longest part
• Testing
– Unit Testing
– Integration Testing
– System Testing
– User Acceptance Test
• Installation
– Old system is turned off
– New system is turned on
Processes and Deliverables
Process Product
Implementation Analysis
(New System) (System Specification)
Design
(System Specification)
References
• Dennis, A., Wixom, B. H., & Tegarden, D.
(2009). System Analysis Design UML Version
2.0. An Object-Oriented Approach (3rd ed.).
New Jersey: John Wiley & Sons.
• Pressman, R. S. (2015). Software Engineering.
A Practitioner's Approach (8th ed.). New York:
McGraw-Hill Education.
• Sommerville, I. (2011). Software Engineering
(9th ed.). Boston: Addison-Wesley.