Fine grained authorization in Overlord projects Currently the only Overlord project that does any fine grained authorization is APIMan. All other projects basically either allow you to do everything or nothing. (Note: actually DTGov does support some ... 
DTG (Design Time Governance) - Concepts & Definitions 1 Overview The purpose of the Overlord:DTG (Design Time Repository) sub-project is to provide Design Time Governance solutions. This paper is intended to document concepts and data models that can be used as t... DTG (Design Time Governance) - User Scenarios 1 Overview This document is intended to outline the roles, activities, and (ultimately) interactions that will make up the functionality of the Overlord:DTG application. Having well understood user scenarios sho... DTG 4.4 Scenario - Creating a New Composition 4.4.1 Background It is often the case that, rather than creating a new Service, an Architect can “compose” multiple existing Services into a new asset called a Composition. Scenario 1.2 above mention... DTG 4.3 Scenario - Creating a New Service 4.3.1 Background Another common task performed by an Architect is creating new assets in a Solution, when there are no existing assets that accomplish some required piece of functionality. The most common asset ... DTG 4.2 Scenario - Adding an Asset to a Solution 4.2.1 Background One of the most common tasks performed by an Architect is adding existing assets (e.g. reusing existing Services) to a Solution. Scenario 1.2 above mentions this task multiple times, when it des... DTG 4.1 Scenario - Full SOA Project Lifecycle 4.1 Scenario - Full SOA Project Lifecycle The following series of sub-scenarios describe the full lifecycle of a new SOA project managed using Overlord:DTG. 4.1.1 Project Initiation4.1.1.1 Background The organization ... DTG 5.3 Scenario - Managing Deployment Unit Lifecycle 5.3.1 Background It’s possible that a user of the Overlord:DTG application may simply want to govern their application deployments while using alternative tools to manage Business Problem definitions and Solutio... DTG 5.2 Scenario - Composition Management 5.2.1 Background In addition to the reasons documented in Section 5.1.1, architects may want to propose new Compositions to be used by other architects for their Solutions. For these reasons, the system allows u... DTG 5.1 Scenario - Service Management 5.1.1 Background Architects may want to document existing Services prior to their use in any Business Problem tracked using the Overlord:DTG application. Alternatively, the application may not have sufficient bu... DTG 5.4 Scenario - Reverse Engineering a Solution 5.4.1 Background It is to be expected that a new user of Overlord:DTG may already have some number of Solutions in production (or working towards production). These existing Solutions have been created using alt... Mapping Drools-guvnor to S-RAMP 1. Read Workflow Definition from S-RAMP I'm working on deploying jBPM workflows into S-RAMP governance; these workflows are the governance workflows and can be customized, or new ones can be created. Workflow c... 
S-RAMP User Scenarios The following scenarios have been created to outline the user interactions in the system in a story-telling manner so that the users, their environment, and their task goals are well understood. Having well unde... 
S-RAMP Scenario: Upload single or ZIP file manually Background: George is adding a new mobile application for users to access that shows the latest currency exchange data as provided by the current vendor. George has determined that he has some XML files that ar... S-RAMP Scenario: View version history Background: A co-worker tells Kim that a project she is going to work on already has a long-standing artifact that she might be able to re-use, but that he’s not sure what the current version supports. Ki... S-RAMP Scenario: Update files manually Background: The afternoon after he uploads his new files, George realizes that he has made modifications to these XML files so he accesses the system to update the files. He can’t quite remember the name ... S-RAMP Scenario: Maven build upload Background: Ted has built a new purchase order web service that he wants to deploy into production. This new web service consists of a WSDL file and numerous XML Schema files. Ted creates and stores the W... S-RAMP Scenario: Create an ontology Background: Lars is responsible for the creation of the many ontologies for his company in order to keep their artifacts organized for future use. Lars worked with the architects in the company to come up... S-RAMP Scenario: Classify artifacts Background: Occasionally, Lars goes through the system to ensure that all the services in S-RAMP are classified correctly to maintain the credibility of these ontologies. System Narrative: System path 1 - ... S-RAMP Scenario: Notification of activity Background: Kim is a regular user of artifacts in the S-RAMP system. She likes to be informed of the latest information so that she can include existing artifacts in her work rather than re-creating the work ot...
Log in to follow, share, and participate in this community.