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)

Computer. Automation --- software engineering

Choose an application

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

This book describes how to apply ICONIX Process (a minimal, use case-driven modeling process) in an agile software project. It's full of practical advice for avoiding common agile pitfalls. Further, the book defines a core agile subset so those of you who want to get agile need not spend years learning to do it. Instead, you can simply read this book and apply the core subset of techniques. The book follows a real-life .NET/C# project from inception and UML modeling, to working code through several iterations. You can then go on-line to compare the finished product with the initial set of use cases. The book also introduces several extensions to the core ICONIX Process, including combining test-driven development (TDD) with up-front design to maximize both approaches (with examples using Java and JUnit). And the book incorporates persona analysis to drive the projects goals and reduce requirements churn.

Computer software --- Development. --- Development of computer software --- Software development --- Information Technology --- Computer Science (Hardware & Networks) --- Java (Computer program language). --- Software engineering. --- Java. --- Software Engineering/Programming and Operating Systems. --- Computer software engineering --- Engineering --- Object-oriented programming languages --- JavaSpaces technology

Choose an application

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

In this chapter we illustrated how to drive unit tests from a software design, identifying test scenarios in a systematic way that ensures the code is covered in all the right places. We also illustrated the use of stunt services  and mock objects to isolate the code being tested; finally, we discussed driving unit tests deeper into algorithmic code that may benefit from finer-grained testing. Is there a way to get 95% of the benefit of the comprehensive unit testing we did in this chapter with significantly fewer tests? In the next chapter, we'll show how to do exactly that with controller tests. As you'll see, unit tests do have their place, but controller tests can often represent a smarter, more structured approach to application testing. 136 C H A P T E R 6 ? ? ? Conceptual Design and Controller Testing As you saw in Chapter 5, unit testing doesn't have to involve exhaustively covering every single line of code, or even every single method, with tests. There's a law of diminishing returns and increasing difficulty as you push the code coverage percentile ever higher. By taking a step back and looking at the design on a broader scale, it's possible to pick out the key areas of code that act as input/output junctures, and focus the tests on those areas.

Programming --- Computer architecture. Operating systems --- Computer. Automation --- computers --- computerbesturingssystemen --- programmeren (informatica) --- programmeertalen --- software engineering

Choose an application

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

Rigor Without the Mortis Many people (especially agilists) associate a high-ceremony software development process with a dead project (i.e., rigor mortis), and this association is not entirely incorrect. Our approach aims to put back the rigor while le- ing out the mortis that is, we can do rigorous analysis and design without killing the project with an excessively high-ceremony approach. The goal of this book is to describe that process in full detail. Agility in theory is about moving ahead at speed, making lots of tiny course corrections as you go. The theory (and it's a good one) is that if you spend months or years producing dry specifications at the start of the project and then set them in concrete,  this doesn't necessarily (and in practice, doesn't) lead to a product that meets the c- tomer's requirements, delivered on time and with an acceptably low defect count. It's likely that the requirements will change over time, so we need to be prepared for that, and it's likely that a lot of the original requirements will turn out to be wrong or new requirements will be discovered after the requi- ments concrete  has set. Agile methods answer this problem in a number of different ways, but the overriding principle is to break things down into smaller chunks and not to go setting anything in concrete (least of all your requirements specs).

Programming --- Agile --- programmeren (informatica)