Software Requirements Nonfunctional requirements 2 Requirements measures Requirements
- Slides: 40
Software Requirements
Non-functional requirements (2)
Requirements measures
Requirements Engineering Processes(1) u요구를 발견하고, 분석하며, 확인하는 과정 u개발대상 영역, 참여하는 사람, 개발팀에 따라 다양한 절차를 사용 u일반적인 절차 § § § 요구추출 (Requirements elicitation) 요구분석 (Requirements analysis) 요구기술 (Requirements specification) 요구확인 (Requirements validation) 요구분석명세서 작성 (Requirements Documents)
Requirements Engineering Processes(2)
Requirements Engineering Processes(3) u요구의 추출, 분석, 기술 절차
인터뷰 기법(4) u질문의 유형 § 열린 질문 (open questions) § 닫힌 질문 (closed questions) § 추가 질문 (probes questions) u인터뷰의 구조 § 피라미드 구조(pyramid structure): closed --> open § 깔때기 구조 (funnel structure): open --> closed § 다이아몬드 구조(diamond structure): closed --> open --> closed
Requirements specification(2) u자연어 이외의 요구기술 언어
Requirements specification(3) u. Interface specification § 인터페이스 명세 § 다른 시스템과의 인터페이스를 기술 § 요구 명세의 일부분으로 반드시 기술하여야 함 § 인터페이스 기술시 포함할 사항 § Procedural interfaces § Data structures that are exchanged § Data representations § 정형적 표기법을 사용하는 것이 효과적 § 예: PDL interface description
Requirements specification(4) § PDL interface description
Requirements validation(3) u요구 확인 기법 § Requirements reviews § 요구 정의시 고객과 계약담당자가 참석하는 검토회의 개최 § 검토는 정형적/비정형적으로 수행할 수 있음 § 원활한 의사소통이 필수 요소 § Prototyping § Using an executable model of the system to check requirements § Test-case generation § Developing tests to check testability of requirements § Automated consistency analysis
Requirements validation(4) u. Automated consistency analysis
Requirements document(3) u요구분석명세서의 구조 § § § § § Introduction Glossary User requirements definition System architecture System requirements specification System models System evolution Appendices Index
Requirements document(4) u요구분석명세서의 평가 기준 § § § § 정확성 (correct) 완전성 (complete) 일관성 (consistent) 명확성 (unambiguous) 기능적 (functional) 검증 가능성 (verifiable) 추적 가능성 (traceable) 변경 용이성 (changeable)
요구 단계의 CASE tools u. Requirements storage § Requirements should be managed in a secure, managed data store u. Change management § The process of change management is a workflow process whose stages can be defined and information flow between these stages partially automated u. Traceability management § Automated retrieval of the links between requirements
- Nonfunctional requirements
- Repeated measures design vs independent measures design
- Requirement vs specification
- Domain requirements
- Inverse requirements
- High level requirements
- Requirements discovery techniques in software engineering
- Dfd
- What is domain requirements
- Domain requirements
- Inception elicitation elaboration negotiation
- Unambiguous requirements in software testing
- What are functional requirements in software engineering
- Requirements in software engineering
- Characteristics of software requirements
- Hardware and software requirements
- Source and sink in software engineering
- Domain requirements
- Applied software project management
- Hardware interfaces in srs example
- Visual models for software requirements
- Ieee830 テンプレート
- Software maintenance process models ppt
- What is software implementation in software engineering
- Improving software economics
- Computer science vs software engineering
- Metrics computer science
- Computer skills for preparatory programs
- Define generic software
- Difference between student software and industrial software
- Software engineering crisis
- Software measurement and metrics in software engineering
- Is an os system software or application software
- Eic software reviews
- Real time software design in software engineering
- Software design fundamentals in software engineering
- What is multimedia software
- What is vertical distance in surveying
- Using statistical measures to compare populations
- Measures of concentration molarity quiz
- Consequences of unemployment