The missing software engineering method

Assessment is expensive.
Make it manageable by making it explicit.

The goal of assessment is decision making. Everyone makes decisions. Managers decide about the overall development. Architects decide the broad technical direction. And, so do developers: they decide daily the course of the implementation. In fact, engineers spend up to 50% of the time assessing the state of the system to know what to do next.

Assessment is expensive and you already pay for it . Make it manageable by making it explicit.

There is no magic.
Craft the tools that match your context.

Effective decision making requires accurate information. Software systems are large and complex in specific ways. Thus, manual code reading does not scale, and standard reporting tools are not enough. The specific details are crucial: from the domain to the technological constraints. You need a humane solution based on custom tools that provide the information that matters.

There is no magic. You know your context. Learn how to craft the tools that match it.

Embed it in the process.
Integrate it in the organization.

Decisions must be taken everyday. Assessment must become a daily reality. Thus, it must be approached explicitly and made integral part of the overall development process. This involves skills that must be present in the organization.

Make it a daily reality. Embed it in the process. Integrate it in the organization.

Tool it up.
Control your effort with an appropriate infrastructure.

Assessment requires a tool infrastructure that makes it practical to build custom analysis solutions for your systems and your problems.

Control your effort with an appropriate infrastructure. The Moose analysis platform was designed for it.

Overview-flyer-a5.png

Blog

  • Quick strategic support
    21 January 201210:49:58 am by Tudor Girba
    Recently, we needed to identify some scripts that: * were executed during the execution of some use cases, and * were executing SQL queries, and * were used heavily internally. In particular, we ...
  • Assessment and the definition of done
    17 January 201211:49:54 pm by Tudor Girba
    One key, yet often overlooked, Scrum concept is the definition of done. It is key because it makes you be explicit about what value means in the context of the project. The definition of done is an i...
  • How many metrics?
    10 January 20127:55:24 am by Tudor Girba
    When I demo Moose, I often get this question: How many metrics does Moose offer? This simple and apparently innocent question holds the essence of what is wrong with how software analysis is approach...