달력

7

« 2020/7 »

  •  
  •  
  •  
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  •  

   

   

   

데이터베이스 구축 방법론

   

목차

I. 방법론 개요

1. 배경 및 목표

2. 방법론 구성

가. 방법론 구조

나. 대상자료 유형

다. 방법론 활용방법

   

II. DB구축 공정 및 산출물

1. DB구축 조직체계

2. DB구축 공정

가. 준비/계획 단계(100)

나. 구축 단계(200)

다. HTML/XML 변환 단계(300)

라. 검수 단계(400)

마. 품질 단계(500)

3. 품질활동

가. 개요

나. 품질활동 공정 및 상세 태스크

다. 품질활동 지침

4. 산출물 정의서 및 활용예

가. 산출물 리스트

나. 산출물 정의서 및 활용예

   

III. 자료별 데이터베이스 구축 공정

1. 메타데이터

2. 텍스트

3. 한적자료

4. 이미지

5. 동영상

6. 사운드

7. 촬영/녹음

8. GIS

9. 항공정사사진

10. 지도제작위성사진

11. 기상위성사진

12. 3D

13. 3D 프린팅

14. LOD(Linked Of Data)

15. 실내공간지도

16. POI

IV. 부록

1. DB구축시 고려할 법/제도/기준 리스트

   

   

개요

데이터베이스 구축 방법론(V4.0)" 은 기존 방법론에서 정립했던 데이터유형과 주요한 공정단계에 대해서는 새로운 업무환경에 적합하게 현행화하고 체계화 하는 방법으로 고도화를 하였다. 또한 여러 데이터유형에 따라 차이 있게 나타난 절차 등에 대해서는 공정의 표준화를 통해 누구나 쉽게 방법론을 이해하고 표준화된 공정에 따라 작업을 수행할 수 있도록 개선하였으며 실내공간지도, 3D프린팅, POI, 링크드데이터 자료유형 구축공정을 추가하였으며 상세 내용은 다음과 같다.

 

o 방법론 자료유형구분의 고도화 수행

각 자료유형에 따른 분류체계에 대해 표준화된 일관성 있는 코드를 부여하여 분류체계를 통해 쉽게 자료유형을 구분할 수 있도록 하였다.

 

o 공정단계의 표준화

자료유형에 따라 자유롭게 부여한 공정(태스크)을 자료유형 간 동일(유사)공정이름을 체계화하여 표준공정으로 재정립하였다. 공통공정의 경우 공정의 이름을 동일하게 적용하여 활용될 수 있도록 하였으며 선택적 공정이 있을 경우 개별공정에 포함된 형태로 하여 공정단계의 표준성을 향상시켰다.

 

o 사용자 활용 용이성 관점의 목차구성

방법론을 적용하기 위해 특정 자료유형을 선택하여 참조하다가 산출물, 작업지침서 등은 또 다른 장을 참조하여 불편했던 구성을 개선하여 각 자료유형에 따라 방법론의 흐름을 이해할 수 있도록 목차와 내용의 구성을 고도화 하였다.

 

o 데이터환경에 부합한 신규DB 유형의 추가

총 1,000개 이상의 RFP 분석, 각 프로젝트에서 추진 중에 발간한 지침서, DB구축사업과 관련된 감리보고서 분석을 통해 DB구축방법론 V3.0에 포함되지 않은 DB유형을 분석하였다. 이 중에서 새롭게 정립이 필요한 데이터 유형을 분석하였으며, 링크드데이터, 실내공간지도, 3D프린팅, POI의 총 4개의 구축공정이 추가되어 현장에서 활용될 수 있도록 정립하였다.

   

   

   

직접 다운로드

데이터베이스구축방법론-1.pdf

데이터베이스구축방법론-2.pdf


   

   

   

   

http://koreadb.data.go.kr/frt/cms/resourceMng/selectResourceMngment.do?nttId=7279&bbsId=BBSMSTR_000007003020&pageIndex=1&searchCnd=&searchWrd=

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

댓글을 달아 주세요

 

SW 업데이트 체계 보안 가이드라인 및 코드서명 검증모듈

SW 업데이트 체계의 취약점을 악용해 악성코드를 대량으로 확산시키는 것을 예방하기 위한 'SW 업데이트 체계 보안 가이드라인' 및 코드서명 검증모듈 배

 

 

내용

  • SW 업데이트 체계 보안 가이드라인 : SW 자동 업데이트 기능 개발 시 준수해야 할 보안 항목 및 주의사항,
    준수하지 않을 경우 발생 할 수 있는 위험성, 그 밖에 해킹에 악용된 사례 및 해결 방안 제시
  • 코드서명 검증모듈 : WindowsTM 환경에서 코드서명된 모듈을 검증하기 위한 라이브러리 API 및 코드서명
    검증모듈 개발자 가이드
    • 코드서명 검증모듈 라이브러리
    • 코드서명 검증모듈 샘플
    • 코드서명 검증모듈 개발자 가이드

 

 

목차

1. 개요

1) 목적

2) 적용대상

3) 구성

2. SW 업데이트 체계 정의 및 현황

1) 정의

2) 현황

3. SW 업데이트 체계 보안위협

1) 보안위협 유형

2) 보안위협 사례

3) 기존 SW 업데이트 체계의 문제점

4. 대응방안

1) 파일보호

2) 채널보호

5. SW 업데이트 체계 보안 십계명

[부록] SW 업데이트 체계 보안 십계명 요약

 

 

직접다운받기

SW 업데이트체계보안가이드라인.pdf

코드서명 검증모듈.zip


 

 

 

 

출처

http://www.boho.or.kr/kor/data/guideView.jsp?p_bulletin_writing_sequence=20544#none

Posted by codedragon codedragon

댓글을 달아 주세요