1 / 12

Systems Integration Referentia Systems Inc.

Systems Integration Referentia Systems Inc. CSDL - January 24, 2007 Ryan Kadomoto, Aaron Kagawa, Austen Ito, Joshua Stupplebeen. Company History. Products have been adopted by: Defense Advance Research Project Agency (DARPA) Defense Information Systems Agency (DISA)

mervyn
Télécharger la présentation

Systems Integration Referentia Systems Inc.

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. Systems Integration Referentia Systems Inc. CSDL - January 24, 2007 Ryan Kadomoto, Aaron Kagawa, Austen Ito, Joshua Stupplebeen

  2. Company History • Products have been adopted by: • Defense Advance Research Project Agency (DARPA) • Defense Information Systems Agency (DISA) • Autodesk, Borland, Seagate, GoldMine

  3. Products • Enterprise-level user login authentication • Networking authorization • Network Operations Center Engineering

  4. Requirements and Goals • Short Term Goals • Increase developer awareness regarding the usage of Ant tools • Increase reporting functionality to provide feedback to management regarding the development process • Long Term Goals • Use Hackystat for CMMI

  5. Current Implementation • Technologies Currently in use • Private Hackystat server supporting an automated build process • Checkstyle • Confluence • Code Reviews

  6. Process • Current Development Process • Developers are not required to run Ant builds before committing • Automated build process • Developers are aware of Hackystat but do not interact with it in any way • Sensors currently collecting data • Checkstyle, PMD, Subversion

  7. Hackystat • Automated build process runs every 10 minutes if a commit has occurred • Developers do not have direct access • Reports are generated but only the Hackystat devs examine them

  8. Hackystat Issues • Memory management • Memory usage goes up and does not go back down • Ideas • Benchmarking, JProfiler

  9. Checkstyle • Configured to a bare minimum • Javadocs, line length • Internal Resistance • Devs view style guidelines and documentation as trivial • Solutions • More immediate feedback: fail the build • Provide longer term feedback: standard violation level • Use PMD or Findbugs instead, but keep collecting Checkstyle data

  10. Reporting • Increase Managerial awareness of Hackystat functionality • Solutions • Reports could be created weekly, posted and commented on in Confluence • Monthly Powerpoint presentation to management based on report statistics

  11. Goals Review • Distance to goals • Difficult to say • Foreseeable problems • Attracting the interest of management • Convincing the developers we’re trying to help them with new technology

  12. Goals for the next 3 weeks • 1. Decipher how hackyStat collects data • 2. Begin figuring out how confluence works (wiki tags) • 3. Conduct a survey of developers • 4. Use JProfiler to profile the hackyStat system • 5. Keep a blog

More Related