달력

12

« 2019/12 »

  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  •  
  •  
  •  
  •  

 

공개SW 마이그레이션 가이드

  • 1장에서는 공공기관에서 마이그레이션 요구 개요 및 공개SW 마이그레이션 개요에 대해서 설명한다.

  • 2장에서는 공개SW 마이그레이션 추진 절차와 검토 사항에 대해서 설명한다.

  • 3장에서는 공개SW 마이그레이션 추진 절차의 공개SW 마이그레이션 계획 수립 방안에 의거한 사례를 설명한다.

  • 참고 문헌에서는 공개SW 마이그레이션 시 필요한 사항 및 관련내용에 대해서 설명한다.

 

 

목차

1장. 공개SW 마이그레이션 가이드 개요

1. 본 가이드의 구성 1

2. 공개SW 마이그레이션 개요 2

3. 필요성 및 목적 3

4. 공개SW 마이그레이션 가이드의 활용 4

 

2장. 공개SW 마이그레이션 추진 절차

1. 공개SW 마이그레이션 추진 절차 5

2. 공개SW 마이그레이션 진단 및 계획 7

3. 공개SW 마이그레이션 준비 및 배치 12

4. 공개SW 마이그레이션 수행 14

5. 공개SW 마이그레이션 최적화 및 안정화 16

6. 공개SW 마이그레이션 가이드의 기대 효과 17

 

3장. 공개SW 마이그레이션 추진 사례

1. 개요 18

2. 마이그레이션 요구 18

3. 공개SW 마이그레이션 계획 수립 19

4. 공개SW 마이그레이션 준비 및 배치 31

5. 공개SW 마이그레이션 수행 39

6. 공개SW 운영 최적화 및 안정화 44

 

참 고 문 헌 45

첨부1. o-ISP 단계별 주요 검토 사항 46

첨부2. 분야별 주요 공개SW 기술지원 기업 47

 

 

공개 SW 마이그레이션 단계별 수행 내용

 

 

직접다운받기

(141104)공개SW_마이그레이션_가이드.pdf

 

Or

http://www.oss.kr/oss_repository12/606089

http://www.oss.kr/?module=file&act=procFileDownload&file_srl=606090&sid=427a18c9871128e8fa801aa059ff1ca4

Posted by codedragon codedragon

댓글을 달아 주세요

   

   

독수독과 이론(fruit of the poisonous tree theory)

  • 독이 있는 나무의 열매도 독이 있다는 뜻으로, 위법하게 수집된 1차적 증거(독수)에 의해 발견된 2차적 증거(과실)에까지도 증거능력을 부정하는 것을 의미
  • 우리나라의 경우는 '대판 2007.11.15, 2007도3061'의 판례에서 원칙적으로 위법수집증거를 기초로 획득한 2차적 증거를 유죄인정의 증거로 삼을 수 없으나, 2차적 증거수집과 관련된 모든 사정을 전체적ㆍ종합적으로 고려하여 예외적인 경우에는 유죄인정의 증거로 사용할 수 있다고 판시

   

   

 

국외 독수독과이론 사례

  • 1769년 영국 제1대 맨스필드 백작이자 대법관인 윌리엄 머레이는 "민사소송에서는 법원이 원고와 피고에게, 그들의 의사에 반하는 증거를 도출하도록 강제할 수 있으나, 형사소송에서는 피고인의 의사에 반하여 이뤄지는 어떤 증거의 도출도 강제할 수 없다"고 판시, "피고인에게서 갈취한 어떤 증거나 자백도, 공판에서 피고인에게 해를 끼칠 수 없다"고 판시
  • 1920년 미국의 실버톤사건의 판결(case of Silverthorne Lumber Co. v. United States)에서 구체화된 것
  • 1939년 Nardone사건에서 그 용어가 처음 사용
  • 1963년 Wong Sun사건에서 위법한 압수·수색뿐만 아니라 위법한 체포로 얻은 자백과 증거물의 증거능력을 부정
  • 1964년 Escobedo사건에서 미국의 수정헌법 제6조에 의한 변호권을 침해하여 얻은 진술을 기초로 하여 수집한 증거에 대해 독수독과에 해당한다고 판시

 

   

   

   

국내 독수독과이론의 대표 사례

삼성 X파일사건

  • 2005년 검찰은 삼성의 비리내용이 담긴 X파일 도청자료를 독수독과이론에 기초해 이건희 삼성회장, 홍석현 전 주미대사, 이학수 삼성구조본부장을 기소할 수 없다고 결론 내림

   

  • 삼성 X파일의 중요내용은 삼성그룹이 대선후보를 포함한 정치인들에게 자금을 제공하고 검찰간부들에게도 떡값을 주었다는 의혹이였다. 안기부가 1997년 대선을 앞두고 이학수 당시 삼성그룹 비서실장과 홍석현 중앙일보 사장의 비자금에 대한 대화를 녹음했는데, 그 후 안기부 담당 직원이 274개의 도청테이프와 녹취록을 밀반출했고, 그 일부가 한 재미교포를 통해 한 기자에게 전달돼 내용이 밝혀진 것이다. 하지만, 불법도청과 불법유출에 초점이 맞추어졌고, 결국 법원판결에서 X파일에 담겨 있는 사람들에게는 면죄부가 주어진 반면, 이를 처음 보도한 한 기자는 통신비밀보호법 위반 혐의로 불구속 기소돼 2006년 11월 2심에서 유죄판결을 받았던 사건.
  • 즉, 불법한 도청과 유출(독수)에 의해 밝혀진 정치자금 제공혐의(과실)는 인정할 수 없다는 것
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

댓글을 달아 주세요