Kku2011

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

Agenda
• Software Development in my perspective
• Methodology
• TDD
• Tools
• QnA
• Little bit about @roofimon

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

Software Development
•
• ?
• “ ”

•
• IT
?

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

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

Software Development
and Operation is like
grocery store

How to build software like 7-11

• Work
• Not over budget
• In time
• Easy to transition
• Easy to operate and maintain

We need
• Methodology
• Good Programmer
• Tools

How to survive?

Methodology

Methodology reflect …

Methodology

Team Individual
Structure Behavior

Discipline

Which one is the best?

Which one is the suitable for us?

The Greatest Waterfall

Requirement

Analysis

Design

Implementation

Integration
Testing

Maintenance

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.

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 ??”.

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

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.

Customers Requirement

Analyst Analysis

Why Agile?
Architect Design

Labor Implementation

Labor Integration

Tester Testing

Maintenance

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.

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

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

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 

We understand the story, so we
Happy.

Good Programmer = Good Software
• Understandable
• Testable

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.

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.

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

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

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

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

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;
}

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;
}
}

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

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

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

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

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

Project Management and
Collaboration

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

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

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

Testing
• Junit
• DB Unit
• Mockito
• Selenium

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

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

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

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

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

Kku2011

More Related Content

What's hot (20)

Viewers also liked (8)

Similar to Kku2011 (20)

More from ทวิร พานิชสมบัติ (20)

Recently uploaded (20)

Kku2011

Editor's Notes