Lester wrote: > I am in the process of developing a formal requirements process for > our product installs (currently the process is basically hallway > conversations and scattered emails). >
I used a similar form approach in a previous life; in general, it worked for high-level things (we need this driver installed, this Web site created) but failed on lower-level things. For example, having a section for "registry values" breaks how components work in MSI; you really want registry values associated with the code that uses it, not grouped together in one big "RegistryComponent." It also encourages problems getting mutated into something for setup to solve. Finally, any low-level form tends to get people thinking that "setup development" means "re-typing the setup spec into <WiX XML, Weyland-Yutani setup-authoring tool, etc.>" That makes it tougher to talk about the need to design setup like every other part of the software. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
