UML Xtra-Light: How to Specify your Software Requirements (SIGS: Managing Object Technology, Series Number 23)

Kratochvil, Milan; McGibbon, Barry

ISBN 10: 0521892422 / ISBN 13: 9780521892421

Published by Cambridge University Press, 2002

About this Item

Gently read. May have name of previous ownership, or ex-library edition. Binding tight; spine straight and smooth, with no creasing; covers clean and crisp. Minimal signs of handling or shelving. 100% GUARANTEE! Shipped with delivery confirmation, if you're not satisfied with purchase please return item! Ships USPS Media Mail.

Seller Inventory # OTV.0521892422.VG

Bibliographic Details

• Title: UML Xtra-Light: How to Specify your Software Requirements (SIGS: Managing Object Technology, Series Number 23)
• Publisher: Cambridge University Press
• Publication Date: 2002
• Language: English
• ISBN 10: 0521892422
• ISBN 13: 9780521892421
• Binding: Soft cover
• Condition: very_good

About this title

Synopsis

Business managers often find it impossible to communicate business objectives and specify their software requirements to technical members of staff. This beginner's guide to the Unified Modeling Language (UML) - the standard for documenting software designs - teaches readers to communicate with software developers in a more focused, effective way. It describes the basic diagrams of the UML modeling notation and shows how they are used to specify requirements in an unambiguous way. When applied on a project, the risk of failure through unclear requirements is removed. If you are a non-technical person with a stake in the success of a software project, this book is for you. Milan Kratochvil has worked as an IT-consultant, instructor and writer in methodology for nearly twenty-five years, focusing on areas where IT and business intersect. Barry McGibbon is a principal consultant for Princeton Softech.

Book Description

If you are a non-technical person with a stake in the success of a software project, this book is for you. Business managers often find it impossible to communicate business objectives and specify their software requirements to technical members of staff. This beginner's guide teaches readers to communicate with software developers in a more focused, effective way. It describes the basic diagrams of the UML modeling notation and shows how they are used to specify requirements in a unambiguous way. When used on project, the risk of failure through unclear requirements is removed.