design question?

Roosevelt Pendill: generally, during the development lifecycle you have several phases that basically translate into:1) Determine the problem you are trying to solve with the customers2) analysts works with customers to document base requirements for what needs to be accomplished3) analysts document the current system (if there is one)4) analysts will compare requirements to current system, and create a technical design document that has a bunch of stuff in it detailing how the new system will work.5) programmers start coding based on design and realize analyst was living in a fairy tale dream world, so they do something totally different than what analyst said to do that will actually work. If it's minor enough, they don't bother telling the analyst. If it is major, they only sometimes bother telling the analyst, because major is sort of a relative term.6) program is installed7) program doesn't work like the customer wanted8) programmers have to go back and cha! nge everythingSo, to avoid the negatives in steps 5, 7, and 8 the analyst will have a design review with the programmers and customers (usually seperately) so they can tear it apart and make revisions before coding actually starts. That helps to ensure that any changes to the design are done with the original requirements in mind and also makes sure the design is technically possible and not something goofy that only a non-programmer would come up with. Also in my company, once you get done with the design phase, they lock the due date down and if you have to go back and make changes to design your project probably runs late (shame shame)... so you want to catch as much in the design phase as possible....Show more

Loise Mausser: You might find this Wiki article helpful:http://en.wikipedia.org/wiki/Software_walkthroughJeffhttp://www.excellentiasoftware.com...Show more