Índice de conceitos de RAS

  1. Teórica 1
    1. Software Engineering
  2. Teórica 2
    1. Requisitos
    2. Requisitos Funcionais
    3. Set de Requisitos
    4. Requisitos Implícitos e Explícitos
    5. Requisitos Não-Funcionais
    6. Classificação de Requisitos
    7. Requisitos de Sistema
    8. Problem Domain
    9. SUMMARY
  3. Teórica 3
    1. Requirements Engineering
    2. Processo de Requirements Engineering
      1. Inception
      2. Elicitation
      3. Elaboration
      4. Negotiation
      5. Documentation
      6. Validation
      7. Management
    3. Dimensões de Requirements Engineering
    4. Dificuldades de Requirements Engineering
    5. SUMMARY
  4. Teórica 4
    1. Templates para documentos de requisitos
    2. Guidelines para escrever documentos de requisitos
      1. Standart format - user requirements
      2. Standart format - User Stories
      3. Standart format - system requirements
      4. Standart format - non-functional requirements
    3. How to write requirements
    4. Issues when writing requirements
    5. Ambiguity
    6. SUMMARY
  5. Teórica 5
    1. Process of Elicitation and Activities
    2. Roles
      1. Ways to identify roles
    3. Users
    4. Client
    5. Customers
    6. Market Segment
    7. Negative Stakeholders
    8. General competencies of a requirements engineer
    9. Groups of techniques of a requirements engineer
    10. Requirements Techniques
      1. Interview
      2. Survey
      3. Introspection
      4. Domain Analysis
      5. Prototyping
      6. Personna
    11. SUMMARY
  6. Teórica 6
    1. Models
    2. Dimensions of a model
      1. Physical Models
      2. Symbolic Models
      3. Descriptive Models
      4. Prescriptive Models
      5. Structural Models
      6. Behavioural models
    3. UML Models
      1. Domain Model
      2. Use Case Model
      3. Class Model
      4. Sequence Model
      5. State Model
      6. Activity Model
    4. SUMMARY
  7. Teórica 7
    1. Principles
    2. Design
      1. Design Levels
    3. Software Architecture
    4. Risks
    5. Architecture design and detailed design
    6. Dependencies
      1. Coupling
    7. Architecture Skeletons
    8. Quality attributes
    9. Architecture is orthogonal to functionality
    10. What makes a good architecture?
    11. Presumptive Architectures
    12. SUMMARY
  8. Teórica 8
    1. Failure
    2. Risk-Driven Approach
    3. Risk = Failure x Impact
    4. Kinds of risks
    5. Prototypical risks
    6. Risk Prioritisation
    7. Risk Mitigation
      1. Risk Techniques
    8. Effort proporcional to risks
    9. Styles of design
      1. Evolutionary design - NDUF
      2. Planned design - BDUF
      3. Minimal planned design - LDUF
    10. SUMMARY
  9. Teórica 9
    1. Tactics
    2. Availability
      1. Fault detection
      2. Fault recovery
      3. Fault prevention
    3. Performance
      1. Events
      2. Resource consumption and blocked time
        1. Resource demand
        2. Resource management
      3. How to get ideal performance?
    4. SUMMARY
  10. Teórica 10
    1. Patterns
  11. Teórica 11
    1. Architectural style
    2. Constraints
    3. Platonic vs. Embodied styles
    4. Styles
      1. Layered style
      2. Big ball of mud style
      3. Pipe and Filter style
      4. Batch-sequencial style
      5. Model-centered style
      6. Publish-subscribe style
      7. Client-server style & N-tie style
      8. Peer-to-peer style
      9. Map-reduce style
      10. Mirrored, rack, and farm style