A component in MAIA is a collection of files in a repository, or a collection of other components.
All components share the same base properties:
- Their content is version controlled.
- They are stored in one or more software repositories.
- They contain one or more tracks (branches) for parallel development.
- The events connected to a component can be tracked. For example, commits, issues, issue status changes, builds, deliveries, test executions and changes in component configurations.
- The access to component information is restricted between teams.
A component has properties unique to the component:
- It can contain meta data needed to build a collection of components.
- When a component is built, the content of the build is defined at build time, when the meta data is processed. This allows for dynamic builds.
- If the component is suite, its component can contain both components, suites and suites-of-suites.
A Collection Component (collection) in MAIA has the same properties as any other component described above, with an additional feature to contain identities of other components. When building and examining data for collections in MAIA, information from the "sub" components are aggregated to the collection level.
This powerful ability creates
- the ability for MAIA to present an overall view for information and activities.
- flexibility to create hierarchies of components.
- better support to reuse components.
A composition represents a set of source code, artifacts, documentation and other compositions.
A software composition is the construction of software applications from components that implement abstractions. It is a way of dealing with complexity, but the real benefit of composable software systems lies in their increased flexibility a system built from components should be easy to recompose to address new requirements.
A build is the processed content of a specific component, for example, a component that has been compiled.
The output from a build can be stored as artifacts in an artifact repository or in a file system.
The result of the build is displayed on the Builds: Show page, and if the build is delivered the content of the build is presented in a delivery report.
A build may have test runs and test results registered to it.
MAIA is currently delivered as an ISO-image for easy installation and upgrade.
The image comes in different versions targeting various platforms: CentOS, Ubuntu and Debian.
MAIA Software requires two licenses for normal operation, a server license and user licenses dedicated for the server.
- Per Server: One license for each server installation.
- Per Active User: One license for each activated user in a dedicated server.
Server licenses comes in three levels, Standard, Plus and Enterprise, with different feature sets.
MAIA Software also comes in a bundled starter version. Server and user licenses (5) in a package.
The starter version has a reduced feature set.
MAIA Software has a subscription based license model.
MAIA licensing is subscription based and maintenance is always included.
Support options are:
- Trial and Startup-level -> User forum for registered users. Mail and ticketing support package is available for purchase.
- Standard and Plus -> User forum, mail and ticketing support.
- Enterprise level -> User forum, mail and ticketing, phone support may be available.