RISS 학술연구정보서비스

검색
다국어 입력

http://chineseinput.net/에서 pinyin(병음)방식으로 중국어를 변환할 수 있습니다.

변환된 중국어를 복사하여 사용하시면 됩니다.

예시)
  • 中文 을 입력하시려면 zhongwen을 입력하시고 space를누르시면됩니다.
  • 北京 을 입력하시려면 beijing을 입력하시고 space를 누르시면 됩니다.
닫기
    인기검색어 순위 펼치기

    RISS 인기검색어

      검색결과 좁혀 보기

      선택해제

      오늘 본 자료

      • 오늘 본 자료가 없습니다.
      더보기
      • 무료
      • 기관 내 무료
      • 유료
      • Parameterizing Decision Factors on Centralization of Software Testing Organization : A Practitioner’s Perspective

        Suman Kumar Kanth,Sanjay Mohapatra,Debashisa Mohanty,P C Basak KINFORMS 2013 Management Review Vol.8 No.2

        This paper is a practitioner’s view of impact of different parameters like Centralization, Offshoring, Productivity mprovement, Quality and other process improvement on Return on Investment calculation for a CTO (Centralized testing Organization). This analysis can help IT QA(Quality Assurance) management to quantify Return on Investment from different parameters of operation and decide on where to invest for optimum benefit. Return on Investment is one the critical factors that any large / small organization chooses before investing. At all the stages of the project life cycle, Return on Investment calculation is a must - that is at business requirements to design, development, testing and implementation phase. In today’s world, independent testing has become very important. The organization needs to do a proper due diligence on selecting testing model, process, time to market, cost etc. For these the organization needs to understand the criteria for selecting the right model for testing which gives the maximum return on investment. This study analyses different parameters and their impact on Return on Investment. This paper does not elaborate on how to establish a CTO. Rather this is an attempt to quantify results after due consideration of various focus areas like - lower cost of operation by offshoring and centralization and savings through Productivity Improvement thru Automated Test Case Execution, savings through Process and tools standardization etc. to implement different parameters within a CTO. The findings are based on authors’ experience of implementing CTOs for reputed clients and implementing that across big size portfolios. The constraints for pure development projects, product testing projects or open system projects may vary in nature. For example scope and benefit from automation may be very high for product testin projects or open system projects but not so for legacy mainframe based maintenance projects.

      연관 검색어 추천

      이 검색어로 많이 본 자료

      활용도 높은 자료

      해외이동버튼