Software prototyping -- Chapter 2, Effective Prototyping for Software Makers

Software prototyping is a process anyone can learn and master, according to the authors. In "Chapter 2, The Effective Prototyping Process," he describes the four phases of the software prototyping process -- plan, specification, design and results -- and how you can use prototyping to communicate software requirements, designs and ideas.

Book description:
Much as we hate to admit it, most prototyping practice lacks a sophisticated understanding of the broad concepts of prototyping -- and its

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software Quality Book Excerpts Perfect Software, Ch. 8: What Makes a Good Test Seven Steps to Mastering Business Analysis, Ch. 1 Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code? The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering for Secure Software Requirements Management Using IBM Rational RequisitePro: Chapter 1, Requirements Management Implementing ITIL Configuration Management: Chapter 3, Determining Scope, Span and Granularity Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams Inherent Quality Simplicity, Section V: The Evolution Managing the Test People, Chapter 6: Keeping Your Beast Effective Software requirements techniques (Prototyping, Storyboards, Modeling, State transitions) Quality assurance (QA) and testing's role in requirements Agile software development tutorial: Agile requirements gathering Reporter's Notebook: Jack Vaughan on agile methodology Pros and cons of requirements-based software testing How to avoid requirements creep Making requirements walkthroughs more effective (and fun) Software development lifecycle (SDLC) trends 2009: Requirements, agile Using proactive test design methods to catch requirements issues early Is a requirements freeze in a software project a bad idea? Requirements elicitation: Workshops vs. apprentice-style analysis

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary requirements analysis  (SearchSoftwareQuality.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

strategic position within the development process. Often we overwhelm with a high-fidelity prototype that designs us into a corner. Or, we can underwhelm with a prototype with too much ambiguity and flexibility to be of much use in the software development process.

This book will help software makers -- developers, designers, and architects -- build effective software prototypes every time: prototypes that convey enough information about the product at the appropriate time and thus set expectations appropriately.

This practical, informative book will help anyone -- whether or not one has artistic talent, access to special tools or programming ability -- to use good prototyping style, methods and tools to build prototypes and manage for effective prototyping.

>> Read Chapter 2: The Effective Prototyping Process.

>> Buy the book