Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Use Case Driven Object Modeling with UML: Theory and Practice shows how to drive an object-oriented software design from use case all the way through coding and testing, based on the minimalist, UML-based ICONIX process. In addition to a comprehensive explanation of the foundations of the approach, the book makes extensive use of examples and provides exercises at the back of each chapter. This book leads by example. It demonstrates common analysis and design errors, shows how to detect and fix them, and suggests how to avoid making the same errors in the future. The book also encourages you to examine its UML examples and to search for specific errors. You'll get clues, then later receive the answers during review sessions toward the end of the book.

UML (Computer science) --- Unified Modeling Language (Computer science) --- Computer software --- Modeling languages (Computer science) --- Object-oriented methods (Computer science) --- Development --- Information Technology --- Software Engineering --- Approche orientee objet (Informatique) --- Cas d'utilisation (Ingenierie des systemes) --- UML (Informatique) --- 681.3*D23 --- 681.3*D2 --- 681.3*D23 Coding: pretty printers; program editors; reentrant code; standards (Softwareengineering) --- Coding: pretty printers; program editors; reentrant code; standards (Softwareengineering) --- 681.3*D2 Software engineering: protection mechanisms; standards--See also {681.3*K63}; {681.3*K51} --- Software engineering: protection mechanisms; standards--See also {681.3*K63}; {681.3*K51} --- Computer science. --- Software engineering. --- Programming Languages, Compilers, Interpreters. --- Software Engineering/Programming and Operating Systems. --- Informatics --- Science --- Computer software engineering --- Engineering --- Programming languages (Electronic computers). --- Computer languages --- Computer program languages --- Computer programming languages --- Machine language --- Electronic data processing --- Languages, Artificial --- 681.3*D32 --- 681.3*D32 language classifications: applicative languages; data-flow languages; design languages; extensible languages; macro and assembly languages; nonprocedural languages; specialized application and very high-level languages (Programminglanguages) --- language classifications: applicative languages; data-flow languages; design languages; extensible languages; macro and assembly languages; nonprocedural languages; specialized application and very high-level languages (Programminglanguages) --- Compilers (Computer programs). --- Compilers and Interpreters. --- Software Engineering. --- Compiling programs (Computer programs) --- Computer programs --- Programming software --- Systems software

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

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.

Software engineering. --- Management information systems. --- Computer science. --- Software Engineering/Programming and Operating Systems. --- Management of Computing and Information Systems. --- Informatics --- Science --- Computer-based information systems --- EIS (Information systems) --- Executive information systems --- MIS (Information systems) --- Sociotechnical systems --- Information resources management --- Management --- Computer software engineering --- Engineering --- Communication systems --- Agile software development. --- Agile development (Computer science) --- Agile methods (Computer science) --- Agile processes (Computer science) --- Computer software --- Development