달력

12

« 2019/12 »

  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  •  
  •  
  •  
  •  



 

폭포수 모델(Waterfall Model)

·         폭포수 모형

·         고전적 생명주기 패러다임

·         흐르듯 차근히 진행되는 모델

·         순차적으로 소프트웨어를 개발하는 전형적인 개발모델입니다.

·         시스템 개발에 단계적, 체계적, 순차적인 접근 방법을 활용합니다.

·         소프트웨어 개발의 과정을 나누어 체계적이고 순차적으로 접근하는 방식입니다.

·         이전 단계가 완료되어야 다음 단계로 진행 있습니다.

·         하향식(Top Down)으로 진행되지만 문제나 개선사항이 발견되면 단계로 돌아가는 피드백(Feedback)과정을 수행합니다.

 

단계

설명

요구사항 분석

(Analysis)

·         사용자가 원하는 시스템의 기능은 무엇인가? (What)

설계

(Design)

·         어떻게 사용자가 원하는 기능을 제공할 것인가? (How)

개발

(Construction)

·         구현이라고도 합니다.

·         프로그램 코딩

테스트(Test)

·         시스템의 오류를 발견하고 수정합니다.

실행 & 유지보수

(Implementation & Maintenance)

·         개발된 시스템을 사용자들에게 교육하고, 실제 업무에 적용합니다.

·         오류, 요구사항 변경 기능향상에 의한 수정이 이루어집니다.

 

 

 


 

 

 

 

 

 

 

절차로 산출물 도식도


 


Posted by codedragon codedragon

댓글을 달아 주세요

 

Summary 

SW 개발의 가장 어려운 부분은 SW의 비가시성에서 기인한다.

SW Visualization은 이러한 SW의 비가시성을 극복함으로써 SW 개발의 전체 과정을 파악할 수 있도록 하며, 이를 통하여 SW의 품질 향상을 실현하기 위한 방안이다.

   

"SW개발 품질관리 매뉴얼"은 SW 품질 관리 전체 프로세스에 대한 이해가 없는 SW개발 이해당사자가 각자 정의된 활동을 수행하고,

시스템을 통해 시각화된 품질 지표를 제공받고,

정의된 품질 기준에 따라 SW 개발 산출물 최종 배포의 적합성 여부를 판단할 수 있도록 하는 SW Visualization 적용 전반에 관한 정보를 담고 있다.

   

 

 

 

목차

Ⅰ. SW Visualization 배경
1. SW의 비가시성 ··············································································································· 3
2. SW의 복잡도 증가 ·········································································································· 4
3. 국내 중소기업의 개발환경 ······························································································ 4

Ⅱ. SW Visualization 정의
1. SW 공학 프로세스 ·········································································································· 9
가. 요구사항 ··················································································································· 10
나. 구현 ·························································································································· 13
다. 테스트 ······················································································································ 15
라. 형상관리 ··················································································································· 17
2. SW Visualization 이란? ······························································································· 18
가. 시각화 ······················································································································ 19
나. 문서화 ······················································································································ 20

Ⅲ. SW Visualization의 기대효과
1. 요구사항의 구현 상태에 대한 실시간 파악 ································································· 23
2. 품질 지표에 의한 객관적이고 정량적인 분석 ····························································· 24
3. 개발 진척상황에 대한 투명성 보장 ············································································· 24
4. 자동화를 통한 SW 관리의 편이성 증가 ······································································ 25
5. SW 개발관리 문서화 작업의 간소화 ··········································································· 25
6. 품질 기반의 미래형 SW개발 문화를 위한 기반 ·························································· 25

   

Ⅳ. 프로세스의 시각화
1. SW Visualization 품질지표 ·························································································· 29
가. 개발 SW에 따른 지표 설정 ···················································································· 29
2. SW Visualization 시스템 ······························································································ 40
가. SW Visualization 프로세스 ····················································································· 40
나. SW Visualization 시스템 구성요소 ········································································· 42
다. 시스템 구성 절차 ···································································································· 51
3. SW Visualization 구성원 역할 ····················································································· 63
가. Role & Responsibility 정의 ···················································································· 63
나. SW 개발단계별 주요 Activity ················································································· 64

Ⅴ. 소스코드의 시각화
1. 역공학 ··························································································································· 71
가. 역공학 기법의 개요 ································································································· 71
2. 소프트웨어의 내부 설계 ······························································································· 73
가. 개요 ·························································································································· 73
나. 품질 지표 ················································································································· 74
3. 소스 코드의 시각화 ···································································································· 76
가. Source Navigator 설치 ························································································· 77
나. Graphviz 설치 ········································································································· 78
다. Code Visualization Tool 동작 ················································································ 79

   

Ⅵ. 소스코드의 문서화
1. JavaDoc ······················································································································· 84
가. JavaDoc 주석 작성방법 ·························································································· 84
나. JavaDoc 명령어를 통한 생성방법 ·········································································· 86
다. 이클립스에서의 JavaDoc 생성 ··············································································· 87
2. Doxygen ······················································································································· 93
가. Doxygen 주석 작성방법 ························································································· 94
나. Doxygen 문서 생성방법 ························································································· 96
다. Doxygen 출력 문서 확인 ····················································································· 100

Ⅶ. 프로세스의 문서화
1. Redmine 및 Impasse 설정 ······················································································· 103
가. Redmine 설정 ······································································································· 103
나. Impasse 설정 ········································································································ 106
2. 프로젝트 산출물 ········································································································· 108
가. 요구사항 명세서 ···································································································· 108
나. 테스트 시나리오 및 결과서 ·················································································· 109
다. 요구사항 추적표 ···································································································· 111
3. Redmine table 분석 ·································································································· 112
가. issues ···················································································································· 113
나. journals ·················································································································· 115
다. journal_details ······································································································· 115
라. custom_values ······································································································ 116

마. projects ·················································································································· 116
바. enumerations ········································································································ 117
4. Impasse table 분석 ·································································································· 118
가. impasse_nodes ····································································································· 118
나. impasse_node_type ····························································································· 119
다. impasse_test_cases ····························································································· 119
라. impasse_test_steps ······························································································ 120
마. impasse_test_suites ······························································································ 120
바. impasse_test_plans ······························································································ 121
사. impasse_test_plan_cases ···················································································· 121
차. impasse_executions ····························································································· 122
5. 프로젝트 산출물 생성용 SQL ···················································································· 124
가. 요구사항 명세서 ···································································································· 124
나. 테스트 시나리오 및 결과서 ·················································································· 126
다. 요구사항 추적표 ···································································································· 128

Ⅷ. 사례
1. 요구사항 명세서 ········································································································· 133
2. 테스트 명세서 ············································································································· 170
3. SW아키텍처 설계 문서 양식 ······················································································ 194

 

 

직접다운받기

SW개발 품질관리 매뉴얼(개정판).pdf


 

 

출처

https://www.sw-eng.kr/mbs/swkr/jsp/board/view.jsp?spage=1&boardId=143&boardSeq=2061385&id=swkr_040100000000

TAG Code Visualization Tool 동작, custom_values, Doxygen, Doxygen 문서 생성방법, Doxygen 주석 작성방법, Doxygen 출력 문서 확인, enumerations, Graphviz 설치, Impasse table 분석, Impasse 설정, impasse_executions, impasse_nodes, impasse_node_type, impasse_test_cases, impasse_test_plans, impasse_test_plan_cases, impasse_test_steps, impasse_test_suites, issues, JavaDoc, JavaDoc 명령어를 통한 생성방법, JavaDoc 주석 작성방법, journals, journal_details, projects, Redmine table 분석, Redmine 및 Impasse 설정, Redmine 설정, Role & Responsibility 정의, Source Navigator 설치, SW Visualization, SW Visualization 구성원 역할, SW Visualization 배경, SW Visualization 시스템, SW Visualization 시스템 구성요소, SW Visualization 정의, SW Visualization 품질지표, SW Visualization 프로세스, SW Visualization의 기대효과, SW 개발관리 문서화 작업의 간소화, SW 개발단계별 주요 Activity, SW 공학 프로세스, sw-eng, SW아키텍처 설계 문서 양식, SW의 복잡도 증가, SW의 비가시성, 개발 SW에 따른 지표 설정, 개발 진척상황에 대한 투명성 보장, 개요, 구현, 국내 중소기업의 개발환경, 문서화, 사례, 소스 코드의 시각화, 소스코드의 문서화, 소스코드의 시각화, 소프트웨어의 내부 설계, 시각화, 시스템 구성 절차, 역공학, 역공학 기법의 개요, 요구사항, 요구사항 명세서, 요구사항 추적표, 요구사항의 구현 상태에 대한 실시간 파악, 이클립스에서의 JavaDoc 생성, 자동화를 통한 SW 관리의 편이성 증가, 테스트, 테스트 명세서, 테스트 시나리오 및 결과서, 품질 기반의 미래형 SW개발 문화를 위한 기반, 품질 지표, 품질 지표에 의한 객관적이고 정량적인 분석, 프로세스의 문서화, 프로세스의 시각화, 프로젝트 산출물, 프로젝트 산출물 생성용 SQL, 형상관리
Posted by codedragon codedragon

댓글을 달아 주세요

WEB Proxy Tool


 

Paros(파로스)

HTTP분석 (프록시 기능) 취약점 분석 도구  



Paros(파로스) 운영 요구 사항


  • 자바 1.4 이상 버전 설치 ( 자바 어플리케이션 구동을 위해 필요)
  • ant(자바 컴파일러) 설치 ( 파로스 소스 수정 및 컴파일 )
  • 운영 환경을 위한 시스템 환경 변수 설정
  • 시스템 리부팅 (환경 변수 설정 적용을 위한 )

   


Paros site

http://sourceforge.net/projects/paros/

   

   

다운로드

홈페이지에서 [Download] 버튼 클릭

 

 

직접 다운받기

paros-3.2.13-win.exe.zip


'Security > Tools' 카테고리의 다른 글

Paros(파로스), 실행  (0) 2014.12.16
Paros(파로스), install (설치)  (0) 2014.12.15
Paros(파로스) - web proxy tool  (0) 2014.12.14
TeamViewer, 원격접속하기  (0) 2014.12.12
.NET Framework2.0 Download  (0) 2014.12.12
JHiJack, 실행하기  (0) 2014.12.11
Posted by codedragon codedragon

댓글을 달아 주세요

2014. 6. 14. 21:00

UML 특징 Development/UML

   

   

UML 특징

시각화 언어

의사 소통 용이

그래픽 언어

상세화 언어

시스템의 복잡성을 명확하게 기술

객체 시스템을 가시적이고 명확하게 기술

구축 언어

다양한 프로그램 언어 지원

(순 공학/역 공학)

문서화 언어

개발자들이 시스템에 적용한 사항들을 문서로 작성.

(요구사항 명세서, 프로세스, 소스코드, Prototype, Release)

   

   

'Development > UML' 카테고리의 다른 글

UML 2.0 Infrastructure Specification  (0) 2014.08.05
UML 2.0 Diagram Interchange Specification  (0) 2014.07.30
UML 특징  (0) 2014.06.14
UML 작성 목적  (0) 2014.06.08
StarUML 5.0 설치  (0) 2014.05.25
StarUML 2.0.0-Beta1 설치  (0) 2014.05.25
Posted by codedragon codedragon

댓글을 달아 주세요



 

UML 작성 목적

·         객체 지향 시스템을 가시화, 명세화, 문서화 하는

·         개발하고자 하는 바를 보다 명확화

·         개발단계인 요구사항, 분석 단계에서의 산출물 작성

·         개발자들끼리의 원활한 의사소통

·         이해하고 소통하기 편해 집니다.(팀장, 부장, 이사, 사장, 디자이너, 영업, 엔지니어, 고객지원등)

 

 

 

 


'Development > UML' 카테고리의 다른 글

UML 2.0 Diagram Interchange Specification  (0) 2014.07.30
UML 특징  (0) 2014.06.14
UML 작성 목적  (0) 2014.06.08
StarUML 5.0 설치  (0) 2014.05.25
StarUML 2.0.0-Beta1 설치  (0) 2014.05.25
StarUML 가이드 문서  (0) 2014.05.25
Posted by codedragon codedragon

댓글을 달아 주세요