Atjaunināt sīkdatņu piekrišanu

UML Xtra-Light: How to Specify your Software Requirements [Mīkstie vāki]

3.40/5 (10 ratings by Goodreads)
(Princeton Softech), (Kiseldalens Metod AB)
  • Formāts: Paperback / softback, 126 pages, height x width x depth: 229x152x7 mm, weight: 180 g, 30 Line drawings, unspecified
  • Sērija : SIGS: Managing Object Technology
  • Izdošanas datums: 18-Nov-2002
  • Izdevniecība: Cambridge University Press
  • ISBN-10: 0521892422
  • ISBN-13: 9780521892421
Citas grāmatas par šo tēmu:
  • Mīkstie vāki
  • Cena: 46,90 €
  • Grāmatu piegādes laiks ir 3-4 nedēļas, ja grāmata ir uz vietas izdevniecības noliktavā. Ja izdevējam nepieciešams publicēt jaunu tirāžu, grāmatas piegāde var aizkavēties.
  • Daudzums:
  • Ielikt grozā
  • Piegādes laiks - 4-6 nedēļas
  • Pievienot vēlmju sarakstam
  • Formāts: Paperback / softback, 126 pages, height x width x depth: 229x152x7 mm, weight: 180 g, 30 Line drawings, unspecified
  • Sērija : SIGS: Managing Object Technology
  • Izdošanas datums: 18-Nov-2002
  • Izdevniecība: Cambridge University Press
  • ISBN-10: 0521892422
  • ISBN-13: 9780521892421
Citas grāmatas par šo tēmu:
Written to help business managers communicate with the technical members of their staff, this brief guide offers advice on using UML notation to describe business objectives to software developers. It uses an e- business case study to explain the basic diagrams of UML and show how these can be used to specify requirements. Kratochvil and McGibbon are IT consultants. Annotation c. Book News, Inc., Portland, OR (booknews.com)

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.

Perfect for managers with a stake in the success of a software project.

Papildus informācija

This is the perfect book for managers with a stake in the success of a software project.
Foreword ix
Preface xi
Acknowledgments xiii
About the Authors xv
How to Customize This Book xvii
Introduction
1(12)
Software -- Yet Another Knowledge Industry
1(1)
Classifying the Knowledge Industry
2(1)
Consequences of the Knowledge Industry
3(2)
Sharing the Knowledge
5(1)
Sharing the Responsibility for Getting It Right
6(2)
Methods and Processes
8(3)
Summary
11(2)
Aligning to the Business
13(14)
Using UML Activity Diagrams
15(8)
Using Business Use-Case Diagrams
23(2)
But What About the Data?
25(1)
Summary
26(1)
Adding Rigor to the Requirements
27(20)
Use Cases
27(2)
Use-Case Example
29(5)
Meeting the Devil
34(2)
Use-Case Analysis at Two Levels, At Least
36(3)
How to Avoid Messing Up Use Cases
39(7)
Summary
46(1)
Sketching the Inside Structure
47(14)
Class Diagrams
48(2)
The Class Diagram
50(2)
Understanding Class Relationships
52(7)
Summary
59(2)
Sketching the Inside Dynamics
61(12)
State Diagrams
61(6)
Tying It All Together
67(3)
UML Collaboration Diagrams
70(1)
Other UML Diagrams
70(1)
Summary
71(2)
Moving Toward Components
73(16)
Components Communicate with Everyone
76(3)
Impact of the Component-Based Approach
79(2)
Reusing Components
81(2)
Building a Component Library
83(1)
Sharing Components in Your Organization
84(1)
Avoiding the Traps
85(2)
Automating the Bid Process
87(1)
Summary
88(1)
Mapping from Classes to Data Models
89(8)
Use Appropriate Diagrams and Standards
90(1)
Mapping Relationships
91(4)
Summary
95(2)
Concluding Remarks
97(4)
Think Big, Start Small, and Sustain the Effort
97(1)
UML Under Time Constraints
98(3)
Some Suggested Readings 101(2)
Index 103