Medium-size system integration or IT Solution Company’s solution development project has limitation as like human resource limitation, budget limitation and expert limitation. Especially it is hard to maintain many IT experts for medium-size and small-size system integration or IT Solution Company. Thus in order to efficiently and beneficially complete projects, medium-size and small-size system integration or IT Solution Company should have appropriate solution development methodology.Solution development projects for medium-size and small-size system integration or IT Solution Company are usually shot-term and small budget so that they need slim and light-weight solution development methodology. But usual medium-size and small-size system integration or IT Solution Company do not have their own appropriate solution development methodology. Thus, if those kinds of solution development methodologies are applied to solution development projects for medium-size and small-size system integration or IT solution company without some modifications, shortage of human resources, incompleteness of solution and deliverables could arouse.Especially unnecessary paper works (deliverables and documentations) to both of projects teams and client’s wastes project resources and time. We analyze previous solution development methodologies and derive mandatory deliverables and optional deliverables. Before deriving them, we newly define procedures and tasks for each project stages which are necessary to projects team and clients, from client and expert of interviews. Our proposed solution development methodology can easily leverage the development overhead of short-term projects. Optional deliverables can be omitted by the contraction between project team and client.

1. Joonho Park, Kwang Sik Chung
Korea National Open University graduate school Dept.
of Computer Science

2.  Introduction
 Overview of Development Methodology
 Previous Works and Analysis
 Solution Development Methodology for Small-Size
Projects
 Conclusion

3.  Solution Development Methodology
 Characteristics of small-size projects
 Problems of small-size projects
 Need a new a solution for the small-size of the project
Development Methodology

4. Year’s Methodology
1960’s No methodology
1970’s Waterfall method
1980’s life cycle perspective
1990’s Rational Unified Process
2000’s Agile Unified Process

5.  A Development Methodology is
 Task procedures
 Task methodology
 Project development document
 Management method
 Development tools

6.  Small-size projects on a small budget and a short-
period development.
 In addition, Problems when to apply the development
methodology that is used by big companies, in the
small-size projects
 Most importantly, Not have a solution development
methodology appropriate for small-size projects.

7.  Low budget
 Short period (less than 6 months)
 Minimized human resources
 Different Development processes
 Different Business scale
 System integration(SI) Vs. Solution Development

8. Step 1 . Analyze solution development methodologies
 eGovFrame , CBD, LG CNS, Samsung SDS, Marmi IV, Dongbu CNI,
Kolon Benit
Step 2 . client Interviews (visit)
Step 3 . Online surveys of developer
Step 4 . Expert advisory
Step 5 . Development methodology theorem

9.  Step 1. Analyze solution development methodologies
IT Solution Development Methodologies Analysis

10. Task Division Document
Interview results
Requirements analysis
Mandatory Deliverables System analysis
Gap analysis
Architecture Design
Analysis
Use-case diagram
(Requirements)
Work flow diagram
Component Diagram
Optional Deliverables
ERD
Interface List
Interface Design
MANDATORY AND OPTIONAL DOCUMENT OF ANALYSIS TASK

11. Task Division Document
Test plan
Interface Design
Table List
Table Design
Mandatory Deliverables
User’s Manual
Operator’s Manual
Design
Integration test results
Unit test results
WebApp design
Integration test scenario
Optional Deliverables
System test scenario
System test results
MANDATORY AND OPTIONAL DOCUMENT OF DESIGN TASK

12. Task Division Document
Mandatory Deliverables Source Code
development
Optional Deliverables Component diagram
MANDATORY AND OPTIONAL DOCUMENT OF DEVELOPMENT TASK

13. Task Division Document
Mandatory Deliverables Education plan
implementation
(operation)
Pilot operating plan and
Optional Deliverables
journal
MANDATORY AND OPTIONAL DOCUMENT OF IMPLEMENTATION TASK

14.  In summary
 Analysis : 5 Mandatory Deliverables
 Design : 8 Mandatory Deliverables
 Development : 1 Mandatory Deliverables
 Implementation : 1 Mandatory Deliverables
 Total : 15 Mandatory deliverables

15.  Step 2. client Interviews
Development documents
etc.
20%
Operator Instructions
40%
Operator's Manual
20%
Program List
20%
[5 users ]

16.  Step 3. Online surveys of developer Survey period : 3 July 2012 ~ 17 August 2012
Methodology need small-size projects
Yes
27%
No
73%
[ 22 users ]

17.  Step 4. Expert advisory
Experts' Necessary Deliverables of Development Methodology
Development methodology
6
5
4
Choice count
3
2
1
0
Soluti
curren
on requir requir Soluti Interg
t Use Archit Interfa Seque Unit Test-
manu ement ement on Class ration Educa Argu
syste case ecture ce nce Test test Source Open operat
al s s GAP Diagra test tion ment
m scenar definit definit Diagra Plan scenar Code plan ed
(devel definit specifi definit m scenar Plan plan
analys io ion ion m io plan
oper , ion cation ion io
is
user)
Analysis∙Design Development delivery
frequency 5 5 5 1 1 3 1 3 1 0 4 2 3 5 1 1 1 4

18.  Step 4. Expert advisory
Experts' Unnecessary Deliverables of Development Methodology
Development methodology
4.5
4
3.5
3
Choice count
2.5
2
1.5
1
0.5
0
Development standard
Table Definition Entity Definition Entity Manula Data conversion plan
defintion
frequency 4 2 2 1 1

19. Stages Task Document
Solution Manual
Pre-education (Solution)
(Uaser’s Manual, Operator’s Manual)
Current system analysis
Interview results
Analysis
Requirement analysis
Analysis & Design Architecture Design
Interface Design
Table Design & List
Design and Test Plan Test Plan
Integration test & Results
Unit test & Results
Development Coding Source code
Education Plan
Open Plan
Implementation Operation
Test operated plan
Take over Plan

20.  Add solution education task on analysis stage
 Client is presented to detail requirement
 Development project management tools
 Standards deliverables format
 Guide document writing to deliverables document

21. Thank you
108.joonho.park@gmail.com