SRS VERIFICATION

Name of Project : E-GRAMSEVA APP

Verified By:
A45 Rajnandini Ingale
A46 Rohit Dolare
A50 Vaibhav Munde
A55 Niketan Raskar
A58 Saikrushna Adepawar
Prepared by:
A48 Sourabh Patil
A49 Chaitanya Jaybhaye
A53 Anand Ratnakar
A57 Rushikesh Methe
A60 Ajit Waghmode

S No. Description Yes/No/NA Remarks

1. Is the purpose of project clearly defined? Yes
2. Is the scope clearly defined? Yes
3. Is document format as per standard guidelines Yes
Is the project formally approved by the customer? The project is still
4. NA in development
phase
Are all requirements, interfaces, constraints, definitions,
5. Yes
etc. listed in the appropriate sections?
Is the expected response time from the user's point of The project is still
6. view, specified for all operations? NA in development
phase
Do all stated requirements express the expectations of
7. yes
customer?
Are there areas not addressed in the SRS document that
8. No
need to be?
9. Are non-functional requirements stated? Yes
Are validity checks properly defined for every input
10. Yes
Condition?
Ambiguity
Are functional requirements separated from non-
11. functional requirements? Yes

Is any requirement conveying more than one

12. No
Interpretation?
13. Are all requirements clearly understandable? Yes
Does any requirement conflict with or duplicate with
14. No
other requirements?
15. Are there ambiguous or implied requirements? No
Completeness
 Are all functional and non-functional requirements
16. stated? Yes

17. Are forms available with validity checks? No

18. Are all reports available in the specified format? No
Are all references, constraints, assumptions, terms and Yes
19.
unit of measures clearly stated?
Has analysis been performed to identify missing No
20.
requirements?
Consistency
Are the requirements specified at a consistent level of Yes
21.
detail?
22. Should any requirement be specified in more detail? No
23. Should any requirement be specified in less detail? No
Are the requirements consistent with other documents Yes
24.
of the project?
Is there any difference in the stated requirement at two
25. No
places?

Verifiability
26. Are all stated requirements verifiable? Yes
Are requirements written in a language and vocabulary Yes
27.
that the stakeholders can understand?
28. Are there any non-verifiable words? No
29. Are all paths of a use case verifiable? Yes
30. Is each requirement testable? Yes
Modifiability
31. Are all stated requirements modifiable? Yes
32. Have redundant requirements been consolidated? No
Has the document been designed to Incorporate Yes
33.
changes?
Is the format structure and style of the document Yes
34.
standard?
35. Is there any procedure to document a change? Yes
Traceability
Can any requirement be traced back to its origin or Yes
36.
source?
37. Is every requirement uniquely identifiable? Yes
Are all requirements clearly understandable for Yes
38.
Implementation?
Has each requirement been cross referenced to Yes
39.
requirements in previous project documents that are
relevant?
Is each requirement identified such that it facilitates
40. referencing of each requirement in future development Yes
and enhancement efforts?
 Feasibility
41. Is every stated requirement feasible? Yes
Is any requirement non-feasible due to technical
42. No
reasons?
Is any requirement non-feasible due to lack of
43. No
resources?
Is any requirement feasible but very difficult to
44. No
Implement?
45. Is any requirement very complex? No
General
46. Is the document concise and easy to follow? Yes
Are requirements stated clearly and consistently
47. Without contradicting themselves or Yes
other requirements?
48. Are all forms, figures and tables uniquely numbered? Yes
Are hardware and other communication requirements Yes
49.
stated clearly?
50. Are all stated requirements necessary? Yes