UML Xtra-Light: How to Specify your Software Requirements / Edition 1

UML Xtra-Light: How to Specify your Software Requirements / Edition 1

ISBN-10:
0521892422
ISBN-13:
9780521892421
Pub. Date:
11/18/2002
Publisher:
Cambridge University Press
ISBN-10:
0521892422
ISBN-13:
9780521892421
Pub. Date:
11/18/2002
Publisher:
Cambridge University Press
UML Xtra-Light: How to Specify your Software Requirements / Edition 1

UML Xtra-Light: How to Specify your Software Requirements / Edition 1

Paperback

$42.99
Current price is , Original price is $42.99. You
$42.99 
  • SHIP THIS ITEM
    In stock. Ships in 1-2 days.
  • PICK UP IN STORE

    Your local store may have stock of this item.

  • SHIP THIS ITEM

    Temporarily Out of Stock Online

    Please check back later for updated availability.


Overview

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.

Product Details

ISBN-13: 9780521892421
Publisher: Cambridge University Press
Publication date: 11/18/2002
Series: SIGS: Managing Object Technology , #23
Edition description: New Edition
Pages: 126
Product dimensions: 5.98(w) x 9.02(h) x 0.28(d)

Table of Contents

1. Introduction. Software - yet another knowledge industry; 2. Aligning to the business; 3. Adding rigor to the requirements; 4. Sketching the inside structure; 5. Sketching the inside dynamics; 6. Moving towards components; 7. Mapping to data structures; 8. Concluding remarks.
From the B&N Reads Blog

Customer Reviews