How to push Process model to design model?

I just learned how to capture business requirements and a logical design using the logical data modeler and process molder to create data flow diagrams, with composite, primitive and transformative processes in SQL Developer 3.0
I know in Oracle Designer we were able to associate entities to business functions and transform the business functions into modules of type PL SQL or screen, etc.... We could create detail design documents from this information in Oracle Designer. In Oracle Designer the modules would be associated to the physical table definitions. However, the data flows in SQL developer are associated to logical entities.
My question is can these objects/items (processes primitive, composite, transformative) be transformed into design items similar to how we transform a business function in Oracle Designer into a modulel?
Thanks
Mark
Mark Kramm

Hi Mark,
there is no support for applications and modules in Data Modeler.
Design can be exported to reporting repository and there is no limit in how you can utilize these meta data. Column groups and UI defaults can be defined at table and column level - I know some people are generating APEX applications and process model can be very helpful for that.
In Oracle Designer the modules would be associated to the physical table definitions. However, the data flows in SQL developer are associated to logical entities.Each entity can be mapped to unlimited number of implementations in form of tables in relational and physical models. You need to engineer logical model to one or more relational models. There is small wizard appearing in context menu of data flow diagram node in browser - "Transform Process model roles to Physical role". You can create roles in process model and assign them to processes connected to data stores. Then this wizard will create these roles in selected physical model and CRUD settings will be transferred to permissions to select, insert, update and delete for related tables. This is just example that physical model can be reachable from process model.
We'll add more utilization of definitions in process model in future releases.
Philip

Similar Messages

How to integrate EA Modeling and Design/Devl tooling (Jdev/OER/OSR)?

Question:_
How to integrate EA Modeling (Sparx EA) and Oracle Design/Devl tooling (JDev/OER/OSR)?
How does the Oracle BPA Suite (Aris) connection to OER /OSR/JDev (SOA Governance) work?
Our challenge is to create lineage and traceability end-to-end. We want to track what was modeled/designed, to what was built and do round-tripping if possible so that the ‘model’ which is stored in EA is the source of truth that can be used for dependency analysis and project planning and impact analysis.
Project:_
Large modernization project – using the entire Oracle FMW stack that includes SOA Suite, BPM Suite, WebCenter Suite, OER/OSR governance. We have all the ‘pieces’ of software, just working on how to stitch it all together.
Tooling:_
For Enterprise Modeling, the project is using the “SPARX Enterprise Architect” (SEA). Our goal is to stick to a ‘Model Based’ (not Model Driven) approach, and we want to create traceability. Within SEA, we have a very complete and traceable model from business requirements to Logical Architecture.
When we move to the Physical Architecture, we need to switch tooling to the JDeveloper world where all the artifacts and components will be created (and versioned and refined..), and hopefully inserted into the SOA Governance tools of OER/OSR/SOA Mgmt Pack.
Boundaries:_
EA Modeling will manage:
Business requirements, Business Architecture, Logical Architecture
JDev/SOA Governance will manage:
Physical Architecture and development (SCAs, BPM, BPEL, WSDL, XML, XSD, POJO, ORMs, Java, SOA Services, etc..)

Question:_
How to integrate EA Modeling (Sparx EA) and Oracle Design/Devl tooling (JDev/OER/OSR)?
How does the Oracle BPA Suite (Aris) connection to OER /OSR/JDev (SOA Governance) work?
Our challenge is to create lineage and traceability end-to-end. We want to track what was modeled/designed, to what was built and do round-tripping if possible so that the ‘model’ which is stored in EA is the source of truth that can be used for dependency analysis and project planning and impact analysis.
Project:_
Large modernization project – using the entire Oracle FMW stack that includes SOA Suite, BPM Suite, WebCenter Suite, OER/OSR governance. We have all the ‘pieces’ of software, just working on how to stitch it all together.
Tooling:_
For Enterprise Modeling, the project is using the “SPARX Enterprise Architect” (SEA). Our goal is to stick to a ‘Model Based’ (not Model Driven) approach, and we want to create traceability. Within SEA, we have a very complete and traceable model from business requirements to Logical Architecture.
When we move to the Physical Architecture, we need to switch tooling to the JDeveloper world where all the artifacts and components will be created (and versioned and refined..), and hopefully inserted into the SOA Governance tools of OER/OSR/SOA Mgmt Pack.
Boundaries:_
EA Modeling will manage:
Business requirements, Business Architecture, Logical Architecture
JDev/SOA Governance will manage:
Physical Architecture and development (SCAs, BPM, BPEL, WSDL, XML, XSD, POJO, ORMs, Java, SOA Services, etc..)

Analysis, Design model, round-trip engineering

ok, here's the point.
We work with the problem domain and develop the analysis model. The analyst at this stage doesn't concern himself with the implementation details, some low-level code patterns and the programming language (well, let's forget for now about C's multiple inheritance and Java's workaround for it). So, when most of the analysis work is done, we end up with major classes (populated only with some basic attribs & behaviour; then, we have a high-level representation of business processes and corresponding activity diagrams. Of course, this model will be refined at a later stage, but for now it will do.
Say, we have the model in a project. Now we move to the design level. More and more details are added to the model, sequence/collaboration diagrams are added, we concern ourselves much more with the detailed class behaviour.
And here's the first question. Should we leave the original high-level diagrams intact and produce separate detailed ones? Generally, they represent the same process, but at a more detailed level. What about duplication of diagrams? Or should we elaborate the existing ones (but then we lose the clear and simple bird-eye view of the problem domain).
After that, we make a decision to implement the system as a set of EJB's. So, we've switch to component modeling at system design. UML model for these components differs quite a lot from a traditional one, so it can be quite painful to refactor the existing interaction diagrams. But do we need to do it? I agree that having <<EJBImplementation>>, <<EJBRealization>> , etc stereotypes displayed in the analysis model is not a nice solution.
Another question - is it a good idea to start a separate project for system design and just import/copy the required pieces from a higher-level design model? Or can we get away with combining all stages in one project file?
Please, read all of the above in the light of round-trip engineering. So, finishing after analysis stage, is not an option, but to lead the whole project to as low level as implementation details.
I'd like to hear from you, some hands-on experience with similar projects, your approaches. Feel free to comment on the flow of events.
Best regards,
Andrew

ok, here's the point.
We work with the problem domain and develop the
analysis model. The analyst at this stage doesn't
concern himself with the implementation details, some
low-level code patterns and the programming language
(well, let's forget for now about C's multiple
inheritance and Java's workaround for it). So, when
most of the analysis work is done, we end up with
major classes (populated only with some basic
attribs & behaviour; then, we have a high-level
representation of business processes and corresponding
activity diagrams. Of course, this model will be
refined at a later stage, but for now it will do.
Say, we have the model in a project. Now we move to
the design level. More and more details are added to
the model, sequence/collaboration diagrams are added,
we concern ourselves much more with the detailed class
behaviour.
And here's the first question. Should we leave the
original high-level diagrams intact and produce
separate detailed ones? Generally, they represent the
same process, but at a more detailed level. What about
duplication of diagrams? Or should we elaborate the
existing ones (but then we lose the clear and simple
bird-eye view of the problem domain).Depends on whether you are concerned about the abstract methodology or more concerned about the implementation methodology.
For full process control, on a large project, you will have a architecture design which will always reflect the target system but has little to do with the implementation design. If the architecture needs to change it means something was "wrong" with it (which could come about due to a change order or a refinement of the specification of the system.) There might be other associated high level documents which occupy the same level - such as the project plan. This would typically be the project initiation phase which occurs before software design starts.
Of course you would keep all of the documents. Just as naturally each version would be checked into the version control system.
>
After that, we make a decision to implement the system
as a set of EJB's. So, we've switch to component
modeling at system design. UML model for these
components differs quite a lot from a traditional one,
so it can be quite painful to refactor the existing
interaction diagrams. But do we need to do it? I agree
that having <<EJBImplementation>>, <<EJBRealization>>
, etc stereotypes displayed in the analysis model is
not a nice solution.I doubt that any reasonable system is going to make the decision to use J2EE in the system design process. That is always going to be a architecture or requirements decision (even if it is implicit.) If not then it suggests that there are probably at least three levels to the design process and the J2EE decision is in the top most layer (maybe there is a "high" and "low" level architecture process.) And architecture design must describe why J2EE was choosen and what if any alternatives were considered.
Again this document will be retained (and checked into version control.)
>
Another question - is it a good idea to start a
separate project for system design and just
import/copy the required pieces from a higher-level
design model? Or can we get away with combining all
stages in one project file?
In the abstract yes.
Why? Because in an ideal design environment, a "high" (system) level design is created by a small very experienced set of developers. Then it is handed off to many junior developers for "low" (detailed) design. That doesn't work if you are using the "same" design. This is only somewhat mitigated by design tools that somewhat support this process (or least last time I checked they didn't support it very well.)
Keep in mind that this is the ideal, and it is unlikely (probability wise) that you are working at or with a company where doing this is feasible much less encouraged.
Please, read all of the above in the light of
round-trip engineering. So, finishing after analysis
stage, is not an option, but to lead the whole project
to as low level as implementation details.
Round trip. You start with the documents that have been checked in. You branch the version control tree or just up the version numbers of the docs (depending on how "deliverables" are being handled) and start over.

Create Application Design Model

Hi,
APEX version is 3.2.1.
When you create a new application, there is the option to choose an existing application design model.
But in our case there are no existing application design models and I don't find how to create one.
Any ideas? Is it possible to create an application design model from an existing application?
Thanks,
Matthias

Hi Bill,
The last step of creating an application using the Application Creation wizard contains a checkbox that allows you to save your definition (i.e. the options you selected) as a design model, which can then be re-used in the first step of the Application Creation wizard in future (it's very easy to miss that final checkbox).
Another option you might find helpful is the 'Application Builder Defaults' option which appears in the 'Tasks' list on the right hand side of the Application Builder home page (if you're using a later version of APEX that is). Here you can define the default theme, tab level etc to use as your defaults.
Another option you might find helpful is the publish/subscribe functionality which is a huge aid in reusing 'standard' functionality/look & feel etc across all your applications. You can (for example) copy and subscribe to a master List Of Values, and then when the master list of values (in another application) is modified you have the option of either pulling down the changes from subscribing application, or having the master application push out the change to all the subscribing applications (which could be in the hundreds etc).
Hope this helps,
John.
Blog: http://jes.blogs.shellprompt.net
Work: http://www.apex-evangelists.com
Author of Pro Application Express: http://tinyurl.com/3gu7cd

Approach to designing model layer

Hi,
I am keen to understand different approaches/routes to be followed to design model layer of an ADF project.
As an example, the embedded URL shows the logical hierarchy strucutre of various business modules -
http://www.slideshare.net/AnkitGupta55/hierarchy-23178558
The logical structure will govern how the data will be shown to the user based on his selection of a value of in a top level LOV/Query component.
For Ex: if the user choose Child 1, then he should be able to see hierarchy : Main > Child 1 > Sub child 1
Every module in the diagram has a backend supporting table, however, the tables may not have the similar relationships. So a follow up query would be - Is it mandatory to have an identical table relationships as depicted in the diagram.
Also, request you to share suggestions on designing Entity Objects, View Objects etc.
JDeveloper Version - 11.1.2.4.39.64.36.1
Best Regards,
Ankit Gupta

Hi,
Every module in the diagram has a backend supporting table, however, the tables may not have the similar relationships
What do you refer to as module? The blocks as I see them can be treated as entities with associated VO. The relation between the two can be defined using entity associations or view links. Unfortunately its not easy to answer your question without knowing what you do know and what you don't know about ADF BC. Have you tried ADF (e..g running a tutorial) or have you only theoretical experience with the product. If you write ....
request you to share suggestions on designing Entity Objects, View Objects etc.
What exactly are you looking for and what does "etc." stand for in regards to the technology aspect it would represent? Entities and VO can be derived from an existing database infrastructure. If you don't have this, starting with teh ADF BC Diagrammer is a good way to start with. All documentation are accessible from otn.oracle.com/products/jdev
Frank

Cannot create a new model in designer

Hi
I am not able to create a new model in designer as I get the following error:
"Invalid column name sysdate"
Does anyone knows how to resolve this? I am on version 10.1.3.6.0.
Thank you
Namita

Hi Namita,
can you please check the table it as a column name as sysdate
Regards,
Phanikanth

Not getting Report Model Query Designer in SSRS

I am working on SQL Server reporting Service(SSRS) with Report Builder 3. I successfully connected Data Source with Oracle Server. When I working in Report Builder I did not find Report Model Query Designer. How can I find this?
How can it possible to merge dataset with datasource(database entity) in SSRS?
Please help me.

Hi Jewel,
To enable Report Model Query Designer in Report Builder, we need use Report Model as the datasource. Report models can be used as data sources for reports created in Report Designer and Report Builder 3.0.
So in your scenario, you need to create a Report Model project in SQL Server Business Intelligence Development Studio (BIDS), and then deploy this report model to report server. Then in Report Builder, you can use this report model as datasource and open
Report Model Query Designer window.
Reference.
Report Models (Report Builder 3.0 and SSRS)
Tutorial: Creating a Report Model
If I have anything misunderstood, please point it out.
Regards,
Charlie Liao
TechNet Community Support

Design Model applications?

The last step in creating a new application has a checkbox with "Save this definition as a design model for reuse" next to it. I could not see an explanation of "design model" in the HTML DB user's guide or on the Internet.
Questions
1) Does this mean you can have one or more template applications to speed up the development of new application?
2) How do you change an application from not being a Design Model to being one? I created a template application without marking it as a Design Model. How can I make it one? I have the application export, but when I import it, I cannot designate it as a Design Model application.
3) In the past I created some "test" applications with the checkboxs checked. I have since deleted these "test" applications, but they are still in the list of Design Model applications. How do I remove them from the Design Model list?
Mike

Mike,
When you use the create application wizard, then the page definitions of the pages youre adding to your application are saved as a model. So all the information about your form pages, report pages, tabular form pages, and if selected, your analysis pages, are all saved if you choose that option. When you use the create application wizard the next time, you will be able to re-use that application definition, perhaps modify it, add new page definitions, change existing page definitions, etc. And then you can create a new application based on that updated model. You can not go back to a model to modify an existing application, nor can you create a model for an application that previously didnt have one.
Please note that a model only stores information about your pages. Your other selections, like what theme you want to use, if you want to copy over any shared components, what kind of authentication you want to use, etc. are not stored in the model. So if you want to save a full application for future re-use, its best to export it, or create copies of the application.
In order to delete an application model, you can go to your application administration, then click on manage service and go to application models. There youll find a list of models and a button to delete those that are no longer needed. Deleting a model has no effect on any existing applications.
Regards,
Marc

Step by step process in BI 7 modeling

hi gurus
please send me the step by step process of BI 7 modeling (measns i want to send data from flat file to cube) iam cinfused in transfermation please guide me.
thanks
Veera

Hi,
In BI7.0, they've replaced BI3.5 upate/transfer rules with "transformations".(its our wish only still if we want to continue with 3.x transfer rules/update rules we can continue using the same or using transformations)
Transformations are used to create the data flow between your source and data target.
Example: DataSource->Transformation->DataTarget
Data Transfer Process (DTP) is now used to load data using the dataflow created by the Transformation. Here's how the DTP data load works:
1) Load InfoPackage
2) Data gets loaded into PSA (hence why PSA only is selected)
3) DTP gets "executed"
4) Data gets loaded from PSA into the data target once the DTP has executed
Below are the basic steps which we follow in any BI 2004S system:
1)Create datasource. Here u can set/check the Soucre System fields.
2)Create Transformation for that datasource. (no more update rules/transfer rules)
2.1) While creating transformation for DS it will ask you for data target name, so just assign where u want to update ur data.
DataSource -> Transformation -> Data Target
Now if you want to load data into data target from Source System Datasource:
1) Create infopackage for that data source. If you are creating infopackage for new datasources, it will only allow you update upto PSA, all other options u can see as disabled.
2)Now Create DTP (Data Transfer Process) for that data source.
3) NOw schdule the Infopackage, once the data is loaded to PSA, you can execute your DTP which will load data to data target.
If you are loading data from one one data target to other, no need to use PSA, you can directly execute DTP in that case.
Hope it helps..
Regards
Ganesh

Designing model from R/3

Hi Experts,
I have designed few models form BI report successfully. Can anyone guide how to design model from R/3 reports?
Regards,
Nirav

Hi Nirav,
here is an overview about what is possible:
[http://help.sap.com/saphelp_nw70/helpdata/en/21/58feb70e884bc68a474429ac26f448/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/en/21/58feb70e884bc68a474429ac26f448/frameset.htm]
Best Regards,
Marcel

ERD designer model dump file from Oracle Consultancy

Hi,
I downloaded the following link:
Oracle Designer 6i Model (application system dump file, version 1.0) 2.48M (zip)
from this site:
http://otn.oracle.com/products/designer/content.html
then I uploaded to a database, but I don't understand the tables imported there.
Could you please tell me more about these tables???
Tx.

Edgardo
If you are referring to the zip file that you get when you download 'Designer Model (application system dump file, v1.0)' then this is an application export that you should load into Designer directly. Do this by performing the following steps with the unzipped file:
1. Invoke the RON as the user which will own the resulting application system
2. Select Utilities > Import
3. Select 'Import from an ORACLE database file', and click Next
4. Browse to the unzipped file, and click next
5. If you see a dialog telling you that there are already temporary export tables, think carefully about what they might contain. Generally you can ignore this content, but the repository user you are using might have been in the middle of an export or import. If it's OK to overwrite them, click Yes. If you click No the process will abort.
The resulting application system contains the Designer meta model definitions and diagrams.
Hope this helps
Regards
Simon Day
Application Developement Tools Product Management

SQL Developer with Data Modeler, No Design Menu Option

Using SQL Developer 3.0.04 Build MAIN-04.34 with Data Modeler. I have created a logical design and wish to forward engineer this to a relational model.
I cannot seem to find the Design Menu option to use the >> Engineer to Relational Model option which is available under the Design Menu on the Stand Alone version of SQL Developer Data Modeler.
Have checked the following locations:
Tools -> Data Modeler
View -> Data Modeler
File -> Data Modeler
Right Click on my Logical Design
I have ensure that all my entities have the Engineer To property set to a valid Relational Model.
Is this a bug or am I missing a menu option / configuration setting?
Thanks in advance for any help
John

Hi John,
you can find ">> Engineer to Relational Mode" button among other buttons for logical diagram.
Philip

How to make linkage query In Data Model for search

I want to make an linkage query as a condition for my report in BI Publisher. how to make the linkage in Date Model ?

This is the forum for SQL Developer, not for general SQL or PL/SQL questions.
Please repost this in the SQL and PL/SQL forum.

How to maintain version in ERwin Data Modeler

Hi all
Please tell me
how to maintain version in ERwin Data Modeler
regards

In SharePoint, navigate to the form library, and then click Library Tools > Library > Settings > Library Settings.
On the Form Library Settings page under General Settings, click
Versioning settings.
On the Versioning Settings page under the Document Version History section, select either the
Create major versions option or the Create major and minor (draft) versions option, and click
OK.
http://www.bizsupportonline.net/blog/2012/10/version-control-infopath-forms-templates-sharepoint-libraries/
Or
plan this wsp nfoPath_VersionHistory.wsp
http://infopathversioning.codeplex.com/

How do I determine which IPad Air model I have?

How do I determine which IPad Air model I have--Air or Air2? Thanks.

The single row I'm speaking of goes across the full width of the iPad but is interrupted by the Lightning connector. Here's an ASCII example:
iPad Air 2
. =speaker holes
O= Lightning connector
...............O...............
iPad Air 1
: = speaker holes
O= Lightning connector
:::::::::::::::O:::::::::::::::
I mentioned them as being rows and not columns because with a single row as with the Air 2, there are no columns when viewed horizontally...if viewed vertically, the rows will of course turn into columns.

How to push Process model to design model?

Similar Messages

Maybe you are looking for