Hi Pathak, I really appreciate the format which you have given and other guyz suggestions, but it will make your cousin's life easier if he/she also consider following tips: 1. As more and more Projects are failing due to poor problem formulation, thus industry is seriously taking steps to cope with that issue through: a. CSH (Classification of Stakeholders) b. QCoH(Qualitative classes of stakeholders c. defining issues through rich pictures d. using Cogitive Maps (CM) instead of conventional DFD's, ERD,s etc. 2. Do not forget to include a. Operational Fesibility (consider user's of the system) b. Political Feasibility (consider user's and organization as a whole, mainly organization's internal environment) c. Schedualing Feasibility (very very very important, its Time Management) 3. And i agree with other guys that since it is a OO application, then you "should" use class diagrams to define the attributes and methods. and in the end, all i can say is "Wish your cousin all the best". cheeerz "Being a Simplebeing means Human Being"