Summary

I l @ ve RuBoard

Before you begin to develop your application, it's important to work out exactly what the application needs to do. This is the purpose of an FRD. It documents the way that users will encounter the application and the functionalities that will be available to them. An FRD also provides a framework for determining issues that must be resolved before development begins. It is the contract between you and the client regarding what must be delivered. An FRD can be developed based on a series of conversations with the client, mockups (sometimes called wireframes), or both.

Some overall issues must be addressed before you can begin to design an FRD, and others will crop up during the thought and design process.

When you've completed the FRD and received approval, you'll be ready to move on to the next phase (design), with a good understanding of the overall needs of the client and how the applications flow will work as a whole.

I l @ ve RuBoard