UML for the IT Business Analyst: A Practical Guide to Object-Oriented Requirements Gathering / Edition 1

Paperback (Print)
Used and New from Other Sellers
Used and New from Other Sellers
from $1.99
Usually ships in 1-2 business days
(Save 96%)
Other sellers (Paperback)
  • All (15) from $1.99   
  • New (3) from $36.98   
  • Used (12) from $1.99   
Sort by
Page 1 of 1
Showing All
Note: Marketplace items are not eligible for any coupons and promotions
Seller since 2008

Feedback rating:



New — never opened or used in original packaging.

Like New — packaging may have been opened. A "Like New" item is suitable to give as a gift.

Very Good — may have minor signs of wear on packaging but item works perfectly and has no damage.

Good — item is in good condition but packaging may have signs of shelf wear/aging or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Acceptable — item is in working order but may show signs of wear such as scratches or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Used — An item that has been opened and may show signs of wear. All specific defects should be noted in the Comments section associated with each item.

Refurbished — A used item that has been renewed or updated and verified to be in proper working condition. Not necessarily completed by the original manufacturer.

Brand New, Perfect Condition, Please allow 4-14 business days for delivery. 100% Money Back Guarantee, Over 1,000,000 customers served.

Ships from: Batavia, IL

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
Seller since 2015

Feedback rating:


Condition: New
Brand new.

Ships from: acton, MA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
Seller since 2008

Feedback rating:


Condition: New

Ships from: Chicago, IL

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
Page 1 of 1
Showing All
Sort by


The IT Business Analyst is one of the fastest growing roles in the IT industry. Business Analysts are found in almost all large organizations and are important members of any IT team whether in the private or public sector. "UML for the IT Business Analyst" provides a clear, step-by-step guide to how the Business Analyst can perform his or her role using state-of-the-art object-oriented technology. Business analysts are required to understand object-oriented technology although there are currently no other books that address their unique needs as non-programmers using this technology. Assuming no prior knowledge of business analysis, IT, or object-orientation, material is presented in a narrative, chronological, hands-on style using a real-world case study. Upon completion of "UML for the IT Business Analyst" the reader will have created an actual business requirements document using all of the techniques of object-orientation required of a Business Analyst. "UML for the IT Business Analyst" puts together all of the technology pieces needed to proficiently perform the Business Analyst role.
Read More Show Less

Product Details

  • ISBN-13: 9781592009121
  • Publisher: Cengage Learning
  • Publication date: 6/7/2005
  • Edition description: Older Edition
  • Edition number: 1
  • Pages: 400
  • Product dimensions: 7.42 (w) x 9.16 (h) x 0.96 (d)

Meet the Author

The author is a sought-after speaker at Business Analysis conference - most recently BA World San Francisco and Vancouver. He plays a leading role in the industry (Business Analysis), as designer of BA training programs for a number of large training institutions (Boston University, TriOS, Humber College, etc.), Subject Matter Expert for the NITAS BA program (co-sponsored by US Dept. of Labor and CompTIA), and reviewer of the profession's standard book of best practices (the BABOK, owned by the International Institute of Business Analysis). Podeswa, through his role as Director for Noble Inc., has provided BA services internationally to a diverse client base, including the Canadian military (MASIS), the U.S. nuclear industry and the insurance and finance sectors.
Read More Show Less

Table of Contents

Introduction Chapter 1: Who Are IT Business Analysts? Chapter 2: The BAs Perspective on Object Orientation Chapter 3: An Overview of Business Object-Oriented Modeling (B.O.O.M.) Chapter 4: Analyzing End-to-End Business Processes Chapter 5: Scoping the IT Project with System Use Cases Chapter 6: Storyboarding the Users Experience Chapter 7: Life Cycle Requirements for Key Business Objects Chapter 8: Gathering Across-the-Board Rules with Class Diagrams Chapter 9: Optimizing Consistency and Reuse in Requirements Documentation Chapter 10: Designing Test Cases and Completing the Project Chapter 11: What Developers Do with Your Requirements Appendix A: The B.O.O.M. Process Appendix B: Business Requirements Document (BRD) Template Appendix C: Business Requirements Document Example: CPP Case Study Appendix D: Decision Table Template Appendix E: Test Script Template Appendix F: Glossary of Symbols Appendix G: Glossary of Terms and Further Reading
Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Reviews
  • Anonymous

    Posted June 10, 2005

    Finally Business and Engineering Can Speak the Same Language

    It's an honor that I can be the first to write a review of Howard's new book 'UML for the IT Business Analyst'. Finally, a book has been written that 'connects the dots' between the buiness community and the software engineering community. Howard has written the book that I wish I had in my library when I was at university and later while first learning to use the UML to perform OO Analysis and Design. The book is extremely well-written and easy to understand. Not only would it make an excellent college textbook for both business and computer science majors, it is a book that every business analyst, project / program and product manager will want to keep close at hand as a desk reference as it is filled with all sorts of real-world examples of applicable 'best practices'. Howard has also managed to bridge the long-standing communication gap between the business and engineering communities. Using the UML to capture, model, and analyze requirements is a stroke of pure genius -- as the UML is a powerful 'translation' tool -- alomost a kind of 'universal translator' that allows the business world to effectively communicate with and be understood by the software engineering world. Howard provides some very helpful templates, as well as special sections early on where he clearly translates some of the more obscure and complex definitions of the UML. These 'What they say:' sections provide the actual textual definitions from the UML 2.0 specification. These are then followed by 'What they mean:' sections where Howard cleverly and clearly explains in simple 'layman's' terms just 'What they say'' REALLY means. I wish he would have included a laminated 'cheat- sheet' containing all of his 'What they mean:' translations on them. I would then copy it and hand it out to the sponsors, every key stakeholder, and every single team member in attendence for each new project 'kick-off' meeting. I would also make sure to give a copy to all project team members (developers, testers, and product support), and all subject matter experts and end-users who will participate in the requirements capture, modeling, and analysis phase of the project. In addition to these most helpful UML definitions, Howard provides an actual case study that allows the reader to literally 'walk-through' every single step of the process for producing a fully developed business requirements document. As a self-study tool or a college text 'UML for the IT Business Analyst' is written in such a way that an entire chapter's content can be 'locked in' memory by simply re-reading and reviewing the 'Chapter Objectives' and 'Chapter Summary' sections. As for the design and formatting of the book -- again Howard demonstrates that he clearly understands design, balance, aesthetics, use of white-space... Every chapter and each individual sub-section is formatted for the highest readability, and each table, chart, diagram or sample artifact, is fully described in meticulous detail. The writing itself is smooth and flowing (which is generally quite challenging to do with books written for both a highly technical engineering audience as well as a much more business focused audience). Finally, the case study is completely believable -- based upon 'real world' experience and not some imaginary set of 'sunny day' scenarios used to explain theoretical principles. Howard has made it possible for the reader to literally use the chapters to set breakpoints and then 'step through' every event that happens during the capture, modeling, and analysis of business requirements leading to a thoroughly 'usable' set of UML-based artifacts. The BRD template alone is worth the investment to buy the book. In over 20 years of working in the computer industry, I have never seen a more thorough example of what should be included in a BRD -- it's that good! I truly thank Howard for writing this book as I belive that it provides much needed information as well as a fully

    1 out of 1 people found this review helpful.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)