Design model of cProjects

Hi Experts,
I am interested in understanding the design model of cProjects.
I mean the way design patterns are used and also the general architecture of cProjects.
Thanks in advance.
best Regards,
Arti.

Hi Arti,
Release 4.0 onwards, cProjects is a web dynpro abap application. It deploys MVC architecture so that the application code is kept separate from the user interface. You may search papers on MVC architecture to understand more on the functionality and deployment.
Here is a [Patent Application Publication|http://www.google.co.in/patents?hl=en&lr=&vid=USPATAPP10327686&id=SYmUAAAAEBAJ&oi=fnd&dq=SAPcProjectsgantt+chart] published by Meyringer on cProjects Gantt Chart. I think this one refers to cProjects 3.0, but helps to understand the technical architecture behind the cProjects graphical view.
Regards,
Vivek

Similar Messages

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

Import Oracle Designer model dependencies between objects

Hello,
I am using the Oracle Designer model import to fill Data Modeler. There are some views which have dependencies on each other, resulting that views which depend on other views are incomplete.
Is there a way to rerun the import again in the same relational model, since the import utility now opens a new relational model again.
Is there a kind of logging where you can find these kind of errors?
Best regards,
Joop

Thanks Phillip, but I was actually referring to the version level of the Designer repository itself, not the database instance in which it resides. I seem to remember that you could not upgrade your Designer repository without also upgrading the Oracle Designer client as well; hence my question about compatibility between SQL Developer Data Modeler and various Repository versions.

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.

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

Importing and Oracle Designer Model

Hi,
Is the "Importing an Oracle Designer Model" functionality enabled ? I seem to be able to test the connection (successful) but the next screen "Selct WorkArea" doesn't seem to be working?
-Tom

Your right!!
build 525 has a problem with importing Designer. A Bug has been generated. and it is internal.
The earlier build works.

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

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

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

Import Oracle Designer Model

Hello,
I have a client who maintains their data model in an old Oracle Designer 6.0 model repository. I would like to help them migrate from this very old data model to SQL Developer Data Modeler, if possible. With what versions of Oracle Designer repository is SQL Developer Data Modeler compatible with for model import?
Thanks in advance.

Thanks Phillip, but I was actually referring to the version level of the Designer repository itself, not the database instance in which it resides. I seem to remember that you could not upgrade your Designer repository without also upgrading the Oracle Designer client as well; hence my question about compatibility between SQL Developer Data Modeler and various Repository versions.

SQL Developer Data Modeling - import from Oracle Designer Model

Hi,
I do want to try to import model from a Designer repository.
The first step is to create connection to the repository (9i version).
I have created the one, however any attempt to test the connection or to go to the next step simply finishes with error "4", without any valueable message.
Any idea or suggestion ?
Thanx.

A clarification of the Data Modeling feedback application and this forum. The developers are part of the SQL Developer development team, but as for all our features, each developer has a focus area, so the Data Modeling developers will tend to answer those questions. There will not be a separate Data Modeling forum, so once we're production all SQL Developer Data Modeling questions will be on this forum. We want to encourage all users to get into the habit of tagging posts. Having the posts tagged means that users can skip them if they're not their focus area and users can search using the tags. The more tags are used in all the forums the better. You may well find find the answers to your questions are outside this forum!
As SQL Developer Data Modeling in in its first early adopter phase, we have provide a feedback application, where users can provide feedback, log bugs and ask questions. We did the same for SQL Developer before it's initial production release and found this to be very useful for the product.
I'm happy for "How To" questions to be on this forum, as the answers benefit the broader community.
Sue Harper

Mathematica Link for LabVIEW Integrates Design Models and Measurements

Mathematica Link for LabVIEW, a new technical computing
application created by BetterVIEW Consulting, is now available.
This software bridges National Instruments LabVIEW graphical
development environment and Wolfram Research Mathematica
technical computing software to help engineers and scientists
more easily acquire and analyze measurements throughout all
phases of the design process.
Mathematica Link for LabVIEW combines the data acquisition,
analysis, and graphical user interface capabilities of LabVIEW
and the modeling and analysis algorithms of Mathematica to speed
development of custom applications in hundreds of industries,
from quantum mechanics to automotive. With this software,
engineers can control a LabVIEW application (Virtual Instrument
or VI) from Mathematica or access Mathematica from within a
LabVIEW VI.
Mathematica Link for LabVIEW features built-in, high-level
functions for creating a communication path between LabVIEW and
Mathematica to achieve seamless integration throughout the
design flow, from the first mathematical model to validating the
final design. For example, engineers and scientists can easily
send numeric computations to the Mathematica kernel and return
results to LabVIEW, visualize LabVIEW data using native
Mathematica data visualization functions, and create simple, yet
flexible simulation and control VIs that take advantage of the
symbolic programming capabilities of Mathematica.
Integrating two leading technical computing systems like
Mathematica and LabVIEW brings technical professionals one step
closer to having the ideal, start-to-finish work environment.
With Mathematica Link for LabVIEW, entirely new, hybrid
workflows become possible, thus enabling users to quickly and
easily find solutions to complex problems--solutions that would
be difficult, if not impossible, to realize using only one of
the component packages.
Mathematica Link for LabVIEW requires Mathematica 4.1 or later
and LabVIEW 6i or later, and is available for Windows and
Macintosh platforms. For more information about Mathematica Link
for LabVIEW, visit:
http://www.wolfram.com/products/applications/labview

Socalledvita-
What functionality are you looking from the Amplitude and Level Measurement Express VI? There is not one-one replacement you can use. However, there are definitely ways of calculating the DC and RMS values of a signal as well as finding the max and min points, etc. Please be more specific in what you are trying to accomplish.
Regards,
Mike S
NI AE

Design Model

How do I design a model for this case
: I ahve a room and in the room I have a parrot this room has one door and every time some one comes in through this door , the parrot says "Hello"

You can implement the Observer pattern.
Room can extend java.util.Observable and Parrot can implement java.util.Observer.
Please take a look @ http://www.javaworld.com/javaworld/javaqa/2001-05/04-qa-0525-observer.html for more information.
import java.util.Observable;
import java.util.Observer;
import java.util.List;
import java.util.ArrayList;
import java.util.Iterator;
public class Room extends Observable{
     private List observers = new ArrayList();
     public void addObserver(Observer o){
          observers.add(o);
     public void removeObserver( Observer o ) {
            observers.remove( o );
    public void notifyObservers(Object arg) {
         Iterator i = observers.iterator();
        while(i.hasNext()) {
             Observer o = (Observer) i.next();
             o.update(this, arg);
     public void openDoor(){
          notifyObservers(null);
     public static void main(String[] args){
          Room room = new Room();
          new Parrot(room);
          room.openDoor();
import java.util.Observable;
import java.util.Observer;
import java.util.List;
import java.util.ArrayList;
import java.util.Iterator;
public class Parrot implements Observer{
     private Room room;
    public void update(Observable o, Object arg) {
          System.out.println(sayHello());
    public String sayHello(){
          return "Hello";
     public Parrot(Room room){
          this.room = room;
          room.addObserver(this);
}

How to design model for staging layer.

Hi expert,
what is the rule when design staging layer? such as how much layer needed for staging? and what objects used in staging? why different layers needed for staging .etc.?

Hi,
Please have a look at SAP Help - Enterprise Data Warehouse (EDW) for basic information around layers and architecture. Moreover, please have a look at my blog Layered, Scalable Architecture (LSA) from an Implementation Perspective - Overview where you can find several "accelerators" to facilitate your implementation.
Best regards,
Sander

Design model of cProjects

Similar Messages

Maybe you are looking for