SRS/BRD

BRD should never mention what is the solution, but not what is the solution. BRD mentions current (as-is) and future state (to-be). Stakeholder requirements are to be grouped by stakeholder 1, 2, 3. Supplemental section of BRD gives glossary, appendix, approvers etc. Needs revision history for each change made to BRD. BRD includes problem and business goals, as well as key objectives (specific things to reduce/improve), success metrics. Scope and limitations: In-scope, out-of-scope.

SRS mentions the solution in terms of use case and sequence diagrams. Main use of sequence diagram is to show particular scenario. SRS needs function and non functional requirements. In Data requirements will have to use data, the type of which mentioned in data dictionary. Intro of SRS has purpose and project scope. Overall desc. has user classes. Product perspective (?) Operating environment is also in main components like what operating system is needed for project. Limitations can include things like only chrome can run this app. Assumptions about project. Dependencies: I may need a quarterly budget to release version. Use case diagram in use cases. Explain data model (E-R diagram), data dictionary (sql table). Have use case diagram