megrath

 Profile Answers by megrath 

• Sep 25th, 2008

 

In gathering requirement I start with the reading of the

• Scope document.

• Vision document.

• And any other related document.

• Discuss with the project manager, his preferred approach to come with the approach for business requirement and to know the list of stakeholders involved.

• Met with the stakeholders to know the business process that has being followed currently to analyze the AS-IS process flow and then conducted meetings with them to know what is being expected of it to analyze the TO-BE process flow.based on these, i documented the first set of requirements tht is the business needs in BRD. 

I use several different methods to collect requirements, based on the kind of user I am dealing with and his availability. Basically if there are several different users of the same designation and performing same jobs, I prefer to conduct certain group sessions, group interviews and focus interviews. In case if I have to interview a manager or a VP I would take a one to one interview or if he is unavailable I would send him a questionnaire online or shall do a telephonic interview. At certain points of the projects, I also facilitate JAD sessions between the technical and non technical groups. In certain extreme cases, I have also been a part of RDT’s (Rapid Development Teams), which are kind of JAD sessions but on an extremely fast schedule.

feverx4u

 Profile Answers by feverx4u 

• Feb 1st, 2009

 

Here is a template.

SRS-RDD format
I. Summary
II. System Overview
III. Scope
V. Implementation Options
VI. Implementation Approach
        A. ALGORITHM AND DATA STRUCTURES USED

        B. MAJOR FEATURE OF THE DESIGN
        C. PROTOTYPE
        D. FUNCTIONAL VIEW
        E. DATA VIEW
        F. IMPLEMENTATION VIEW
        G. USER INTERFACE
        H. IMPLEMENTATION STANDARDS
        I. CONTROL IMPLEMENTATION
VII. Performance Considerations
VIII. Security Considerations
        A. ACCESS CONTROL
        B. DATA SECURITY
        C. AUDIT TRAILS
        D. APPLICATION ENVIRONMENT SECURITY
IX. Integration Strategy
        A. EXTERNAL APPLICATION INTEGRATION
X. Testing Process
XI. System Requirements
XII. Disaster Recovery
XIII. Data Backup and Archival Strategy
XIV. Future Enhancements

suresh vegi

• Jul 23rd, 2012

 

basically requirements means the needs of the client,so we have to gather all the requirements from client by conducting jad sessions,workshops,brainstorming so on,finally requirements which are gathered have to be documented i.e business requirements specifications(BRS) which contains high level business problems and high level solutions,based on these BRS ,system requirement specification(SRS) document will be prepared.