원본 위치 <http://www.kffa.or.kr/Businfo/Businfo_transport.ASP>

Total Cost of Ownership (TCO): A Gartner cost optimization and investment justification model that captures the true cost of sustaining an IT asset throughout its useful life. The TCO product/service suite includes a financial model, a methodology, consulting services, best practices and software tools for understanding not only the initial acquisition cost, but the support, maintenance and disposal costs of an asset as it ages. TCO is particularly useful for managing obsolescence, optimizing asset utilization, justifying reinvestment in infrastructure, and finding hidden costs embedded in non-IS-organizational units.

Information Technology Infrastructure Library (ITIL): A well-established, easily accessible, affordable process model for IT service management that is built around a set of best practices. ITIL bundles IS core process definitions into integrated, published sets. ITIL's structure enables incremental adoption, which facilitates continuous improvement. A well-established service and consulting industry has been built around ITIL, especially in Europe. ITIL is better known for its back-office operational process definitions than for its application management processes.

Capability Maturity Model (CMM): An IS process and performance improvement framework that has emerged as a de facto standard for application development and maintenance processes. The CMM is highly prescriptive because it provides diagnostics for assessing an organization's performance on a maturity scale, and it defines objective criteria for reaching subsequent maturity levels. It also captures the processes and process outcomes that are relevant to those maturity levels. However, it does not provide "how to" information. That is, it helps IS organizations identify where they are and what their next goals should be, but does not address how to get there.

Control Objectives for Information and Related Technology (CobiT): A standardized set of guidelines establishing which formal IS processes, practices and controls should be in place and the minimum results they should predictably deliver. CobiT is used predominantly by independent auditors to authenticate the integrity, reliability and security of IT systems and data. Its orientation is risk mitigation. To achieve this, it presents a comprehensive checklist of all IS processes and controls, and establishes guidelines for acceptable performance. CobiT is useful for understanding the universe of IS processes and establishing initial performance targets, but it does nothing to support the goals of continuous improvement or IS service optimization, and the cost of achieving the prescribed level of risk mitigation can potentially exceed the benefit.

Six Sigma: A philosophy and method for improving process outcomes by establishing acceptable levels for defects and modifying processes until the defect level is achieved. Six Sigma is "process-agnostic"; it does not matter which processes are being modified or which outcomes are being monitored. Six Sigma is a generic technique for understanding how to conduct and achieve process improvement while keeping an eye on quality outcomes. As such, it is fairly pragmatic and potentially quite relevant to the execution of process improvement goals. However, because Six Sigma originated in the manufacturing sector, there is an ongoing debate concerning its relevance to service industries and organizations. IS organizations that adopt Six Sigma will likely need to modify it.

ISO 9000: A standard for achieving predictability and repeatability in processes. ISO 9000 is generic and essentially assumes that predictable results mean good results. An organization can be ISO 9000-compliant if it adheres to its documented practices, even though those practices may not produce results that are consistent with even-baseline peer group performance, let alone best-practice performance levels. ISO 9000 introduces discipline and rigor into an environment, but does not support continuous improvement goals or guarantee acceptable levels of performance.

National Awards (such as the Malcolm Baldrige Award): Self-assessment programs for performance improvement sponsored by different countries. These national awards for performance excellence are granted based on criteria such as leadership, process management and business results. These programs provide a consistent framework for defining quality and assessing improvements across a holistic set of drivers (not just process), but they do not provide guidelines on how to achieve quality objectives and improvements.

Scorecards: Reporting and monitoring tools designed to provide a focused, balanced insight into performance by measuring the variables that directly affect required outcomes. Scorecards are generally articulated in business terms by using easily understood measures, such as financial results or customer satisfaction. However, they lack a universal, formally defined structure, content or definition. This absence of standards often means that scorecards are employed to monitor and report things that sound important, without ultimate objectives or causal relationships being defined or understood. This renders them impractical for external comparison, and sometimes limits their roles to reliable communication tools, rather than devices that produce desired outcomes.

운영체제를 새롭게 설치 후 새로 설치한 Office 2010의 제한된 보기 설정으로 인해서 인터넷에서 다운로드 받은 파일이나 메일에 첨부로 들어 온 문서가 열리지 않은 경우를 경험해 보셨을 겁니다.

아래 설정은 Office 2010의 제한된 보기 설정을 해제하는 방법입니다.

파일 → 옵션

출처 : http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html

국내 기업의 대부분이 Java 플랫폼으로 도배되어 가고 있는 상황(금융권 차세대, 공공기관 등)에 .NET 개발자나 교육센터가 보기 드물어졌다는 거 아시나요?

다른 나라에 비해 국내는 유독 Java를 선호하는 것 같습니다. 누군가는 언어 선택에 따라서 몸값이 틀려진다고 하는데 많은 사람들이 언어 보다는 개발을 즐기면서 살았으면 좋겠습니다.

새벽에 준영이에게 분유를 먹이기 위해 일어났다가, 핸드폰에서 확인한 AdSense 계정 정지 메일… ㅎㅎ 며칠간 Google AdSense 앱을 통해서 $가 늘어나는걸 보며 기뻐했는데, 이렇게 정지 메일을 받으니까 좀 아쉽네요.

이의 신청을 해 볼까 하다가도 처음에 신기해서 제가 몇 번 클릭을 했던 게 있기 때문에 얼마 되지 않는 $를 위해 제 양심을 팔기 싫어 이의 신청은 하지 않고 계정 정지를 시킬 예정입니다.

AdSense에 대한 짧은 추억을 간직하고 다시는(평생) AdSense 근처에는 갈 수 없으니, 본업인 개발과 블로그에 올릴 유용한 컨텐츠 제작에 집중 할 생각입니다.

선의의 AdSense 피해자분들 파이팅입니다.

Blog나 Tistory에 글을 올리는 방법은 여러가지가 있겠지만, 제가 자주 사용하는 방법은 Microsoft Word를 이용한 방법을 좋아합니다.

이전에는 Windows Live Writer라는 도구를 이용해서 작업을 했었지만, 그 방법에도 단점이 몇가지가 보여 이제는 MS Word를 이용하는 방법만을 사용하고 있습니다.

먼저, Tistory에 글을 올리기 위해서는 아래와 같아 몇 가지 셋팅을 해 주시면 손 쉽게 글을 게시할 수 있습니다.

저를 따라서 셋팅을 진행해 보시죠.

1. 파일 à 저장/보내기 à 블로그 게시물로 게시 à 블로그 게시물로 게시 메뉴를 선택합니다.

2. 글을 올리기 위해서는 Tistory 계정 셋팅을 해줘야겠죠.

3. 블로그 공급자는 "기타"를 선택합니다.

4. "기타" 선택 후 다음 버튼을 누릅니다.

5. API 선택은 MetaWebLog를 선택하고, 블로그 게시 URL은 http:// 이후에 본인의 Tistory URL을 입력해 줍니다. 마지막엔 /api를 꼭 붙여 주어야 합니다.

Ex) http://axmvp.tistory.com/api

사용자 이름과/암호는 티스토리의 계정을 입력해 주시면 됩니다.

6. 확인 버튼을 누르면 티스토리에 게시글을 올리기 위한 셋팅이 마무리가 됩니다.

7. 게시글을 올리기 위해서는 1)번 내용과 동일하게 파일 à 저장/보내기 à 블로그 게시물로 게시 à 블로그 게시물 을 누르면 새로운 창이 뜨고 아래와 같은 화면이 나타나게 됩니다.

게시글의 제목을 입력 후 상단에 있는 "게시" 버튼을 눌러주면 글이 게시된 것을 확인 할 수 있습니다.

8. 게시글 확인