Archive for March, 2009

  • JSR 305: a silver bullet or not a bullet at all?

    on Mar 30, 09 • by Mikhail Ksenzov • with 9 Comments

    JSR-305 is a Java Specification Request intended to improve the effectiveness of static analysis tools operating in Java 5+ environments. The idea here is that one can use special purpose annotations in order to provide static analysis tools with hints regarding the behaviour and side effects of methods. An example of such annotations can be found in the presentation ‘Annotations for Software Defect Detection’ by William Pugh, who is masterminding the whole spec. Here we go: 1: void test() { 2:    if (spec != null) fFragments.add(spec); 3:    if (isComplete(spec)) fPreferences.add(spec); 4: } 6: 5: boolean isComplete(AnnotationPreferences spec)

    Read More »
  • Klocwork Releases Standalone Java Source Code Analysis Tool for Android Mobile and Web Application Development

    on Mar 30, 09 • by Meranda Powers • with No Comments

    Klocwork Solo arms developers with industry leading static analysis technology that supports the Android platform BURLINGTON, Mass. — Mar 30, 2009 — Klocwork, Inc., the proven leader in automated source code analysis solutions for improving software security and quality, today announced the availability of Klocwork Solo. This new product from Klocwork delivers proven, enterprise-ready, static analysis technology to the individual Java developer. Klocwork Solo is a downloadable Java static source code analysis (SCA) product that automatically identifies critical bugs and security vulnerabilities in Java source code quickly and accurately. Additionally, Klocwork’s newest product ships with

    Read More »
  • Now’s the time to invest in developer productivity.

    on Mar 24, 09 • by Mike Laginski • with No Comments

    As software managers you’re undoubtedly being asked to do more with less in this economy. With companies continuously being forced to cut costs, the first shoe to drop is when you are told you need to cut headcount. The second shoe drops the day after the painful deed is done and you look into the eyes of the team members that are left behind and try to put a positive spin on your world – their world. And that is when reality really hits home.  Less people, same number of problems.  No one “downsized” the

    Read More »
  • Avionics Software Development and DO-178B

    on Mar 18, 09 • by Brendan Harrison • with 2 Comments

    Today, I had a chance to connect with Connie Beane, the Director of Certification and Safety Critical Software for ENEA Embedded Technology, Inc. Connie has a deep background in safety-critical avionics systems development as a Federal Aviation Administration Designated Engineering Representative (DER) with authority for design assurance level A systems, software and complex electronic hardware. Her additional experience includes 12 years with the FAA in the Transport Airplane Directorate as a Project Officer, Federal representative and Secretary of the RTCA committee SC-180, which produced DO-254, as well as 8 years at Boeing as a Lead

    Read More »
  • Klocwork Delivers Source Code Analysis Solution for the Avionics Software Developoment Market

    on Mar 16, 09 • by Meranda Powers • with No Comments

    Partnership with Enea® provides best of breed software and services solution to D0-178B avionics market BURLINGTON, Mass. and STOCKHOLM, Sweden — Mar 16, 2009 — Klocwork, Inc., the proven leader in automated source code analysis solutions for improving software security and quality, and Enea® , a world leading provider of mission critical software and services, today announced a partnership to deliver enhanced value to avionics software customers who need to comply with DO-178B. Together, the companies deliver a joint technology and services solution that will reduce customers’ development costs while streamlining their FAA certification activities

    Read More »
  • Using Iteration Offsets in Agile Development

    on Mar 9, 09 • by Todd Landry • with No Comments

    I thought for today’s topic I would delve into something that many organizations have to confront when moving to Agile that is, how to structure their iterations. Many organizations will find that iterations work better if development, testing, and documentation are all done within the same iteration period. Other organizations prefer to offset the testing and/or documentation ½ or a full iteration period after the development is complete. Having lived through both, I thought it might be useful to briefly list the good, and not so good of iteration offsetting. First the good: * Testing

    Read More »
Scroll to top