Different kind of documents for application development in mobile and web domain.
1) Requirement docs:
basically it is prepared by SME or business development executive. It should be written in a story mode or in a point. Sometimes it is written in a step by step. then actual requirement gathering will be start or project will start after detailed discussion with team members project manager business development executive and team member basically it will be depend on company some some times team member are not included.
2) Use case docs:
Basically it is done by the behalf of requirement docs which is given by the stakeholder use case is the second docs which is prepared by the same once it will be completed given to stake holder once stake holder review the docs and give green signal to the company actual work will start now everybody is a part of team. Then project manager will decide a team and and other hardware requirement. And this is a write time to decide the time period how long application goes or estimation goes. In a normal water fall model project manager will decide estimation. But in scrum stake holder and some time stake holder cannot able to decide due to any reason then the team will decide the time estimation and stake holder will agree behalf of conversation but other things will be decide by stakeholder.
3)Behalf of use case tester will start writing test case parallel development team will write functional and architectural diagram manager will get the right resource if resource is available if not he will send a request for new resource to the hr manager hr manager can hire or assign previous employee get the training and make it available.
4) If company is using scrum framework expert from different domain will work as a team member or cross functional team. All will be a part of team and attend all the desire meeting happens with stake holder and internal meeting. So he is able to understand the application well and gave some good suggestion to make a good product.
5) If it is a traditional testing envy... once integration is completed tester will get the build for integration testing and write a bug in bug tracking tool complete the testing and send report to the developer and project manager and wait for second round of testing or regration testing but company is using scrum development tester will get the more release in a short sprint but send a report to the developer and project manager basically in scrum there is no project manager only scrum master his duty to update the development or status of project to the stake holder.
6) Before releasing the application for beta testing tester will develop the acceptance test plan and detailed UI test plan behalf of SRS and use. It will cover explicit and implicit scenario. It means low level and high level test cases high level contains database, functionality; low level contain UI and localization.
7) Staging server: Basically it is a real environment for testing which can be available by customer or stakeholder it behaves a real server with less load once application will run perfectly on that server the application will be live and user can upload.
basically it is prepared by SME or business development executive. It should be written in a story mode or in a point. Sometimes it is written in a step by step. then actual requirement gathering will be start or project will start after detailed discussion with team members project manager business development executive and team member basically it will be depend on company some some times team member are not included.
2) Use case docs:
Basically it is done by the behalf of requirement docs which is given by the stakeholder use case is the second docs which is prepared by the same once it will be completed given to stake holder once stake holder review the docs and give green signal to the company actual work will start now everybody is a part of team. Then project manager will decide a team and and other hardware requirement. And this is a write time to decide the time period how long application goes or estimation goes. In a normal water fall model project manager will decide estimation. But in scrum stake holder and some time stake holder cannot able to decide due to any reason then the team will decide the time estimation and stake holder will agree behalf of conversation but other things will be decide by stakeholder.
3)Behalf of use case tester will start writing test case parallel development team will write functional and architectural diagram manager will get the right resource if resource is available if not he will send a request for new resource to the hr manager hr manager can hire or assign previous employee get the training and make it available.
4) If company is using scrum framework expert from different domain will work as a team member or cross functional team. All will be a part of team and attend all the desire meeting happens with stake holder and internal meeting. So he is able to understand the application well and gave some good suggestion to make a good product.
5) If it is a traditional testing envy... once integration is completed tester will get the build for integration testing and write a bug in bug tracking tool complete the testing and send report to the developer and project manager and wait for second round of testing or regration testing but company is using scrum development tester will get the more release in a short sprint but send a report to the developer and project manager basically in scrum there is no project manager only scrum master his duty to update the development or status of project to the stake holder.
6) Before releasing the application for beta testing tester will develop the acceptance test plan and detailed UI test plan behalf of SRS and use. It will cover explicit and implicit scenario. It means low level and high level test cases high level contains database, functionality; low level contain UI and localization.
7) Staging server: Basically it is a real environment for testing which can be available by customer or stakeholder it behaves a real server with less load once application will run perfectly on that server the application will be live and user can upload.
Comments
Post a Comment