Skip to content

Commit

Permalink
🐛 Create a better template for questionnaires (#1583)
Browse files Browse the repository at this point in the history
- Add a more relevant template questionnaire demonstrating all of the
assessment capabilities

Signed-off-by: ibolton336 <ibolton@redhat.com>
  • Loading branch information
ibolton336 committed Dec 4, 2023
1 parent 17369d3 commit 293a1d0
Showing 1 changed file with 64 additions and 81 deletions.
145 changes: 64 additions & 81 deletions client/public/templates/questionnaire-template.yaml
Original file line number Diff line number Diff line change
@@ -1,103 +1,86 @@
name: Test questionnaire (SAMPLE)
description: This is a sample questionnaire in YAML format
name: Uploadable Cloud Readiness Questionnaire Template
description: This questionnaire is an example template for assessing cloud readiness. It serves as a guide for users to create and customize their own questionnaire templates.
required: true
sections:
- order: 1
name: Section 1
name: Application Technologies
questions:
- order: 1
text: What is your favorite color?
explanation: Please select your favorite color.
includeFor:
- category: Category1
tag: Tag1
excludeFor: []
text: What is the main technology in your application?
explanation: Identify the main framework or technology used in your application.
answers:
- order: 1
text: Red
risk: red
rationale: Red is a nice color.
text: Quarkus
risk: green
rationale: Quarkus is a modern, container-friendly framework.
mitigation: No mitigation needed.
applyTags: []
autoAnswerFor: [{ category: Category1, tag: Tag1 }]
selected: false
applyTags:
- category: Technology
tag: Quarkus
- order: 2
text: Blue
text: Spring Boot
risk: green
rationale: Blue is a calming color.
mitigation: No mitigation needed.
applyTags: []
autoAnswerFor: []
selected: false
rationale: Spring Boot is versatile and widely used.
mitigation: Ensure container compatibility.
applyTags:
- category: Technology
tag: Spring Boot
- order: 3
text: Legacy Monolithic Application
risk: red
rationale: Legacy monoliths are challenging for cloud adaptation.
mitigation: Consider refactoring into microservices.
applyTags:
- category: Architecture
tag: Monolith
- order: 2
text: What is your favorite sport?
explanation: Please select your favorite sport.
excludeFor:
- category: Category1
tag: Tag1
text: Does your application use a microservices architecture?
explanation: Assess if the application is built using a microservices architecture.
answers:
- order: 1
text: Soccer
risk: red
rationale: There are other sports?
mitigation: Beware of crunching tackles. High risk of injury.
applyTags: []
autoAnswerFor: []
selected: false
text: Yes
risk: green
rationale: Microservices are well-suited for cloud environments.
mitigation: Continue monitoring service dependencies.
applyTags:
- category: Architecture
tag: Microservices
- order: 2
text: Cycling
risk: red
rationale: Correct.
mitigation: High risk of decapitation by car.
applyTags: []
autoAnswerFor: []
selected: false
- order: 3
text: Climbing
text: No
risk: yellow
rationale: Climbing is fun.
mitigation: Slight bit of mitigation needed.
applyTags: []
autoAnswerFor: []
selected: false
- order: 4
text: Swimming
risk: yellow
rationale: Swimming is fun, too.
mitigation: Slight bit of mitigation needed. Drowning can be a problem.
applyTags: []
autoAnswerFor: []
selected: false
- order: 5
text: Running
risk: red
rationale: Oof.
mitigation: Some mitigation required. High risk of injury. Don't run with scissors (or at all).
applyTags: []
autoAnswerFor: []
selected: false
rationale: Non-microservices architectures may face scalability issues.
mitigation: Assess the feasibility of transitioning to microservices.
- order: 3
text: Unknown
risk: unknown
rationale: Lack of clarity on architecture can lead to unplanned issues.
mitigation: Conduct an architectural review.

- order: 3
text: What is your favorite shape?
explanation: Please select your favorite shape.
includeFor:
- category: Category1
tag: Tag1
excludeFor: []
text: Is your application's data storage cloud-optimized?
explanation: Evaluate if the data storage solution is optimized for cloud usage.
answers:
- order: 1
text: Circle
risk: red
selected: false
- order: 2
text: Square
text: Cloud-Native Storage Solution
risk: green
selected: false
rationale: Cloud-native solutions offer scalability and resilience.
mitigation: Ensure regular backups and disaster recovery plans.
- order: 2
text: Traditional On-Premises Storage
risk: red
rationale: Traditional storage might not scale well in the cloud.
mitigation: Explore cloud-based storage solutions.
- order: 3
text: Hybrid Storage Approach
risk: yellow
rationale: Hybrid solutions may have integration complexities.
mitigation: Evaluate and optimize cloud integration points.
thresholds:
red: 5
yellow: 10
red: 1
yellow: 30
unknown: 15
riskMessages:
red: High risk
yellow: Medium risk
green: Low risk
unknown: Unknown risk
red: Requires deep changes in architecture or lifecycle
yellow: Cloud friendly but needs minor changes
green: Cloud Native
unknown: More information needed

0 comments on commit 293a1d0

Please sign in to comment.