Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Sparx Systems Enterprise Architect
Score 6.3 out of 10
N/A
Enterprise Architect is the flagship architecture management platform from global, Australian-headquartered company Sparx Systems.
$229
per license
Pricing
Azure DevOps
Sparx Systems Enterprise Architect
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
I have used Orbus iServer. EA compares well with iServer, though iServer is a very useful cloud service that allows access from many locations. Licensing costs of iServer are very favourable compared to EA for a larger number of users.
Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.
Enterprise Architect can be used to capture business requirements, design and management of all successive models, algorithms, process flows/workflows, design of business data objects and other artifacts. The strong point is the ability to link the items in all models with each other, the more time the analysts and designers "invest" into making nice and clearly defined models, the higher the future pay-off by any successive changes to the systems. Enterprise Architect is not a good tool for capturing rather unstructured business requirements, use e.g. Confluence or other solutions instead. EA should comprise the extracted models with very little unstructured information. Management of the changes process should not be done in Enterprise Architect, rather use JIRA/Confluence or similar.
Open Architecture - A wide and extensive set of options, plug-ins and customization options make Sparx EA more of a tool kit than just a tool. Most tools allow customization but Sparx EA is built from the ground up with this in mind.
Wide variety of formats, lexicons, standards and data import export capabilities allow different roles to interact with the information in different ways.
Automated report generation allows architects and designers to spend less taking on word processing and more time on performing architecture and design.
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
BiZZdesign represents a different new concept to enterprise architecture, its gravity center is not technical modelling, but rather a view on capturing the whole end-user experience or customer journey. It also allows to grasp areas as internal company capabilities, required for adoption/changes and operation of the solution, uses the same Archimate modelling language. This solution is in my opinion a new generation enabling to not only design the solutions, but also manage the whole application portfolio with respect to capabilities and requirement parameters.
We have saved a ton of time not calculating metrics by hand.
We no longer spend time writing out cards during planning, it goes straight to the board.
We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.