메뉴 건너뛰기




Volumn , Issue , 2003, Pages

Best Practices for Software Performance Engineering

Author keywords

[No Author keywords available]

Indexed keywords

SOFTWARE DESIGN;

EID: 85154025290     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper
Times cited : (17)

References (10)
  • 1
    • 0025791156 scopus 로고
    • Software Risk Management: Principles and Practice
    • [Boehm 1991]
    • [Boehm 1991] B. Boehm, “Software Risk Management: Principles and Practice,” IEEE Software, vol. 8, no. 1, pp. 32-41, 1991.
    • (1991) IEEE Software , vol.8 , Issue.1 , pp. 32-41
    • Boehm, B.1
  • 2
    • 0003408303 scopus 로고    scopus 로고
    • [Clements and Northrop 1996] Technical Report No. CMU/SEI-96-TR-003, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA
    • [Clements and Northrop 1996] P. C. Clements and L. M. Northrop, “Software Architecture: An Executive Overview,” Technical Report No. CMU/SEI-96-TR-003, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 1996.
    • (1996) Software Architecture: An Executive Overview
    • Clements, P. C.1    Northrop, L. M.2
  • 3
    • 84872111050 scopus 로고    scopus 로고
    • [Javelin 2002] Javelin Technologies, Oakville, Ontario, Canada
    • [Javelin 2002] Javelin Technologies, “Best Practice Definition,” Oakville, Ontario, Canada, 2002 (www.javelin-tech.com)
    • (2002) Best Practice Definition
  • 8
    • 79957636524 scopus 로고    scopus 로고
    • SM: An Architectural Approach to Fixing Software Performance Problems
    • [Williams and Smith 2002] Reno, December
    • SM: An Architectural Approach to Fixing Software Performance Problems,” Proceedings of the CMG, Reno, December 2002.
    • (2002) Proceedings of the CMG
    • Williams, L. G.1    Smith, C. U.2
  • 10


* 이 정보는 Elsevier사의 SCOPUS DB에서 KISTI가 분석하여 추출한 것입니다.