Showing posts with label software engineering. Show all posts
Showing posts with label software engineering. Show all posts

Software Testing Techniques, 2nd Edition Review

Software Testing Techniques, 2nd Edition
Average Reviews:

(More customer reviews)
Software Testing Techniques by Boris Beizer is an absolutemust for anyone who has a serious interest in software testing. This 549-page book covers nearly every aspect of the process of finding errors in computer programs, moving from basic definitions and terminology through detailed and easy-to-understand explanations of most testing strategies in use today, finishing with a chapter on implementing testing strategies in a development organization.
This book is written with the practitioner in mind, but can equally well be used by students in software engineering curriculums. It presents both theory and practice in a thorough and clear manner, illustrating both concepts and practical techinqes with numerous realistic examples.
All in all, in this reviewers mind, this is a very good book on software testing, in particular for the active practicioner, but could definitely be used by students of software engineering.

Click Here to see more reviews about: Software Testing Techniques, 2nd Edition



Buy Now

Click here for more information about Software Testing Techniques, 2nd Edition

Read More...

Object-Oriented Software Engineering: Using UML, Patterns and Java (2nd Edition) Review

Object-Oriented Software Engineering: Using UML, Patterns and Java (2nd Edition)
Average Reviews:

(More customer reviews)
Many SE books tell you about SE (eg., Sommerville). Those kinds of books equip you to win in a software engineering version of the trivia game Jeopardy! but will hardly impart any skill and will not make you a better software engineer, only more informed.
In contrast, this book tells you how to do software engineering. They tell you what, Bruegge shows you how. Rather than cover all the concepts in SE, Bruegge picks the most essential ones, gives you a brief but thorough explication of those and then proceeds to teach how they are used.
Professor Bruegge's approach to teaching his SE students is by having his entire class work *together* as one team on *one* real-life project during the term (that's one project for the whole class).
Typically, this project is an upgrade of the previous class's project. Stop and imagine how realistic this approach is -- modifying a system created by engineers who are no longer available for interview, working with as many as 50 different people, working with designs that do not match the code anymore, working with code of varying quality, etc.
Bruegge distills the lessons learned from these practical projects and illustrates practical (not idealistic) approaches to solutions.
Expect German thoroughness and a lucid, unpretentious prose that heeds Strunk and White's dictum: "Omit needless words".
Highly recommended.
-vja

Click Here to see more reviews about: Object-Oriented Software Engineering: Using UML, Patterns and Java (2nd Edition)

For courses in Software Engineering, Software Development, or Object-Oriented Design and Analysis at the Junior/Senior or Graduate level. This text can also be utilized in short technical courses or short, intensive management courses.This textbook shows how to use both the principles of software engineering as well as the practices of various object-oriented tools, processes, and products. Using a step by step case study to illustrate the concepts and topics in each chapter, this book emphasizes practical experience: participants can apply the techniques learned in class by implementing a real-world software project.

Buy Now

Click here for more information about Object-Oriented Software Engineering: Using UML, Patterns and Java (2nd Edition)

Read More...

Software Engineering (6th Edition) Review

Software Engineering (6th Edition)
Average Reviews:

(More customer reviews)
Sommerville gives a keen view of the entire breath of this broad topic. His text is filled with easy to understand illustrations and chapter summaries. The examples are end-to-end because he provides the needed preliminaries (concepts and foundations) to understand the results. His treatment of requirements engineering and formal specification methods is quite good. In addition to the key points (of each chapter) he provides pointers to other resources on each subtopic. I find this text better for use in the classroom than the other leading text (which I use as a reference) because Sommerville's presentation provides a more logical flow and organization (i.e., its easier to read). I used the slides that are available (.ppt) from his web site to supplement my lectures.

Click Here to see more reviews about: Software Engineering (6th Edition)

Software Engineering presents a broad perspective on software systems engineering, concentrating on widely-used techniques for developing large-scale software systems. This best-selling book covers a wide spectrum of software processes from initial requirements elicitation through design and development to system evolution. It supports students taking undergraduate and graduate courses in software engineering. The sixth edition has been restructured and updated, important new topics have been added and obsolete material has been cut. Reuse now focuses on component-based development and patterns; object-oriented design has a process focus and uses the UML; the chapters on requirements have been split to cover the requirements themselves and requirements engineering process; cost estimation has been updated to include the COCOMO 2 model.

Buy Now

Click here for more information about Software Engineering (6th Edition)

Read More...

Object Oriented Programming In C++ Review

Object Oriented Programming In C++
Average Reviews:

(More customer reviews)
This book covers the important aspects of OO approach as well as the STL for C++. It is definitely not suitable for those who have no programming experience in C, and indeed, I find that one actually even needs to have a little knowledge of C++ to benefit from the book. The first two chapters let the C programmer make a transition to C++, and explain clearly on input and output in C++. The next three chapters then strive to explain the OO features in C++.
Generally, the book goes at lengths to illustrate classes in C++ and their workings, and offers many tips and traps as well as certain programming styles and approaches which would produce robust programs. The worked examples were also quite comprehensive. However I feel that the concepts of OO were not well illustrated, and from my experience, a thorough understanding of OO concepts help very much in being able to manipulate classes and using the methods in C++. The chapter on MFC was not very useful, it really looked as if it was just there to fill in space. It does not teach much about MFC.
All in all, however, I would still consider it a fairly good book to keep as a reference.

Click Here to see more reviews about: Object Oriented Programming In C++

A valuable handbook/reference for professionals who need to learn C++ and master its latest updates, this exceptionally organized, #1-rated guide teaches the power and flexibility of the C++ programming language through object-oriented programming applications. Examines the most up-to-date C++ features, including new-style headers, new-style casts, type bool, type string, stringstream classes, namespaces, namespace std., exception handling, run-time type identification, operator new , the template input/output classes, and more. Offers complete coverage on STL (standard template library), including containers, iterators, algorithms, and function objects; the standard input/output library IN DETAIL; and the Microsoft Foundation Classes. Contains an extensive number of well-constructed examples, beautifully fashioned sample applications, interesting and practical programming exercises, boxed figures and vibrant illustrations. A companion web site providesthe book's source code, header files, and data files; sample syllabi; transparencies; and an errata list. For professionals in computer science and related fields.--This text refers to the Paperback edition.

Buy Now

Click here for more information about Object Oriented Programming In C++

Read More...

Agile Software Development Review

Agile Software Development
Average Reviews:

(More customer reviews)
Every fifteen years or so, a great book pops up that describes what
projects are really like. There was Brooks, then DeMarco and Lister,
and now there's Cockburn.
Why is there such a gap between these great books? Possibly because
the message they contain isn't the easy-to-digest dictate: "run your
project this way and everything will be fine." Instead these books all
focus on the fundamentals of projects: people and the way they work
together. These books treat people as people, and not replaceable
parts in a process. The books accept people's foibles and
inconsistencies, and work out how to work with them, rather than how
to try to stamp them out. The books ask: how can we help these funky
people work better together to produce great software?
Agile Software Development has some great answers, which makes it a
significant book. It deals with the issue that programming is
essentially communicating. It looks at the success factors of
individuals, and how to help align the project with these. It
discusses practical ways to reduce the latency of communication (do
you know how much each extra minute taken finding things out costs on
a 12 person project? How do you line your walls with information
radiators?) The book mines the metaphor of development as a
cooperative team game, and looks at development organizations as a
community, where good citizenship pays.
So how _do_ you organize all these people, these team players, these
citizens? The answer is with methodologies. But not with something you
buy off-the-shelf. Cockburn argues that teams should work to define,
and then refine, their own methodologies, bringing in standard ones
where they fit. To help the teams, he has a wonderful section
describing what methodologies _are_, and how to build them. This is
good, solid, practical advice. He talks about when it's good to be
light, and when you need to be heavier, when laissez-faire works, and
when you need ceremony to reduce risks. Then, not content with helping
you create a methodology, Cockburn explains how to adapt what you have
to a changing world.
If you work in or with a team developing software, then you owe it to
yourself (and your team) to read this book. You'll come away with a
far clearer understanding of the dynamic at work in your team, and
with lots of ideas for improving it. And that's the whole point.

Click Here to see more reviews about: Agile Software Development

Lightweight methodologies are exploding in popularity because their flexibility is ideal for today's fast-changing development environments. In Agile Software Development, legendary software expert Alistair Cockburn reviews the advantages and disadvantages of lightweight methods, synthesizing the field's key lessons into a simplified approach that allows developers to focus on building quality software rapidly, cost-effectively, and without burnout. Ideal for managers seeking to transcend yesterday's failed approaches, the agile movement views software development as a cooperative game. As players move throughout the game, they use markers and props to inform, remind, and inspire themselves and each other. The goal of the game: to deliver a working software system -- and to use the lessons of each project to build a new, smarter "game" for the next project. For every IT executive and manager, software developer, team leader, team member, and client concerned with building robust, cost-effective software.

Buy Now

Click here for more information about Agile Software Development

Read More...

Software Engineering: (Update) (8th Edition) Review

Software Engineering: (Update) (8th Edition)
Average Reviews:

(More customer reviews)
I used this book as the text in my software engineering class in the spring semester of 2008. When I was evaluating it for potential adoption, I did not read through it in detail, I looked over the chapter titles and subtitles, read the first few chapters and examined the exercises at the end of the first few chapters. As the semester progressed, I found myself wishing I had read further into the text.
As I moved through the chapters, I found myself mentally noting over and over again that topics are repeated. When the class was over, I asked the students their opinion of the book and they were unanimous, with no prompting from me, in saying that there is a great deal of repetition after the first chapters.
I have no complaint about the quality of exposition or the coverage of software engineering in this book. My reason for not continuing to use it in future classes is solely due to my belief that the size could have been reduced from the current 840 pages to around 600 pages with no real loss of content of flow.


Click Here to see more reviews about: Software Engineering: (Update) (8th Edition)

THE most current Software Engineering text in the market– quality trusted coverage, practical case studies, strong lecturer support.

Buy Now

Click here for more information about Software Engineering: (Update) (8th Edition)

Read More...

Software Requirements Review

Software Requirements
Average Reviews:

(More customer reviews)
Karl Wieger's book is destined to be classic in software requirements. It delivers a large set (over 40) no-nonsense best practices in highly readable, non-nonsense manner. I believe every project manager, IT (Information Technology) and business analyst, and IT account manager should read this book. Further, developers would do well to read it to gain critical insight into the 'big picture' of requirements engineering.
The book is broken down into three sections: the case for requirements engineering best practices ("What and Why"), the requirements discovery, verification and validation process ("Software Requirements Engineering"), and the essentials of requirements management ("Software Requirements Management"). Throughout, the dual necessities of doing requirements right (verification) and doing the right requirements (validation) is addressed. Wiegers has thoroughly delved into the literature in the software requirements field. The text is liberally spiced with tidbits of data to support the business case for implementing these best practices. I found myself making notes in the inside cover and folding back pages to reference again as I read through the book.
Early in the book, Wiegers presents a set of software engineering best practices which are classified into priority (high, medium, low) and difficulty (high, medium, low). Although you may disagree with the specific rankings for your shop, this table is an excellent example of modeling appropriate requirements engineering practices - prioritizing requirements! Other goodies abound. For example, a partial case study flows throughout the book which gives the reader enough of an idea of what a use case, dialog map, text requirement, etc. looks like to get the concept being resented. Each chapter ends with a concise list of suggested next steps, providing the reader with concrete actions to take to implement the practices covered in that chapter. In addition, there are numerous sample templates (e.g. Risk Item Tracking, Software Requirements Specification), several excellent checklists (e.g. Inspection Checklist for Software Requirements Spec, Software Elements Affected by a Proposed Change,), visual models (e.g. Requirements Traceability Links, Change Control Process) and a wonderful "bill of rights" for the software customer which boldly and directly asserts both rights and responsibilities of the customer.
A set of example models is provided in the chapter called "A Picture is Worth 1024 Words". You will need to read other books or take training on the mechanics, notations and semantics of these models for visualized functional requirements. But the author covers the key models and their purpose succinctly.
This book is easy to read, cuts to the chase, and provides a bounty of information that will wet our appetite to take action. This book is not a requirements engineering method or methodology, which would prescribe step-by-step protocols of task, roles, and techniques. Rather, like the classic cookbook The Joy of Cooking, you will find well-proven, sensible, and reusable practices. In Software Requirements, you will find the right ingredients and essential practices needed to 'cook' tasty requirements.

Click Here to see more reviews about: Software Requirements


Without formal, verifiable software requirements-and an effective system for managing them-the programs that developers think they've agreed to build often will not be the same products their customers are expecting. In SOFTWARE REQUIREMENTS, Second Edition, requirements engineering authority Karl Wiegers amplifies the best practices presented in his original award-winning text?now a mainstay for anyone participating in the software development process.

In this book, you'll discover effective techniques for managing the requirements engineering process all the way through the development cycle-including dozens of techniques to facilitate that all-important communication between users, developers, and management. This updated edition features new case examples, anecdotes culled from the author's extensive consulting career, and specific Next Steps for putting the book's process-improvement principles into practice. You'll also find several new chapters, sample documents, and an incisive troubleshooting guide.

Discover how to:

Set achievable expectations for functionality and quality
NEW: Incorporate business rules into application development
Employ use cases to discover user requirements
Arrest creeping requirements and manage change requests
NEW: Deal with requirements on maintenance, outsourced, and package solution projects
Curb the impulse to "gold-plate" your programs
NEW: Grow effective requirements analysts
Cut revisions-and costs-dramatically
Produce better software!

No matter what kind of software you build, or what your role in the development process, SOFTWARE REQUIREMENTS, Second Edition, delivers expert guidance and field-tested techniques for engineering software success.


Buy Now

Click here for more information about Software Requirements

Read More...

Software Architecture: Foundations, Theory, and Practice Review

Software Architecture: Foundations, Theory, and Practice
Average Reviews:

(More customer reviews)
Software Architecture: Foundations, Theory, and Practice is a landmark text that will become an essental introduction to the discipline of software systems architecture. If you are a student, tester, manager, methodologist, developer, or simply an architect, and want a holistic understanding of what real software architects think software architecture is and why it matters, this is the place to start.
I bought this after Roy Fielding (of REST and HTTP fame) mentioned it on the rest-discuss mailing list. Roy is one of the industry's top architects, and I wasn't disappointed. The book is timely - architecture is coming to be accepted as an important activity, especially for distributed, and large scale systems. What many people don't realize is that drawing pictures, writing documents no-one reads, meta-modeling, and pontificating on "concerns" are not software architecture. Software architecture is about introducing constraints via principled, objective design to achieve particular system properties. Architecture is difficult and exhausting work, but done well can offer immense value to users and stakeholders. This book, along with Rozanski and Woods' "Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives" makes that explicit.
The book is unapologetic about software architecture's standing in the industry. SAFTAP positions architecture as the primary design activity for software - not development, not requirements analysis, not testing, not methodology, but architecture. That will make for interesting debate.
My single criticism of this book is that it does not do enough to treat user experience (Ux) and informatics as architecturally significant, but not enough to take away a star. I'm hoping a future edition will rectify that.
Some noteworthy chapters in the book (there are 17 chapters in all):
* The Big Idea: explains what architecture is and why it matters. The building metaphor (often heavily criticised in the industry, see the excellent "Software is not Bricks" by Raganwald) is dealt with calmly and then put to one side.
* Architecture in Context: explains how architecture fits into the overall lifecycle and process of software systems.
* Connectors: this is one of my favourite chapters. The concept of a connector is vital to a software system, but is rarely if ever discussed in programming or engineering texts.
* Modeling: probably not what you think. This chapter emphasizes communication, clarity and disambiguation over notations and diagrams.
* Implementation: programmers hate the quip "implementation detail", but in truth many things in a system are just that and it does not mean they are unimportant. This chapter covers those details and why they matter.
* Deployment and Mobility: good architects understand that a systems have a life well beyond initial delivery, which is where most developers, managers and stakeholders tend to focus attention. This was one of favorite sections as the running system simply doesn't get enough attention in most projects today.
* Applied architecture and Styles: covers some examples of architectural styles, notably REST and SOA, which are certainly the best known architectures in my part of the industry.
* Designing for non-functional properties: many non-functional concerns don't start to matter until the system is deployed and there isn't always agreement among technical specialists over what's truly important. If you are technical specialist this should help you articulate the cost/benefit of looking at the "unfeatures" of a system.
* Security and Trust: software is increasingly distributed, and increasingly a super-system of components interacting over the Internet and Mobile Networks. So it's good to see a text that makes security a first order concern and not just a non-functional ones.
* Domain Specific Software Engineering: I'm trained as an industrial designer where the notion of common modular components with standard interfaces acting as a platform for product development is a known Good Thing in domains such as the automotive and consumer electronics industries. This chapter gives a good overview of modular design focusing on the software product lines approach. The example given is from Philips, but it could as easily have been from Toyota.
* People, Roles and Teams: software architecture, like other architecture disciplines, has a strong social dimension. This chapter explains how the architect role fits into an organisation and where they can add value and exert influence.

Click Here to see more reviews about: Software Architecture: Foundations, Theory, and Practice

Software architecture is foundational to the development of large, practical software-intensive applications. This brand-new text covers all facets of software architecture and how it serves as the intellectual centerpiece of software development and evolution. Critically, this text focuses on supporting creation of real implemented systems. Hence the text details not only modeling techniques, but design, implementation, deployment, and system adaptation -- as well as a host of other topics -- putting the elements in context and comparing and contrasting them with one another. Rather than focusing on one method, notation, tool, or process, this new text/reference widely surveys software architecture techniques, enabling the instructor and practitioner to choose the right tool for the job at hand. Software Architecture is intended for upper-division undergraduate and graduate courses in software architecture, software design, component-based software engineering, and distributed systems; the text may also be used in introductory as well as advanced software engineering courses.

Buy Now

Click here for more information about Software Architecture: Foundations, Theory, and Practice

Read More...

Applied Software Project Management Review

Applied Software Project Management
Average Reviews:

(More customer reviews)
I've tried many project management processes and have searched through most of the popular literature over the years trying to find the best way to implement real process change. Much of the literature describes the processes well but ignores the implementation entirely. Applied Software Project Management does a wonderful job both describing the various tools and techniques and giving detailed instructions on how to implement them. The book even goes so far as to describing how to implement processes in an organization that is openly hostile to change and/or process in general.
I find this book to be an invaluable resource for any project manager. It's great for newbies, who will learn all the vocabulary and process theory. Experienced project managers will learn new tools and techniques as well as innovatives ways of getting them implemented.

Click Here to see more reviews about: Applied Software Project Management


"If you're looking for solid, easy-to-follow advice on estimation, requirements gathering, managing change, and more, you can stop now: this is the book for you." --Scott Berkun, Author ofThe Art of Project Management

What makes software projects succeed? It takes more than a good idea and a team of talented programmers. A project manager needs to know how to guide the team through the entire software project. There are common pitfalls that plague all software projects and rookie mistakes that are made repeatedly--sometimes by the same people! Avoiding these pitfalls is not hard, but it is not necessarily intuitive. Luckily, there are tried and true techniques that can help any project manager.

In Applied Software Project Management, Andrew Stellman and Jennifer Greene provide you with tools, techniques, and practices that you can use on your own projects right away. This book supplies you with the information you need to diagnose your team's situation and presents practical advice to help you achieve your goal of building better software.

Topics include:

Planning a software project
Helping a team estimate its workload
Building a schedule
Gathering software requirements and creating use cases
Improving programming with refactoring, unit testing, and version control
Managing an outsourced project
Testing software

Jennifer Greene and Andrew Stellman have been building software together since 1998. Andrew comes from a programming background and has managed teams of requirements analysts, designers, and developers. Jennifer has a testing background and has managed teams of architects, developers, and testers. She has led multiple large-scale outsourced projects. Between the two of them, they have managed every aspect of software development. They have worked in a wide range of industries, including finance, telecommunications, media, nonprofit, entertainment, natural-language processing, science, and academia. For more information about them and this book, visit http://www.stellman-greene.com.


Buy Now

Click here for more information about Applied Software Project Management

Read More...

The Business Analyst's Handbook Review

The Business Analyst's Handbook
Average Reviews:

(More customer reviews)
This book has solid reference material that experienced Business Analysts can utilize on virtually any assignment. This is not the best book for a new Business Analyst and is really geared towards a practitioner that understands their craft and appreciates additional guidance. Coverage of techniques and models is very comprehensive.

Click Here to see more reviews about: The Business Analyst's Handbook

The Business Analyst (BA) plays an important role as liaison between business stakeholders and the technical team (software developers, vendors, etc.), ensuring that business needs are reflected in any software solution. Despite the importance of the job, there is currently no book specifically designed as a comprehensive reference manual for the working BA. The Business Analyst's Handbook solves this problem by providing a useful compendium of tools, tables, lists, and templates that BAs can use on-the-job to carry out their tasks. For example, you might be preparing for an interview session and use the book's checklist of interviewees to verify whether there is appropriate coverage of business stakeholders. Or you might be asked to review some diagrams and refer to the Glossaries of Symbols (organized by diagram type) for guidance. Or you may be asked to prepare textual requirements documentation and refer to the Business Requirement template for a list of artifacts and table of contents. Whatever your BA needs, the Business Analyst's Handbook places the necessary information right at your fingertips.

Buy Now

Click here for more information about The Business Analyst's Handbook

Read More...

Object-Oriented Software Engineering: Practical Software Development using UML and Java Review

Object-Oriented Software Engineering: Practical Software Development using UML and Java
Average Reviews:

(More customer reviews)
This is an excellent introductory textbook for CS courses on software engineering. It features OO, UML, iterative processes, a good treatment of software frameworks and design patterns, constructive sample projects, and complete set of slides and full-length lecture RealOne video for free downloading. It is a thin book, but it contains more updated information than many classical ones. Most importantly, the authors have the confidence to air their opinions with justification, instead of compiling and citing a lot of inconsistent historical definitions or events.

Click Here to see more reviews about: Object-Oriented Software Engineering: Practical Software Development using UML and Java

This book covers the essential knowledge and skills needed by a student who is specializing in software engineering. Readers will learn principles of object orientation, software development, software modeling, software design, requirements analysis, and testing. The use of the Unified Modelling Language to develop software is taught in depth. Many concepts are illustrated using complete examples, with code written in Java.

Buy Now

Click here for more information about Object-Oriented Software Engineering: Practical Software Development using UML and Java

Read More...

Testing Computer Software, 2nd Edition Review

Testing Computer Software, 2nd Edition
Average Reviews:

(More customer reviews)
Testing Computer Software is one of the those rare books that has taken on the problems of the Verification Engineer. As all of us know, most books written today are targeted for the development audience and even many of these are either poorly written or try to cover too much area. This book however, though broad in its scope, does a good job of treating all of the important areas in verification and testing.
I have found Chapters 2, 3, 7, 11 and 12 to be the most useful and poignant to the average engineer. Not only is each chapter well laid out, but the authors also offer compelling arguments in each chapter to back up their arguments as well. I enjoyed particularly Chapter 3 the section on Path Testing, which conjures up horror stories from my development days. In this section the authors assert that 100% path testing does not imply 100% test coverage. They go on to argue with some rigor why the two are not necessarily the same. Many of you as I can probably claim that though all of the paths in their code were tested, verification was still able to find some condition that would make some part of the code fail. This chapter explains why this may be so and methodologies on how to attack testing those areas.
You will find the book well structured, informative and actually intuitive to navigate through. Each chapter builds on the previous chapters to provide the engineer with a clear idea of all the steps and intricacies involved in testing and verifying complex programs. It can therefore be used by the beginner as a source book for specific test applications, or by the team lead or manager who needs to know more about the actual scope and planning of a complex testing project. This book surely fills a great void in the area of publications software verification.

Click Here to see more reviews about: Testing Computer Software, 2nd Edition



Buy Now

Click here for more information about Testing Computer Software, 2nd Edition

Read More...

IBM Rational Unified Process Reference and Certification Guide: Solution Designer (RUP) Review

IBM Rational Unified Process Reference and Certification Guide: Solution Designer (RUP)
Average Reviews:

(More customer reviews)
This was the only book I used to pass the IBM Certified Solution Developer exam. I did very well on it. (I did do a little research on the internet also.) Prior to reading this book, I had no practical experience with RUP other than knowing its theoretical construct.
The book covers all the areas that you need to know for the exam, although there were a couple of terms that weren't in this book at all. That really surprised me, since this is the official IBM Press book. And I read this book very carefully.
I haven't given this book a higher rating because of 1) its organization and 2) the way it is written. I would recommend reading the first couple of chapters and then the last chapters to understand how RUP works. Then move into the chapters on UMA and the other areas.
The writing often isn't very clear. You have to read everything several times to make sure you really understand what the authors are trying to say. Much of what they write is ambiguous, or at worst, nebulous. The chapters were either written by one of the two authors or co-written, and this results in a jumbled presentation. There are several typos, including in the sample tests, that might lead you to get some answers wrong.
However, if you want to be confident of passing the exam, read this book carefully. I felt the exam matched the level of difficulty of the sample tests in the book. However, in taking the actual exam, I began to wonder whether I had studied the right material at all. While taking the test, for quite a while I wondered whether I was being given the wrong test!


Click Here to see more reviews about: IBM Rational Unified Process Reference and Certification Guide: Solution Designer (RUP)

The Only Official RUP® Certification Prep Guide and Compact RUP Reference The IBM® Rational Unified Process® has become the de facto industry-standard process for large-scale enterprise software development. The IBM Certified Solution Designer - IBM Rational Unified Process V7.0 certification provides a powerful way for solutions developers to demonstrate their proficiency with RUP. The first and only official RUP certification guide, this book fully reflects the latest versions of the Rational Unified Process and of the IBM RUP exam. Authored by two leading RUP implementers, it draws on extensive contributions and careful reviews by the IBM RUP process leader and RUP certification manager. This book covers every facet of RUP usage. It has been carefully organized to help you prepare for your exam quickly and efficiently--and to provide a handy, compact reference you can rely on for years to come. Coverage includes A full section on RUP exam preparation and a 52-question practice examCore RUP concepts, the new RUP process architecture, and key principles of business-driven developmentRUP's architecture-centric approach to iterative development: practical issues and scenariosPatterns for successful RUP project implementation–and "anti-patterns" to avoidThe Unified Method Architecture (UMA): basic content and process elementsRUP content disciplines, in depth: Business Modeling, Requirements, Analysis and Design, Implementation, Test, Deployment, Project Management, Change and Configuration Management, and Environment Essential RUP work products, roles, and tasksRUP phases, activities, and milestonesRUP tailoring and tools for your organization--including introductions to IBM Rational Method Composer (RMC) and MyRUP

Buy Now

Click here for more information about IBM Rational Unified Process Reference and Certification Guide: Solution Designer (RUP)

Read More...