When people think of Sparx Enterprise Architect they often think it’s a tool just for architects. Tom O’Reilly, the COO of Sparx Systems, explored how Sparx’s features serve much more than just that. Kanban boards, requirements management features such as reuse, and complemented by EA’s robust modeling capabilities support BA practices. The ability to integrate application and product requirements, architecture, and design artifacts in a single tool breaks down the silos between practices. Sparx ensures traceability requirements and related information that users can present with views that are readily tailored to the audience.
Every IT organization needs an integrated toolchain to manage delivery of valuable software. Tools such as EA that serve multiple aspects of the delivery lifecycle allow you to simplify your integrations and reduce costs on IT tooling. In my previous experience implementing and rolling out EA for architects and BAs, the tool works well as a one-stop shop for requirements, analysis, and design collaboration. The breadth of features also means that IT leaders must invest in building an integrated practice that spans different professionals and educate their teams on how to use Sparx EA as part of that practice. In addition, Sparx EA must be integrated with your downstream build and deploy software in order to manage the whole delivery process effectively.
If you’re interested in Sparx you can find out more at SoftwareReviews.
Info-Tech’s Modernize Your SDLC, Transition to Product Delivery, and Build a Strong Approach to Business Requirements Gathering blueprints have the information and exercises to help you define the practices you need to complement a product or requirements management tool implementation.
These are the trends we predict will be most important is it relates to Enterprise Architecture in 2021.
Lean IX and Apptio have partnered to produce an integrated solution that better informs the strategic decision-making process with improved visibility into an application’s total cost of ownership and alignment to business capabilities.
From the business architecture perspective, agility is the ability to quickly change structurally and operationally to react to external changes or to create new business value. Enterprise architecture comprises business and service/application architecture – therefore, it needs to provide an environment for harmonized agility at each level.
This note outlines some of the fundamental KPIs that you should measure to show the success of the enterprise architecture team. It also discusses how you measure them and visualize the result.
The application portfolio management (APM) tool space can be a confusing one, as many software vendors offer their own take of what APM is. Enterprise architecture, application management and project portfolio management tools offer an APM use case, but these are often quite skewed the primary function of the tool.
Application rationalization fails when the chosen framework does not match your scenario or the goals for your application portfolio. This note looks at how to apply application rationalization during an M&A.
Many vendors suggest application rationalization is quick and easy. It isn’t. This claim does you a disservice and most importantly they’ve missed the point. Rationalization as part of a continuous application portfolio management function is about becoming a driver of the business.
Often people misidentify the purpose of application rationalization, leading to misuse and unsatisfactory results. We try to break application rationalization down to its simplest form to understand how to make the most of this critical IT function. tr
Measuring technical debt is important, but more important is communicating the implications of this problem in terms of risk to business capabilities. Cast Highlight tools are used for application portfolio management (APM), specializing in applying code analytics to business decisions regarding your organization’s applications.