it really depends where you are heading to. Do you want to document a software project? Or are you trying to document a business requirement? ARIS is all about documenting the as-is and to-be state. We also got some specific requirements management models, which you might want to check out. Also, pay attention to the capability object, which can be used to model what someone needs (i.e. requirements) and what someone else is able to offer (e.g. a service).
I can comment on point 2 on how we created Functional specs:
What we did was to create FADs from the inscope function objects on the EPCs - from the screen object create an assignment to a screen navigation and then to a screen design.
Also reuse the inscope functions on a UML use case model and create the dialog of the functions in a UML Activity Diagram
The Action States from the UML Activity Diagrams were then reused on the screen design (basically were it all comes together then)
Our scripted solution then generated a functional spec from these models and attributes
We used a similar script and more UML models to create the technical specs
Yes, I'm keen on seeing an example on using ARIS throughout a software implementation/ upgrade project.
I've seen some model types for UML, Project Timeline, etc. But want to know how to string it all together from a project perspective. Also, if there were standard reports that could tie all this in to create project documents.
My vision is to use ARIS during Plan & Design phases of the project. Some things that I want to try are mentioned below.
1. The Business Analysts (BAs) model Business Requirements (BR) as high level conceptual requirements in ARIS.
2. The BAs decompose the BRs with more specific Functional Requirements (FRs) using UML Use Cases.
3. BAs run a report to generate a document linking BRs to FRs for the business users to sign off.
4. BAs run a report to generate a details FR document to hand over to Technical Analysts (TAs)
5. The TAs then use these Use Cases & FR document to develop Sequence Diagrams, Activity Diagrams, Applications Landscapes, Integration Views, Data Models, Network Diagrams etc.
It would be great if we can see an example of how this all ties in together within the ARIS toolset.
@Anita: Thank you! This sounds fantastic. It would be great if we can see a graphical model depicting these corelations.
this reminds me that I wanted to ask one of our delivery managers to write an article how we use internally ARIS to plan ARIS releases and development resources. Here is a short summary:
- each team collects the user stories in some kind of backlog
- on a quarterly basis, user stories are selected for realisation
- this also includes estimating them
- this gives us a good portfolio planning so that we know what we are working on and what needs to be delayed
- each developer, tech doc writer, requirements engineer, etc. have to record the amount of days spent on a user story
- a MashZone dashboard is provided to visualise progress
So we mainly use ARIS for portfolio planning and for tracking progress. Besides, we have automated the requirements roll-in process using ARIS Process Governance. This process is run each time a customer or consultant raises the need for a new feature.
In the past, I have used ARIS also for gathering and structuring requirements using the requirements object. You can create a work breakdown structure and link requirements to projects.
Personally, I have not used ARIS to further refine requirements. Of course, you can assign use-case diagrams, process models, etc. to requirements. The concrete method used heavily depends on what you want to cover and what you want to keep in text documents or other systems.
I like to develop a software requirment project in ARIS. Could please share any docments or sites for the clear understanding..