This compact book helps application developers bridge the gap between the theory of the newly created Unified Software Development Process and the practical realities necessary to design and build a software system. The authors present the key ingredients of the Unified Process and demonstrate how the process was conceived to work with UML, emphasizing the application of Use Cases as a primary design tool. The book incorporates a wealth of practical experience showcased by four case studies -- a hospital information system, a video on demand system, a portfolio management system, and a vehicle navigation (IVHS) system.

Use Case Driven Object Modeling with UML: A Practical Approach

Computers & Technology

Rosenberg, Doug

Programming

Addison-Wesley Professional

Applying Use Case Driven Object Modeling with UML: An Annotated e-Commerce Example is a practical, hands-on guide to putting use case methods to work in real-world situations. This workbook is a companion to Use Case Driven Object Modeling with UML. It bridges the gap between the theory presented in the main book and the practical issues involved in the development of an Internet e-commerce application. Uniquely conceived as a workbook and featuring as a running example an e-commerce system for an online bookstore, Applying Use Case Driven Object Modeling with UML examines design in detail, demonstrating the most common design mistakes and the correct design solutions. The hands-on exercises allow you to detect, identify, and correct critical errors on your own, before reviewing the solutions provided in the book. Structured around the proven ICONIX Process, this workbook presents a streamlined approach to UML modeling designed to avoid analysis paralysis without skipping analysis and design. The book presents the four key phases of this minimalist approach to use case driven design--domain modeling, use case modeling, robustness analysis, and sequence diagramming--and for each top

Applying Use Case Driven Object Modeling With Uml: An Annotated E-Commerce Example

Scott, Kendall

Aiming to help developers bridge the gap between theory of Unified Software Development Process and the practical realities necessary to design and build a software system, this text incorporates practical experience and four case studies.

Use Case Driven Object Modeling with UML: ICONIX Process in Theory and Practice (Addison-Wesley Object Technology Series)

Stephens, Matt

Software development can go in many different directions... ICONIX Process has a long track record of helping companies avoid analysis paralysis on a multitude of projects, and is best suited for developing web and GUI-based systems. But what if your project has some other complexities? What if you're modeling business processes, or developing with web services, or designing an embedded hardware/software system? Answer: Use one (or more) of the process roadmaps in this book! This book contains a treasure-trove of tailored roadmaps, proven on demanding real-life projects: Business Process Modeling; Service Oriented Architecture (SOA) web service orchestration with BPMN/BPEL; Embedded hardware/software systems designed with SysML; Design Driven Testing of SysML Models; and Algorithmically complex systems. This book will guide you through these roadmaps, illustrating their use by example. From the author of "Use Case Driven Object Modeling with UML".

Iconix Process Roadmaps: Step-By-Step Guidance for Soa, Embedded, and Algorithm-Intensive Systems

Computer Science

Fingerpress

Here is another ground-breaking book on software development from the team behind Extreme Programming Refactored. Its novel approach of turning test-driven development on its head will attract developers disappointed with the approach of eXtreme programmers.

Design Driven Testing: Test Smarter, Not Harder

Apress

*Describes an agile process that works on large projects 
*Ideal for hurried developers who want to develop software in teams *Incorporates real-life C#/.NET web project; can compare this with cases in book

Agile Development with ICONIX Process: People, Process, and Pragmatism

Business & Money

Collins-Cope, Mark

Management & Leadership

Parallel Agile – faster delivery, fewer defects, lower cost

From the Back Cover From the beginning of software time, people have wondered why it isn’t possible to accelerate software projects by simply adding staff. This is sometimes known as the “nine women can’t make a baby in one month” problem. The most famous treatise declaring this to be impossible is Fred Brooks’ 1975 book The Mythical Man-Month, in which he declares that “adding more programmers to a late software project makes it later,” and indeed this has proven largely true over the decades. Aided by a domain-driven code generator that quickly creates database and API code, Parallel Agile (PA) achieves significant schedule compression using parallelism: as many developers as necessary can independently and concurrently develop the scenarios from initial prototype through production code. Projects can scale by elastic staffing, rather than by stretching schedules for larger development efforts. Schedule compression with a large team of developers working in parallel is analogous to hardware acceleration of compute problems using parallel CPUs.PA has some similarities with and differences from other Agile approaches. Like most Agile methods, PA "gets to code early" and uses feedback from executable software to drive requirements and design. PA uses technical prototyping as a risk-mitigation strategy, to help sanity-check requirements for feasibility, and to evaluate different technical architectures and technologies.Unlike many Agile methods, PA does not support "design by refactoring," and it doesn't drive designs from unit tests. Instead, PA uses a minimalist UML-based design approach (Agile/ICONIX) that starts out with a domain model to facilitate communication across the development team, and partitions the system along use case boundaries, which enables parallel development. Parallel Agile is fully compatible with the Incremental Commitment Spiral Model (ICSM), which involves concurrent effort of a systems engineering team, a development team, and a test team working alongside the developers. The authors have been researching and refining the PA process for several years on multiple test projects that have involved over 200 developers. The book’s example project details the design of one of these test projects, a crowdsourced traffic safety system. Product Description From the beginning of software time, people have wondered why it isn’t possible to accelerate software projects by simply adding staff. This is sometimes known as the “nine women can’t make a baby in one month” problem. The most famous treatise declaring this to be impossible is Fred Brooks’ 1975 book The Mythical Man-Month, in which he declares that “adding more programmers to a late software project makes it later,” and indeed this has proven largely true over the decades. Aided by a domain-driven code generator that quickly creates database and API code, Parallel Agile (PA) achieves significant schedule compression using parallelism: as many developers as necessary can independently and concurrently develop the scenarios from initial prototype through production code. Projects can scale by elastic staffing, rather than by stretching schedules for larger development efforts. Schedule compression with a large team of developers working in parallel is analogous to hardware acceleration of compute problems using parallel CPUs.PA has some similarities with and differences from other Agile approaches. Like most Agile methods, PA "gets to code early" and uses feedback from executable software to drive requirements and design. PA uses technical prototyping as a risk-mitigation strategy, to help sanity-check requirements for feasibility, and to evaluate different technical architectures and technologies.Unlike many Agile methods, PA does not support "design by refactoring," and it doesn't drive designs from unit tests. Instead, PA uses a minimalist UML-based design approach (Agile/ICONIX) that starts out with a domain model to facilitate communicat

Wang, Bo

Boehm, Barry

Suscheck, Charles

Dhalipathi, Shobha Rani

Springer

AI Assisted MBSE with SysML: An Integrated Systems/Software Approach

Weilkiens, Tim

Moberley, Brian

MBSE4U

See the best price to sell, buy, or rent books by Rosenberg, Doug. BookScouter helps to compare book prices from 25+ online bookstores and 30+ buyback vendors with a single search.

Books by Rosenberg, Doug