A bunch of scripts made with love, to take advantage of archimate models on Archi, with the aim of:
- Perform analysis of an enterprise architecture modeled using archimate.
- Communicate in a graphic way key aspects of an enterprise architecture, like technology risk or functional coverage.
- Accelerate the execution of common task while govern enterprise architecture using archimate.
Knowledge, teaching and learning are at the heart of Ingenia’s DNA. Being an Ingenial means forming part of a crew with a passion for problem solving.
At the core of our work process are people and collaboration, both of which we value above hierarchies and roles. An understanding of constant change and active learning form the basis of what we do. We believe in the dynamism of the team and the individual above procedures. Our aim is the constant search for new knowledge to enable us to support our clients with solutions that take them to the next level.
- Create or upload files
- Add files using the command line or push an existing Git repository with the following command:
cd existing_repo
git remote add origin https://gitlab.com/ingeniaca/open-ingenia/jarchi-scripts.git
git branch -M main
git push -uf origin main
This scripts run on Archi, using the jArchi plugin. Follow the defined steps to install the tool and the plugin.
This isn’t an exhaustive list of things that you can or can't do. Rather, take it in the spirit in which it’s intended - a guide to make it easier to enrich all of us and the technical communities in which we participate.
- Be friendly and patient.
- Be welcoming. We welcomes and supports people of all backgrounds and identities. This includes, but is not limited to members of any race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.
- Be considerate. Your work will be used by other people, and you in turn will depend on the work of others.
- Be respectful. Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners.
- Be careful in the words that you choose. We are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants.
- When we disagree, try to understand why. Disagreements, both social and technical, happen all the time. It is important that we resolve disagreements and differing views constructively.
### Before submitting a Pull Request If your planned contribution is to provide a new feature please present it by opening a new issue. This way we can discuss how, or if, it will fit into the roadmap. It may be that the feature will fit into another proposal or is dependent on some other feature or fix.
For all practical purposes, the jArchi-script project follows standard GitHub procedures. To contribute code, you would usually perform the following steps.
- Fork the Archi project
- Clone your new fork to your own PC & configure a remote
- Create a feature branch
- Make the changes to the code/docs you wish to make (test as needed).
- Commit the changes to your local clone
- Push the changes to your forked repository on GitHub
- Create a Draft Pull Request for the feature branch
If you have any doubt or suggestions, please send an email to enterprisearchitects@ingenia.la.