Visão Geral

Os requisitos constituem a principal força motriz para qualquer projeto. O grau em que os requisitos são definidos é o grau em que o projeto é bem-sucedido. Este curso especifica como identificar e documentar requisitos de qualidade para produzir um produto de qualidade. Como os requisitos podem ser renderizados de muitas maneiras diferentes, desde documentos de requisitos clássicos até formas de história de usuário mais ágeis, o curso apresenta técnicas para desenvolver e documentar todas as formas de representação de requisitos.

Objetivo

Ao final do curso, você aprenderá a:

• Como determinar a diferença entre coletar informações e gerar requisitos
• Como definir os requisitos reais no formato mais útil para os desenvolvedores
• A importância de definir o problema antes de definir os requisitos
• Como desenvolver requisitos com um processo consistente e produzir requisitos para qualquer abordagem de desenvolvimento de software

Publico Alvo

• Analistas de negócios, analistas de requisitos, gerentes de projeto e qualquer pessoa interessada em um projeto de desenvolvimento de software bem-sucedido.

Pre-Requisitos

• Não são assumidos pré-requisitos específicos. É recomendada familiaridade com conceitos de sistemas de informação.

Informações Gerais

FORMATO:

• 100% On-Line na presença de um instrutor/consultor ativo no mercado e docente em sala de aula.
• In-company.
• Presencial.

PERÍODO:

• Noturno em noites intercaladas exemplo: terça-feira e quinta-feira das 19h às 23h,total de 4h por encontro.
• Aos sábados das 8h às 12h, total de 4h ou das 09h às 18h, total de 8h.
• Integral consultor disponibilidade

LAB:

• Apostila
• Laborátorio individual
• Exercícios práticos

Conteúdo Programatico

Understanding Requirements

• What Are Requirements?
  1. Requirements Analyst in the Center
  2. Project, Product, and Process
  3. The Challenge of Quality
  4. Why Don’t We Get Good Requirements?
  5. What Are Requirements?
  6. Business, User, System Requirements
  7. Requirements Aspects
• Reason for Requirements
  1. Relative Cost of Defect Fix
  2. Linking Requirements to the Life Cycle
  3. Why Organizations Don’t Get Good Requirements
• Requirements Process
  1. Software Engineering Process
  2. Software Development Processes
  3. Requirements in Agile Approaches to Software Development
  4. General Requirements Process Overview

Gather Information to Identify Requirements

• Prepare an Information Gathering Plan
  1. Developing the Plan
  2. The Primary Questions
  3. What to Gather Information About
  4. Sources of Information
• Methods of Gathering Requirements
  1. Forms of One-on-One Information Gathering
  2. Requirements Sessions
  3. Observation
  4. Demonstration
  5. Choosing an Approach
• Information Gathering Process
• Workshop: Information Gathering Plan

Identifying the Problem and Vision

• Define the Problem
  1. Determine the Problem
  2. Components of the Problem
  3. Basic Problem Definition
  4. Identify the Real Problem
  5. Establish the Product Vision
• The Business Orientation
  1. Justification
  2. Product Risks
  3. Business and Product Constraints
  4. Context Analysis
• Establish Product Scope
  1. Functional Goals
  2. The Product Scope Formula
  3. Product Glossary
  4. Deliver the Message
  5. Agile Product Roadmaps

Gather the Information

• Six Questions
• What Information?
  1. How to Gather Information
  2. Focuses of Information
  3. Identifying Non-Functional Requirements
  4. Iterative Information Acquisition
• Interviewing
  1. Interviewing Levels of the Organization
  2. The Interview
  3. Success in Gathering Information
  4. Gaining Interviewing Skill
  5. Forms of Interviewing
  6. Getting the Most Information
  7. Categories of Questions
  8. Interview Considerations
• Information Gathering Tips and Techniques
  1. Meetings
  2. Brainstorming
  3. Use Cases and Use Case Models
• Recording the Information
  1. Methods of Recording
  2. CRC Card Model
  3. Recording Prototype Information
• Workshop: Developing Use Cases 

Requirements Analysis

• Modeling and Diagramming Techniques
  1. What Is Analysis?
  2. Why Model?
  3. Modeling the Problem and Solution
  4. Model with a Purpose
  5. Modeling Perspectives
• Analysis Methods
  1. Categorization
  2. Scope Filter
  3. Process Lists
  4. Diagrams
• Derive the Functional Requirements
  1. Gap Analysis: Methods for Identifying the Gap
  2. Scenarios
  3. Gap Analysis Chart
  4. Develop Scenarios
• User Stories
  1. The Purpose of User Stories
  2. Write a User Story in Standard Format
  3. Alternate Formats for User Stories
  4. Epics and Themes
  5. The Product Backlog and User Stories
• Including the Non-Functional Requirements
  1. Analyzing the Data for Non-Functional Requirements
  2. Quality Issues
• Prioritizing the Requirements
  1. Need for Priority
  2. The Priority Filter
  3. Constraining the Design
  4. Prioritization in Agile Approaches
• Workshop: Modeling Requirements

Guidelines to Valid Requirements

• Requirements Format and Contents
• Requirements Representation
  1. Quality Requirements
  2. General Content Recommendations
  3. Structured English
  4. Good and Valid Requirements
• Requirements Documentation Guidelines
  1. Writing Valid Requirements
  2. Things to Avoid
  3. Accuracy
  4. Consistency
  5. Precision
  6. Completeness
  7. Correctness
  8. Traceability
  9. Testability
  10. Validation Filter

Requirements Communication and Management

• Requirements Communication
  1. Steps in Approval Process
  2. Confirmation and Approval Levels
  3. Using Use Case to Confirm Requirements
  4. Communication with User Stories
  5. Formal Approval
• Inspecting Requirements
  1. Review Processes
  2. Inspection and Verification Methods
  3. The Inspection Process
  4. Checklist for Requirements Reviews
• Requirements Confirmation and Approval
  1. Confirmation
  2. Approval process
  3. Formal Approval
  4. Negotiating Requirements
  5. Requirements Confirmation and Approval in Agile Approaches
• Requirements Management
  1. Need for Requirements Management
  2. The Traceability Matrix
  3. Tracing the Requirements
  4. Tracing to Use Cases
  5. Change Management
  6. Requirements Management in Agile Approaches

The Bottom Line

1. Develop a Quality Requirements Process
2. The Processes Reviewed
3. Ideas to Use
4. Where to Go for Additional Information