Topic: What are 5 common solutions to software developm..

Message

What are 5 common solutions to software development problems? 

•solid requirements -
clear, complete, detailed, cohesive, attainable, testable requirements
that are agreed to by all players. Use prototypes to help nail down
requirements. 

•realistic schedules - allow
adequate time for planning, design, testing, bug fixing, re-testing,
changes, and documentation; personnel should be able to complete the
project without burning out.

•adequate testing - start testing early on, re-test after fixes or changes, plan for adequate time for testing and bug-fixing. 

•stick to initial requirements as much as possible -
be prepared to defend against changes and additions once development
has begun, and be prepared to explain consequences. If changes are
necessary, they should be adequately reflected in related schedule
changes. If possible, use rapid prototyping during the design phase so
that customers can see what to expect. This will provide them a higher
comfort level with their requirements decisions and minimize changes
later on. 

•communication -
require walkthroughs and inspections when appropriate; make extensive
use of group communication tools - e-mail, groupware, networked
bug-tracking tools and change management tools, intranet capabilities,
etc.; insure that documentation is available and up-to-date -
preferably electronic, not paper; promote teamwork and cooperation; use
protoypes early on so that customers' expectations are clarified.

Edited by tanushree - 16Oct2007 at 5:56am

Author	Message
tanushree Senior Member Joined: 04Apr2007 Online Status: Offline Posts: 2160	Topic: What are 5 common solutions to software developm.. Posted: 16Oct2007 at 5:55am
	What are 5 common solutions to software development problems? •solid requirements - clear, complete, detailed, cohesive, attainable, testable requirements that are agreed to by all players. Use prototypes to help nail down requirements. •realistic schedules - allow adequate time for planning, design, testing, bug fixing, re-testing, changes, and documentation; personnel should be able to complete the project without burning out. •adequate testing - start testing early on, re-test after fixes or changes, plan for adequate time for testing and bug-fixing. •stick to initial requirements as much as possible - be prepared to defend against changes and additions once development has begun, and be prepared to explain consequences. If changes are necessary, they should be adequately reflected in related schedule changes. If possible, use rapid prototyping during the design phase so that customers can see what to expect. This will provide them a higher comfort level with their requirements decisions and minimize changes later on. •communication - require walkthroughs and inspections when appropriate; make extensive use of group communication tools - e-mail, groupware, networked bug-tracking tools and change management tools, intranet capabilities, etc.; insure that documentation is available and up-to-date - preferably electronic, not paper; promote teamwork and cooperation; use protoypes early on so that customers' expectations are clarified. Edited by tanushree - 16Oct2007 at 5:56am Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Types Of Software Testing @ OneStopTesting : Manual Testing @ OneStopTesting