|
No edit summary
|
|
||
| Line 8: | Line 8: | ||
==Elicitation== |
==Elicitation== |
||
Elicitation is the gathering and discovery of requirements from stakeholders and other sources. A variety of techniques can be used such as [[Joint application design|Joint Application Design]] (JAD) sessions, interviews, document analysis, focus groups, etc. Elicitation is the first step of requirements development. |
Elicitation is the gathering and discovery of requirements from stakeholders and other sources. A variety of techniques can be used such as [[Joint application design|Joint Application Design]] (JAD) sessions, interviews, document analysis, focus groups, etc. Elicitation is the first step of requirements development. |
||
name :- yangya prasad karna |
|||
==Analysis== |
==Analysis== |
||
Software Requirements is a field within Software Engineering that deals with establishing the needs of stakeholders that are to be solved by software. The IEEE Standard Glossary of Software Engineering Technology defines a software requirement as:[1]
Software Requirements can broadly be broken up into Elicitation, Analysis, Specification, and Management.[2]
Elicitation is the gathering and discovery of requirements from stakeholders and other sources. A variety of techniques can be used such as Joint Application Design (JAD) sessions, interviews, document analysis, focus groups, etc. Elicitation is the first step of requirements development. name :- yangya prasad karna
Analysis is the logical breakdown that proceeds from elicitation. Analysis involves reaching a richer and more precise understanding of each requirement and representing sets of requirements in multiple, complementary ways.
Specification involves representing and storing the collected requirements knowledge in a persistent and well-organized fashion that facilitates effective communication and change management. Use cases, user stories, functional requirements, and visual analysis models are popular choices for requirements specification.
Validation involves techniques to confirm that the correct set of requirements has been specified to build a solution that satisfies the project's business objectives.
Requirements change during projects and there are often many of them. Management of this change becomes paramount to insuring that the correct software is built for the stakeholders.
Specialized commercial tools for requirements engineering are Gatherspace, Rational RequisitePro, Doors, CaliberRMorQFDCapture, but also free tools like FreeMind can be used.[3] Issue trackers implementing the Volere requirements template have been used successfully in distributed environments.[4]
Software Requirements Specification
{{cite web}}: |access-date= requires |url= (help); Missing or empty |url= (help)
{{cite web}}: Explicit use of et al. in: |last2= (help)
{{cite book}}: Cite has empty unknown parameter: |1= (help){{cite book}}: Cite has empty unknown parameter: |1= (help){{cite book}}: Cite has empty unknown parameter: |1= (help)
