1. What is an SRS document? It is a document that specifies the requirements of the system. Short for System/Software Requirement Specification. Describe in detail the functional and non-functional requirements of the system. General requirements, data requirements, interfaces, etc. For all Stakeholders to read and understand the business of the functions, etc. An important document for development and testing teams.
Watching: What is Srs
2. Why SRS documentation is needed Help all stakeholders understand the system in the same way. Help the development team rely on to build the exact features to the customer’s requirements. Help testers to read, understand and write test cases. Make it easier to maintain and improve the system later.3. Key elements of the SRSIntroduction document – IntroductionHigh Level Requirement – General level requirements Security Requirement – Security requirementsUse Case Specification – Use case specification Wireframe – Design of screensOther Requirement – Other requirementsIntegration – Requirements IntegratedAppendices – Appendix
4. Section Introduction Details in the Introduction section include:
1.Purpose: This section describes in detail the meaning and purpose of an SRS document, helping people better understand what an SRS document is and why it is important.
2.Application Overview: This section describes an overview of the system you want to work on. The overview must ensure factors such as: What is a general description of the system? What are the main features, who has the rights and the purpose of the system created to serve, etc.
3.Intended Audience and Reading Suggestions: This section describes who the SRS document is intended for and what they will do.
4.Abbreviations: Defines abbreviations used in the document. For example, SRS is the System Requirement Specification, etc.
5.References: Allows you to attach or describe documents related to the system.
5. Section High Level Requirement and Security
Details in the High Level Requirement section include:
1.Object Relationship Diagram: ORD is a static relationship model between objects in the system. An object can be described as an instance of a particular entity in the system.
2.Workflow Diagram: This section shows the workflow or steps taken by each system user to complete the business process. User actions are shown in each stage of the system’s business process and what happens before it can move on to the next, or back to, previous stage.
Workflow describes the workflow and steps taken by each User in the system, to complete a particular business process. The steps in the workflow must ensure that the state of the process changes.
3.
See also: What Are Calories – Calories: Not Just Numbers!
State Transition Diagram: Describes each step-by-step state of the workflow. Users looking at State Transition can imagine who each step in the workflow is performing, and what actions change the state in the system process ntn?
4.Use Case Diagram: Diagram to show how the users in the system interact with the features in the system.
6. Section Security Requirement
A complete description of the permissions of each actor in the system. Which actor does what functions, etc.
Matrix table of permissions corresponding to each actor in the system. Show that, with any Actors they have the right to do what actions in the system
7. Section Use case Specification
This section includes the system’s functional requirements, which detail what the system must do in terms of input, behavior, and expected output.
It elicits the interaction between the agent(s) and the system, the behavior of the system, and the results of their interactions.
8. Other parts
Wireframe: This allows you to attach wireframe documents so that readers can refer to the screen.
Confirm system functional requirements with customers faster. Customers understand and visualize the system more easily. Demonstrate understanding of BA’s requirements with customers’ expectations. Prove the capacity of the project team. Internal team is easier to approach, grasp and understand the system faster. Tools: Recommend figma.com, Balsamiq mockups, …
Other requirement: Describes the additional requirements of the system, this belongs to the non-functional requirement.
Integration: This section allows you to describe or attach documentation related to external systems.
Appendices:
Email template: This section allows you to define the email templates used in the systemError message: This section allows you to define the error messages in the system.
9. Main elements in attached Wireframe document
The document includes the following main sheets:
1.Table of Contents: Defines all the urls to each sheet in the wireframe document, this is also considered the direction of the file. This helps the reader to navigate to each sheet easily.
2.Version history: Describes how to type the versions of the document, and also records all version upgrades and revisions, edited content, who edited, etc.
3.
See also: What is Cgi – Active Cgi How to move?
System’s screen: List the screens in the system, how many main screens in the system correspond to many sheets. However, the layout of the screen and the corresponding sheets depends on the layout of each person.
