Overview
Ansys SCADE ALM Gateway connector for MS-Office demonstrates the usage of Ansys SCADE ALM Gateway based on MS Office documents, avoiding the availability of an external ALM tool:
It imports requirements from MS-Word documents
It produces traceability matrices as MS-Excel documents
It is also a usage example of Ansys SCADE ALM Gateway Python Toolbox.
Requirements
The ansys-scade-almgw-msoffice package supports only the versions of Python delivered with Ansys SCADE, starting from 2021 R2:
2021 R2 through 2023 R1: Python 3.7
2023 R2 through 2025 R2: Python 3.10
2026 R1 and later: Python 3.12
Ansys SCADE ALM Gateway connector for MS-Office has two installation modes: user and developer. To install for use, see Getting started. To install for development, see Contribute.
Documentation and issues
Documentation for the latest stable release of Ansys SCADE ALM Gateway connector for MS-Office is hosted at Ansys SCADE ALM Gateway connector for MS-Office documentation.
In the upper right corner of the documentation’s title bar, there is an option for switching from viewing the documentation for the latest stable release to viewing the documentation for the development version or previously released versions.
On the Ansys SCADE ALM Gateway connector for MS-Office Issues page, you can create issues to report bugs and request new features. On the Discussions page on the Ansys Developer portal, you can post questions, share ideas, and get community feedback.
License
Ansys SCADE ALM Gateway connector for MS-Office is licensed under the MIT license.
This toolkit makes no commercial claim over Ansys whatsoever. The use of this toolkit requires a legally licensed copy of the Ansys SCADE Suite. For more information, see the Ansys SCADE Suite page on the Ansys website.
1 maintainer
Release files for ansys-scade-almgw-msoffice 3.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ansys_scade_almgw_msoffice-3.2.0.tar.gz | 23.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansys_scade_almgw_msoffice-3.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 56.3 kB
Release files / ansys_scade_almgw_msoffice-3.2.0.tar.gz
| Download URL | ansys_scade_almgw_msoffice-3.2.0.tar.gz |
|---|---|
| Size | 23.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab49c719d77976b075868d6f8ec9ba29ae09a4b5250c78ed8c31f5bc2b855c4c
|
|
BLAKE2b-256 checksum How to use checksums |
6c6a2dd66f3b4001809921ce4397d32c323dabd5b3f42517a8dc1d0446c1c83f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 20, 2026.
Transparency logRelease files / ansys_scade_almgw_msoffice-3.2.0-py3-none-any.whl
| Download URL | ansys_scade_almgw_msoffice-3.2.0-py3-none-any.whl |
|---|---|
| Size | 32.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ffec84715316926de52e4b782272a63596f531d8a3e823ee45bfa6275657915f
|
|
BLAKE2b-256 checksum How to use checksums |
e15063bee0e0c474c2acad353beb74b47ae06a07ab45ec97e3f9564560d3d031
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 20, 2026.
Transparency log
