Realising evidence-based software engineering
REBSE '05 Proceedings of the 2005 workshop on Realising evidence-based software engineering
Using version control to observe student software development processes
Journal of Computing Sciences in Colleges
Encouraging Self-Organization: Reflections on a Quality Improvement Workshop
EUROMICRO '05 Proceedings of the 31st EUROMICRO Conference on Software Engineering and Advanced Applications
Peer Reviews in Real Life - Motivators and Demotivators
QSIC '05 Proceedings of the Fifth International Conference on Quality Software
The design of a component-oriented framework for numerical simulation software
Advances in Engineering Software
The soft side of software engineering
Journal of Computing Sciences in Colleges
Proceedings of the 2008 ACM SIGMIS CPR conference on Computer personnel doctoral consortium and research
Functional size measurement revisited
ACM Transactions on Software Engineering and Methodology (TOSEM)
Motivation in Software Engineering: A systematic literature review
Information and Software Technology
Modelling Web-Based Systems Requirements Using WRM
WISE '08 Proceedings of the 2008 international workshops on Web Information Systems Engineering
A UML Profile for Modelling Measurable Requirements
ER '08 Proceedings of the ER 2008 Workshops (CMLSA, ECDM, FP-UML, M2AS, RIGiM, SeCoGIS, WISM) on Advances in Conceptual Modeling: Challenges and Opportunities
Collaboration in Distributed Software Development
Software Engineering
Communications of the ACM - Finding the Fun in Computer Science Education
Language subsetting via reflection and overloading
FIE'09 Proceedings of the 39th IEEE international conference on Frontiers in education conference
Information and Software Technology
Cost estimation and analysis for government contract pricing in china
ICSP'07 Proceedings of the 2007 international conference on Software process
How a human-centered approach impacts software development
HCI'07 Proceedings of the 12th international conference on Human-computer interaction: interaction design and usability
Agile web engineering (AWE) process: perceptions within a fortune 500 financial services company
Journal of Web Engineering
Assessment of maintainability metrics for object-oriented software system
ACM SIGSOFT Software Engineering Notes
ACM SIGSOFT Software Engineering Notes
Systems evolution and software reuse in object-oriented programming and aspect-oriented programming
TOOLS'11 Proceedings of the 49th international conference on Objects, models, components, patterns
Architecture for the use of synergies between knowledge engineering and requirements engineering
CAEPIA'11 Proceedings of the 14th international conference on Advances in artificial intelligence: spanish association for artificial intelligence
Practical problems of programming in the large (PPPL)
ECOOP'04 Proceedings of the 2004 international conference on Object-Oriented Technology
Best practices for teaching UML based software development
MoDELS'05 Proceedings of the 2005 international conference on Satellite Events at the MoDELS
Establishing linux driver verification process
PSI'09 Proceedings of the 7th international Andrei Ershov Memorial conference on Perspectives of Systems Informatics
Empirical investigation on the benefits of using UML in software maintenance
Proceedings of the 12th International Conference on Product Focused Software Development and Process Improvement
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Assessing maintainability metrics in software architectures using COSMIC and UML
ICCSA'12 Proceedings of the 12th international conference on Computational Science and Its Applications - Volume Part IV
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
Hi-index | 0.00 |
From the Book:When I first heard that Bob Glass was going to write this book and model it after my 201 Principles of Software Development, I was a bit worried. After all, Bob is one of the best writers in the industry, and he would provide tough competition for my book. And then, when Bob asked me to write his foreword, I became even more worried; after all, how can I endorse a book that seems to compete directly with one of mine? Now that I have read Fifty-Five Facts, I am pleased and honored (and no longer worried!) to have the opportunity to write this foreword. The software industry is in the same state of affairs that the pharmaceutical industry was in during the late nineteenth century. Sometimes it seems that we have more snake-oil salespeople and doomsayers than sensible folks practicing and preaching in our midst. Every day, we hear from somebody that they have discovered this great new cure for some insurmountable problem. Thus we have oft heard of quick cures for low efficiency, low quality, unhappy customers, poor communication, changing requirements, ineffective testing, poor management, and on and on. There are so many such pundits of the perfunctory that we sometimes wonder if perhaps some portion of the proclaimed panaceas are possibly practical. Who do we ask? Who in this industry can we trust? Where can we get the truth? The answer is Bob Glass. Bob has had a history of providing us with short treatises on the many software disasters that have occurred over the years. I have been waiting for him to distill the common elements from these disasters so that we can benefit more easily from his many experiences. The 55 facts that Bob Glass discusses in thiswonderful book are not just conjectures on his part. They are exactly what I have been waiting for: i.e., the wisdom gained by the author by examining in detail the hundreds of cases he has written about in the past. The 55 facts that follow are likely to not be popular with all readers. Some are in direct opposition to the so-called “modern” ways of doing things. For those of you who wish to ignore the advice contained within these covers, I can only wish you the safest of journeys, but I fear for your safety. You are treading on well-trod territory, known to be full of mines, and many have destroyed their careers trying to pass. The best advice I can give you is to read any of Bob Glass’ earlier books concerning software disasters. For those of you who wish to follow the advice contained herein, you too are following a well-trod path. However this path is full of successful testimonies. It is a path of awareness and knowledge. Trust Bob Glass because he has been there before. He has had the privilege of analyzing his own successes and failures along with hundreds of others’ successes and failures. Stand on his shoulders, and you will more likely succeed in this industry. Ignore his advice and be prepared for Bob to call you in a few years to ask you about your project—to add it to his next compilation of software disaster stories. Alan M. Davis, Spring, 2002