MetaCart Sign in to MyCiteSeerX

Include Citations | Advanced Search | Help

Disambiguated Search | Include Citations | Advanced Search | Help

Searching for "Architectural Mismatch Why Reuse Is So Hard." – sorted by Relevance.

Order by: Citations | Year (Descending) | Year (Ascending) | Recency
Try your query at: Scholar | Yahoo! | Ask | Bing | CSB
Help! 5 documents found, showing 1 through 5.
ATOM RSS
  • to  
  • by Barry Boehm, Barry Boehm
  • … et al., “Architectural Mismatch: Why Reuse is So Hard,” IEEE Software, November 1995, pp. 17…
  • Add To MetaCart
  • Overview  
  • by Nicholas Lay — 2005
  • …) Architectural Mismatch: Why Reuse is So Hard. Software, 12, 17-26. 8 Component based development � Builds…
  • Add To MetaCart
  • Schema Types  
  • by Each Schema Defines
  • …., and Ockerbloom, J. (1995). Architectural mismatch: Why reuse is so hard. IEEE Software, pages 17 --26. Garlan, D…
  • Add To MetaCart
  • Product Development With Massive Components  
  • by Kevin J. Sullivan, John C. Knight, Jake Cockrell, Shengtong Zhang — 1996 — In Proceedings of the 21st Annual Software Engineering Workshop
  • …. Allen and J. Ockerbloom, "Architectural Mismatch: Why Reuse is so Hard," IEEE Software, vol. 12 No. 6…
  • Cited by 1 (1 self) – Add To MetaCart
  • Architectural Why reuse is so hard  
  • by David Garlan, David Garlan, Robert Allen, Robert Allen, John Ockerbloom, John Ockerbloom — 1995 — IEEE Software
  • …www.computer.org/software Architectural Mismatch: Why Reuse Is So Hard David Garlan, Robert Allen…
  • Cited by 2 (0 self) – Add To MetaCart
Help! Showing 1 through 5.
ATOM RSS
Try your query at: Scholar | Yahoo! | Ask | Bing | CSB