Notes

P1

Create a complete INCOSE/ISO 29148 compliant requirements package for the following capability:

<CAPABILITY DESCRIPTION>

Develop:
- SyRB
- SyRS
- SyAD
- SyID

Include:
- Functional requirements
- Non-functional requirements
- Constraints
- Interfaces
- Security
- Performance
- Availability
- Scalability
- Operations
- Verification methods
- Full traceability

Output in Excel-ready CSV format.

P2
Act as a Senior Systems Engineer with expertise in INCOSE Systems Engineering Handbook, ISO/IEC/IEEE 29148, IEC 62443, and requirements engineering best practices.

Given a system capability, feature, or stakeholder need, develop a complete and traceable requirements package.

Produce the following specifications:

1. Stakeholder Requirements Baseline (SyRB)
2. System Requirements Specification (SyRS)
3. System Architecture Description (SyAD)
4. System Interface Description (SyID)

Requirements shall:

- Follow ISO/IEC/IEEE 29148 requirements writing guidelines
- Use "shall" statements
- Be atomic (one requirement per statement)
- Be clear and unambiguous
- Be verifiable
- Be traceable
- Avoid implementation details unless they are true constraints
- Clearly distinguish requirements from design decisions

For each requirement, provide:

- Requirement Identifier
- Document Source (SyRB, SyRS, SyAD, SyID)
- Requirement Category
- Parent Requirement(s)
- Requirement Statement
- Rationale (optional)
- Verification Method
- Implementation Responsibility
- Verification Responsibility

Identify and create requirements for all applicable categories, including:

- Functional Requirements
- Security Requirements
- Performance Requirements
- Availability Requirements
- Reliability Requirements
- Maintainability Requirements
- Usability Requirements
- Safety Requirements (if applicable)
- Operational Requirements
- Data Requirements
- Interface Requirements
- Architecture Requirements
- Constraint Requirements
- Regulatory/Compliance Requirements
- Audit and Logging Requirements
- Scalability Requirements
- Access Control and Authorization Requirements
- Authentication Requirements (if applicable)

Generate traceability:

- Stakeholder Requirements → System Requirements
- System Requirements → Architecture Requirements
- Architecture Requirements → Interface Requirements

Also generate:

1. Forward Traceability Matrix
2. Backward Traceability Matrix
3. Verification Traceability Matrix
4. Requirement Coverage Summary
5. Requirement Allocation Summary

Output all requirements in Excel-ready CSV format.

Where appropriate, identify:
- Assumptions
- Constraints
- Risks
- Open Issues
- External dependencies

Before generating requirements, perform a requirements analysis and identify:
- Functional needs
- Non-functional needs
- Interfaces
- External systems
- Users and actors
- Security considerations
- Operational considerations

Ask clarifying questions if information is missing before generating the requirements package.

P2

Act as a Senior Systems Engineer with expertise in INCOSE Systems Engineering Handbook, ISO/IEC/IEEE 29148, IEC 62443, and enterprise Identity and Access Management (IAM).

Create a complete requirements package for introducing Single Sign-On (SSO) functionality into an existing system.

The solution shall use:

- OAuth 2.0 Authorization Framework
- OpenID Connect (OIDC)
- Microsoft Active Directory based Identity Provider (Active Directory / AD FS / Microsoft Entra ID)
- Role-Based Access Control (RBAC)
- Token-based authentication and authorization
- Browser-based access
- Command-line access using tools such as curl and wget
- Machine-to-machine application access using OAuth2 Client Credentials Grant

Generate the following specifications:

1. System Requirements Baseline (SyRB)
2. System Requirements Specification (SyRS)
3. System Architecture Description (SyAD)
4. System Interface Description (SyID)

Requirements shall comply with:
- ISO/IEC/IEEE 29148
- INCOSE recommended requirements writing practices
- Single requirement per statement
- Use "shall" statements
- Verifiable requirements
- Unambiguous requirements
- Traceable requirements

Include requirements covering:

AUTHENTICATION
- Single Sign-On
- OpenID Connect authentication
- OAuth2 authorization
- Browser login
- API authentication
- Command-line authentication

AUTHORIZATION
- Role-Based Access Control (RBAC)
- Role assignment
- Active Directory group mapping
- Authorization scopes
- Least privilege principle
- Administrative roles
- Application roles
- API endpoint authorization

TOKEN MANAGEMENT
- Access tokens
- ID tokens
- JWT tokens
- Token issuance
- Token validation
- Token revocation
- Token expiry
- Configurable token lifetimes
- Refresh token management
- Prevention of expired-token reuse
- Prevention of revoked-token reuse

ACTIVE DIRECTORY INTEGRATION
- Active Directory as authoritative identity source
- User identity claims
- Group membership claims
- Federation using OIDC
- Centralized authentication

SECURITY
- TLS 1.3 minimum
- Token signature validation
- Issuer validation
- Audience validation
- Expiration validation
- Rejection of malformed tokens
- Rejection of tampered tokens
- Audit logging
- Authorization failure logging
- Expired token logging

PERFORMANCE
- Authentication response time
- Concurrent session support

AVAILABILITY
- Authentication service availability requirements
- Redundancy requirements

ARCHITECTURE
- Centralized Identity Provider
- Token validation component
- Authorization component
- Scalability requirements
- High availability requirements

INTERFACES
- OIDC Discovery
- Authorization Endpoint
- Token Endpoint
- UserInfo Endpoint
- JWKS Endpoint
- HTTPS interfaces
- JSON payloads
- JWT token processing

CONSTRAINTS
- OAuth 2.0 compliance
- OIDC compliance
- Active Directory integration
- HTTPS transport
- JSON payload format
- JWT token format

For every requirement provide the following columns:

Requirement ID
Document
Requirement Type
Category
Parent Requirement(s)
Requirement Statement
Verification Method
Implementation Responsibility
Verification Responsibility

Implementation Responsibility:
Development Team

Verification Responsibility:
V&V Team

Generate the output as Excel-ready CSV tables.

Also generate:

1. Full forward traceability matrix
SyRB → SyRS → SyAD → SyID

2. Backward traceability matrix
SyID → SyAD → SyRS → SyRB

3. Verification traceability matrix

4. Requirement coverage summary

5. Requirement count by document

Use requirement identifiers similar to:

SYRB-SSO-001
SYRB-RBAC-001
SYRB-CON-001

SYRS-IAC-001
SYRS-TOK-001
SYRS-RBAC-001
SYRS-SEC-001
SYRS-CON-001
SYRS-PERF-001
SYRS-AVL-001
SYRS-INT-001

SYAD-ARC-001
SYAD-RBAC-001
SYAD-CON-001
SYAD-TOK-001

SYID-INT-001
SYID-PRO-001
SYID-DAT-001
SYID-SEC-001
SYID-RBAC-001
SYID-TOK-001
SYID-CON-001
SYID-OPS-001
SYID-ERR-001

Ensure all requirements are uniquely traceable and suitable for import into requirements management tools such as IBM DOORS, Jama, Polarion, or Azure DevOps.