Software Development Methodology

Department of Information Tech.

DIT-CEIT
Software Development Methodology
● Rapid development
● Lack of developer (technical)

● Limited technology

● Output oriented

● Simple software

documentation activities
Software Development Methodology
● A methodology fit for additional
computerized functions to be
linked in an already stable
system.
● A hybrid methodology that will

support the objectives of the

client needs and existing
resources.
 ANALYZE /
PLANNING

BREAKDOWN
PRIORITY
PROJECT

DESIGN MODULE

INTEGRATION OF
SUB PROCEDURE CODE TEST
AND TESTING

INTEGRATION
EXISTING
SYSTEM

TEST /
IMPLEMENTATION DEBUG
Software Development Methodology
● Easy to start project software methodology
● A hybrid methodology to accommodate
sudden changes during development phase
● To enable expansion of existing software
which is a common development scenario
● With proper documentation, using UML tools.
● Iterative and systematic
 ANALYZE /
PLANNING

BREAKDOWN
PRIORITY
PROJECT

DESIGN MODULE

INTEGRATION OF
SUB PROCEDURE CODE TEST
AND TESTING

INTEGRATION
EXISTING
SYSTEM

TEST /
IMPLEMENTATION DEBUG
Analyze / Planning
● Data gathering
● Review of existing system (for
existing/upgrade)
● Tools to be used for development
● Client background
● Available resources
● Technical staff
● Possible risks
(initial data, proposed development tools, etc)
 ANALYZE /
PLANNING

BREAKDOWN
PRIORITY
PROJECT

DESIGN MODULE

INTEGRATION OF
SUB PROCEDURE CODE TEST
AND TESTING

INTEGRATION
EXISTING
SYSTEM

TEST /
IMPLEMENTATION DEBUG
Breakdown priority project
● Which should be done first
● Identify modules and sub modules
● Determine DB changes (existing)
● What are the appropriate tools for coding, designing
and documenting.
● Skills needed
Output
● Class diagram (whole system)
● Database schema (if requires DB or if DB structure
already existing)
● Gantt Chart
 ANALYZE /
PLANNING

BREAKDOWN
PRIORITY
PROJECT

DESIGN MODULE

INTEGRATION OF
SUB PROCEDURE CODE TEST
AND TESTING

INTEGRATION
EXISTING
SYSTEM

TEST /
IMPLEMENTATION DEBUG
Design module
● Broken down modules will be prepared for coding.
● Stage where modules are designed and determined
whether it contains sub modules.
● Design the hierarchy of modules for easier testing
and integration
● Clients will be involved in interface design
Output
● Component Diagram
● Use case Diagram
● Updated class diagram (if any additional modules)
● Sample interface design
 ANALYZE /
PLANNING

BREAKDOWN
PRIORITY
PROJECT

DESIGN MODULE

INTEGRATION OF
SUB PROCEDURE CODE TEST
AND TESTING

INTEGRATION
EXISTING
SYSTEM

TEST /
IMPLEMENTATION DEBUG
Code – Test / Debug
● Coding and testing are done simultaneously.
● Available data will be used like a dummy
database that contains actual data.
● Codes will be formalized after debug
● Optimization (not required)
Output
● Programming logs
● Activity diagram (per module => Required)
● State machine diagram (if special interfaced hardware is required in the system)
 ANALYZE /
PLANNING

BREAKDOWN
PRIORITY
PROJECT

DESIGN MODULE

INTEGRATION OF
SUB PROCEDURE CODE TEST
AND TESTING

INTEGRATION
EXISTING
SYSTEM

TEST /
IMPLEMENTATION DEBUG
 ANALYZE /
PLANNING

BREAKDOWN
PRIORITY
PROJECT

DESIGN MODULE

INTEGRATION OF
SUB PROCEDURE CODE TEST
AND TESTING

INTEGRATION
EXISTING
SYSTEM

TEST /
IMPLEMENTATION DEBUG
Integration of sub procedures
● Integration of modules will follow after the coding
phase. This is to ensure the integrity of the
developed module.
Output
● Communication diagram (as refer to the class, sequence, and use case Diagram)
● Interaction overview diagram (if needed to support or summarize the
communication diagram)

● Update all diagrams if needed

● Problem encountered during integration
● Compilation of code test & debug phase (all logs hand
written is accepted)
 ANALYZE /
PLANNING

BREAKDOWN
PRIORITY
PROJECT

DESIGN MODULE

INTEGRATION OF
SUB PROCEDURE CODE TEST
AND TESTING

INTEGRATION
EXISTING
SYSTEM

TEST /
IMPLEMENTATION DEBUG
Integration with existing system
● Complete project with modules and sub modules will be
connected to the stable existing system
● Testing of this phase will require participation of actual
users
● If no integration part to old or existing system in
development, proceed to test and implementation.
Output
● Initial testing results
● Feedback from test
 ANALYZE /
PLANNING

BREAKDOWN
PRIORITY
PROJECT

DESIGN MODULE

INTEGRATION OF
SUB PROCEDURE CODE TEST
AND TESTING

INTEGRATION
EXISTING
SYSTEM

TEST /
IMPLEMENTATION DEBUG
Test / Implementation
● Implementation will be observed maximum of 1 week
● Monitoring of DB will be done
● Feedback from users will be addressed immediately
Output
● Finalized diagram (all)
● Monitoring results (from both DB and users)
● Compilation of all programming logs
● Package diagram
Suggested UML tools

Please use free software!