[Software Architecture] SA 개요 - 추가

추가 고려해야할 사항

• 개요를 잘 작성해야 함
• Business Context를 알아야 한다
  • IT가 Business를 leading하는 형태로 변모됨 (IT 기획 -> Business 기획으로 확대 됨)
  • 요구사항은 사용자가 작성해야 함 (해외의 경우는..)
  • 남의 일 처럼 개발자가 작성하고 요청받아서 다시 수정하고 ?
  • 목적을 잘 파악해야 함 -> 이해당사자 파악을 통해서 파악 가능
• 변화 방향성 (요구사항 정리)
  • 큰 Agenda를 잡고, 개별로 정리
  • 예) 보고서의 Framework
    • Mega process = AS-IS, Pre-Investment, Investment Execution, Post-Investment
    • To-Be Directions (미래 방향성)
    • Process (Structure + Operation)
    • IT (System Support) << Associate Architect가 수행
    • Others (People, Org)
• IT Vision (ISP 등에서 많이 사용)
  • 예) NEW NIIS Information Vision
    • IT Vision (For Activation of private sector investment in Vietnam)
    • Core Value (Investor-oriented, Innovation, Performance, Expertise, Reliability)
    • IT Key workds (Flexibility & Scalability, Speed & Convenience, Communication & Reliability, Capability)
    • Change Direction
      • Legal & BA (Business) 
        - Related laws and policies should be adjusted and supplemented
        - Reporting system should be realigned
      • AA (Application)
        - Improved application reliability
        - Strenghening inter-Ministry System Interface
      • DA (Data)
        - Data structure optimization from system integration point of view
        - Current System Data Cleansing and Integrated Database Buidl
        - Performance optimization
      • TA (Technical)
        - Reorganization all Infra facility for improving operational efficiency
        - Build advaned IT infrastructure
        - Build DR Infra
        - Strenghen security policy and build security system
        - Apply E-government framework of Vietnam Government
• Architecture Transformation Map 작성
  • AS-IS Applciation Map
  • TO-BE APplication Map

 

 

 

아키텍팅은

• Reference model은 좋은 것을 참조해야 함
  • 좋은 것 / 나쁜 것을 구분하는 힘이 필요함 -> Standard를 많이 활용해야 함

 

정보화역량 수준 평가 모델 (예)

Subject	Verification	Evaluation	Goal	Mandatory/ Optional
CMMI	Recognition / Application (Interview)	Check Application Level	Level 2	Mandatory
SPICE	Recognition / Application (Interview)	Check Application Level	Level 2	Optional
SW Quality Process (ISO9126)	Recognition / Application (Interview)	Check Application Level	Apply 50% of unit process	Mandatory
SW Project Management Process (PMBOK)	Recognition / Application (Interview)	Check Application Level	Apply 50% of unit process	Mandatory
SW Estimation Function Point (ISO/IEC 14143)	Recognition / Application (Interview)	Check Application Level	Application after training	Mandatory
SW Dev Method (Structural)	Recognition / Application (Interview)	Check Related Doc	Application after training	Mandatory
SW Dev Methodology (IEM)	Recognition / Application (Interview)	Check Related Doc	Application after training	Mandatory
SW Dev Methodology (OO)	Recognition / Application (Interview)	Check Related Doc	Training	Optional
SW Dev Methodology (CBD)	Recognition / Application (Interview)	Check Related Doc	Training	Optional
Enterprise Architecture (TOGAF Model)	Recognition / Application (Interview)	BA, AA, DA, TA Dc	Application & Technology Transfer	Mandatory
SW System Config (HW, OS, DB, Solution, Programming Language)	Recognition / Application (Interview)	Document & Procurement	Application & Technology Transfer

 

EA-Based System Build Model

 

TOGAF 모델을 활용한 EA 관점