• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 25. Planning Considerations When... > Establishing Project Requirements

Establishing Project Requirements

Without question, the number one reason for a software project's downfall is the failure to gather adequate requirements, and gather them correctly. Anyone undertaking a project to deploy Crystal Enterprise must take the time to discover exactly what the tool is required to accomplish. This need is initially defined by the business problem. Remember, the business problem should be considered the starting point for a Crystal Enterprise solution, allowing the enterprise reporting technology to be embraced and extended to an entire organization.

CAUTION

Don't get caught stating technical solutions as requirements rather than the true requirements. For example you might state a requirement that: “I want to produce .pdf files from a report.” This is actually a solution statement! If you examine why you made this statement, you might see that you thought an Adobe Acrobat (.pdf) file would enable you to share information over the Web. In that case, your requirement should state: “End users can all see the information on Internet Explorer and Netscape browsers on the corporate network.” The technical solution to this problem arrives in the next phase, and stating technical solutions instead of actual requirements is a typical and costly mistake.



PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint