소프트웨어 요구사항
package.lua 80번째 줄에서 Lua 오류: module 'Module:Namespace detect/data' not found. package.lua 80번째 줄에서 Lua 오류: module 'Module:Message box/localize' not found.
소프트웨어 요구사항은 a field within 소프트웨어 공학 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]
- A condition or capability needed by a user to solve a problem or achieve an objective.
- A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document.
- A documented representation of a condition or capability as in 1 or 2.
The activities related to working with 소프트웨어 요구사항 can broadly be broken up into Elicitation, Analysis, Specification, and Management.[2]
도출[편집]
도출(Elicitation)은 이해관계자들(stakeholders) 및 다른 출처로부터 요구사항을 수집하고 발견하는 것이다. 결합 응용 설계 (JAD) sessions, 인터뷰, 문서 분석, focus groups 및 기타 다양한 기술들을 사용할 수 있다. 도출은 요구사항 개발(requirements development)의 첫 단계이다.
분석[편집]
분석(Analysis)은 the logical breakdown that proceeds from 도출. Analysis involves reaching a richer and more precise understanding of each requirement and representing sets of requirements in multiple, complementary ways.
Specification(명시)[편집]
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(검증)[편집]
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.
Management(관리)[편집]
Requirements change during projects and there are often many of them. Management of this change becomes paramount to ensuring that the correct software is built for the stakeholders.
Tool support for requirements engineering[편집]
Specialized commercial tools for requirements engineering are Gatherspace, Rational RequisitePro, Doors, CaliberRM or QFDCapture, but also free tools like FreeMind and Concordion can be used.[3] Issue trackers implementing the Volere requirements template have been used successfully in distributed environments.[4]
같이 보기[편집]
- 요구동학
- 소프트웨어 요구사항 명세서(Software requirements specification, SRS)
각주[편집]
더 읽어보기[편집]
- 스크립트 오류: "citation/CS1" 모듈이 없습니다.
- 스크립트 오류: "citation/CS1" 모듈이 없습니다.
- 스크립트 오류: "citation/CS1" 모듈이 없습니다.
This article "소프트웨어 요구사항" is from Wikipedia. The list of its authors can be seen in its historical. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
