1 / 8

iStudio Overhaul Strategies

iStudio Overhaul Strategies. Daniel Link. 1. Acceptance of iStudio. Unintuitive GUI (component properties vs. properties, user is not prompted for details when adding new component etc.) Missing online help or other guides

sera
Download Presentation

iStudio Overhaul Strategies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. iStudio Overhaul Strategies • Daniel Link 1

  2. Acceptance of iStudio • Unintuitive GUI (component properties vs. properties, user is not prompted for details when adding new component etc.) • Missing online help or other guides • No documentation of entity XML format -> no way to exchange created entities with other teams 2

  3. Acceptance of iStudio continued • Compatibility checking based on XML descriptions is a sound idea, but... • Outdated XML definitions prevent current systems from being represented in models (Win7, Server 2008, MSIE on Vista) • Cries wolf too often (~80 supposed mismatches on included sample with FAMP config, though components are well-known to integrate) • Impossible to address alleged mismatches within reasonable time frame • Bottom line: dismissed as nuisance, no value gained 3

  4. Suggestions • Bring project up to speed by adding XML descriptions for current releases of OSs, tools etc. • Fix obvious errors (e.g. Safari only on MacOS) • Reduce warning output • Update XML descriptions each semester (5-10 hrs.) • Have each team whose config not already represented in the system add config at end of CS577b 4

  5. Suggestions (cont’d) • “When you lose interest in a program, your last duty to it is to hand it off to a competent successor.” -> Make iStudio open source • Solicit community input • Rename so name associated with function (e.g. COMA - compatibility analyzer, COMB - compatibility builder, Matchbox or even better names) and doesn’t sound like a rejected Apple product 5

  6. Benefits • Actually add value to projects • Well maintained, updated tool that makes a difference from too many abandoned academic projects • Empower students and users • Give back to the open source community • Industry might see value and contribute to the project • Make USC, CSSE and me proud 6

  7. References • Raymond, Eric. "The Cathedral and the Bazaar". April 26, 2010 <http://catb.org/~esr/writings/homesteading/cathedral-bazaar/index.html#catbmain>. • O'Hara, Keith and Kay, Jennifer. "Open source software and computer science education". Journal of Computing Sciences in Colleges February 2003: 1-7. • Pedroni, Michaela et al. "Open source projects in programming courses". ACM SIGCSE Bulletin March 2007: 454-458.

  8. Questions 8

More Related