메뉴 건너뛰기




Volumn 27, Issue 2, 2010, Pages 41-48

Agile architecture interactions

Author keywords

Agile development; Enterprise architecture; Project management; Software engineering; Team organization

Indexed keywords

AGILE DEVELOPMENT; ARCHITECTURAL WORK; ENGINEERING TEAMS; ENTERPRISE ARCHITECTURE; FUNDAMENTAL PRINCIPLES; PROJECT MANAGEMENT SOFTWARE;

EID: 77649259492     PISSN: 07407459     EISSN: None     Source Type: Journal    
DOI: 10.1109/MS.2010.35     Document Type: Article
Times cited : (54)

References (16)
  • 6
    • 77649258093 scopus 로고    scopus 로고
    • R. Kazman, M. Klein, and P. Clements, ATAM: Method for Architecture Evaluation, tech. report CMU/SEI-2000-TR-004, ESC-TR-2000-004, Software Eng. Inst., Carnegie Mellon Univ., 2000.
    • R. Kazman, M. Klein, and P. Clements, ATAM: Method for Architecture Evaluation, tech. report CMU/SEI-2000-TR-004, ESC-TR-2000-004, Software Eng. Inst., Carnegie Mellon Univ., 2000.
  • 11
    • 0141502307 scopus 로고    scopus 로고
    • Who Needs an Architect?
    • M. Fowler, "Who Needs an Architect?" IEEE Software, vol. 20, no. 5, 2003, pp. 11-13.
    • (2003) IEEE Software , vol.20 , Issue.5 , pp. 11-13
    • Fowler, M.1
  • 16
    • 77649263331 scopus 로고    scopus 로고
    • Best Practices in Business Intelligence: Creating an Agile BI Infrastructure
    • "Best Practices in Business Intelligence: Creating an Agile BI Infrastructure," Computerworld, 2009; www.biperspectives.com/awards. aspx.
    • (2009) Computerworld


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