flazx Feed, books with series: Addison Wesley Object Technology Series http://www.flazx.us/series/76-Addison-Wesley-Object-Technology-Series flazx Feed, books with series: Addison Wesley Object Technology Series en feedback@flazx.us Copyright 2012 Software Development for Small Teams: A RUP-Centric Approach http://www.flazx.us/books/4182-Software-Development-for-Small-Teams-A-RUP-Centric-Approach/ http://www.flazx.us/books/4182-Software-Development-for-Small-Teams-A-RUP-Centric-Approach/ Many people are extreme and agile has long held the Process RationalUnified as antithetical approach to program development, citing it as too process-oriented, too rigid and structured, and overlyconcerned with documentation. While not take extreme or agile community to express their hatred taskfor to process, this book shows that the process caneffectively accommodating approach notusually design and development related to the RUP. ]]> Wed, 30 May 2012 16:25:56 +0700 Managing Software Requirements: A Unified Approach http://www.flazx.us/books/1953-Managing-Software-Requirements-A-Unified-Approach/ http://www.flazx.us/books/1953-Managing-Software-Requirements-A-Unified-Approach/ - Ivar Jacobson

"Many projects fail for the simple reason that the developer failed to build the right thing: They also provide a system that does not meet the expectations of the intended users, or they provide a system that focuses on secondary functions at the expense of primary use - Grady Booch.

Despite the wealth of development knowledge, experience, and tools generally available today, most software projects continue to fail, often because requirements are not determined and defined at the beginning, or is not managed correctly as the project unfolds. By using force, was approached informally, their own war stories, and a comprehensive case study they show how designers and developers can effectively identify requirements by using the power of use cases and more traditional forms of requirements expression. It describes six vital Team Skills for managing requirements throughout the project life cycle: Analyze the Problem, Understanding User Needs, Defining the System, Managing Scope, Refining System Definition, and Building The Right System. Managing Software Requirements specifically addresses the ongoing challenge of managing change and explain the process to ensure that the project scope of work defined and agreed upon by all stakeholders.

Topics covered include:

* The five steps in problem analysis * Business modeling and system engineering * Techniques to bring the needs of clients, users, developers, and stakeholders * Applying and refining use cases * Prototyping * Organizing and managing requirements information * Define project scope and manage customer * Using both informal and technical methods to determine requirements * How to measure and improve the quality of your product requirements * Moving from requirements to implementation * Verifying and validating * Manage system change

The book concludes with a step-by-step to combine powerful techniques into future projects. ]]> Wed, 30 May 2012 16:25:56 +0700 Visual Modeling with Rational Rose 2000 and UML (2nd Edition) http://www.flazx.us/books/528-Visual-Modeling-with-Rational-Rose-2000-and-UML-2nd-Edition/ http://www.flazx.us/books/528-Visual-Modeling-with-Rational-Rose-2000-and-UML-2nd-Edition/ Comprehensive introduction and tutorial with guidance on how to use a tool (Rational Rose 2000) and language (the UML) to successfully visualize, specify, document, and build software systems. DLC: Visual programming (computer science) ]]> Wed, 30 May 2012 16:25:56 +0700 The Unified Modeling Language User Guide http://www.flazx.us/books/255-The-Unified-Modeling-Language-User-Guide/ http://www.flazx.us/books/255-The-Unified-Modeling-Language-User-Guide/ This book opens with a basic tour of the essential concepts and modeling diagrams used in UML, including class diagrams, use case diagrams, modeling and basic principles. This book mixes in a theory of software engineering-small, too, but it uses clear examples and actual UML diagrams to illustrate key concepts.

Later in this book, the author discusses the diagram notation is more difficult (such as state diagrams and activity diagrams, which can be used to model the behavior of the system). With a combination of expert modeling advice and excellent detail on the specifics of UML, this book will truly essential reading for anyone who wants to use UML for real-world software design. ]]> Wed, 30 May 2012 16:25:56 +0700