Home > Articles > Software Development & Management

The Essence of Software Engineering: An Interview with Ivar Jacobson

  • Print
  • + Share This
Scott Ambler interviews Ivar Jacobson, author of The Essence of Software Engineering: Applying the SEMAT Kernel, about the agnostic approach of SEMAT and why it is a paradigm shift in the way we look upon ways of working.
Like this article? We recommend

The Essence of Software Engineering: Applying the SEMAT Kernel from Addison-Wesley Professional was released in January 2013. Written by Ivar Jacobson, Pan-Wei Ng, Paul E. McMahon, Ian Spence, and Svante Lidman this book describes the work to date of the Software Engineering Method and Theory (SEMAT) community. The goal of the SEMAT community is, as expressed in the SEMAT Call for Action, to “refound software engineering based on a solid theory, proven principles and best practices.” In this article I interview Ivar Jacobson about this fascinating work.

Scott Ambler: In 100 words or less, what is “the essence” of software engineering?

Ivar Jacobson: The software world has a huge number of methods. I believe there are more than 100,000 methods out there. Some have a brand such as Rational Unified Process (RUP), Scrum, Extreme Programming (XP), but most of them are homegrown with some ideas picked up from textbooks or magazines. Underneath all these methods we can find a common ground, or a kernel, of things we always have and things we always do when developing software. These things form the essence of software engineering. A kernel has been developed within the SEMAT community and is now likely becoming adopted as a standard by Object Management Group (OMG).

Scott: With all the other software engineering books out there, why did you feel this book was needed? 

Ivar: This book is fundamentally different from any other book in software engineering. It describes this kernel, and it teaches software development based on this kernel in a method-independent way. This is very much needed in education – both at universities and in the industry. Instead of teaching different methods separately, you can now teach the kernel and then specialize this to teach specific methods. Once you have learnt the universal kernel, it becomes significantly easier to learn any specific approach, for instance Scrum, Lean, Kanban. They have a lot in common which is not easily visible today, but the kernel clearly reveals that.

Scott: You describe software engineering in terms of alphas. What are they and why are they important?

Ivar: The alpha concept is a powerful construct, the value of which has been proven over that last 7-8 years in many organizations - clients of my company. It incorporates several practical ideas, the most important one being that teams can measure the progress and health of their endeavors in a practice-independent way. At any moment in time the team can identify where it is now and where it is going next. It makes the team result focused instead of document driven or activity centric. The alpha concept is also fundamental to implementing the idea of a method being a composition of practices built on top of a universal kernel. It is the alpha concept that enables us to be able to create a robust, extensible, intuitive common ground.

Scott: Can you provide a few examples of alphas?

Ivar: We have identified seven top-level alphas: Requirements, Software System, Work, Team, Way of Working, Opportunity and Stakeholders. Take for example Software System, which has the following potential states: Architecture Selected, Demonstrable, Usable, Ready, Operational and Retired. To achieve a particular state there is a set of checkpoints to fulfill.

Apart from the top-level alphas, the kernel can be extended by adding lower level alphas--sub-alphas to the top-level alphas. These are typically added by the practices that the team adopts. For instance Requirements can have sub-alphas, which represent the individual requirement items--for instance a user story, a use case slice, or a feature. 

Scott: How do the ideas you capture in this book relate to agile?  To lean?  To RUP?

Ivar: The beauty of the approach is that it is agnostic to any particular method. You can apply the ideas of the book with agile, lean or any other legacy or new method. Since agile and lean today are the dominant ways of working, I will give two examples of how we make these better: 1) we can measure progress and health systematically at any point in time, and 2) it is easier to select and adopt the most appropriate set of agile practices to be used. We know that we will find better practices as we learn more about software development. The SEMAT approach allows the team to make major changes to their way of working in an evolutionary way instead of doing what they have done in the past: throw out the old way of working and start all over with a new way of working.

Scott: Many organizations are now trying to apply agile at scale. What insights does this book provide for doing so?

Ivar: Agile at scale is what my company has been doing for many years, and with that background many of the ideas behind SEMAT have been developed. The kernel idea became evident when we tried to help large companies to govern their methodologies, usually many but with no common ground. Large companies will use the kernel as a base and allow teams to select practices from a practice library to create their diverse methods. It helps the organization to become a learning one, since practices (much smaller than methods) can be adopted and improved across the organization. Practices will be improved, taught and mix-and-matched across the organization. Practices are by definition designed to be lean so the methods applied in the organization will naturally become lean.

Scott: In the book you indicate that there is more work to do on this topic. So, how has this work evolved since then and where will do you hope it will go in 2013 and 2014?

Ivar: Thus far SEMAT has focused on getting a widely agreed upon kernel. The next step of SEMAT is to create a practice library described on top of the kernel. There are today a set of 25 or more such practices defined on top of an earlier version of the kernel, so we are not starting from scratch. Tools are being developed to support practice authoring and practice exchange. Courses are being written to teach the kernel and practices. And more of similar nature.  However, we are also working on a different area, an underlying theory for software engineering, which has got a lot of attention from the academic world.

Scott: Who is working on the SEMAT effort?

Ivar: SEMAT was founded by Bertrand Meyer, Richard Soley and me.  Today we serve as an advisory board.  SEMAT has an executive committee of 7-8 people who lead the work in the community. More than 20 people have been working together for a long time to get where we now are: a widely agreed upon kernel. SEMAT has also local chapters in several countries, in China, South Africa, Latin America, Russia and under formation in Japan and South Korea.

Getting to this kernel was the very first milestone of SEMAT. Now the work scales up, and many more people are joining the effort. We have just appointed a new chairman of the executive committee-- professor June Park--with experience from both the academic world as a professor at the University of Iowa in Iowa City and from the industry as CTO of Samsung SDS.

We will be working in primarily two areas: 1) the practice area and 2) the theory area.

The practice area will work on creating a practice library of well-proven practices such as user stories, use-case 2.0, Scrum, architecture design, etc., which can be mixed and matched to create specific methods.

The theory area has been very active this last year and successful in creating a significant interest in the academic world. The objective is to come up with a general theory in software engineering. The SEMAT kernel is interesting as a base for such a theory – it works as a definition of what software engineering is.

Scott: Do you have any parting thoughts to share with us?

Ivar: SEMAT represents a paradigm shift in the way we look upon ways of working. The kernel is a simple thinking framework to help teams understand the progress and health of their endeavor. As with every paradigm shift there is a threshold to step over before being able to see the fundamental differences with what you had before. Once over, you get a very good basis for discussing and comparing practices, you can easier upgrade your existing way of working in small controllable steps, and you can systematically learn from other teams inside or outside your company. 

Dr. Ivar Jacobson is a father of components and component architecture, use cases, the Unified Modeling Language and the Rational Unified Process. He has contributed to modern business modeling and aspect-oriented software development. Lately, Ivar has been working on how to deal with methods and tools in an agile and lean way. He is one of the leaders of SEMAT discussed in this interview. In 2004, Ivar received the Gustaf Dalen medal from Chalmers Institute Of Technology, Gothenburg Sweden.  He is an international honorary advisor at Peking University, Beijing, and he is an honorary doctor at San Martin de Porres University, Peru. He is the principal author of six influential and best-selling books, including Object-Oriented Software Engineering, Business Process Reengineering with Objects, Software Reuse: Architecture, Process and Organization for Business Success, The Road to the Unified Software Development Process, and The Unified Software Development Process. He co-authored two UML books with Grady Booch and James Rumbaugh.  Ivar is also a founder of Ivar Jacobson International, operating in seven countries around the world.  His company’s home page is ivarjacobson.com.

Scott W. Ambler is a Senior Consulting Partner of Scott Ambler + Associates, working with organizations around the world to help them to improve their software processes. He provides training, coaching, and mentoring in disciplined agile and lean strategies at both the project and organizational level. Scott is the founder of the Agile Modeling (AM), Agile Data (AD), Disciplined Agile Delivery (DAD), and Enterprise Unified Process (EUP) methodologies. He is the (co-)author of several books, including Disciplined Agile Delivery, Refactoring Databases, Agile Modeling, Agile Database Techniques, The Object Primer 3rd Edition, and The Enterprise Unified Process. Scott is a senior contributing editor with Dr. Dobb’s Journal and his company’s home page is ScottAmbler.com.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020