IBM Engineering Lifecycle Management (ELM) is an end-to-end engineering solution used to manage system requirements to design, workflow, and test management, extending the functionality of ALM tools for better complex-systems development.
N/A
Sparx Systems Enterprise Architect
Score 6.6 out of 10
N/A
Enterprise Architect is the flagship architecture management platform from global, Australian-headquartered company Sparx Systems.
IBM Engineering Requirements Management DOORS former IBM Rational DOORS profits very much from the mighty market position it had till today. It had been the most favored requirement engineering tools suite with the highest investments in the infrastructure concerning hardware, software, and knowledge sources. It was embedded in knowledge sources of test stands, hardware labs, and knowledge database servers. It allowed for some of the highest profit changes and made the fame with it. But the paradigms of requirements engineering change. If not were superseded by completely different approaches for the target solution worlds. The foremost position in the selling tables is unstable if changes are not solved or coped with by the strategist at IBM and their customers. Since the highly successful alternative suits are already at the market, and some are from IBM already the lifecycle for IBM Engineering Requirements Management DOORS is at the later highs. But the suite is still at the very top and very popular. There are still many problems unsolved and many wishes at the customers to make the use more comfortable and efficient at the overall level. If the time of setting up the software package is passed the adoption get more extended and complicated. There is a lot of work at the stage around and the expertise will be required for a long time from now.
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.
Easy to use with well defined template and user defined fields. New team can setup a project area easily by copying an existing template and adding customized fields for their special needs.
It can be used during almost the whole project cycle and give us a better view and control on the projects.
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.
Wireframes are quite basic. If you need intuitive and interactive wireframes to elaborate the requirements. you probably need to define outside the tool and then upload as image.
ER (define data dictionaries) modeling is not there.
Use case modeling is quite basic. You can visualize the use case and actors relation but the tool does not enforce the rules.
At the moment we are required by contract to continue to use the IBM DOORS software for our current client. Given that it can be expensive, if we were to use it after our current client's needs were met, we would have to secure other projects in order to justify the continued use of the software.
The UI is terrible and not intuitive. Users need training in order to complete tasks. Much like SAP, it's not the clearest tool. The tracing feature is especially complicated because you must write the scripts yourself. There is a learning curve. Also, even the setup, installation, and logging in each time takes a considerable amount of time.
It does a basic job and has the potential to complete some robust reporting tasks, however, it really is a clunky piece of software with a terrible user interface that makes using it routinely quite unpleasant. Many of our legacy and maintenance projects still use DOORS but our department and company use many alternatives and are looking for better tools.
It was easier to do all the change management-related activities, even configurations were handled very effectively. New process definitions and initiatives made it easier for better project deliverables. Effective resource allocations and better reporting and defect management. The overall cost of the tool is great too and well within budget.
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.
