Sequential Diagram For Library Management System

Almost all software projects are risky. The goal of every project manager is to somehow deal with the cost and schedule uncertainty while meeting your customer's needs. In Object-Oriented Project Management with UML, Murray Cantor describes an elegant, UML-based approach to managing object-oriented projects guaranteed to deliver high-quality software on time and within budget.
Drawing on his experience managing major software projects at IBM and TASC, Cantor supplies you with:
* Proven ways to reap the benefits of using UML tools to tame most project demons and deliver optimal OO systems
* Tips on integrating object-based techniques with traditional methods for project planning, risk management, scheduling, time-phased budgeting, and more
* Expert advice on how to handle all the important 'people' issues that crop up during a development project
* Real-life war stories that let you see firsthand what worked and what didn't on several major development projects
* A full-length project example that walks you through every phase of a project told in terms of problems and solutions
Visit the companion Web site at www.wiley.com/compbooks/cantor to find:
* Sample project schedules, budgets, database templates for managing use cases, and a work-breakdown structure
* A spreadsheet workbook for managing incremental development
* A development tracking diagram
Prior to joining TASC, Dr. Cantor was a development manager at IBM, where he oversaw the development of high-end graphics and multimedia systems.
Filled with real-world advice for managing software projects, Murray Cantor's Object-Oriented Project Management with UML shows you how to tackle any project using UML and the latest thinking on project management. There's little doubt that this even-handed, commonsensical guide can benefit anyone who manages or designs object-oriented software for a living.
The best thing about this book has to be its honest, real-world mix of software engineering theory and real-world practice for managing object-oriented software development. The author refuses to be doctrinaire and continually offers valuable nuggets of practical advice. Regarding the pitfalls of one software development process, he writes, 'I am sure someone has succeeded, but I have never seen it done.' Later, he advises managers to 'never show panic.'
The book doesn't skimp on specifics with a sample case study on a jet fighter trainer simulation system that has a budget of over $22 million. The book also provides real numbers for project estimation, bug tracking, and resource allocation. You'll even find numbers for measuring productivity, including KLOCs. Numerous sample documents (including sample meeting agendas) round out the tour here. The book offers plenty of good advice for working with upper management, customers, and development teams throughout the software development process.
While there's certainly no substitute for actual project management experience, Object-Oriented Project Management with UML may be the next best thing. The author's tour of how to manage object-oriented software development offers dozens of savvy tips and a very thorough guide to using some of the best available techniques for software management. This book is perfect for practically minded IS managers or project leaders who want to see how their software development process can be improved using UML with rigorous management techniques. --Richard Dragan
Topics covered: object-oriented project management overview; obstacles; UML basics; use cases; class diagrams; lifecycle models: waterfall, spiral, RAD; time box model and controlled iteration; Software Development Plans (SDPs); budgeting; project estimation; management tips for inception, elaboration, construction, and transition phases; software metrics: KLOCs and COCOMO; measuring productivity; and sample meeting agendas.

UML Class Diagram - This translates to:
public class Person {
private Title title;
private String firstName;
private String surName;
}
Black Diamond = composition
White Diamon = aggregation

A UML Class diagram for a mini accounting software

Use cases have never been this easy to understand -- or this easy to create! In Writing Effective Use Cases, Alistair Cockburn offers a hands-on, soup-to-nuts guide to use case development, based on the proven concepts he has refined through years of research, development, and seminar presentations. Cockburn begins by answering the most basic questions facing anyone interested in use cases: 'What does a use case look like? When do I write one?' Next, he introduces each key element of use cases: actors, stakeholders, design scope, goal levels, scenarios, and more. Writing Effective Use Cases contains detailed guidelines, formats, and project standards for creating use cases -- as well as a detailed chapter on style, containing specific do's and don'ts. Cockburn shows how use cases fit together with requirements gathering, business processing reengineering, and other key issues facing software professionals. The book includes practice exercises with solutions, as well as a detailed appendix on how to use these techniques with UML. For all application developers, object technology practitioners, software system designers, architects, and analysts.
Alistair Cockburn's Writing Effective Use Cases is an approachable, informative, and very intelligent treatment of an essential topic of software design. 'Use cases' describe how 'actors' interact with computer systems and are essential to software-modeling requirements. For anyone who designs software, this title offers some real insight into writing use cases that are clear and correct and lead to better and less costly software.
The focus of this text is on use cases that are written, as opposed to modeled in UML. This book may change your mind about the advantages of writing step-by-step descriptions of the way users (or actors) interact with systems. Besides being an exceptionally clear writer, the author has plenty to say about what works and what doesn't when it comes to creating use cases. There are several standout bits of expertise on display here, including excellent techniques for finding the right 'scope' for use cases. (The book uses a color scheme in which blue indicates a sea-level use case that's just right, while higher-level use cases are white, and overly detailed ones are indigo. Cockburn also provides notational symbols to document these levels of detail within a design.)
This book contains numerous tips on the writing style for use cases and plenty of practical advice for managing projects that require a large number of use cases. One particular strength lies in the numerous actual use cases (many with impressive detail) that are borrowed from real-world projects, and demonstrate both good and bad practices. Even though the author expresses a preference for the format of use cases, he presents a variety of styles, including UML graphical versions. The explanation of how use cases fit into the rest of the software engineering process is especially good. The book concludes with several dozen concrete tips for writing better use cases.
Software engineering books often get bogged down in theory. Not so in Writing Effective Use Cases, a slender volume with a practical focus, a concise presentation style, and something truly valuable to say. This book will benefit most anyone who designs software for a living. --Richard Dragan
Topics covered: Introduction to use cases
Requirements
Usage narratives
Actors and goals
Stakeholders
Graphical models for use cases
Scope for use cases (enterprise-level through nuts-and-bolts use cases)
Primary and supporting actors
Goal levels: user goals, summary level, and subfunctions
Preconditions, triggers, and guarantees
Main success scenarios
Extensions for describing failures
Formats for use cases (including fully dressed one- and two-column formats)
Use case templates for five common project types
Managing use cases for large projects
CRUD use cases
Business-process modeling
Missing requirements
Moving from use cases to user-interface design
Test cases
eXtreme Programming (XP) and use cases
Sample problem use cases
Tips for writing use cases
Use cases and UML diagrams