COEPD – Center of Excellence for Professional Development Happy Learning
- Can you explain SRS and its Key Elements?
– SRS Means Software Requirements Specifications. Which includes Functional Requirement and technical requirement.
This is very simple and most important process in requirement specifications. It will help to provide basic cost of product and what will be the risk for product in future. It will help to endues or new user to operate things in proper way with guidance. This requirement specification forms basis of an organizations entre project. It will create set of all frame work which need to follow by all development team. It will provide critical information to all team members all things such as- development, operation, quality assurance and maintenance. Need to ensure the teams are in agreement. We can say that there are three types of requirements – 1. Functional Requirement. 2. Non- Functional Requirement 3. domain requirements
The key Elements of SRS are:
1. Keep it organized – start with a template
This is very simple that we have to define the future of the company and products. Before starting any document we need to start with simple template. To be perfect in all the document. All the documents should be cut short and properly organized to be more efficient.
2. As per user point of view-
It will help to know how an organizational system can be used as user points from different stakeholders. The document should have a conceptual grasp of the system. It will also help illustrate high-level threats to a proposed system or situation. This helps and identifies the vague capabilities of a project before it even begins and gives a more clear and specific technical basis that will make it more successful.
3. Write implementation-
This is very simple that we have to define the future of the company and products. Before starting any document we need to start with simple template. To be perfect in all the document. All the documents should be cut short and properly organized to be more efficient.
4. Analyze, Refine, Decompose Requirements
Here we need to analyze after analyzing need to rework if required and after that we need to decompose requirement with all proper manner to meet all requirements from end user view.
This is very simple that we have to define the future of the company and products. Before starting any document we need to start with simple template. To be perfect in all the document. All the documents should be cut short and properly organized to be more efficient.
5. Need to Make requirements testable at high level
This is a very common and standard and even then organizations fail to meet the criteria. High-level requirements often not meet inspection or user testing, Here we need to check requirement with high to low level.
6. Evaluate documentation with stakeholders from start to end
After all process has been documented we need to evaluate the final documentation in proper manner before development begins. After all we need ensure that satisfaction is reached across the teams and increase the probability that the requirements will meet their needs.
This is very simple that we have to define the future of the company and products. Before starting any document we need to start with simple template. To be perfect in all the document. All the documents should be cut short and properly organized to be more efficient.
7. Manage requirements changes
Need to manage all requirement changes in proper manner with all excepting changes. the situations and project requirements are always developing or ever-changing. Requirements can change for plenty of reasons. Its quite lengthy process to do changed in all documents as per requirement.
