<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1907245749562386&amp;ev=PageView&amp;noscript=1">

The Leonardo Blog

All Posts

Bringing together project requirements in ARIS

We all agree it is important to monitor, track and report on the ‘common theme’ that runs through IT projects – such as implementing or developing a new system from initiation stage to rollout and implementation phase. In this article, we discuss how the requirements and artefacts – use cases, functional specifications, technical specifications and prototypes – can be managed effectively during the project’s life cycle.

The concept of monitoring these artefacts from ‘cradle to grave’ (inception to implementation), leads to a myriad of questions:

  1. Is it possible to manage all these documents, spreadsheets, artefacts, and deliverables in a central place?
  2. How can we follow the ‘common theme’ from use case to functional specification to technical specification?
  3. How can we track, monitor and manage them in a central repository?
  4. How do we version, minor and major, and track changes?
  5. How can we re-use these and make them available to other projects?
  6. How do we ensure ‘a single version of the truth’?
  7. How do we re-use architectural artefacts (organisational structures, application systems, etc.)?
  8. How can we manage central libraries of governance, risk, requirements and controls?
  9. Is there the ability to govern access to this information?

The Project Management monster and its artefacts!

During an IT project’s life cycle, numerous tasks and activities are facilitated and managed. These may include, but are not limited to:

  • Management approval, which is obtained by signing off on business cases, as well as functional and technical
  • Business and technical
  • Design review – by validating the wireframes (ARIS/OBPA screen navigation and screen design diagrams).
  • Software development and programming – the system/user interaction and expected sequence result are further annotated in UML activity
  • Documentation and training – user and

Risk is mitigated by maintaining complete records of project activities in a central repository, and providing a periodic review of project activities and artefacts.

Bringing it all together

These project requirements can successfully be hosted in tools such as ARIS.

From the UML Use Case diagram:


This illustrates the processes and represents the business system under analysis. The UML Use Case diagram defines the scope of the project, and is the root of the functional decomposition at the conceptual level of detail.

New Call-to-action

Related Posts

Leonardo wins 2020 Red Hat ANZ Professional Services Partner of the Year

Red Hat announced Leonardo as their 'ANZ Professional Services Partner of the Year'. This is the third year in a row Leonardo has been recognised at these regional awards, and we're extremely honoured again for this acknowledgement. Well done to Team Leonardo for your superb work delivering great outcomes for clients - and to Red Hat Asia Pacific for their amazing partner growth and results over the past year.

Leonardo Invests in Apromore to advance AI-Driven, Open-Source Process Mining Technology

MELBOURNE, AUSTRALIA – 7 July 2020 – Leonardo today announced its investment in Apromore - a leading developer of open-source, AI-driven process mining technology. The investment forms part of a Series A round of funding totalling $A6.8 million, led by German business process management specialist GBTEC, and also included The University of Melbourne, which helped to incubate Apromore prior to spin off.

Leonardo wins 2019 Red Hat Hackathon - Customer Experience with OpenSource

      We're thrilled to share with you that Leonardo has won 2019 Red Hat Hackathon 'ReBoot Customer Experience with Open Source'. Early on Friday morning ( 5am AEDT 13th December 2019),  Leonardo awarded first place from a field that included 320 participants from across the globe.  The Hackathon's brief was to reinvent customer experience using Open Source. Providing an outstanding customer experience that customers actually love is especially challenging in more traditional industries like banking, insurance, telecommunication, public sector/government, healthcare, manufacturing, or transportation. These markets offer great opportunities for change and disruption as has been shown by many examples such as Uber disrupting transportation, Twilio disrupting telcos and Stripe or Transferwise disrupting banking.  We want you to be the next disrupter who creates a customer experience that users actually love.  An Open Source solution - ACE  Airline Customer Experience Our project is an application using a Red Hat Process Automation Manager process-as-microservice developed for "ACE Airlines", our fictional client (see video above for the demo). It communicates personalised, event-driven (gate change, delay, etc.) messages to passengers in the language of their choice, using their preferred communications type (SMS, push notification, email).