Search Results - WOOK

Skip to main content

Skip to Braille books

ENGLISH

Complete Systems Analysis - The Workbook, The Textbook, The Answers

by James Robertson e Suzanne Robertson

23,84€ + 10% CARD

 <div usercontent"=""> <p style="margin:0px;">This is the digital version of the printed book (Copyright © 1998, 1994).</p> <p style="margin:0px;"> </p> <p style="margin:0px;">In a fundamentally new approach, <i><b><i>Complete Systems Analysis </i></b></i>teaches everything you need to know about analyzing systems: the methods, the models, the techniques, and more.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">A definitive text on modern systems analysis techniques is combined with an extensive case study to give readers hands-on experience in completing an actual analysis project.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Readers proceed through each step of a full-scale analysis project, analyzing the complex requirements of a television station’s airtime programming department. Each phase of the case study and each exercise in the textbook section is thoroughly explained in separate review and answer sections.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">An innovative Trail Guide system-inspired by the difficulty levels marked on ski trails-encourages readers to follow a sequence that suits their skill level. Beginners follow the full trail while experienced analysts fill in gaps in their training, refresh their understanding of key concepts, and practice their skills. Managers review key concepts but can skip the detailed work with models.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The book shows how analysis is used for object-oriented implementation, and how event-response data flow models and entity-relationship data models are complementary, not competing, models.</p> <p style="margin:0px;"> </p> <p style="margin:0px;"><i><b><i>Complete Systems Analysis </i></b></i>adapts to the reader’s needs and provides an appropriate learning path for the beginner, with a more direct route for experienced analysts wanting to make better use of today’s techniques. Since its initial publication in 1994 as a two-volume set in hardcover, this highly acclaimed text-released in 1998 as a single, softcover volume-has served as a course text in classes throughout the world. </p> <p style="margin:0px;"> </p> <p style="margin:0px;">Topics include</p> <ul> <li> <div style="MARGIN: 0px"> Analysis Models </div></li> <li> <div style="MARGIN: 0px"> Data Flow Diagrams </div></li> <li> <div style="MARGIN: 0px"> Data Viewpoint </div></li> <li> <div style="MARGIN: 0px"> Data Models </div></li> <li> <div style="MARGIN: 0px"> Leveled Data Flow Diagrams </div></li> <li> <div style="MARGIN: 0px"> Current Physical Viewpoint </div></li> <li> <div style="MARGIN: 0px"> Building the Data Dictionary </div></li> <li> <div style="MARGIN: 0px"> Strategy: Focusing on the Essentials </div></li> <li> <div style="MARGIN: 0px"> Identifying Events </div></li> <li> <div style="MARGIN: 0px"> Modeling an Event Response </div></li> <li> <div style="MARGIN: 0px"> Writing Mini Specifications </div></li> <li> <div style="MARGIN: 0px"> CRUD Check </div></li> <li> <div style="MARGIN: 0px"> Modeling New Requirements </div></li> <li> <div style="MARGIN: 0px"> New Physical Viewpoint </div></li> <li> <div style="MARGIN: 0px"> Object-Oriented Viewpoint </div></li> <li> <div style="MARGIN: 0px"> Strategy: Toward Implementation </div></li> </ul> </div> <p style="margin:0px;"> </p>
ENGLISH

Adrenaline Junkies And Template Zombies - Understanding Patterns Of Project Behavior

by James Robertson, Peter Hruschka, Steve Mcmenamin, Suzanne Robertson, Tim Lister e Tom DeMarco

11,91€ + 10% CARD

 <div usercontent"=""> <p style="margin:0px;">This is the digital version of the printed book (Copyright © 2008).</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Adrenaline junkies, dead fish, project sluts, true believers, Lewis and Clark, template zombies . . .</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Most developers, testers, and managers on IT projects are pretty good at recognizing patterns of behavior and gut-level hunches, as in, "I sense that this project is headed for disaster."</p> <p style="margin:0px;"> </p> <p style="margin:0px;">But it has always been more difficult to transform these patterns and hunches into a usable form, something a team can debate, refine, and use. Until now.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">In <b><i><b>Adrenaline Junkies and Template Zombies,</b></i></b> the six principal consultants of The Atlantic Systems Guild present the patterns of behavior they most often observe at the dozens of IT firms they transform each year, around the world.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The result is a quick-read guide to identifying nearly ninety typical scenarios, drawing on a combined one-hundred-and-fifty years of project management experience. Project by project, you’ll improve the accuracy of your hunches and your ability to act on them.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The patterns are presented in an easy-reference format, with names designed to ease communication with your teammates. In just a few words, you can describe what’s happening on your project. Citing the patterns of behavior can help you quickly move those above and below you to the next step on your project. You’ll find classic patterns such as these: </p> <ul> <li> <div style="MARGIN: 0px"> News Improvement </div></li> <li> <div style="MARGIN: 0px"> Management by Mood Ring </div></li> <li> <div style="MARGIN: 0px"> Piling On </div></li> <li> <div style="MARGIN: 0px"> Rattle Yer Dags </div></li> <li> <div style="MARGIN: 0px"> Natural Authority </div></li> <li> <div style="MARGIN: 0px"> Food++ </div></li> <li> <div style="MARGIN: 0px"> Fridge Door </div></li> <li> <div style="MARGIN: 0px"> <i>and more than eighty more!</i> </div></li> </ul> <p style="margin:0px;">Not every pattern will be evident in your organization, and not every pattern is necessarily good or bad. However, you’ll find many patterns that will apply to your current and future assignments, even in the most ambiguous circumstances. When you assess your situation and follow your next hunch, you''ll have the collective wisdom of six world-class consultants at your side.</p> </div> <p style="margin:0px;"> </p>
ENGLISH

Waltzing With Bears - Managing Risk On Software Projects

by Tim Lister e Tom DeMarco

11,91€ + 10% CARD

 This is the digital version of the printed book (Copyright © 2003). <b><br><br>If There’s No Risk On Your Next Project, Don’t Do It.</b> <p style="margin:0px;"> </p> <p style="margin:0px;">Greater risk brings greater reward, especially in software development. A company that runs away from risk will soon find itself lagging behind its more adventurous competition. By ignoring the threat of negative outcomes-in the name of positive thinking or a can-do attitude-software managers drive their organizations into the ground.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">In Waltzing with Bears, Tom DeMarco and Timothy Lister-the best-selling authors of Peopleware-show readers how to identify and embrace worthwhile risks. Developers are then set free to push the limits. </p> <p style="margin:0px;"> </p> <p style="margin:0px;">The authors present the benefits of risk management, including that it makes aggressive risk-taking possible, protects management from getting blindsided, provides minimum-cost downside protection, reveals invisible transfers of responsibility, isolates the failure of a subproject.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Readers are armed with strategies for confronting the most common risks that software projects face: schedule flaws, requirements inflation, turnover, specification breakdown, and under-performance.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Waltzing with Bears will help you mitigate the risks-before they turn into project-killing problems. Risks are out there-and they should be there-but there is a way to manage them.</p> <p style="margin:0px;"> </p>
ENGLISH

Adaptive Software Development - A Collaborative Approach To Managing Complex Systems

by Jim Highsmith

10,48€ + 10% CARD

 <div usercontent"=""> <p style="margin:0px;">This is the digital version of the printed book (Copyright © 2000).</p> <p style="margin:0px;"> </p> <i> <p style="margin:0px;">Winner of the 2001 Software Development Jolt Product Excellence Award</p> </i> <p style="margin:0px;"> </p> <p style="margin:0px;">This innovative text offers a practical, realistic approach to managing high-speed, high-change software development projects. Consultant James A. Highsmith shows readers how to increase collaboration and adapt to uncertainty.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Many organizations start high-speed, high-change projects without knowing how to do them-and even worse, without knowing they don’t know. Successful completion of these projects is often at the expense of the project team.</p> <p style="margin:0px;"> </p> <p style="margin:0px;"><b><i><b>Adaptive Software Development</b></i></b> emphasizes an adaptive, collaborative approach to software development. The concepts allow developers to "scale-up" rapid application development and extreme programming approaches for use on larger, more complex projects.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The four goals of the book are to </p> <ul> <li> <div style="MARGIN: 0px"> support an adaptive culture or mindset, in which change and uncertainty are assumed to be the natural state-not a false expectation of order </div></li> <li> <div style="MARGIN: 0px"> introduce frameworks to guide the iterative process of managing change </div></li> <li> <div style="MARGIN: 0px"> institute collaboration, the interaction of people on three levels: interpersonal, cultural, and structural </div></li> <li> <div style="MARGIN: 0px"> add rigor and discipline to the RAD approach, making it scalable to the uncertainty and complexity of real-life undertakings </div></li> </ul> </div> <p style="margin:0px;"> </p>
ENGLISH

Best Practices For The Formal Software Testing Process - A Menu Of Testing Tasks

by Rodger Drabick

10,48€ + 10% CARD

 This is the digital version of the printed book (Copyright © 2004). <br> <br>Testing is not a phase. Software developers should not simply throw software over the wall to test engineers when the developers have finished coding. A coordinated program of peer reviews and testing not only supplements a good software development process, it supports it. <p style="margin:0px;"> </p> <p style="margin:0px;">A good testing life cycle begins during the requirements elucidation phase of software development, and concludes when the product is ready to install or ship following a successful system test.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Nevertheless, there is no one true way to test software; the best one can hope for is to possess a formal testing process that fits the needs of the testers as well as those of the organization and its customers.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">A formal test plan is more than an early step in the software testing process—it''s a vital part of your software development life cycle. This book presents a series of tasks to help you develop a formal testing process model, as well as the inputs and outputs associated with each task. These tasks include:</p> <p style="margin:0px;"> </p> <ul> <li>review of program plans</li> <li>development of the formal test plan</li> <li>creation of test documentation (test design, test cases, test software, and test procedures)</li> <li>acquisition of automated testing tools</li> <li>test execution</li> <li>updating the test documentation</li> <li>tailoring the model for projects of all sizes</li> </ul> <p style="margin:0px;"> </p> <p style="margin:0px;">Whether you are an experienced test engineer looking for ways to improve your testing process, a new test engineer hoping to learn how to perform a good testing process, a newly assigned test manager or team leader who needs to learn more about testing, or a process improvement leader, this book will help you maximize your effectiveness.</p> <p style="margin:0px;"> </p>
ENGLISH

Communication Gaps And How To Close Them

by Naomi Karten

10,48€ + 10% CARD

 <div usercontent"=""> <p style="margin:0px;">This is the digital version of the printed book (Copyright © 2002).</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The success of systems or software development depends on effective communication. But have you ever had trouble articulating a complex concept? Have you ever doubted that someone truly understood you-or that you completely received someone’s message?</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Managers and technical professionals have to communicate effectively in order to understand client requirements, build work-related relationships, meet market demands, and survive time pressures. So often, though, communication breaks down, and nothing gets done (or done well, at least).</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Thankfully, Naomi Karten-author of <i>Managing Expectations</i>-is here to help. Readers learn how to improve the way they handle a wide variety of communication conflicts, from one-on-one squabbles to interdepartmental chaos to misinterpretations between providers and customers.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Drawing on a variety of recognizable experiences and on useful models for understanding personalities, such as the Myers-Briggs Type Indicator and the teachings of family therapist Virginia Satir, Karten provides a series of powerful tools and concepts for resolving communication problems-as well as methods for preventing them in the first place.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Inadequate communications include misunderstood or missed messages, contradictory or mixed messages, and messages that are intentionally sabotaged. As the author notes, these miscommunications "can have a damaging, puzzling, and counterproductive impact on projects and relationships." Karten helps readers identify many of the common factors that can cause communication gaps. For example, </p> <ul> <li> <div style="MARGIN: 0px"> mistaken assumptions of understanding </div></li> <li> <div style="MARGIN: 0px"> lack of follow-up </div></li> <li> <div style="MARGIN: 0px"> unfixed project terminology </div></li> <li> <div style="MARGIN: 0px"> emotional baggage </div></li> <li> <div style="MARGIN: 0px"> personality conflicts </div></li> <li> <div style="MARGIN: 0px"> mismatched communication preferences </div></li> </ul> <p style="margin:0px;">Karten’s witty, conversational tone makes this book easy to read; her real-life stories and examples make it easy to understand; and her use of hilarious cartoons by Mark Tatro brings her lessons to life.</p> <p style="margin:0px;"> </p> <b><i><b>Communication Gaps and How to Close Them</b></i></b> is a must-read for anyone who recognizes that the way he or she communicates in professional encounters, as well as in personal ones, can be improved. With Karten’s useful insights and practical techniques, this book will change not only how you communicate but also how you think about communication. </div> <p style="margin:0px;"> </p>
ENGLISH

Managing Expectations - Working With People Who Want More, Better, Faster, Sooner, Now!

by Naomi Karten

10,48€ + 10% CARD

 This is the digital version of the printed book (Copyright © 1994). <br> <br>People have expectations. Your clients, for example. Sometimes their expectations of you seem unreasonable. But sometimes your expectations of them seem just as unreasonable (in their eyes). <br> <br>The problem is that these mismatched expectations can lead to misunderstandings, frayed nerves, and ruffled feathers. More seriously, they often lead to flawed systems, failed projects, and a drain on resources. <br> <i><br><b>Managing Expectations</b></i> shows how to identify expectations and suggests ways to gain more control of them. In today''s turbulent business world, understanding and meeting your customers'' expectations is indeed a challenge, and it''s not hard to understand why: Expectations affect a range of interactions, including service responsiveness, service capability, product functionality, and project success. <br> <br>Expectations are difficult to control and impossible to turn off. However, by learning to identify and influence what your customers expect, you can dramatically improve the quality, impact, and effectiveness of your services. <br> <br>Contents include sections on communication skills, information gathering, policies and practices, building win-win relationships, as well as a concluding chapter on how to formulate an action plan. <br> <br>A Step-by-Step Guide to Managing Expectations <br> <br>Guard Against Conflicting Messages <br>Use Jargon with Care <br>Identify Communication Preferences <br>Listen Persuasively <br>Help Customers Describe Their Needs <br>Become an Information-Gathering Skeptic <br>Understand Your Customers'' Context <br>Try the Solution On for Size <br>Clarify Perceptions <br>Set Uncertainty-Managing Service Standards <br>When Appropriate, Just Say Whoa <br>Build Win-Win Relationships <br>Formulate an Action Plan <p style="margin:0px;"> </p>
ENGLISH

Process For System Architecture And Requirements Engineering

by Derek Hatley, Imtiaz Pirbhai e Peter Hruschka

23,84€ + 10% CARD

 <p style="margin:0px;"> This is the digital version of the printed book (Copyright © 2000).</p> <p style="margin:0px;"><br></p> <div usercontent"=""> Derek Hatley and Imtiaz Pirbhai—authors of <i>Strategies for Real-Time System Specification</i>—join with influential consultant Peter Hruschka to present a much anticipated update to their widely implemented Hatley/Pirbhai methods. <br> <br> <i><b>Process for System Architecture and Requirements Engineering</b></i> introduces a new approach that is particularly useful for multidisciplinary system development: It applies equally well to all technologies and thereby provides a common language for developers in widely differing disciplines. <br> <br>The Hatley-Pirbhai-Hruschka approach (H/H/P) has another important feature: the coexistence of the requirements and architecture methods and of the corresponding models they produce. These two models are kept separate, but the approach fully records their ongoing and changing interrelationships. This feature is missing from virtually all other system and software development methods and from CASE tools that only automate the requirements model. <br> <br>System managers, system architects, system engineers, and managers and engineers in all of the diverse engineering technologies will benefit from this comprehensive, pragmatic text. In addition to its models of requirements and architecture and of the development process itself, the book uses in-depth case studies of a hospital monitoring system and of a multidisciplinary groundwater analysis system to illustrate the principles. <br> <br>Compatibility Between the H/H/P Methods and the UML: <br> <br>The Hatley/Pirbhai architecture and requirements methods—described in <i>Strategies for Real-Time System Specification</i>—have been widely used for almost two decades in system and software development. Now known as the Hatley/Hruschka/Pirbhai (H/H/P) methods, they have always been compatible with object-oriented software techniques, such as the UML, by defining architectural elements as classes, objects, messages, inheritance relationships, and so on. In <i><b> Process for System Architecture and Requirements Engineering,</b></i> that compatibility is made more specific through the addition of message diagrams, inheritance diagrams, and new notations that go with them. In addition, state charts, while never excluded, are now specifically included as a representation of sequential machines. <br> <br>These additions make definition of the system/software boundary even more straightforward, while retaining the clear separation of requirements and design at the system levels that is a hallmark of the H/H/P methods—not shared by most OO techniques. Once the transition to software is made, the developer is free to continue using the H/H/P methods, or to use the UML or any other software-specific technique. </div>
ENGLISH

Practical Guide To Business Process Reengineering Using Idefo, The

by Clarence Feldmann

10,48€ + 10% CARD

 This is the digital version of the printed book (Copyright © 1998). <br> <br> <p style="margin:0px;">This book answers the call for a concise, comprehensive introduction to IDEF0 and its application in business process reengineering (BPR) efforts.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Here is all the essential information about the IDEF0 method, the function analysis portion of the Integration Definition (IDEF) Methods—its definition, basic rules of usage (including the standard language syntax and semantics as contained in the Federal Standard), and lessons learned from many years of application in the real world.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The book features examples based on actual models of commercial clients and government agencies. By studying IDEF0 models, readers learn how the method might be applied to the various aspects of enterprise analysis or systems analysis and what goals and benefits are reasonable to expect from its application.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">IDEF0 is at the heart of the DoD''s version of BPR. In the private sector, industrial organizations that may have initially discovered IDEF through one or more government contracts have adopted it as a method for use with their own corporate BPR efforts.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Use this book to apply the techniques of this increasingly popular member of the IDEF family of methods!</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Three Major Elements of the Method:</p> <p style="margin:0px;"> </p> <p style="margin:0px;">1. The concepts are at the foundation of IDEF0, and they preserve the logical sense and intention of the model. These concepts answer why one approach is used over another in the application of IDEF0, and they provide the experienced analyst with the rationale for when it may be necessary to bend the rules. </p> <p style="margin:0px;"> </p> <p style="margin:0px;">2. The language of IDEF0 is the analyst''s means of describing the activities of an enterprise to other analysts, readers, enterprise management and staff, and others. The language is written in graphical box-and-arrow notation on diagram forms that are structured to form IDEF0 models. </p> <p style="margin:0px;"> </p> <p style="margin:0px;">3. The pragmatics of IDEF0 provide the engineering procedures and the do''s and don''ts for the use of IDEF0. In many cases, the pragmatics are so closely tied to the concepts and language that they are inseparable, and analysts who have attempted to use IDEF0 without employing the pragmatics have typically been unsuccessful. The most common misuses of IDEF0 are illustrated to show the kinds of problems that can occur if the pragmatics are not followed.</p> <p style="margin:0px;"> </p>
ENGLISH

Complete Systems Analysis - The Workbook, The Textbook, The Answers

by James Robertson e Suzanne Robertson

23,84€ + 10% CARD

 <div usercontent"=""> <p style="margin:0px;">This is the digital version of the printed book (Copyright © 1998, 1994).</p> <p style="margin:0px;"> </p> <p style="margin:0px;">In a fundamentally new approach, <i><b><i>Complete Systems Analysis </i></b></i>teaches everything you need to know about analyzing systems: the methods, the models, the techniques, and more.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">A definitive text on modern systems analysis techniques is combined with an extensive case study to give readers hands-on experience in completing an actual analysis project.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Readers proceed through each step of a full-scale analysis project, analyzing the complex requirements of a television station’s airtime programming department. Each phase of the case study and each exercise in the textbook section is thoroughly explained in separate review and answer sections.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">An innovative Trail Guide system-inspired by the difficulty levels marked on ski trails-encourages readers to follow a sequence that suits their skill level. Beginners follow the full trail while experienced analysts fill in gaps in their training, refresh their understanding of key concepts, and practice their skills. Managers review key concepts but can skip the detailed work with models.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The book shows how analysis is used for object-oriented implementation, and how event-response data flow models and entity-relationship data models are complementary, not competing, models.</p> <p style="margin:0px;"> </p> <p style="margin:0px;"><i><b><i>Complete Systems Analysis </i></b></i>adapts to the reader’s needs and provides an appropriate learning path for the beginner, with a more direct route for experienced analysts wanting to make better use of today’s techniques. Since its initial publication in 1994 as a two-volume set in hardcover, this highly acclaimed text-released in 1998 as a single, softcover volume-has served as a course text in classes throughout the world. </p> <p style="margin:0px;"> </p> <p style="margin:0px;">Topics include</p> <ul> <li> <div style="MARGIN: 0px"> Analysis Models </div></li> <li> <div style="MARGIN: 0px"> Data Flow Diagrams </div></li> <li> <div style="MARGIN: 0px"> Data Viewpoint </div></li> <li> <div style="MARGIN: 0px"> Data Models </div></li> <li> <div style="MARGIN: 0px"> Leveled Data Flow Diagrams </div></li> <li> <div style="MARGIN: 0px"> Current Physical Viewpoint </div></li> <li> <div style="MARGIN: 0px"> Building the Data Dictionary </div></li> <li> <div style="MARGIN: 0px"> Strategy: Focusing on the Essentials </div></li> <li> <div style="MARGIN: 0px"> Identifying Events </div></li> <li> <div style="MARGIN: 0px"> Modeling an Event Response </div></li> <li> <div style="MARGIN: 0px"> Writing Mini Specifications </div></li> <li> <div style="MARGIN: 0px"> CRUD Check </div></li> <li> <div style="MARGIN: 0px"> Modeling New Requirements </div></li> <li> <div style="MARGIN: 0px"> New Physical Viewpoint </div></li> <li> <div style="MARGIN: 0px"> Object-Oriented Viewpoint </div></li> <li> <div style="MARGIN: 0px"> Strategy: Toward Implementation </div></li> </ul> </div> <p style="margin:0px;"> </p>
ENGLISH

Adrenaline Junkies And Template Zombies - Understanding Patterns Of Project Behavior

by James Robertson, Peter Hruschka, Steve Mcmenamin, Suzanne Robertson, Tim Lister e Tom DeMarco

7,94€ + 10% CARD

 <div usercontent"=""> <p style="margin:0px;">This is the digital version of the printed book (Copyright © 2008).</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Adrenaline junkies, dead fish, project sluts, true believers, Lewis and Clark, template zombies . . .</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Most developers, testers, and managers on IT projects are pretty good at recognizing patterns of behavior and gut-level hunches, as in, "I sense that this project is headed for disaster."</p> <p style="margin:0px;"> </p> <p style="margin:0px;">But it has always been more difficult to transform these patterns and hunches into a usable form, something a team can debate, refine, and use. Until now.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">In <b><i><b>Adrenaline Junkies and Template Zombies,</b></i></b> the six principal consultants of The Atlantic Systems Guild present the patterns of behavior they most often observe at the dozens of IT firms they transform each year, around the world.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The result is a quick-read guide to identifying nearly ninety typical scenarios, drawing on a combined one-hundred-and-fifty years of project management experience. Project by project, you’ll improve the accuracy of your hunches and your ability to act on them.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The patterns are presented in an easy-reference format, with names designed to ease communication with your teammates. In just a few words, you can describe what’s happening on your project. Citing the patterns of behavior can help you quickly move those above and below you to the next step on your project. You’ll find classic patterns such as these: </p> <ul> <li> <div style="MARGIN: 0px"> News Improvement </div></li> <li> <div style="MARGIN: 0px"> Management by Mood Ring </div></li> <li> <div style="MARGIN: 0px"> Piling On </div></li> <li> <div style="MARGIN: 0px"> Rattle Yer Dags </div></li> <li> <div style="MARGIN: 0px"> Natural Authority </div></li> <li> <div style="MARGIN: 0px"> Food++ </div></li> <li> <div style="MARGIN: 0px"> Fridge Door </div></li> <li> <div style="MARGIN: 0px"> <i>and more than eighty more!</i> </div></li> </ul> <p style="margin:0px;">Not every pattern will be evident in your organization, and not every pattern is necessarily good or bad. However, you’ll find many patterns that will apply to your current and future assignments, even in the most ambiguous circumstances. When you assess your situation and follow your next hunch, you''ll have the collective wisdom of six world-class consultants at your side.</p> </div> <p style="margin:0px;"> </p>
ENGLISH

Waltzing With Bears - Managing Risk On Software Projects

by Tim Lister e Tom DeMarco

23,84€ + 10% CARD

 This is the digital version of the printed book (Copyright © 2003). <b><br><br>If There’s No Risk On Your Next Project, Don’t Do It.</b> <p style="margin:0px;"> </p> <p style="margin:0px;">Greater risk brings greater reward, especially in software development. A company that runs away from risk will soon find itself lagging behind its more adventurous competition. By ignoring the threat of negative outcomes-in the name of positive thinking or a can-do attitude-software managers drive their organizations into the ground.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">In Waltzing with Bears, Tom DeMarco and Timothy Lister-the best-selling authors of Peopleware-show readers how to identify and embrace worthwhile risks. Developers are then set free to push the limits. </p> <p style="margin:0px;"> </p> <p style="margin:0px;">The authors present the benefits of risk management, including that it makes aggressive risk-taking possible, protects management from getting blindsided, provides minimum-cost downside protection, reveals invisible transfers of responsibility, isolates the failure of a subproject.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Readers are armed with strategies for confronting the most common risks that software projects face: schedule flaws, requirements inflation, turnover, specification breakdown, and under-performance.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Waltzing with Bears will help you mitigate the risks-before they turn into project-killing problems. Risks are out there-and they should be there-but there is a way to manage them.</p> <p style="margin:0px;"> </p>
ENGLISH

Adaptive Software Development - A Collaborative Approach To Managing Complex Systems

by Jim Highsmith

7,94€ + 10% CARD

 <div usercontent"=""> <p style="margin:0px;">This is the digital version of the printed book (Copyright © 2000).</p> <p style="margin:0px;"> </p> <i> <p style="margin:0px;">Winner of the 2001 Software Development Jolt Product Excellence Award</p> </i> <p style="margin:0px;"> </p> <p style="margin:0px;">This innovative text offers a practical, realistic approach to managing high-speed, high-change software development projects. Consultant James A. Highsmith shows readers how to increase collaboration and adapt to uncertainty.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Many organizations start high-speed, high-change projects without knowing how to do them-and even worse, without knowing they don’t know. Successful completion of these projects is often at the expense of the project team.</p> <p style="margin:0px;"> </p> <p style="margin:0px;"><b><i><b>Adaptive Software Development</b></i></b> emphasizes an adaptive, collaborative approach to software development. The concepts allow developers to "scale-up" rapid application development and extreme programming approaches for use on larger, more complex projects.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The four goals of the book are to </p> <ul> <li> <div style="MARGIN: 0px"> support an adaptive culture or mindset, in which change and uncertainty are assumed to be the natural state-not a false expectation of order </div></li> <li> <div style="MARGIN: 0px"> introduce frameworks to guide the iterative process of managing change </div></li> <li> <div style="MARGIN: 0px"> institute collaboration, the interaction of people on three levels: interpersonal, cultural, and structural </div></li> <li> <div style="MARGIN: 0px"> add rigor and discipline to the RAD approach, making it scalable to the uncertainty and complexity of real-life undertakings </div></li> </ul> </div> <p style="margin:0px;"> </p>
ENGLISH

Best Practices For The Formal Software Testing Process - A Menu Of Testing Tasks

by Rodger Drabick

7,94€ + 10% CARD

 This is the digital version of the printed book (Copyright © 2004). <br> <br>Testing is not a phase. Software developers should not simply throw software over the wall to test engineers when the developers have finished coding. A coordinated program of peer reviews and testing not only supplements a good software development process, it supports it. <p style="margin:0px;"> </p> <p style="margin:0px;">A good testing life cycle begins during the requirements elucidation phase of software development, and concludes when the product is ready to install or ship following a successful system test.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Nevertheless, there is no one true way to test software; the best one can hope for is to possess a formal testing process that fits the needs of the testers as well as those of the organization and its customers.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">A formal test plan is more than an early step in the software testing process—it''s a vital part of your software development life cycle. This book presents a series of tasks to help you develop a formal testing process model, as well as the inputs and outputs associated with each task. These tasks include:</p> <p style="margin:0px;"> </p> <ul> <li>review of program plans</li> <li>development of the formal test plan</li> <li>creation of test documentation (test design, test cases, test software, and test procedures)</li> <li>acquisition of automated testing tools</li> <li>test execution</li> <li>updating the test documentation</li> <li>tailoring the model for projects of all sizes</li> </ul> <p style="margin:0px;"> </p> <p style="margin:0px;">Whether you are an experienced test engineer looking for ways to improve your testing process, a new test engineer hoping to learn how to perform a good testing process, a newly assigned test manager or team leader who needs to learn more about testing, or a process improvement leader, this book will help you maximize your effectiveness.</p> <p style="margin:0px;"> </p>
ENGLISH

Creating A Software Engineering Culture

by Karl Wiegers

23,84€ + 10% CARD

 <div usercontent"=""> <p style="margin:0px;">This is the digital version of the printed book (Copyright © 1996).</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Written in a remarkably clear style, <b><i><b>Creating a Software Engineering Culture </b></i></b>presents a comprehensive approach to improving the quality and effectiveness of the software development process.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">In twenty chapters spread over six parts, Wiegers promotes the tactical changes required to support process improvement and high-quality software development. Throughout the text, Wiegers identifies scores of culture builders and culture killers, and he offers a wealth of references to resources for the software engineer, including seminars, conferences, publications, videos, and on-line information.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">With case studies on process improvement and software metrics programs and an entire part on action planning (called "What to Do on Monday"), this practical book guides the reader in applying the concepts to real life.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Topics include software culture concepts, team behaviors, the five dimensions of a software project, recognizing achievements, optimizing customer involvement, the project champion model, tools for sharing the vision, requirements traceability matrices, the capability maturity model, action planning, testing, inspections, metrics-based project estimation, the cost of quality, and much more!</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Principles from Part 1</p> <ul> <li> <div style="MARGIN: 0px"> Never let your boss or your customer talk you into doing a bad job. </div></li> <li> <div style="MARGIN: 0px"> People need to feel the work they do is appreciated. </div></li> <li> <div style="MARGIN: 0px"> Ongoing education is every team member’s responsibility. </div></li> <li> <div style="MARGIN: 0px"> Customer involvement is the most critical factor in software quality. </div></li> <li> <div style="MARGIN: 0px"> Your greatest challenge is sharing the vision of the final product with the customer. </div></li> <li> <div style="MARGIN: 0px"> Continual improvement of your software development process is both possible and essential. </div></li> <li> <div style="MARGIN: 0px"> Written software development procedures can help build a shared culture of best practices. </div></li> <li> <div style="MARGIN: 0px"> Quality is the top priority; long-term productivity is a natural consequence of high quality. </div></li> <li> <div style="MARGIN: 0px"> Strive to have a peer, rather than a customer, find a defect. </div></li> <li> <div style="MARGIN: 0px"> A key to software quality is to iterate many times on all development steps except coding: Do this once. </div></li> <li> <div style="MARGIN: 0px"> Managing bug reports and change requests is essential to controlling quality and maintenance. </div></li> <li> <div style="MARGIN: 0px"> If you measure what you do, you can learn to do it better. </div></li> <li> <div style="MARGIN: 0px"> You can’t change everything at once. Identify those changes that will yield the greatest benefits, and begin to implement them next Monday. </div></li> <li> <div style="MARGIN: 0px"> Do what makes sense; don’t resort to dogma. </div></li> </ul> </div> <p style="margin:0px;"> </p>
ENGLISH

Surviving The Top Ten Challenges Of Software Testing - A People-Oriented Approach

by Randall Rice e William Perry

7,94€ + 10% CARD

 <div usercontent"=""> This is the digital version of hte printed book (Copyright © 1997). <br> <br>Software testers require technical and political skills to survive what can often be a lose-lose relationship with developers and managers. <br> <br>Whether testing is your specialty or your stepping stone to a career as a developer, there''s no better way to survive the pressures put on testers than to meet the ten challenges described in this practical handbook. <br> <br>This book goes beyond the technical skills required for effective testing to address the political realities that can''t be solved by technical knowledge alone. Communication and negotiation skills must be in every tester''s tool kit. <br> <br>Authors Perry and Rice compile a "top ten" list of the challenges faced by testers and offer tactics for success. They combine their years of experience in developing testing processes, writing books and newsletters on testing, and teaching seminars on how to test. <br> <br>The challenges are addressed in light of the way testing fits into the context of software development and how testers can maximize their relationships with managers, developers, and customers. <br> <br> <br>In fact, anyone who works with software testers should read this book for insight into the unique pressures put on this part of the software development process. <br> <br>"Somewhere between the agony of rushed deadlines and the luxury of all the time in the world has got to be a reasonable approach to testing."—from Chapter 8 <br> <br>The Top Ten People Challenges Facing Testers <br> <br>Challenge #10: Getting Trained in Testing <br>Challenge #9: Building Relationships with Developers <br>Challenge #8: Testing Without Tools <br>Challenge #7: Explaining Testing to Managers <br>Challenge #6: Communicating with Customers—And Users <br>Challenge #5: Making Time for Testing <br>Challenge #4: Testing What''s Thrown Over the Wall <br>Challenge #3: Hitting a Moving Target <br>Challenge #2: Fighting a Lose-Lose Situation <br>Challenge #1: Having to Say No </div> <p style="margin:0px;"> </p>
ENGLISH

Iteam - Putting The ''I'' Back Into Team

by William Perry

23,84€ + 10% CARD

 This is the digital version of the printed book (Copyright © 2009). <br> <br>It will surprise few professionals working in software development today to read that teams and teamwork are critical ingredients of a global economy. Productivity, product development and release, and even a company''s survival increasingly will depend on teams to solve business problems. What may come as a surprise -- and a wake-up call -- is that, in many businesses, teams are completely ineffective. <br> <br>One reason, posits William E. Perry in <i><b> iTeam: Putting the "I" Back into Team</b></i>, is that most organizations put too much emphasis on joint effort, removing responsibility, ownership, and reward from individuals appointed to teams. What typically results is dysfunctional, essentially leaderless, and lacking in motivation. <br> <br>Perry''s call to put the emphasis back on individual responsibility among collaborating teammates is an urgent one. Decisions now made by management will more and more frequently be made and implemented by teams, making it necessary for organizations to ensure that the creativity and innovative methods of individuals be retained on teams. <br> <br>Through extensive team experience and interviews with hundreds of individuals who have spent thousands of hours in team meetings, Perry has identified the attributes of great teams and great teamwork. <i><b> iTeam</b></i> examines the ten biggest challenges standing between most teams and excellence and explores in depth the fifty best practices teams can employ to improve performance. <br> <br>Concluding that world-class teams comprise individuals who do what is right for their organization, and do what is right the right way, <i><b>iTeam</b> </i>presents a clear, practical argument for building teams that have at their core a strong, proven leader who encourages and motivates team members to fulfill their team responsibilities. <br> <br>Topics include: <br> <br>Reengineering the Team Approach to Problem Solving <br>The Top-Ten Challenges to Effective Teamwork <br>Selecting a Team Leader Who Will Lead <br>Defining Team Entrance and Exit Criteria <br>Selecting Team Members for Specific Roles <br>Building Trust Among Team Members <br>Training Team Members to Accomplish Their Assignments <br>Listening to the Voice of the Customer <br>Breaking Down Silos <br>Avoiding Groupthink <br>Assuring That Team Efforts Are Successful <br>Rewarding Individual Team Members <br>Keeping Teamwork Competitive <br>Emerging Team Practices <br>and much more <p style="margin:0px;"> </p>
ENGLISH

Communication Gaps And How To Close Them

by Naomi Karten

7,94€ + 10% CARD

 <div usercontent"=""> <p style="margin:0px;">This is the digital version of the printed book (Copyright © 2002).</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The success of systems or software development depends on effective communication. But have you ever had trouble articulating a complex concept? Have you ever doubted that someone truly understood you-or that you completely received someone’s message?</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Managers and technical professionals have to communicate effectively in order to understand client requirements, build work-related relationships, meet market demands, and survive time pressures. So often, though, communication breaks down, and nothing gets done (or done well, at least).</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Thankfully, Naomi Karten-author of <i>Managing Expectations</i>-is here to help. Readers learn how to improve the way they handle a wide variety of communication conflicts, from one-on-one squabbles to interdepartmental chaos to misinterpretations between providers and customers.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Drawing on a variety of recognizable experiences and on useful models for understanding personalities, such as the Myers-Briggs Type Indicator and the teachings of family therapist Virginia Satir, Karten provides a series of powerful tools and concepts for resolving communication problems-as well as methods for preventing them in the first place.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Inadequate communications include misunderstood or missed messages, contradictory or mixed messages, and messages that are intentionally sabotaged. As the author notes, these miscommunications "can have a damaging, puzzling, and counterproductive impact on projects and relationships." Karten helps readers identify many of the common factors that can cause communication gaps. For example, </p> <ul> <li> <div style="MARGIN: 0px"> mistaken assumptions of understanding </div></li> <li> <div style="MARGIN: 0px"> lack of follow-up </div></li> <li> <div style="MARGIN: 0px"> unfixed project terminology </div></li> <li> <div style="MARGIN: 0px"> emotional baggage </div></li> <li> <div style="MARGIN: 0px"> personality conflicts </div></li> <li> <div style="MARGIN: 0px"> mismatched communication preferences </div></li> </ul> <p style="margin:0px;">Karten’s witty, conversational tone makes this book easy to read; her real-life stories and examples make it easy to understand; and her use of hilarious cartoons by Mark Tatro brings her lessons to life.</p> <p style="margin:0px;"> </p> <b><i><b>Communication Gaps and How to Close Them</b></i></b> is a must-read for anyone who recognizes that the way he or she communicates in professional encounters, as well as in personal ones, can be improved. With Karten’s useful insights and practical techniques, this book will change not only how you communicate but also how you think about communication. </div> <p style="margin:0px;"> </p>
ENGLISH

Managing Expectations - Working With People Who Want More, Better, Faster, Sooner, Now!

by Naomi Karten

7,94€ + 10% CARD

 This is the digital version of the printed book (Copyright © 1994). <br> <br>People have expectations. Your clients, for example. Sometimes their expectations of you seem unreasonable. But sometimes your expectations of them seem just as unreasonable (in their eyes). <br> <br>The problem is that these mismatched expectations can lead to misunderstandings, frayed nerves, and ruffled feathers. More seriously, they often lead to flawed systems, failed projects, and a drain on resources. <br> <i><br><b>Managing Expectations</b></i> shows how to identify expectations and suggests ways to gain more control of them. In today''s turbulent business world, understanding and meeting your customers'' expectations is indeed a challenge, and it''s not hard to understand why: Expectations affect a range of interactions, including service responsiveness, service capability, product functionality, and project success. <br> <br>Expectations are difficult to control and impossible to turn off. However, by learning to identify and influence what your customers expect, you can dramatically improve the quality, impact, and effectiveness of your services. <br> <br>Contents include sections on communication skills, information gathering, policies and practices, building win-win relationships, as well as a concluding chapter on how to formulate an action plan. <br> <br>A Step-by-Step Guide to Managing Expectations <br> <br>Guard Against Conflicting Messages <br>Use Jargon with Care <br>Identify Communication Preferences <br>Listen Persuasively <br>Help Customers Describe Their Needs <br>Become an Information-Gathering Skeptic <br>Understand Your Customers'' Context <br>Try the Solution On for Size <br>Clarify Perceptions <br>Set Uncertainty-Managing Service Standards <br>When Appropriate, Just Say Whoa <br>Build Win-Win Relationships <br>Formulate an Action Plan <p style="margin:0px;"> </p>
ENGLISH

Process For System Architecture And Requirements Engineering

by Derek Hatley, Imtiaz Pirbhai e Peter Hruschka

23,84€ + 10% CARD

 <p style="margin:0px;"> This is the digital version of the printed book (Copyright © 2000).</p> <p style="margin:0px;"><br></p> <div usercontent"=""> Derek Hatley and Imtiaz Pirbhai—authors of <i>Strategies for Real-Time System Specification</i>—join with influential consultant Peter Hruschka to present a much anticipated update to their widely implemented Hatley/Pirbhai methods. <br> <br> <i><b>Process for System Architecture and Requirements Engineering</b></i> introduces a new approach that is particularly useful for multidisciplinary system development: It applies equally well to all technologies and thereby provides a common language for developers in widely differing disciplines. <br> <br>The Hatley-Pirbhai-Hruschka approach (H/H/P) has another important feature: the coexistence of the requirements and architecture methods and of the corresponding models they produce. These two models are kept separate, but the approach fully records their ongoing and changing interrelationships. This feature is missing from virtually all other system and software development methods and from CASE tools that only automate the requirements model. <br> <br>System managers, system architects, system engineers, and managers and engineers in all of the diverse engineering technologies will benefit from this comprehensive, pragmatic text. In addition to its models of requirements and architecture and of the development process itself, the book uses in-depth case studies of a hospital monitoring system and of a multidisciplinary groundwater analysis system to illustrate the principles. <br> <br>Compatibility Between the H/H/P Methods and the UML: <br> <br>The Hatley/Pirbhai architecture and requirements methods—described in <i>Strategies for Real-Time System Specification</i>—have been widely used for almost two decades in system and software development. Now known as the Hatley/Hruschka/Pirbhai (H/H/P) methods, they have always been compatible with object-oriented software techniques, such as the UML, by defining architectural elements as classes, objects, messages, inheritance relationships, and so on. In <i><b> Process for System Architecture and Requirements Engineering,</b></i> that compatibility is made more specific through the addition of message diagrams, inheritance diagrams, and new notations that go with them. In addition, state charts, while never excluded, are now specifically included as a representation of sequential machines. <br> <br>These additions make definition of the system/software boundary even more straightforward, while retaining the clear separation of requirements and design at the system levels that is a hallmark of the H/H/P methods—not shared by most OO techniques. Once the transition to software is made, the developer is free to continue using the H/H/P methods, or to use the UML or any other software-specific technique. </div>
ENGLISH

Practical Guide To Business Process Reengineering Using Idefo, The

by Clarence Feldmann

23,84€ + 10% CARD

 This is the digital version of the printed book (Copyright © 1998). <br> <br> <p style="margin:0px;">This book answers the call for a concise, comprehensive introduction to IDEF0 and its application in business process reengineering (BPR) efforts.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Here is all the essential information about the IDEF0 method, the function analysis portion of the Integration Definition (IDEF) Methods—its definition, basic rules of usage (including the standard language syntax and semantics as contained in the Federal Standard), and lessons learned from many years of application in the real world.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">The book features examples based on actual models of commercial clients and government agencies. By studying IDEF0 models, readers learn how the method might be applied to the various aspects of enterprise analysis or systems analysis and what goals and benefits are reasonable to expect from its application.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">IDEF0 is at the heart of the DoD''s version of BPR. In the private sector, industrial organizations that may have initially discovered IDEF through one or more government contracts have adopted it as a method for use with their own corporate BPR efforts.</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Use this book to apply the techniques of this increasingly popular member of the IDEF family of methods!</p> <p style="margin:0px;"> </p> <p style="margin:0px;">Three Major Elements of the Method:</p> <p style="margin:0px;"> </p> <p style="margin:0px;">1. The concepts are at the foundation of IDEF0, and they preserve the logical sense and intention of the model. These concepts answer why one approach is used over another in the application of IDEF0, and they provide the experienced analyst with the rationale for when it may be necessary to bend the rules. </p> <p style="margin:0px;"> </p> <p style="margin:0px;">2. The language of IDEF0 is the analyst''s means of describing the activities of an enterprise to other analysts, readers, enterprise management and staff, and others. The language is written in graphical box-and-arrow notation on diagram forms that are structured to form IDEF0 models. </p> <p style="margin:0px;"> </p> <p style="margin:0px;">3. The pragmatics of IDEF0 provide the engineering procedures and the do''s and don''ts for the use of IDEF0. In many cases, the pragmatics are so closely tied to the concepts and language that they are inseparable, and analysts who have attempted to use IDEF0 without employing the pragmatics have typically been unsuccessful. The most common misuses of IDEF0 are illustrated to show the kinds of problems that can occur if the pragmatics are not followed.</p> <p style="margin:0px;"> </p>

DIDN'T FIND WHAT YOU'RE LOOKING FOR?

Browse by the menu categories.

Check the search criteria in help .

Finally, if needed, use the we'll search for you .