Errors drive us crazy. Computers can reduce errors, but in a minute can multiply a single error a million times. To use a computer successfully, you need to know more about errors than you ever imagined.
“How do I make my user stories smaller?” “What is the right size for a user story?” “What is the difference between an Epic and a Story? And where do Tasks and Sub-tasks fit in?” “Who writes user stories?” “Why user stories?” "Do I have to use User Stories?" Allan Kelly found himself answering these questions, and similar ones, again and again so one day he sat down to answer them all once and for all. The result is this book. Short. Practical. To the point. And cheap.
The first part of a three part book series focused on lifting the security knowledge of Software Developers, Engineers, and their teams, so that they can continuously deliver secure technical solutions on time and within budget. Free Online: https://f0.holisticinfosecforwebdevelopers.com
SaltStack For DevOps Through this book you will learn how to use one of the most powerful DevOps orchestration tools.
SaltStack For DevOps Through this book you will learn how to use one of the most powerful DevOps orchestration tools.
connect adapt simplify
"Consciousness raising for systems analysts."—Tom Demarco, Principal, Atlantic Systems Guild "It's likely that this book will not only give you concrete ways to improve our requirements gathering process, but will also change the way that you look at requirements."—Elisabeth Hendrickson, Quality Tree Consulting
"The authors combine the views of their disciplines and look at larger issues such as the interplay between systems and people, the abstract and concrete, and the theoretical and practical . The authors' style is light and sometimes humorous with a large number of quotations from literature. . . . Never dull . . . the book bears evidence of a global view in which systems design is a means if organizing ideas, structures, things, and experience."
One of the wonderful things about the Weinbergs' series of books -- and this one in particular -- is that the ideas and the examples really make you think. With examples chosen from many fields, the book illustrates its central ideas with a cross-fertilization that helps one think outside ones box.
A true classic, not just in computing but in the broad area of scholarship. It is partly about the philosophy and mechanisms of science; partly about designing things so they work but mostly it is about how humans view the world and create things that match that view. This book will still be worth reading for a long time to come. - Charles Ashbacher
The modeling of variants is a common use case in MBSE (for example for product line engineering or trade-off studies). Although SysML does not provide explicit model elements for variants, it is possible to create a variant model with SysML. The book explains the approach and provides a SysML profile for variants.
This is part 1 of the latest edition of the classic, Quality Software Management. Its fundamental purpose is to teach how to understand the dynamics of software development organizations, to plan software projects, and to act effectively to carry out those plans.
This is the classic volume on every variety of technical review of programs, designs, tests, documentation, plans, requirements, ...
SYSMOD is an MBSE toolbox for pragmatic modeling of systems. It is well-suited to be used with SysML. The book provides a set of methods with roles and outputs. Concrete guidances and examples show how to apply the methods with SysML.
Jerry Weinberg has been observing software development for more than 50 years. Lately, he's been observing the Agile movement, and he's offering an evolving set of impressions of where it came from, where it is now, and where it's going.