SDE Navigation

The URL to the SDE environment is accessible only after the invitation process, which requires setting up multi-factor authentication, is completed.

When connecting to the SDE URL, the following screens appear:

• Azure DevOps landing page: The visible implementation project represents where the project team customizes Aras Innovator for subscribers.

• Azure DevOps Structure: Displays required information.

• Dashboards: Scrum masters use these to track project progress for team members’ Views. A link is provided for traceability between change management and implementation.

• Analytics Views and Wiki Page: The team project Wiki is a platform for sharing information with other team members. Provisioning a Wiki from scratch initiates a new Git Repository that stores Markdown files, images, attachments, and a sequence of pages. The Wiki can support collaborative editing of both its content and structure. Aras uses Wiki to share the URLs of SIT test instances.

• Work Items: These Items are required for approved changes. This may encompass other tasks necessitated by the project or the tracking of requests made to Aras.

• Work Item Structure: Azure DevOps manages the process according to the definition set by Aras Global Cloud Services (GCS). GCS continually updates the process to address subscriber input and feedback. The current Agile Solution Delivery version is 4.1.

• Boards: The Boards can track various Work Items, including features, user stories, tasks, bugs, etc. They support both Scrum and Kanban methodologies. Additionally, the Boards include capabilities for planning Sprint, managing Backlogs, and generating reports on work progress.

• Backlogs: Backlogs in Azure DevOps are used to manage and prioritize Work Items in a queue. They provide an ordered list of Work Items, such as user stories, features, or bugs that the team needs to work on.

• Sprints: Sprints in Azure DevOps represent time-boxed iterations where a set amount of work is completed.

• Queries: Queries enable users to filter Work Items within or across projects for listing, updating, or sharing Work Items.

• Repos: There is only one main configuration Repo per project for the Standard Development Environment. Notice the orange and white backgrounds of the Git logo. The white background repositories are Forks.

• Files, Commits, and Pushes: In Azure DevOps, Files are the individual project components, Commits are snapshots of changes made to those files, and Pushes are the action of uploading these Commits to a Remote Repository for team access and collaboration.

• Branches, Tags, and Pull Request: In Azure DevOps, Branches are separate versions of the codebase for isolated development, Tags are reference points to specific versions of the code, and a Pull request is a mechanism for developers to propose, review, and merge changes from one Branch to another.

• Pipelines: Pipelines in Azure DevOps are automated workflows for Continuous Integration and Delivery, enabling code build, test, and deployment processes.

• Test Plans: Test Plans in Azure DevOps provide a structured approach for defining, tracking, and managing testing activities to ensure software quality.

• Progress Reports and Runs: Progress Reports in Azure DevOps provide insights into the development lifecycle and project milestones, while Runs represent individual executions of tests, builds, or deployments.

• Baselines and Artifacts: Baselines in Azure DevOps represent specific versions of the project for comparison or recovery, while Artifacts are the output files generated from build and release Pipelines.