What do you think?
Rate this book
Essence of Software Engineering, The: Applying the SEMAT Kernel: Applying the SEMAT Kernel
Using the proposed SEMAT Object Management Group standard, development organizations can "re-found" software engineering based on solid theory, proven principles, and best practices that have earned wide support. Using SEMAT, they can address both technology and human issues, while achieving easy extensibility to support diverse uses, changing requirements, and new technologies.
In The Essence of Software Engineering, a team of key SEMAT pioneers introduce this new standard, explaining how it defines a common ground for more agile and effective software development. Led by Ivar Jacobson, one of this generation's most influential software innovators, they fully introduce both elements of SEMAT: the kernel, encompassing Requirements, Software System, Team, Work, other key elements of software projects, and their states, and can be used by practitioners to make better choices about how they develop software systems; ahe language, defining syntax and semantics for organizing and composing practices and methods. For all software engineering practitioners, including architects, designers, developers, testers, requirements engineers, process engineers, and project managers.
In The Essence of Software Engineering, a team of key SEMAT pioneers introduce this new standard, explaining how it defines a common ground for more agile and effective software development. Led by Ivar Jacobson, one of this generation's most influential software innovators, they fully introduce both elements of SEMAT: the kernel, encompassing Requirements, Software System, Team, Work, other key elements of software projects, and their states, and can be used by practitioners to make better choices about how they develop software systems; ahe language, defining syntax and semantics for organizing and composing practices and methods. For all software engineering practitioners, including architects, designers, developers, testers, requirements engineers, process engineers, and project managers.
224 pages, Paperback
First published January 9, 2013
3 people are currently reading
123 people want to read
About the author
Ivar Jacobson
27 books12 followersIvar Hjalmar Jacobson is a Swedish computer scientist and software engineer, known as major contributor to UML, Objectory, Rational Unified Process (RUP), aspect-oriented software development and Essence.
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 4 of 4 reviews
March 31, 2018
It’s been a while since I was so impressed by a book.
The book describe in details the SEMAT (Software Engineering Method and Theory) work on the Kernel.
They propose the “essence” of software projects, which they call Alphas: Opportunity, Stakeholder, Requirement, Software System, Work, Team, Way do Working. Out of that, they define how we can progress within each one of them.
The main idea is to provide a thought framework for software teams where they can customise and measure the way they work, and choose the appropriate practices to their own contexts.
The Kernel serves to guide software teams all the way from a potential business opportunity to software running in production, satisfying stakeholders and later retired. The way they use cards make everything even nicer and more visible.
This is a must read book for any software professional. Highly recommended.
The book describe in details the SEMAT (Software Engineering Method and Theory) work on the Kernel.
They propose the “essence” of software projects, which they call Alphas: Opportunity, Stakeholder, Requirement, Software System, Work, Team, Way do Working. Out of that, they define how we can progress within each one of them.
The main idea is to provide a thought framework for software teams where they can customise and measure the way they work, and choose the appropriate practices to their own contexts.
The Kernel serves to guide software teams all the way from a potential business opportunity to software running in production, satisfying stakeholders and later retired. The way they use cards make everything even nicer and more visible.
This is a must read book for any software professional. Highly recommended.
April 17, 2013
“The Essence of Software Engineering – Applying the SEMAT Kernel” looks to be a classic one day. Not today of course because it just came out. But one day.
SEMAT stands for Software Engineering Methods and Theory. Don't let the word “theory” scare you. It's not a book about theory. It's a way of looking at software. All projects have some things in common. Using a common language to describe them and looking at key concepts (alphas) makes for better software. The book is geared to software professionals and students. With a goal of making for better developers. And SEMAT isn't done. They are incremental releasing supporting products through 2014.
I liked the parts about practices more than the kernel – I think because it was more concrete. The kernel does raise key points though. Some of which we take for granted and some of which we forget about.
The cards and checklists are useful. Did I mention the cards? They are quite prevalent in the book. I wish it said where to buy them.
I particularly liked the chapter on scaling. It didn't just cover scaling volume. It also covered zooming in and reaching out to others.
It will be interesting to see if SEMAT catches on. But even it doesn't, the key points still matter and it is worth the read.
Disclosure: I received a free copy of this book from the publisher in exchange for writing a review.
SEMAT stands for Software Engineering Methods and Theory. Don't let the word “theory” scare you. It's not a book about theory. It's a way of looking at software. All projects have some things in common. Using a common language to describe them and looking at key concepts (alphas) makes for better software. The book is geared to software professionals and students. With a goal of making for better developers. And SEMAT isn't done. They are incremental releasing supporting products through 2014.
I liked the parts about practices more than the kernel – I think because it was more concrete. The kernel does raise key points though. Some of which we take for granted and some of which we forget about.
The cards and checklists are useful. Did I mention the cards? They are quite prevalent in the book. I wish it said where to buy them.
I particularly liked the chapter on scaling. It didn't just cover scaling volume. It also covered zooming in and reaching out to others.
It will be interesting to see if SEMAT catches on. But even it doesn't, the key points still matter and it is worth the read.
Disclosure: I received a free copy of this book from the publisher in exchange for writing a review.
May 23, 2013
Since the first time that I heard about the Software Engineering Method and Theory (SEMAT) initiative in 2010, I have been interested to see what would be the result. The publications of the first book about the essence of software engineering gives visibility for SEMAT to a larger audience. At the same time, the actionable kernel is also something that is useful in software development organizations to understand and improve their way of working.
The kernel described in the book consists of all kinds of activities that are done by software engineering teams. Teams can use the kernel elements to discuss how they are doing the software engineering activities, and explore different ways of doing them depending on their needs. The detailed descriptions of the elements on cards can be used by team members in their daily work, enabling teams to self asses their way of working and continuously improve themselves.
This first SEMAT book gives much attention to the agile principles and ways of software development, thereby confirming that agile is a usable and relevant approach to develop software. For organizations that are adopting agile and lean this book can be very helpful, as it actively support the agile concept of self-organization with the software engineering kernel.
The kernel described in the book consists of all kinds of activities that are done by software engineering teams. Teams can use the kernel elements to discuss how they are doing the software engineering activities, and explore different ways of doing them depending on their needs. The detailed descriptions of the elements on cards can be used by team members in their daily work, enabling teams to self asses their way of working and continuously improve themselves.
This first SEMAT book gives much attention to the agile principles and ways of software development, thereby confirming that agile is a usable and relevant approach to develop software. For organizations that are adopting agile and lean this book can be very helpful, as it actively support the agile concept of self-organization with the software engineering kernel.
August 26, 2014
After all the SEMAT claims that they are going to fix all that is broken with current software engineering, this book is quite a let-down. It just repeats and re-packages the current state of practice. Maybe that was the goal all along and I just misunderstood it?
Displaying 1 - 4 of 4 reviews