Resources

The term paradigm shift may be a bit overused these days; nevertheless, the kernel-based Essence approach to software engineering can quite reasonably be considered to be such a shift. It truly represents a profound change of viewpoint for the software-engineering community. In this paper, Ivar Jacobon and Ed Seidewitz explore what happened to to the promise of rigorous, disciplined, professional practices for software development, like those observed in other engineering disciplines and explain how the Essence standard is the answer.

Use-Case 2.0 re-focuses on the essentials and offers a slimmed down, leaner way of working, for software teams seeking the benefits of iterative, incremental development at an enterprise level.

Use-Case 2.0 re-focuses on the essentials and offers a slimmed down, leaner way of working, for software teams seeking the benefits of iterative, incremental development at an enterprise level.

Use-Case 2.0 re-focuses on the essentials and offers a slimmed down, leaner way of working, for software teams seeking the benefits of iterative, incremental development at an enterprise level

Combining agile and SEMAT yields more advantages than either one alone. This paper discusses how two current popular movements complement one another to provide a powerful basis for software development.

In the same way that Google map shows you where you are, where you want to go, and the best way to get there when making a journey, SEMAT and Essence can do the same for teams of engineers developing software.

Ivar Jacobson International (IJI) is delighted to see that OMG has announced The Essence Kernel as a new industry standard for software engineering practices.

Ben LInders interviews Ivar Jacobson and Ian Spence on the use of SEMAT within agile adoption. Published on InfoQ.

IJI has been engaged with a major UK bank over the last 18 months helping them introduce new methods of working, and IBM’s Collaborative Lifecycle Management tooling to support these methods. Business Analysts now capture their requirements in Rational Requirements Composer (RRC), Solution Architects create their designs in Rational Software Architect (RSA) using the Unified Modelling Language (UML), Infrastructure & Security Architects add deployment topologies to the designs using RSA’s Deployment Planning extension, and everything is underpinned by Work Items and Source Control in Rational Team Concert (RTC).

New article published on ACM Queue discusses two powerful complementary movements in software development.