21
Joonho Park, Kwang Sik Chung Korea National Open University graduate school Dept. of Computer Science Study of Solution Development Methodology for Small-Size Projects
| Date post: | 29-Nov-2014 |
| Category: |
Documents |
| View: | 1,367 times |
| Download: | 2 times |
Joonho Park, Kwang Sik Chung
Korea National Open University graduate school Dept.
of Computer Science
Study of Solution Develop-ment Methodology for
Small-Size Projects
Introduction
Overview of Development Methodology
Previous Works and Analysis
Solution Development Methodology for Small-
Size Projects
Conclusion
Agenda
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
Introduction
History of Development Method-ology
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
Definition of Development MethodologyA Development Methodology is
Task procedures
Task methodology
Project development document
Management method
Development tools
Small-size projects on a small budget and a short- period development.
In addition, Problems when to apply the de-velopment methodology that is used by big companies, in the small-size projects
Most importantly, Not have a solution devel-opment methodology appropriate for small-size projects.
Problems of small-size projects
Low budget
Short period (less than 6 months)
Minimized human resources
Different Development processes
Different Business scale
System integration(SI) Vs. Solution Develop-
ment
Characterize of small-size projects
Step 1 . Analyze solution development method-
ologies 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
Methodology
Previous Works and AnalysisStep 1. Analyze solution development
methodologiesIT Solution Development Methodologies Analysis
Task Division Document
Analysis(Requirements)
Mandatory Deliverables
Interview resultsRequirements analysis
System analysisGap analysis
Architecture Design
Optional Deliverables
Use-case diagramWork flow diagram
Component DiagramERD
Interface ListInterface Design
Previous Works and Analysis
MANDATORY AND OPTIONAL DOCUMENT OF ANALY-SIS TASK
Task Division Document
Design
Mandatory Deliverables
Test planInterface Design
Table ListTable Design
User’s ManualOperator’s Manual
Integration test resultsUnit test results
Optional Deliverables
WebApp designIntegration test scenario
System test scenarioSystem test results
Previous Works and Analysis
MANDATORY AND OPTIONAL DOCUMENT OF DESIGN TASK
Task Division Document
development
Mandatory Deliverables Source Code
Optional Deliverables Component diagram
Previous Works and Analysis
MANDATORY AND OPTIONAL DOCUMENT OF DEVELOP-MENT TASK
Task Division Document
implementation (operation)
Mandatory Deliverables Education plan
Optional DeliverablesPilot operating plan and
journal
Previous Works and Analysis
MANDATORY AND OPTIONAL DOCUMENT OF IMPLEMENTA-TION TASK
In summary
Analysis : 5 Mandatory Deliverables
Design : 8 Mandatory Deliverables
Development : 1 Mandatory Deliverables
Implementation : 1 Mandatory Deliverables
Total : 15 Mandatory deliverables
Previous Works and Analysis
Previous Works and AnalysisStep 2. client Interviews
Operator Instructions40%
Program List20%
Operator's Manual20%
etc.20%
Development documents
[5 users ]
Previous Works and Analysis
Yes27%
No73%
Methodology need small-size projects
Step 3. Online surveys of developer
[ 22 users ]
Survey period : 3 July 2012 ~ 17 August 2012
Previous Works and AnalysisStep 4. Expert advisory
Experts' Necessary Deliverables of Development Methodology
Anal-ysis∙De-sign Solu-tion man-ual
(de-veloper , user)
Anal-ysis∙De-sign cur-rent sys-tem anal-ysis
Anal-ysis∙De-sign re-
quirements def-ini-tion
Anal-ysis∙De-sign re-
quirement
s spec-ifica-tion
Anal-ysis∙De-sign Use case sce-nario
Anal-ysis∙De-sign Solu-tion GAP defi-nition
Anal-ysis∙De-sign Ar-chi-tec-ture defi-nition
Anal-ysis∙De-sign
Inter-face defi-nition
Anal-ysis∙De-sign
Class Dia-gram
Anal-ysis∙De-sign Se-
quence
Dia-gram
Anal-ysis∙De-sign Test Plan
Anal-ysis∙De-sign Unit test sce-nario
Anal-ysis∙De-sign In-ter-gra-tion test sce-nario
De-vel-op-
ment Source
Code
de-livery Edu-catio
n Plan
de-livery
Ar-gu-
ment plan
de-livery Open plan
de-livery Test-op-er-
ated plan
frequency
5 5 5 1 1 3 1 3 1 0 4 2 3 5 1 1 1 4
0.5
1.5
2.5
3.5
4.5
5.5
Development methodology
Choic
e c
ount
Previous Works and AnalysisStep 4. Expert advisory
Experts' Unnecessary Deliverables of Development Methodology
Table Definition Entity Definition Entity Manula Data conversion plan Development stan-dard defintion
frequency 4 2 2 1 1
0.25
0.75
1.25
1.75
2.25
2.75
3.25
3.75
4.25
Development methodology
Choic
e c
ount
Solution Development Methodology for Small-Size
ProjectsStages Task Document
Analysis & Design
Pre-education (Solution)Solution Manual(Uaser’s Manual, Operator’s Man-ual)
Analysis
Current system analysis
Interview results
Requirement analysis
Architecture Design
Design and Test Plan
Interface Design
Table Design & List
Test Plan
Integration test & Results
Unit test & Results
Development Coding Source code
Implementation Operation
Education Plan
Open Plan
Test operated plan
Take over Plan
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 doc-
ument
Conclusion
