This document discusses software development methodology and tools. It compares waterfall and agile methodologies, emphasizing that agile is better suited for delivering working software frequently. It also advocates for test-driven development (TDD) to produce code that is understandable and testable. Finally, it outlines various tools used in software development projects, including project management, version control, build tools, testing frameworks, continuous integration, and monitoring.

1. //@roofimon

2. “ ”

3. “ ”

4. You can not find the best
solution but you can find the
optimal one.

5. Agenda
• Software Development in my perspective
• Methodology
• TDD
• Tools
• Q n A
• Little bit about @roofimon

6. • 26 2518 1 2
• A-F
• IT Technical Architect DTAC
• Architect ?
• “ ”

7. Software Development
•
• ?
• “ ”
•
• IT
?

8. Just an Example
• Programmer
• Project Management
• Solution Architecture
• System Integration
• Database Administration
• Testing
• Security
• Operation
• Infrastructure

9. - -
English for Communication
000102 - -
English for Academic Purposes (EAP
II)
000103 - -
English for Academic Purposes I
(EAP II)
000112 - -
Thai for Academic Purposrs(???

10. Software Development
and Operation is like
grocery store

12. How to build software like 7-11
• Work
• Not over budget
• In time
• Easy to transition
• Easy to operate and maintain

13. We need
• Methodology
• Good Programmer
• Tools

14. Lack of Methodology

15. How to survive?
Methodology

16. Methodology reflect …
Methodology
Team
Structure
Individual
Behavior
Discipline

18. Which one is the best?
Which one is the suitable for us?

19. The Greatest Waterfall

20. The Greatest Waterfall
Requirement
Analysis
Design
Implementation
Integration
Testing
Maintenance

21. Waterfall Team

22. Waterfall Discipline
• Project is divided into sequential phases.
• Emphasis an entire system at one time.
• Tight control is maintained through the use of
extensive written documentation.

23. Waterfall s..ks?

24. Waterfall not wrong
• 90% of enterprise firm in Thailand still using
waterfall model.
• It’s big , really big. 100 people involve with
project.
• Match with their procurement process
• Strong Audit process.
• “Trust ??”.

25. Developer Discipline
• Depends on developers themselves
• Mostly, make it fast.
• Mostly, make it done.
• Deadline ahead
• Quality ummmmm QA team will cover it for
somehow
• Aggressive Regression Test
• Customer will come when our software is “done”.
• Change request, Change request, Change request

27. What about small organization?
• They need something that is really “work”.
• They can spend time with your team.
• So Waterfall again?
• We need methodology that focus on
delivering software that working.

29. Agile Development Methodology

30. WhyAgile?
Requirement
Analysis
Design
Implementation
Integration
Testing
Maintenance
Customers
Analyst
Architect
Labor
Labor
Tester

31. Three simple truths
• 1. It is impossible to gather all the
requirements at the beginning of a project.
• 2. Whatever requirements you do gather are
guaranteed to change.
• 3. There will always be more to do than time
and money will allow.

32. Agile Team

33. Discipline
• Customer satisfaction by rapid delivery of useful software
• Welcome changing requirements, even late in development
• Working software is delivered frequently (weeks rather than
months)
• Working software is the principal measure of progress
• …
• …
• …
• Regular adaptation to changing circumstances

34. Developer Discipline
• According to 3 simple truth
• Agile coder will carry these four basic activities
along with them
– Coding
– Testing
– Listening
– designing

36. Anyway
• Grocery Store does exist but …?
• Waterfall and Agile
• Waterfall still dominate the market.
• Waterfall itself doesn’t encourage
programmer to write good code.
• We need something.
• Applied TDD into development phase in
Waterfall 

37. We understand the story, so we
Happy.

38. Produce good code

39. Good Programmer = Good Software
• Understandable
• Testable

40. Understandable

41. The Program
• a1 is a yng and gftd sftwreng attempting to
hackMnfrm() of sftw company ENCOM in
order to fndEvdc() that senior executive
a2 stole() a1's cde and prsnt() it as his own,
earning him a rapid series of promotions. a1 is
blcked() by the MCP, an ai that ctrl the ENCOM
mnfrm.

42. The Program
kevinFlynn is a young and gifted
SOFTWARE_ENGINEER attempting to hack() into
the mainframe of encom =
SoftwareCompany(“ENCOM”) in order to
findEvidence() that ENIOR_EXECUTIVE
edDillinger stole(kevinFlynn) code and presented
it as his own, earning him a rapid series of
promotions. kevinFlynn is blocked() by the
MasterControlProgram , an
artificialIntelligence that controls(encom) the
ENCOM mainframe.

43. Understandable
• Use Intention-Revealing Names
• Make Meaningful Distinctions
• Use Pronounceable Names
• Use Searchable Names
• Avoid Encodings

44. Use Intention-Revealing Names
//================================
int d // elapsed time in days
//=================================
int elapsedTimeInDays;
int daysSinceCreation;
int daysSinceModification;
int fileAgeInDays;

45. Use Intention-Revealing Names
public List<int[]> getThem() {
List<int[]> list1 = new
ArrayList<int[]>();
for (int[] x : theList)
if (x[0] == 4) list1.add(x);
return list1;
}

46. Use Intention-Revealing Names
public List<Cell> getFlaggedCells() {
List<Cell> flaggedCells =
new ArrayList<Cell>();
for (Cell cell : gameBoard)
if (cell.isFlagged())
flaggedCells.add(cell);
return flaggedCells;
}

47. Use Searchable Names
int realDaysPerIdealDay = 4;
const int WORK_DAYS_PER_WEEK = 5;
int sum = 0;
for(int j=0; j<NUMBER_OF_TASKS; j++){
int realTaskDays =
taskEstimate[j]*realDaysPerIdealDay;
int realTaskWeeks =
(realdays / WORK_DAYS_PER_WEEK);
sum += realTaskWeeks;
}

48. Avoid Side Effect
public class UserValidator {
private Cryptographer cryptographer;
public boolean checkPassword(String userName,
String password) {
User user = UserGateway.findByName(userName);
if (user != User.NULL) {
String codedPhrase =
user.getPhraseEncodedByPassword();
String phrase =
cryptographer.decrypt(codedPhrase,
password);
if ("Valid Password".equals(phrase)) {
Session.initialize();
return true; }
} return false;
}
}

49. Testable
• What?
• We just understand our code.
• Dependency?

50. Test Driven Development AKA TDD
– Executable Document Spec
– Executable functional checking
– Executable dependency checking
– Executable integration test

51. Normal Cycle
• Read function spec
• Start coding
• Monkey see and monkey do
• It might not effect to other functions
• Waiting for defect ticket

52. TDD cycle
• Read function spec
• (Re)Write Test
• Run Test fail
• Write Production Code
• Run all test
• Refactor
• Cool 

53. Demo

54. Code

56. Part II Tools
• Project Management
• Collaboration
• Development Environment
• Development Tools
• Testing
• Continuous Integration
• Deployment
• Monitoring

57. Project Management and
Collaboration

59. # Flexible issue tracking system
# Gantt chart and calendar
# News, documents & files management
# Feeds & e-mail notifications.
# Per project wiki
# Per project forums

60. Redmine Demo

61. Version Control
• You are not alone
• Code is your asset
• Choose one:
• GIT, SVN, CVS

62. Development Tools
• Build Tool
• Library dependency checking
• Single Repository
• Check Style
• IDE

63. Testing
• Junit
• DB Unit
• Mockito
• Selenium

64. JUnit
• JUnit is a unit testing framework
• Unit test itself is not enough we need
company

65. DBUnit
• Why do we need to test our database?
• You need [multiple] databases

66. Mock Object
• Mock objects are simulated objects that mimic
the behavior of real objects in controlled ways.
• supplies non-deterministic results
• has states that are difficult to create or reproduce
• is slow
• does not yet exist or may change behavior;
• would have to include information and methods
exclusively for testing purposes

67. Web App Test
• Selenium is a suite of tools to automate web
app testing across many platforms.

68. Continuous Integration
• Execute all unit test in integration
environment
• Code coverage checking
• Automatic Branch/Tag

69. Deployment

70. Monitoring