Visão Geral

Curso Requirements Engineering, cobre todos os aspectos de gerenciamento e engenharia de requisitos. Requisitos são a base para qualquer sistema ou produto. Eles determinam O QUE o sistema ou o produto deve fazer e, eventualmente, conduzem o desenvolvimento do sistema. Requisitos geralmente são derivados de Conceitos de Operações que são usados ​​para validar a operação do sistema. Os requisitos também são usados ​​para determinar [verificar] se o projeto ou a equipe do sistema construiu o sistema corretamente. A engenharia de requisitos gerencia o desenvolvimento e o processo de todas as atividades necessárias para produzir um conjunto de requisitos completos e verificáveis.

A Engenharia de Requisitos estabelece o que o cliente requer de um sistema, software ou produto.

O processo de engenharia de requisitos inclui:

• Estudo de viabilidade tratando de descobrir se o usuário atual precisa ser satisfeito, dada a tecnologia disponível, restrições e orçamento.
• Análise de requisitos para descobrir o que as partes interessadas do sistema exigem do sistema
• Definição de requisitos para definir os requisitos de uma forma compreensível para o cliente e as partes interessadas
• Especificação de requisitos para definir e especificar todos os requisitos em detalhes

Os requisitos podem ser funcionais ou não funcionais. Os requisitos funcionais descrevem serviços ou funções do sistema. O processo de requisitos funcionais estabelece os serviços e funções que o cliente requer de um sistema e as restrições sob as quais ele opera e é desenvolvido.

Os requisitos não funcionais podem ser uma restrição no sistema ou no processo de desenvolvimento:
uma declaração abstrata de alto nível de um serviço ou de uma restrição do sistema para um detalhado. Isso é inevitável, pois os requisitos podem servir a uma função dupla:

• Pode ser a base para uma licitação para um contrato - portanto, deve estar aberto à interpretação
• Pode ser a base para o próprio contrato - portanto, deve ser definido em detalhes

As atividades e processos de engenharia de requisitos estabelecem diretrizes sobre a criação e gerenciamento de requisitos. Os requisitos geralmente começam com uma declaração vaga de intenção. O primeiro problema é estabelecer o limite da investigação e o escopo do sistema ou produto pretendido. .

Objetivo

Após realziar este Curso Requirements Engineering, você será capaz de:

• Introduzir a noção de engenharia de requisitos e processo de engenharia de requisitos
• Para introduzir o estudo de viabilidade, análise de requisitos
  descobrir o que as partes interessadas do sistema exigem do sistema e especificação de requisitos
  definir os requisitos em detalhes
• Para explicar por que requisitos em diferentes níveis de detalhe são necessários
• Descrever como o documento de requisitos do sistema pode ser organizado
• Para descrever o processo de validação de requisitos
• Explicar por que os requisitos evoluem durante o tempo de vida de um sistema
• Para escrever e gerenciar requisitos
• Aprender técnicas para reescrever os requisitos ruins e enganosos

Publico Alvo

• Qualquer um ou qualquer organização que possa ser os operadores
• Analista de NEgoc,ios,
• Gerente de Projetos,
• Arquitetos,
• Administradores
• planejadores
• Usuários
• mantenedores
• usuários do sistema
• Testadores de software

Materiais

Conteúdo Programatico

Introduction to Requirements and Requirements Engineering

1. Introduction to Systems Engineering
2. What is Requirements Engineering?
3. Quality of Requirements
4. Stakeholder Involvement
5. Requirements Lifecycle
6. Requirements Traceability
7. Analysis and Modeling
8. Testing and Integration
9. Requirements Verification and Validation
10. Mapping Requirements from Problem to Solution Domains
11. Effective requirements management
12. Principles of requirements definition and management
13. Best practices for requirements engineering
14. Requirements Baselining

 Requirements Engineering Framework

1. The Requirements Engineering Process
2. Requirements and the Business Context
3. Hierarchy of requirements
4. Stakeholders in the requirements process
5. Eliciting and Documenting Requirements
6. Requirements Elicitation
7. Interviewing for Requirements
8. Use of models in Requirements Engineering
9. Requirements Documentation
10. Requirements Analysis
11. Analyzing and Negotiating Requirements
12. Requirements Validation and Verification
13. Requirements Management

Requirements Engineering and System Views

1. Process View
2. Deliverable View
3. pertinent information for RFPs, SEMPs, ConOps, etc
4. Checklist View
5. Project View
6. SE process applies

Activities in the Requirements Engineering

1. Develop requirements
2. Write and document requirements
3. Check completeness
4. Analyze, refine, and decompose requirements
5. Validate requirements
6. Manage requirements

Basic Requirements Engineering and Management

1. Techniques for drawing out stakeholder needs, goals, requirements, constraints, priorities, normal operations, and preferences
2. Initial needs assessment leading to the development of requirements
3. .Elicitation
4. Stakeholder Analysis
5. Interviews and Workshops
6. Observation
7. Creativity
8. Analysis
9. Kano
10. Specification
11. Use Cases and ConOps
12. BPMN
13. Verification
14. Validation
15. Prototypes
16. Inspection
17. Testing
18. Demo
19. Change management
20. Version control
21. Customer acceptance and validation

Elicitation Techniques

1. Interviews and Focus groups
2. Questionnaires, surveys and Brainstorming
3. Role play
4. Review incident reports, enhancement requests and Joint authorship
5. Benchmark – similar or competing systems
6. Prototype
7. Throw-away
8. Evolutionary

Process for Requirements Engineering 

1. Value of Systems Engineering
2. Value of Requirements Engineering
3. Customer Requirements
4. Functional Requirements
5. Performance Requirements
6. Design Requirements
7. Derived Requirements
8. Allocated Requirements
9. Concept of Operations(ConOps)
10. System Requirements
11. Integration and Verification
12. System Validation
13. Project Planning
14. Project Monitoring and Control
15. High-level identification of user needs and system capabilities
16. Project stakeholders
17. Stakeholder agreement
18. Interrelationships and roles and responsibilities
19. Shared understanding by system owners, operators, maintainers, and developers
20. who, what, why, where, and how of the system and product
21. Agreement on key performance measures
22. Plan for how the system will be validated
23. Developing Systems
24. Input Requirements and Derived Requirements
25. Acceptance Criteria and Qualification Strategy
26. Generic Process Introduction
27. Development in the Context of Change

System Modeling for Requirements Engineering 

1. Requirements Engineering and System Modeling
2. Use Cases and Actors
3. Data Flow Diagrams
4. Entity-Relationship (E-R) Diagrams
5. Statecharts
6. Object-Oriented Approaches
7. DoDAF and NAF Viewpoint Methods
8. The UML and SysML Notations
9. Formal Methods
10. Model Based System Engineering (MBSE) and Requirements Engineering

Managing, Writing and Reviewing Requirements

1. System Life Cycle
2. The systems engineering process
3. Development of system architecture and detail design
4. The Origin of Requirements
5. Concept of the system boundary
6. The modeling boundary
7. Managing Requirements
8. Validating Requirements
9. Requirements traceability
10. Baselines and their use
11. The waterfall vs. agile life cycle paradigm
12. Structuring Requirements
13. Requirements Engineering in the Problem Domain
14. Identify Stakeholders
15. Operational and Use Scenarios
16. Scoping the System
17. Derive Requirements
18. Allocated Requirements
19. Requirements Engineering in the Solution Domain
20. Stakeholder Requirements mapped to System Requirements
21. System Requirements
22. Requirements to Subsystems
23. Traceability
24. Metrics for Traceability

Requirements Engineering Management  

1. Requirements Management
2. Planning
3. Monitoring
4. Changes
5. Development
6. Relationship to design
7. Relationship to baselines
8. Types of Requirements
9. Differences between requirements for hardware, software, services
10. Non-functional requirements
11. Quality of Requirements
12. Requirements Analysis
13. Context analysis
14. Operational Concept Description
15. Verification requirements development
16. “TBDs”
17. Requirements and Requirements Specifications
18. Requirements Flowdown into Specifications

Requirements Engineering Gates and Cross-Cutting Activities

1. Stakeholder Involvement
2. Elicitation
3. Project Management Practices
4. Risk Management
5. Metrics
6. Configuration Management
7. Project Process Improvement
8. Decision Gates
9. Decision Support/Trade Studies
10. Technical Reviews
11. Traceability

Working with Requirements – Deliverable Checklist

• Are all the bases covered?
• Is there a definition of all the major system functions?
• With each function of the system, is there a set of requirements that describes: what the function does, who is assigned to do it, and under what conditions [e.g. environmental, reliability, and availability.]
• Are all terms, definitions, and acronyms defined?
• Are all supporting documents such as standards, concept of operations, and others reference
• Does each requirement have a link [traceability] to a higher level requirement of a user-specified need?
• Is each requirement concise, verifiable, clear, feasible, necessary, unambiguous, and technology independent?
• Are all technology dependent requirements identified as constraints?
•  Does each requirement have a method of verification defined?  
• Has the trace from requirements to hardware and software components been checked and verified?

Working with requirements and requirement types

1. Functional
2. Performance
3. Enabling
4. Data
5. Interface
6. Environmental