I'm working in a company and we want to implement a document management system using SP. As a software engineer I will handle the requirement gathering. The document management system is somehow standard so the main requirement will be as follow:-
1. what are the document hierarchy for each department for example in the financial department they might have the following hierarchy:
2. Second requirement will be regarding the users permissions, for example who can add documents, edit document, delete document under each department.
So to be able to provide an agile and reliable approach to do the requirement gathering I'm planning to do the following:-
I will hold a meeting with the departments mangers; where I will describe what I'm planning to build with some screens shots regarding a sample of what the document magement system is.
Secondly I'm going to forward a document for each department manager to specify the following:-
- What are the document categories hierarchy they like to have?
- Specify the user names who can add, edit , delete, view the department documents?
Is the above approach considered an accurate method to follow, or it will not be a professional way to do a requirement gathering?