Prolaborate User Guides: Administrator Guide

[Pages:67]Prolaborate Guide - Administrators

Prolaborate User Guides:

Administrator Guide

Document Version: 0.6 Date 09 Feb 2017 Author: Ian Mitchell, Prolaborate Sales & Support, ian@ Release Notes: This is a draft of the Prolaborate User Guide for Administrators which will eventually be delivered via the website. This draft is for the short-term use of KPMG only, who will be informed once the production version is available.

1 ? Prolaborate 2017

Prolaborate Guide - Administrators

2 ? Prolaborate 2017

Prolaborate Guide - Administrators

Contents

3 ? Prolaborate 2017

Prolaborate Guide - Administrators

Decision 1: Guide to this Guide

This guide is designed to help you use Prolaborate to give users access to your Sparx Enterprise Architect (EA) models. It describes, for each area:

1. The decisions you need to make about how to setup Prolaborate, These sections will set out the options which Prolaborate offers, plus some advice on best practice for getting the most out of Prolaborate, based on our experience in real-world implementations.

2. Detailed instructions on how to implement your decisions in Prolaborate. This will show you in detail how to use the Administrator features of Prolaborate.

1.1 Decisions

We'll present these decisions in a sequence, which is just the order in which we think is most helpful.

Decision 2: - Decisions will look like this

In reality, you may be driven by, for example, the needs of a particular user group, or the needs of a specific project, so you may make the decisions in a different order. For each decision, we'll suggest an approach, like this:

Models and Repositories

Here you will decide which of your EA models Prolaborate users are able to see. If you have everything in one big EA model, this is easy! But even then, there are a few tricks you can use to make Prolaborate even more useful.

Sections

Once you've decided which models Prolaborate can see, you need to look inside those models, and decide the granularity of access.

Users

Create users, and make those users belong to groups. Then you're ready for...

4 ? Prolaborate 2017

Prolaborate Guide - Administrators Access Permissions Access permissions link users/groups to Sections, and say who can do what. Profiles and views (this section will not be completed until later. This deals with why & how to change the Prolaborate Profiles for models and users, to deliver a more customised user experience.

5 ? Prolaborate 2017

Prolaborate Guide - Administrators

Decision 3: Models and Repositories

Here you will decide which of your EA models Prolaborate users are able to see. If you have everything in one big EA model, this is easy! But even then, there are a few tricks you can use to make Prolaborate even more useful.

3.1 Features & Decisions Decision 4: - Location and connectivity of EA Repository

EA users have lots of choices about where they store their EA data: local EAP files, shared EAP files or shared databases, and Prolaborate supports all those choices:

So you can connect to an EAP file, either on the same server as Prolaborate or remote (not shown on diagram), though

these don't perform as well as databases a database repository on the same server (option A above) a database repository on a different server (option B)

6 ? Prolaborate 2017

Prolaborate Guide - Administrators

Decision 5: ? Mapping EA Repositories to Prolaborate Repositories

Prolaborate lets you map one EA repository to one or more Prolaborate Repositories. The most common way to use Prolaborate is to map them 1:1, but you can map 1: many.

Mapping 1: many can be really useful, because each Prolaborate Repository defines a `Profile' (see below), which determines what parts of the EA repository can be seen, how much detailed data is displayed to users, what formats are used for lists, and lots more options. So you might choose, for example, to let users who are just browsing the information in EA to use one Prolaborate Repository (Repository A above) and so use profile X, but have other users use Prolaborate Repository B, which uses Profile Y. In both cases, all users are seeing the real-time content of EA Repository #1: they just get a different view of it.

7 ? Prolaborate 2017

Prolaborate Guide - Administrators

5.1 Detailed Instructions

5.1.1 Adding a Prolaborate Repository This section will illustrate how to add a Prolaborate Repository. Adding a Prolaborate repository primarily involves three steps:

1. Connect to EA Database using ODBC (in Sparx Enterprise Architect) 2. Save EA Project as EAP (Connection String) 3. Add new Prolaborate Repository using the EAP file (with connection string) The following sections will describe these steps in detail. 5.1.1.1 Connect to EA Database using ODBC For effective functioning of Prolaborate, the EA repository is expected to be hosted in one of the EA supported RDBMS. The first step involves the ability to be able to connect to this EA repository using Sparx EA. Steps to connect 1. Open Enterprise Architect in the server where Prolaborate is setup. 2. Connect to the remote database using `Connect to Server' option. 3. Use ODBC connection string to connect to the database server.

8 ? Prolaborate 2017

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download