The Essence of Software Engineering und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr
  • Alle Preisangaben inkl. MwSt.
Nur noch 2 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon.
Geschenkverpackung verfügbar.
The Essence of Software E... ist in Ihrem Einkaufwagen hinzugefügt worden
+ EUR 3,00 Versandkosten
Gebraucht: Wie neu | Details
Verkauft von ---SuperBookDeals---
Zustand: Gebraucht: Wie neu
Kommentar: 100% Geld zurueck Garantie. Zustand Wie neu. Schneller Versand, erlauben sie bitte 8 bis 18 Tage fuer Lieferung. Ueber 1,000,000 zufriedene Kunden. Wir bieten Kundenbetreuung in Deutsch.
Ihren Artikel jetzt
eintauschen und
EUR 5,39 Gutschein erhalten.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Anhören Wird wiedergegeben... Angehalten   Sie hören eine Probe der Audible-Audioausgabe.
Weitere Informationen
Dieses Bild anzeigen

The Essence of Software Engineering: Applying the SEMAT Kernel (Englisch) Taschenbuch – 16. Januar 2013

Alle 2 Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Amazon-Preis Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
"Bitte wiederholen"
EUR 26,95
EUR 23,52 EUR 19,95
59 neu ab EUR 23,52 7 gebraucht ab EUR 19,95
Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.


  • Taschenbuch: 300 Seiten
  • Verlag: Addison Wesley (16. Januar 2013)
  • Sprache: Englisch
  • ISBN-10: 0321885953
  • ISBN-13: 978-0321885951
  • Größe und/oder Gewicht: 15,9 x 1,8 x 23,2 cm
  • Durchschnittliche Kundenbewertung: 4.0 von 5 Sternen  Alle Rezensionen anzeigen (1 Kundenrezension)
  • Amazon Bestseller-Rang: Nr. 212.098 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
  • Komplettes Inhaltsverzeichnis ansehen

Mehr über die Autoren

Entdecken Sie Bücher, lesen Sie über Autoren und mehr



Scott W. Ambler In early 2006, Ivar told me about his ideas around the essentials of the software process and about how to describe them with alphas and work products. At the time, I knew he had some work to do but clearly had important insights to share. This work eventually dovetailed into SEMAT, which I was honored to be involved with at its inception. This book reflects the hard-earned experiences of a host of people, and it is destined to become a classic in the field of software engineering. -Scott W. Ambler, Founder, AmbySoft Inc. Dines Bjorner This book is the result of an intensive effort, SEMAT, originated by Ivar Jacobson. In close collaboration with a string of software engineering consultants, researchers, and practitioners, the authors suggest a basis for software engineering that ties together a number of issues heretofore not adequately covered in the literature. An aim of this book is to provide a basis for both a comprehensive methodology and a theory for software engineering. The book powerfully provides cogent arguments and proposes a number of solutions. I most sincerely hope that this timely book will be studied by many academic researchers and that it will spur widespread discussions and even debates, while at the same time influencing current software engineering and programming methodology research and teaching. -Dines Bjorner, Ph.D., Dr.h.c., Prof. Emeritus DTU Informatics, Denmark Barry Boehm There is an increasing need for software process approaches that are sufficiently flexible to fit the variety of development situations that projects will encounter, but that have sufficient integrity to serve as a basis for developing trustable software systems. Having tried to do this by evolving the spiral model and finding how hard it is, I salute the SEMAT developers for converging on a flexible but gently prescriptive approach to cover the full range of software engineering concerns with its kernel of key process, product, and people elements. Its key principles of value-driven system definition and evolution; balancing of near-term agility and architecting for the long term; and attacking risks early and continuously, are critical success factors for coping with software's increasing complexity, dynamism, and enterprise-criticality. -Barry Boehm, USC, Los Angeles, CA, USA Capers Jones This book is not just another surface view of software engineering, but rather an attempt to distill the fundamental concepts of software engineering into an effective model that can be used as a guide for any size and kind of software project. The book considers and addresses all factors that influence software applications, including the need or opportunity that initiates a software project, stakeholders, requirements, and the team who will construct it. The book is not all theory, but includes a number of useful examples based on real problems that many readers will recognize. -Capers Jones, Vice President and Chief Technology Officer, Namcook Analytics LLC Thomas Atwood A brilliant approach to bring focus back to the fundamentals in making software projects actually work. I've been most recently involved with websites built using dynamic object programming languages like Ruby, cutting edge app servers like Rails, and a new generation of semantic databases. Agile programming, test-driven development, and powerful application frameworks have made tremendous strides on the technology side. Yet the fundamentals of clearly understanding the objectives of a project, and building development teams that work, has lagged behind. SEMAT's alphas lay it out in a simple, cohesive, and practical fashion. They help everyone who has a stake in the effort, including the customer and the development team, understand the scope and state of the project. Bravo! The distilled wisdom of some of the truly great thinkers who have shaped the software development landscape. -Thomas Atwood, Ph.D., Director, CloudSuite Media, San Francisco, CA, USA Arne J. Berre The SEMAT community should be commended for addressing the identification of a common ground for a much-needed, practice-oriented and adaptive framework for software engineering. It is encouraging to see that the SEMAT Language and kernel also has been contributed as input to a new standard development by the Object Management Group (OMG). This book is an excellent introduction for both practitioners and academics to the principles of this emerging standard and its approach of working with software engineering methods in an agile and lean way. -Arne J. Berre, Chief Scientist and Associate Professor II, SINTEF and University of Oslo, Norway Kari Brey The Essence of Software Engineering: Applying the SEMAT Kernel is what we all have been waiting for. Being a practitioner, and leading organizational transformation in software development for more than ten years, I am often asked why there isn't something written that guides teams on how to be flexible with their approach to delivering software solutions. This book does just that. The book isn't about a new methodology. It is about the essentials! It is about figuring out which essentials will be needed for each type of effort, whether it be a small team building a small solution or a large distributed team with several interdependencies building large, complex solutions. One size does not fit all and The Essence of Software Engineering provides the examples for readers to relate to. The book also stresses the importance of collaborating with the stakeholders, understanding their needs, starting out with building a skinny system and building on the skinny system. I am excited to be a part of SEMAT and even more excited in applying the kernel and sharing those learnings with the software community. -Kari Brey, Office of the CTO, WellPoint, Inc. Zhong Chen Simple is beautiful. You won't be able to imagine how simple and effective the SEMAT way is to address the tough problems of software engineering that have surrounded us for more than forty years, until you read this book-The Essence of Software Engineering. The book clearly presents the concise notation, the elegant kernel elements, and the great thought behind the grand vision of "refounding software engineering based on a solid theory, proven principles and best practices." It is a good start to establishing a common ground for practitioners and scholars in the software engineering community, as well as a solid foundation for software engineering education. The SEMAT initiative, like a fresh breeze, is blowing from west to east, and from north to south over the continents. We can see the new era of software engineering is coming. -Dr. Zhong Chen, Chairman of SEMAT Chapter in China; Professor and Chairman, Department of Computer Science and Technology, School of EECS, Peking University, China; Deputy-Chair of Software Engineering Teaching Guidance Committee, Ministry of Education, China Leo Crawford For too long, software engineers have been embroiled in ideological battles. Initially these were on the placement of braces and the method of indentation. Those battles are mostly behind us, but there are new ones on how we run our software projects-the process and practices we use. I'm delighted to finally see a text that gives us a framework for discussing and comparing the approaches we use-hopefully moving us from religion to science. -Leo Crawford, FBCS CEng CITP, Cirencester, UK Barry Dwolatzky Teaching software engineering within a university curriculum has always been a difficult task. In most other engineering disciplines, one begins by developing a deep understanding of the theory-the foundational principles that hold true over long periods of time. Only once the student has mastered the theory does one introduce specific methods, practices, and applications. The challenge in software engineering is to separate out the foundational principles-the "theory"-from the practice. In The Essence of Software Engineering, Ivar Jacobson and his coauthors have tackled the ambitious task of distilling out those essential elements, the "kernel," that lie at the heart of all software engineering methods and practices. This work holds out the promise of giving those of us engaged in teaching software engineering a "theory" upon which to build a coherent and successful curriculum. -Barry Dwolatzky, Chairman of SEMAT Chapter in South Africa; Professor of Software Engineering and Director, Joburg Centre for Software Engineering (JCSE), Johannesburg, South Africa Michael Goedicke The SEMAT initiative provides a range of important possibilities in terms of teaching software engineering. This is a strong motivation for me to engage myself in this activity. The kernel, with its essential notions of software engineering, will enable a systematic and structured teaching. The potential to compare and to assess practices and entire methods will not only be instrumental in teaching and training activities. It also has the potential to identify and categorize new research questions in softwar engineering! -Prof. Dr. Michael Goedicke, Specification of Software Systems, Paluno, The Ruhr Institute for Software Technology, University of Duisburg-Essen, Germany; Associate Dean, College of Engineering, Carnegie Mellon University Martin Griss This book presents an exciting new way of looking at software development and software engineering. What motivates me as a teacher, researcher, and practitioner of software engineering and software reuse is that for the first time we have a robust basis for a solid product-line approach to describing, analyzing, and running software development processes. * SEMAT provides a kernel and well-founded building blocks, the essential elements of software development. These elements can be composed, adapted, and extended to describe a variety of well-known methods, such as Scrum, XP, and RUP, as well as newer methods, such as for software services, embedded systems, and systematic reuse. The reusable kernel elements can be enhanced with specific practices to describe details of the method you need. * Not only can you define and describe your method with precision, but you can also use the selected elements t...

Über den Autor und weitere Mitwirkende

Dr. Ivar Jacobson, one of the prime movers behind SEMAT, is the principal author of six books, including, with Pan-Wei Ng, Aspect-Oriented Software Development with Use Cases (Addison-Wesley, 2005). Dr. Pan-Wei Ng is the Asia Pacific CTO and chief scientist at IvarJacobson International and coaches large-scale development extensively. Paul E. McMahon, principal of PEM Systems, is the author of Integrating CMMI(R) and Agile Development (Addison-Wesley, 2011). Ian Spence, chief scientist and principal consultant at Ivar Jacobson International, is the coauthor of Managing Iterative Software Development Projects (Addison-Wesley, 2007). Svante Lidman is a senior productivity expert at Hansoft and has been leading and coaching software development teams for twenty years.

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?

In diesem Buch (Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Hier reinlesen und suchen:


4.0 von 5 Sternen
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne
Siehe die Kundenrezension
Sagen Sie Ihre Meinung zu diesem Artikel

Die hilfreichsten Kundenrezensionen

Von Bücherkeule am 16. Februar 2013
Format: Taschenbuch Verifizierter Kauf
SEMAT is a very welcome addition to the ongoing discussions on what software-engineering is (craft or engineering), and how the endeavor of building software must be organized. The initiators of SEMAT quite rightly point out that many of the discussions about methods tend to look at the question from a particular viewpoint at the expense of other viewpoints. As a result single truths emerge where some aspects of the endeavor outshine others: Artifact-centric, management-driven processes like RUP versus action-driven, people-centric lean processes such as SCRUM or XP versus architecture-centric methods verses test-centric methods such as TDD versus etc. SEMAT is the result of several years of discussions among some of the figure-heads of software engineering, and thus the result, for the first time explained in the present book, should be considered with interest.

SEMAT takes a bold step backwards. It advocates looking at the software endeavor in a more balanced way by identifying the key areas of activity which together are part of the endeavor, and where failure in any of the ereas would imply failure of the overall effort. These key areas are called alphas (a choice of name which seems somewhat arbitrary and may make you feel uneasy if you dislike management waffle or sectarian talk). By default, there are seven such areas: Opportunity, Stakeholders, Requirements, Software System, Team, Work, and Way of Working. For each area there is a high level work-flow with states through which the endeavor progresses from initiation to finish. You may, if you find it necessary, add more such areas, but where exactly the delineation between alpha and the doing within an alpha is remains somewhat unclear.
Lesen Sie weiter... ›
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen

Die hilfreichsten Kundenrezensionen auf (beta) 19 Rezensionen
20 von 23 Kunden fanden die folgende Rezension hilfreich
Not quite wrong, not quite right 4. Juni 2013
Von Per Holst - Veröffentlicht auf
Format: Taschenbuch
I am a bit confused. I had the notion that this was about improving software quality through the application of a rigorous set of rules. Section 1.1 "Why is developing good software so challenging?" seems like we're on the right track. But I find that it has not that much to do with Software, nor Engineering. It seems it is a method for applying rules and visual indications for the progress of tasks by people for people. Which means that to me at least, this book is more about general project management than anything near software or engineering.

I found the tone of the book to be rather preaching and praising of this new found holy grail, the Kernel, all praise the Kernel, apply it to anything and everything. A common phase throughout is: "How can the kernel help you." The kernel consist of just about 57 cards, but can be extended. Seems like the marketing managers choice for gamification Yu-gi-oh!-style.

I'm all for simple and concise ways of working. I do believe that visual aids can support collaboration and communication as well as bring a quick overview, and that these are needed for projects to succeed, but they are not all which is needed.

I believe in the "as simple as possible, but no simpler." - as Einstein put it. As well as Antoine de Saint-Exupéry's "You have achieved perfection not when there is nothing left to add, but when there is nothing left to take away."

Throughout the book the Kernel will simply help do everything, it's a veritable Swiss Army knife. I don't think I've seen any professional choose the Swiss Army knife above their own set of tools. While the Kernel is lightweight - at least compared to RUP - then there are alternatives, which are even more lightweight, e.g. Impact Mapping.

To me it seems that applying the Kernel kind of looks like Kanban with a "work in progress"-board. But then it also looks a bit like a concurrent waterfall, which could be due to the fact that I read RUP and UML into the stuff that Ivar writes. Both of which were praised. In my opinion wrongly so. UML is great for back of the napkin illustration of concepts, a variant worked wonders in the Design Patterns book, but UML in the latest incarnation seems overly verbose as a modelling language - under the notion that a model is a simplified abstraction of the real thing.

Perhaps Ivar is biased from electronic engineering with all their symbols and glyphs (Try looking for IEC 60617 on Google). But what he fails to realize is that those symbols are really their programming language. For software development, we have our own programming languages, and we don't need a modelling language to go into minute details - at least not as a document. If you generate the model from the source code you can apply as much details as you want, but believing that a change is applied both to the model and to the source code is betting against the DRY principle: Don't Repeat Yourself.

Why do have a sense of concurrent waterfall? Well, the cards follow 7 aspects, called alphas: Opportunity, Stakeholders, Requirements, Software System, Team, Work, and Way of Working. While I agree to these, and their connections noted in the graphs, e.g. Figure 2-1 on page 15 (not shown here), then there is a notion of the 5 or 6 steps, and seemingly you can only progress, e.g. from Opportunity :: Identified to Opportunity :: Solution Needed. And while that might be true for opportunities, then I don't see why Way of Working :: Working Well will stay there until the project is done.

Some of the praise in the book is from academia, and while it is easier to teach a rigorous system, it may still not be the right thing to do - at least it hasn't helped adding UML, RUP, etc. to the curriculum.

In the praise section, Ed Seymour notes that: "This book represents a significant milestone in the progression of software engineering." I'm sure that any book is a milestone in its domain, I just feel that this book is a milestone along a different road going in the, not quite right, not quite wrong, direction.

Uncle Bob - one of the three to write a foreword - wrote: "After reading the book, I found myself wanting to get my hands on a deck of cards so that I could look through them and play with them." I felt the same at the beginning of the book, but now I'm thinking more about which game to play, and how many expansion packs will be published in the future.

All in all I'm quite disappointed with the contents of the book, though I'm sure it'll get wide adoption, and we will be off course for another 10 years. Some of the contents is true and solid, the rest - apart from the intentionally left blank pages (all 34 of them approximately 10% of the book) - seems to me to be more of an academic solution to something which is only half the problem. It is easy to prove me wrong though - apply the Kernel to 12 or more different and average teams and have them develop successful software solutions on time and on budget for projects around the $5-10 million budget. Public projects seem to fare really poorly, that would be an interesting case to follow. If more than 1 project fails, then the Kernel is not the holy grail, depending on the success rate, we could argue whether or not the method is helpful at all.
9 von 13 Kunden fanden die folgende Rezension hilfreich
One of a Kind.... A MUST READ 20. Februar 2013
Von T. Anderson - Veröffentlicht auf
Format: Taschenbuch
I have had the opportunity to lead dozens of software development projects which I love doing. I have also had the opportunity to watch dozens of software development project from the sidelines, while working on my own project, or in place as a consultant to accomplish something other than run the development process.

From the sidelines I have seen some succeed, some crash and burn, and the rest get close enough to success that the team can sell it as a success. Sometimes the later takes a heck of a sales job. I would say in my book 80% of those sold as successes failed. They either came in well over budget, well beyond their projected delivery date, or delivered such buggy software that the maintenance effort was as big as the development effort. Success to the team simply meant they considered the project over. You will find of those project teams run as fast as they can instead of doing a retrospective study.

The hard, and sad part, of watching the projects flop is that they are so predictable. A lot of times I find an environment has just come to terms with the fact that all the projects will come in late, over budget, and buggy. They have accepted reaching the end of the project as the only measure of success. You will usually find those environments are running in fire mode. Meaning the highest priorities for the day are the hottest fires and there are fires for everyone every day. They can't see it, but even there larger strategic projects are reacting to fires. They never get ahead, they just keep slowly slipping further behind.

So by now you are probably wondering what all that blather has to do with this book? To be able to recognize a project that is going off-track takes years of experience. The SEMAT Kernel provides a set of tools that enable those, that would normally not have enough experience to recognize when the project is going off-track, to be able to. The book is broken down into seven parts. I have listed each part below with the chapters they contain.

Part I: The Kernel Idea Explained
1. A Glimpse of How the Kernel Can Be Used
2. A Little More Detail about the Kernel
3. A 10,000-Foot View of the Full Kernel
4. The Kernel Alphas Made Tangible with Cards
5. Providing More Details to the Kernel through Practices
6. What the Kernel Can Do for You

Part II: Using the Kernel to Run an Iteration
7. Running Iterations with the Kernel: Plan-Do-Check-Adapt
8. Planning an Iteration
9. Doing and Checking the Iteration
10. Adapting the Way of Working
11. Running an Iteration with Explicit Requirement Item States

Part III: Using the Kernel to Run a Software Endeavor
12. Running a Software Endeavor: From Idea to Production
13. Building the Business Case
14. Developing the System
15. Operating the Software

Part IV: Scaling Development with the Kernel
16. What Does It Mean to Scale?
17. Zooming In to Provide Details
18. Reaching Out to Different Kinds of Development
19. Scaling Up to Large and Complex Development

Part V: How the Kernel Changes the Way You Work with Methods
20. Thinking about Methods without Thinking about Methods
21. Agile Working with Methods

Part VI: What’s Really New Here?
22. Refounding Methods
23. Separation of Concerns Applied to Methods
24. The Key Differentiators

Part VII: Epilogue
25. This Is Not the End
26. ... But Perhaps It Is the End of the Beginning
27. When the Vision Comes True

Appendix A. Concepts and Notation
Appendix B. What Does This Book Cover with Respect to the Kernel?

This book is not about defining or executing a new software development process, so don't expect to find how to create user stories, manage a product backlog, implement an instance of the RUP, or document your software architecture. This book is about the essential elements that are part of every software development process and how to recognize their current state in order to understand where you are in the process of your choice. It also walks you through the process of assembling a method from activities you have selected to use.

The kernel is broken down into three areas of concern which include Customer, Solution, and Endeavor. Each area of concern encapsulates alphas (things that progress and evolve) and activities.

Alphas include Opportunity, Stakeholders, Requirements, Software System, Team, Work, and Way of Working. Each of these have six different states attached to them which reflect their maturity.

The book defines activity spaces as explore possibilities, understand stakeholder needs, ensure stakeholder satisfaction, use the system, understand the requirements, shape the system, implement the system, test the system, deploy the system, operate the system, prepare to do the work, coordinate activity, support the team, track progress, and stop the work.

The next step the book takes is to assemble the alphas and activities into practices. An example of a practice would be a requirements elicitation practice. The practices are then used to build methods.

One really nice thing this book does is provide a common vocabulary that can be use across processes. Meaning that no matter what process you are using the kernel's alphas and activities apply. This will make it easier to see the different processes for what they really are at their core and make them easier to understand.

One thing I would have like to see different with this book is the alphas full checklist be used instead of the short-form, or at least have the long form list included in an appendix. You can get the full checklist from the Essence – Kernel and Language for Software Engineering Methods which is on the SEMAT web site. This does not take anything away from the book, it is just a pet peeve of mine. I don't like when a book provides less detail than the free specifications available on line.

I have found some books that are just summaries of the online work and you end up being pointed to that work in every chapter. That is not the case with this book, there is a lot of information in this book you won't find in the specs on line. The format and writing style of the book also makes reading the book much more pleasurable than reading the Essence – Kernel and Language for Software Engineering Methods OMG submission.

Overall I found this book to be a breath of fresh air. It is hard to find any pure software engineering process books anymore. They all tend to be a rehash of all the latest agile processes out there, which are all just reworks of all the iterative processes out there. The book and its material is very usable. I highly recommend this book to anyone with any role in the software development field.
2 von 3 Kunden fanden die folgende Rezension hilfreich
SEMAT enables teams to self asses their way of working and continuously improve themselves. 23. Mai 2013
Von Ben Linders - Veröffentlicht auf
Format: Taschenbuch
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.
3 von 5 Kunden fanden die folgende Rezension hilfreich
Getting back to basics 18. Februar 2013
Von Barry Dwolatzky - Veröffentlicht auf
Format: Taschenbuch Verifizierter Kauf
I've been involved in "Software Engineering", both as a teacher and a user, all of my working life. Like many others I have become frustrated and disillusioned by the failure of "Software Engineering" to live up to its initial ambition - namely to solve the so-called "software crisis". The founders of the discipline of Software Engineering set out in the late 1960's to deal with the fact that most large software projects were completed (very) late, were (way) over budget and had (far too many) defects. Fifty years later these problems are still a reality. In spite of decades of silver bullets and methodology debates we still struggle to deliver high quality software in a repeatable and predictable manner.

Has "software engineering" failed? Is there any hope that it will ever succeed.? This book by Ivar Jacobson, et al describes an attempt to get back to basics. They define a very small set of elementary practices - the SEMAT Kernel - and show how these can be used to describe existing methods. This stripping of things down to basic building blocks is a very different approach from what we have seen before. It gives us a new way to understand and use the key concepts at the heart of "good" Software Engineering.

There is still much work to be done, but I believe that this book will become a seminal text in the re-founding of the important discipline of Software Engineering. And not only that - its extremely readable!
1 von 2 Kunden fanden die folgende Rezension hilfreich
Holy Grail of software engineering 16. März 2013
Von Pontus Johnson - Veröffentlicht auf
Format: Taschenbuch
I would like to take this opportunity to restate my opinion of this work as I have expressed it in the book. The goal of the book is very important: to describe a sound, common foundation for software development. Reaching beyond the hypes, the Kernel represents the most important elements of any software engineering endeavor and their relation to each other. From a practical perspective, this allows developers to break free of methodological dogmas and tailor their methods according to their own needs. From a theoretical perspective, the Kernel is a frame for a comprehensive theory of software engineering. Such a theory is a Holy Grail of software engineering, elevating the discipline from the travails of trial and error to the province of premeditated design.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.