Skip to content

Commit aa36416

Browse files
committed
docs: formatting changes
1 parent 12907b4 commit aa36416

File tree

7 files changed

+160
-94
lines changed

7 files changed

+160
-94
lines changed

docs/templates/software-requirements-specification.md.j2

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ The containers may be used both for local development and continuous integration
5353
{%- for aspect_id, aspect in sbdl.items() %}
5454
{%- if aspect.type == 'aspect' %}
5555

56-
## {{ reencode(strip_gherkin_prefix(aspect_id)) | title }}
56+
## {{ reencode(strip_gherkin_prefix(aspect['custom:title'])) }}
5757

5858
{{ reencode(aspect.description) }}
5959

test/cpp/features/compatibility.feature

Lines changed: 17 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -29,16 +29,15 @@ Feature: Compatibility
2929
req-compat-0002 is requirement {
3030
custom:title is "[@-LINE]"
3131
description is
32-
"amp-devcontainer *SHALL* be compatible with both the x86-64 (AMD64)
33-
*and* AArch64 (ARM64) host architectures."
32+
"amp-devcontainer *SHALL* be compatible with both the x86-64 (AMD64) *and* AArch64 (ARM64)
33+
host architectures."
3434
remark is
35-
"Supporting both x86-64 and AArch64 has several advantages:
35+
"Supporting both x86-64 and AArch64 has several advantages:\n\n
3636
37-
- Increasing usability on a wide range of host machines,
38-
from PC hardware using the x86-64 architecture to
39-
Apple Silicon using the AArch64 architecture
40-
- Unlocking the power efficiency of the AArch64 architecture,
41-
potentially reducing energy consumption and cost for metered ci-systems"
37+
- Increasing usability on a wide range of host machines, from PC hardware using the x86-64
38+
architecture to Apple Silicon using the AArch64 architecture\n
39+
- Unlocking the power efficiency of the AArch64 architecture, potentially reducing energy
40+
consumption and cost for metered ci-systems"
4241
}
4342
# @sbdl-end
4443

@@ -50,11 +49,11 @@ Feature: Compatibility
5049
"amp-devcontainer *SHOULD* be compatible with [VS Code](https://code.visualstudio.com/)
5150
*and* [GitHub Codespaces](https://github.com/features/codespaces)."
5251
remark is
53-
"It should be possible to use amp-devcontainer and all of its features in both VS Code
54-
and GitHub Codespaces with minimal effort. Where minimal effort means: with the least
55-
amount of additional set-up, user intervention or configuration for all functionality
56-
that is provided by amp-devcontainer. Features and functions should work \"out-of-the-box\"
57-
without being overly opinionated."
52+
"It should be possible to use amp-devcontainer and all of its features in both VS Code and
53+
GitHub Codespaces with minimal effort. Where minimal effort means: with the least amount of
54+
additional set-up, user intervention or configuration for all functionality that is
55+
provided by amp-devcontainer. Features and functions should work \"out-of-the-box\" without
56+
being overly opinionated."
5857
}
5958
# @sbdl-end
6059

@@ -66,11 +65,10 @@ Feature: Compatibility
6665
"amp-devcontainer *SHOULD* support seamless integration with
6766
[GitHub Actions](https://github.com/features/actions) without additional configuration."
6867
remark is
69-
"Seamless integration with GitHub Actions allows users to easily incorporate
70-
amp-devcontainer into their ci/cd workflows. This integration helps automate
71-
the build, test, and deployment processes, improving efficiency and reducing
72-
manual errors. By minimizing the need for additional configuration, users can
73-
quickly set up and start using amp-devcontainer in their GitHub Actions workflows,
74-
enhancing their overall development experience."
68+
"Seamless integration with GitHub Actions allows users to easily incorporate amp-devcontainer
69+
into their ci/cd workflows. This integration helps automate the build, test, and deployment
70+
processes, improving efficiency and reducing manual errors. By minimizing the need for
71+
additional configuration, users can quickly set up and start using amp-devcontainer in their
72+
GitHub Actions workflows, enhancing their overall development experience."
7573
}
7674
# @sbdl-end

test/cpp/features/compilation.feature

Lines changed: 31 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -16,10 +16,16 @@ Feature: Compilation
1616
req-comp-0001 is requirement {
1717
custom:title is "[@-LINE]"
1818
description is
19-
"amp-devcontainer *SHALL* be able to compile valid source code into a working executable targeting the container host architecture and operating system."
19+
"amp-devcontainer *SHALL* be able to compile valid source code into a
20+
working executable targeting the container host architecture and operating system."
2021
remark is
21-
"Compiling valid source code into working software, able to run on the container host architecture and operating system,
22-
can be necessary in several scenarios; for example when:\n\n- the container host is the deployment target\n- running tests on the container host\n- building plug-ins, extensions, code generators, or other additional tools that need to run on the container host"
22+
"Compiling valid source code into working software, able to run on the container host
23+
architecture and operating system, can be necessary in several scenarios; for example when:\n\n
24+
25+
- the container host is the deployment target\n
26+
- running tests on the container host\n
27+
- building plug-ins, extensions, code generators, or other additional tools that need to
28+
run on the container host"
2329
}
2430
# @sbdl-end
2531

@@ -35,11 +41,12 @@ Feature: Compilation
3541
req-comp-0002 is requirement {
3642
custom:title is "[@-LINE]"
3743
description is
38-
"amp-devcontainer *SHOULD* be able to compile valid source-code into a working ELF executable targeting the ARM Cortex architecture."
44+
"amp-devcontainer *SHOULD* be able to compile valid source-code into a working ELF
45+
executable targeting the ARM Cortex architecture."
3946
remark is
40-
"Compiling valid source-code into working ELF executables, able to run on the ARM Cortex architecture,
41-
is a primary function for amp-devcontainer. It enables building firmware for micro-controllers based
42-
on the ARM Cortex architecture."
47+
"Compiling valid source-code into working ELF executables, able to run on the ARM Cortex
48+
architecture, is a primary function for amp-devcontainer. It enables building firmware for
49+
micro-controllers based on the ARM Cortex architecture."
4350
}
4451
# @sbdl-end
4552

@@ -48,9 +55,15 @@ Feature: Compilation
4855
req-comp-0003 is requirement {
4956
custom:title is "[@-LINE]"
5057
description is
51-
"amp-devcontainer *SHOULD* be able to compile valid source-code into a working executable targeting the Microsoft® Windows operating system."
58+
"amp-devcontainer *SHOULD* be able to compile valid source-code into a working executable
59+
targeting the Microsoft® Windows operating system."
5260
remark is
53-
"Compiling valid source-code into working executables, able to run on the Microsoft® Windows operating system, can be necessary in several scenarios e.g.\n\n- Cross platform code is written and needs to be compiled and deployed\n- Executables needs to be deployed outside of container context to a host running the Microsoft® Windows operating system"
61+
"Compiling valid source-code into working executables, able to run on the Microsoft® Windows
62+
operating system, can be necessary in several scenarios e.g.\n\n
63+
64+
- Cross platform code is written and needs to be compiled and deployed\n
65+
- Executables needs to be deployed outside of container context to a host running the
66+
Microsoft® Windows operating system"
5467
}
5568
# @sbdl-end
5669

@@ -59,8 +72,15 @@ Feature: Compilation
5972
req-comp-0004 is requirement {
6073
custom:title is "[@-LINE]"
6174
description is
62-
"amp-devcontainer *MAY* be able to cache the results of a compilation to speed-up subsequent compilations."
75+
"amp-devcontainer *MAY* be able to cache the results of a compilation to speed-up subsequent
76+
compilations."
6377
remark is
64-
"Maintaining a compilation cache can be useful in both local and ci development scenarios. A compilation cache can provide benefits like:\n\n- Reduce developer waiting time and context switches, [maintaining flow-state](https://azure.microsoft.com/en-us/blog/quantifying-the-impact-of-developer-experience/)\n- Reduce CPU usage at the cost of more storage usage, potentially reducing energy consumption and cost for metered ci-systems"
78+
"Maintaining a compilation cache can be useful in both local and ci development scenarios.
79+
A compilation cache can provide benefits like:\n\n
80+
81+
- Reduce developer waiting time and context switches,
82+
[maintaining flow-state](https://azure.microsoft.com/en-us/blog/quantifying-the-impact-of-developer-experience/)\n
83+
- Reduce CPU usage at the cost of more storage usage, potentially reducing energy
84+
consumption and cost for metered ci-systems"
6585
}
6686
# @sbdl-end

test/cpp/features/debugging.feature

Lines changed: 18 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -16,12 +16,16 @@ Feature: Debugging
1616
req-debug-0001 is requirement {
1717
custom:title is "[@-LINE]"
1818
description is
19-
"amp-devcontainer *SHALL* provide debugging support for the primary programming language(s) used within the container."
19+
"amp-devcontainer *SHALL* provide debugging support for the primary programming language(s)
20+
used within the container."
2021
remark is
21-
"Providing debugging support within the development environment enhances the developer experience and productivity.
22-
It allows developers to efficiently identify and resolve issues in their code by setting breakpoints, inspecting variables, and stepping through code execution.
23-
This capability is essential for diagnosing complex problems, understanding code flow, and ensuring the correctness of software.
24-
By having integrated debugging tools, developers can streamline their workflow and reduce the time spent on troubleshooting and fixing bugs."
22+
"Providing debugging support within the development environment enhances the developer
23+
experience and productivity. It allows developers to efficiently identify and resolve
24+
issues in their code by setting breakpoints, inspecting variables, and stepping through
25+
code execution. This capability is essential for diagnosing complex problems, understanding
26+
code flow, and ensuring the correctness of software. By having integrated debugging tools,
27+
developers can streamline their workflow and reduce the time spent on troubleshooting and
28+
fixing bugs."
2529
}
2630
# @sbdl-end
2731

@@ -30,11 +34,15 @@ Feature: Debugging
3034
req-debug-0002 is requirement {
3135
custom:title is "[@-LINE]"
3236
description is
33-
"amp-devcontainer *MAY* provide tools to upload compiled firmware to a connected micro-controller."
37+
"amp-devcontainer *MAY* provide tools to upload compiled firmware to a connected
38+
micro-controller."
3439
remark is
35-
"Providing tools to upload compiled firmware to a connected micro-controller enhances the development workflow for embedded systems.
36-
It allows developers to quickly and easily transfer their compiled code to the target hardware for testing and debugging.
37-
This capability is essential for validating the functionality of the firmware on the actual device, ensuring that it behaves as expected in real-world scenarios.
38-
By having integrated tools for firmware upload, developers can streamline their workflow, reduce manual steps, and improve overall productivity when working with micro-controllers."
40+
"Providing tools to upload compiled firmware to a connected micro-controller enhances the
41+
development workflow for embedded systems. It allows developers to quickly and easily
42+
transfer their compiled code to the target hardware for testing and debugging. This
43+
capability is essential for validating the functionality of the firmware on the actual
44+
device, ensuring that it behaves as expected in real-world scenarios. By having integrated
45+
tools for firmware upload, developers can streamline their workflow, reduce manual steps,
46+
and improve overall productivity when working with micro-controllers."
3947
}
4048
# @sbdl-end

test/cpp/features/maintainability.feature

Lines changed: 33 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,11 @@ Feature: Maintainability
1818
description is
1919
"amp-devcontainer *SHOULD* contain up-to-date tools and dependencies."
2020
remark is
21-
"Keeping tools and dependencies up-to-date helps ensure that the development environment remains secure, stable, and compatible with the latest technologies.
22-
It also helps prevent issues related to deprecated or unsupported software versions, reducing maintenance overhead and improving overall developer productivity.
23-
Regular updates can also introduce new features and improvements that enhance the development experience."
21+
"Keeping tools and dependencies up-to-date helps ensure that the development environment
22+
remains secure, stable, and compatible with the latest technologies. It also helps prevent
23+
issues related to deprecated or unsupported software versions, reducing maintenance overhead
24+
and improving overall developer productivity. Regular updates can also introduce new
25+
features and improvements that enhance the development experience."
2426
}
2527
# @sbdl-end
2628

@@ -29,11 +31,15 @@ Feature: Maintainability
2931
req-maint-0002 is requirement {
3032
custom:title is "[@-LINE]"
3133
description is
32-
"amp-devcontainer *SHOULD* provide support for automatic updates when consumed as a dependency."
34+
"amp-devcontainer *SHOULD* provide support for automatic updates when consumed as a
35+
dependency."
3336
remark is
34-
"Providing support for automatic updates when amp-devcontainer is consumed as a dependency helps ensure that users always have access to the latest features, bug fixes, and security patches.
35-
This reduces the maintenance burden on users, as they do not need to manually track and apply updates.
36-
Automatic updates can also help ensure compatibility with other dependencies and tools, improving the overall stability and reliability of the development environment."
37+
"Providing support for automatic updates when amp-devcontainer is consumed as a dependency
38+
helps ensure that users always have access to the latest features, bug fixes, and security
39+
patches. This reduces the maintenance burden on users, as they do not need to manually
40+
track and apply updates. Automatic updates can also help ensure compatibility with other
41+
dependencies and tools, improving the overall stability and reliability of the development
42+
environment."
3743
}
3844
# @sbdl-end
3945

@@ -42,10 +48,14 @@ Feature: Maintainability
4248
req-maint-0003 is requirement {
4349
custom:title is "[@-LINE]"
4450
description is
45-
"amp-devcontainer *SHOULD* provide re-usable building blocks to enable building, publishing and testing derived containers."
51+
"amp-devcontainer *SHOULD* provide re-usable building blocks to enable building, publishing
52+
and testing derived containers."
4653
remark is
47-
"Providing re-usable building blocks for building, publishing and testing derived containers reduces duplication, and ensures consistent application of practices.
48-
Derived containers (i.e. containers using amp-devcontainer as a base for further extension) should be able to build, push and test in the same way that amp-devcontainer does, without the need to duplicate the build system."
54+
"Providing re-usable building blocks for building, publishing and testing derived containers
55+
reduces duplication, and ensures consistent application of practices. Derived containers
56+
(i.e. containers using amp-devcontainer as a base for further extension) should be able to
57+
build, push and test in the same way that amp-devcontainer does, without the need to
58+
duplicate the build system."
4959
}
5060
# @sbdl-end
5161

@@ -56,9 +66,12 @@ Feature: Maintainability
5666
description is
5767
"amp-devcontainer *SHOULD* document its architectural decisions."
5868
remark is
59-
"Documenting architectural decisions helps provide context and rationale for the design choices made in the development environment.
60-
This information can be valuable for future maintainers, as it helps them understand the reasoning behind certain implementations and can guide them in making informed decisions when modifying or extending the environment.
61-
Clear documentation of architectural decisions can also facilitate collaboration among team members and improve overall maintainability."
69+
"Documenting architectural decisions helps provide context and rationale for the design
70+
choices made in the development environment. This information can be valuable for future
71+
maintainers, as it helps them understand the reasoning behind certain implementations and
72+
can guide them in making informed decisions when modifying or extending the environment.
73+
Clear documentation of architectural decisions can also facilitate collaboration among team
74+
members and improve overall maintainability."
6275
}
6376
# @sbdl-end
6477

@@ -67,15 +80,13 @@ Feature: Maintainability
6780
req-maint-0005 is requirement {
6881
custom:title is "[@-LINE]"
6982
description is
70-
"amp-devcontainer *SHOULD* aim to keep its container image size as small as possible without compromising functionality."
83+
"amp-devcontainer *SHOULD* aim to keep its container image size as small as possible without
84+
compromising functionality."
7185
remark is
72-
"Keeping the container image size small helps improve performance, reduce resource consumption, and minimize the time required to download and deploy the development environment.
73-
A smaller image size can also help reduce storage costs and improve scalability, particularly in cloud-based environments.
74-
By optimizing the container image size, amp-devcontainer can provide a more efficient and user-friendly experience for developers."
86+
"Keeping the container image size small helps improve performance, reduce resource
87+
consumption, and minimize the time required to download and deploy the development
88+
environment. A smaller image size can also help reduce storage costs and improve scalability,
89+
particularly in cloud-based environments. By optimizing the container image size,
90+
amp-devcontainer can provide a more efficient and user-friendly experience for developers."
7591
}
7692
# @sbdl-end
77-
78-
<acceptance-criteria>
79-
- The container image size is monitored.
80-
- The compressed image size is kept below 1 GiB.
81-
</acceptance-criteria>

0 commit comments

Comments
 (0)