WedIT! or wednesday IT day (rabu IT) is an event of sharing & upgrading at PT Jerbee Indonesia.

1. http://flickr.com/photos/ricardo_ferreira/2475319350/
WedIT
Pengenalan Software Engineering
(Rekayasa Perangkat Lunak)

2. #1 [ S O F T W A R E ]

3. http://flickr.com/photos/striatic/2326860/

4. a collection of computer programs, procedures and documentation
that perform some tasks on a computer system
~ Wikipedia.org

6. #2 [ J E N I S – J E N I S S O F T W A R E ]

7. http://www.flickr.com/photos/isriya/22487125/
System Software
device drivers, operating systems,
servers, utilities, window manager

8. http://www.flickr.com/photos/mrqf/1150458179/
Programming Software
compilers, debuggers, interpreters,
linkers, text editors ~ IDE

9. http://www.flickr.com/photos/21160667@N07/2056870120/
Application Software
business/office, education, games
entertainment dll.

10. #3 [ S O F T W A R E E N G I N E E R I N G ? ]

11. a systematic, disciplined, quantifiable approach to the
development, operation, and maintenance of software
~ Wikipedia.org

12. software development process...
software life cycle...

13. #4 [ A K T I F I T A S S O F T W A R E E N G I N E E R I N G ]

14. apapun metodologinya, aktifitas di dalamnya
kurang lebih tetap sama...

15. http://www.flickr.com/photos/claudio_ar/2939243781/
Analogi :
Apapun strateginya (4­4­2, 4­5­1), gayanya (total football,joga
bonito, kick n rush, cattenacio)... aktivitas di lapangan hijau
tetaplah menendang bola, mengoper, menangkap bola dst.

16. apapun metodologinya, aktifitas pengembangan
perangkat lunak umumnya...

17. http://www.flickr.com/photos/smiling_da_vinci/14785644/
1. Requirements
mendapatkan kejelasan bisnis proses dari
user melalui komunikasi langsung
output: dokumen wawancara (waterfall),
diagram use case (UML), user stories (XP)

18. http://www.flickr.com/photos/merydith/3215847513/
2. Modelling
menerjemahkan bisnis proses ke bentuk
model atau diagram (UML, DFD,
Flowchart/flowmap, ER).

19. http://www.flickr.com/photos/samuraislice/2985906586/
3. Design
merencanakan rancangan software agar
fault­tolerance, compatibility, extensibility,
reliability, maintainability, availability,
usability → contoh: desain arsitektur
( client­server? N­tier? MVC?), platform dll.

20. http://www.flickr.com/photos/tobanblack/3251282019/
4. Implementation
aksi logic dan programming, tapi aktivitas
lain selain engineering bisa muncul juga di
sini (science, mathematics dan seni)

21. http://www.flickr.com/photos/pgautier/1298109082/
5. Testing
identify the correctness, completeness,
security and quality (data sample,
simulation, alpha test, beta test)

22. http://www.flickr.com/photos/smart_growth/2454419537/
6. Deployment
instalasi, aktivasi, update, adaptasi dan
sosialisasi, (membuat software kita siap
digunakan oleh user)
++ issue: maintenance...

23. selain aktifitas standar di atas, seperti halnya peran
medic & wasit di sepak bola.. ada aktifitas pendukung lain
yang menopang poin 1­6 di atas...

24. http://www.flickr.com/photos/yaffamedia/1387424309/
X. Supporting Disciplines
dokumentasi
project management
quality assurance dll.

25. #5 [ MODELING / DIAGRAM & DOKUMENTASI ]

26. CONTEXT DIAGRAM (CD)
­ represent all external entities that may interact with a system
­ lingkaran (sistem) + kotak (entity) + panah + input output

28. DATA FLOW DIAGRAM (DFD)
­ detailing context diagram
­ level kedalaman idealnya 1­3
­ hukum: data/info yang masuk = data/info yang keluar

29. CONTEXT DIAGRAM
DFD LEVEL 1

30. ENTITY RELATIONSHIP DIAGRAM (ERD)
­ abstract and conceptual representation of data
­ skema & modelling database

32. USE CASE DIAGRAM
­ description of a system’s behaviour / responds to a request
­ describes quot;whoquot; can do quot;whatquot; with the system
­ user point of view
­ part of UML tools

34. FLOW MAP DIAGRAM
­ advance flow chart: object movement by location/position

36. SOFTWARE DEVELOPMENT DOCUMENTATION
­ IEEE Software Document Definitions (7 items)
­ MIL­STD­498 Data Item Descriptions (22 items)
­ SRS, SDD, STD, SUM

37. Software Requirements Specifications (SRS)
Cover Page
Revisions Page
1 INTRODUCTION
1.1 Product Overview
1.2 Purpose
1.3 Scope
1.4 Reference
1.5 Definition And Abbreviation
2 SPECIFIC REQUIREMENTS
2.1 External Interface Requirements
2.1.1 User Interfaces
2.1.2 Hardware Interfaces
2.1.3 Software Interfaces
2.1.4 Communications Protocols
2.1.5 Memory Constraints
2.1.6 Operation
2.1.7 Product function
2.1.8 Assumption and Dependency
2.2 Software Product Features
2.3 Software System Attributes
2.3.1 Reliability
2.3.2 Availability
2.3.3 Security
2.3.4 Maintainability
2.3.5 Portability
2.3.6 Performance
2.4 Database Requirements

38. Software Design Description (SDD)
1. INTRODUCTION
1. Design Overview
2. Requirements Traceability Matrix
2. SYSTEM ARCHITECTURAL DESIGN
1. Chosen System Architecture
2. Discussion of Alternative Designs
3. System Interface Description
3. DETAIL DESCRIPTION OF COMPONENTS
1. Component n
2. Component n+1
4. USER INTERFACE DESIGN
1. Description of the User Interface
1. Screen Image
2. Objects and Actions
5. ADDITIONAL MATERIAL

39. #6 [ M E T O D O L O G I ]

40. http://www.flickr.com/photos/3336/142845984/
1. Waterfall
paling konvensional
flowing steadily downwards
serial banget... kaku...

42. http://www.flickr.com/photos/gigaboss/100381027/
membuat prototype atau mock­up
2. Prototyping

44. http://www.flickr.com/photos/slr/11147904/
3. Spiral
kombinasi top­down & bottom­up
cikal bakal iterative

46. http://www.flickr.com/photos/rutlo/3339656017/
4. Rapid App. Dev.
fast development & smaller/modular
(karena ada RAD tools yang OK)

48. http://www.flickr.com/photos/lenore­m/2400412112/
5. Iterative
basic concept, banyak menjadi bagian
metode lainnya...

50. RUP, Rational Unified Process...
­ Divisi IBM
­ UML
­ Rational Rose

52. XP, extreme programming...
­ day­to­day practices for developers and managers
­ more responsive to customer needs (agile)
­ pragmatis

54. Agile Software Development...
XP+Scrum+DSDM+Crystal+Pragmatic+FDD = agile manfesto
­ customer satisfaction by rapid, continuous delivery of useful software
­ working software is delivered frequently (measure of progress)
­ late changes in requirements are welcomed
­ close, daily cooperation between business people and developers
­ face­to­face conversation is the best form of communication
­ projects are built around motivated individuals, who should be trusted
­ continuous attention to technical excellence and good design
­ simplicity
­ self­organizing teams
­ regular adaptation to changing circumstances

55. web development “banget”, pragmatic, representasi → scrum

57. adaptasi software development methodology “untuk kita” ?

60. #7 [ R E F E R E N S I ]

61. Kitab RPL
dari yang antik hingga yang
pragmatis, demi dasar kuda­kuda
yang kuat
http://flickr.com/photos/ashitaka96/319032681/

62. Software Engineering – Roger S. Pressman
Software Engineering – Ian Sommerville
Modern Structured Analysis – Edward Yourdon

63. Pragmatic Programmer – A. Hunt & D. Thomas
Getting Real – 37Signals
Joel On Software – Joel Spolsky

64. Diki Andeas ST.
Direktur Teknik
PT Jerbee Indonesia
diki.andeas@jerbeeindonesia.com - http://slideshare.net/niwat0ri
Credits: Flickr CreativeCommons licensed image collections (URL at each page)