Choosing a design pattern for duplicate processes

I need to create an application that controls and aquires data for two basins in a wastewater treatment pilot plant. Both basins go through the same series of states aerobic, anoxic, settle and decant but at different times (and therefore need to be controlled independently). Can I run two state machines in parallel or would it be best to use a different design pattern altogether (eg Master/Slave)? The application is intended to be run off a FP-2010.

You certainly can run two state machines in parallel - maybe you could put the state machine in a re-entrant subVI and place two copies of that subVI on your top-level diagram, passing in different parameters to specify e.g. interface channels and output filenames. If it's not possible for two independent VI's to communicate directly with your I/O hardware then they could use e.g. queues to communicate with a separate I/O process. Queues could also be used to communicate with a user interface process if that's required. I guess the choice is influenced by how important it is for your solution to be re-usable and scalable.

Similar Messages

How to look for duplicate process instances?

In Oracle BPM 11g, is there a good way to look for duplicate process instances based on process data attributes? For example, I have entered an instance of a process for 'John Smith' with a date of '4/1/2010' and I want to see if there is another instance in the same process with these same data values to evaluate as a potential duplicate. I believe we can write a java service to invoke the API to do this, but I am wondering if there is a better way within the process design to do this (XPath extension functions or soemthing?). It seems like this would be a common need.

I am really looking for an approach to looking for duplicate instances within my process flow, not from EM. So, if the user starts a new instance of a process, I can check for another instance that appears to be a duplicate and direct the flow to a human activity to review the potential duplicate and make a decision as to whether to continue processing the new instance or reject it. My guess is that we need to us a service task to invoke java code which uses the API to investigate other instances with the same values. But, I was hoping for a simpler solution....I have to think that this is not too uncommon.

Choice of design pattern for data acquisition system

Hello all
I have a trouble about selecting the suitable design pattern / architecture for a data acquisition system.
Here is the details of the desired system:
There is data acquisition hardware and I need to use it by observing parameters on User interface.
the data acquisiton period, channel list to scan should be chosen on User interface. Besides, there are many user interface interactions. e.g. if user selects a channel to add scanlist, then I need to enable and make visible some other parts on user interface.
When user completes the channel selection, then he will press the button to start data acquisition. Then I also need to show the scanned values on a graph in real time and log them in txt file.
I know that I cannot use producer consumer pattern here. because the data acquisition loop should wait for parameters to scan channels. and it works in a given period by user. so the user interface loop performs higher rate then consumer loop (data acquisition loop). it means queue will be bigger bigger. if I use notifier it will loss some data come from user interface.
is there any idea about that ? is there any suitable design pattern for this case ?
Thanks in advance
best regards
Veli BAYAR
Embedded Systems Software and Hardware Engineer
"You live in a graphical world. Why not program in one?"
Solved!
Go to Solution.

johnsold wrote:
Veli,
I recommend the Producer/Consumer model with some modifications.
You might need three loops. I cannot tell for sure from your brief description.
The User Interface loop responds to the user inputs for configuration and start/stop of acquisition. The parameters and commands are passed to the Data Acquisition loop via a queue. In this loop is a state machine which has Idle, Configuration, Acquisition, and Shutdown states (and perhaps others). The data is sent to the Processing loop via a different queue. The Processing loop performs any data processing, displays the data to the user, and saves it to file. A notifier can be used to send the Stop or shutdown command from the User Interface loop to the other loops. If the amount of processing is minimal and the file write times are not too long, the Processing loop functions might be able to occur in the Timeout case of the UI loop Event structure. This simplifies things somewhat but is not as flexible when changes need to be made.
I am not sure that a Design Pattern for this exact setup exists but it is basically a combination of the Producer/Consumer (Events) and Producer/Consumer (Data) Design Patterns.
Lynn
Check out this thread: http://forums.ni.com/t5/LabVIEW/Multiple-poll-case-structures-to-event-help/td-p/2551309
There are discussions there about a 3-loop architecture that may help you.
Jeff
Jeffrey Zola

Is there a design pattern for this?

I'm looking for a solution to a design problem I have.
For a restaurant booking system I need a number of different opening times describing when you can and cannot book. These opening times are essentially Jodatime Period objects. There's a set of opening times spanning a week and these are repeated for every week (a default set of opening times) however it's possible to override these opening times say for a specific day.
The domain model would be something like a Restaurant class holding 2 Lists of OpeningTime objects one for defaultOpeningTimes and the other for overiddenOpeningTimes the overidden ones get used if they exist for the requested time period. However the database model would be a bit messy as I'd have 2 lists mapping to the same table (OpeningTime). Is that a good idea? Perhaps there's a design pattern for this, if someone could point me in the right direction I'd be very grateful, or perhaps this is the best solution? Thanks!

jduprez wrote:
But why do you put the logic in the database too (I'm no DB expert and I didn't know these concepts until I read your post, but that's what a dynamic view based on derived values looks like to me): performance (1 round-trip instead of two)?Hi jduprez. Long time no speakee.
I guess part of it is that I spent many years as a DBA and modeller, and really appreciate what it's taught me about design. Also, databases are (or should be) designed from the ground up to provide data-directed requests optimally, and include all sorts of nice stuff like transaction handling that aid consistency, as well as speed.
That said: I HATE SQL. Think Coliseum, with that emblazoned in 60-foot high letters around its walls, and it might come close to just how much I hate that so-called "language". I hate its form; I hate it's inconsistencies; I hate the fact that something like what OP is trying to do is NOT an easy task (and might involve the creation of a table that simply contains Dates, just in order to satisfy Boolean logic).
However, once you work it out, a database view (at least from the database's standpoint; JDBC I'm not so sure about) is just like any other Table - and that I DO like.
Programs are good at processing parameterized (ugh) temporal information; databases are good at persistence and high volume. Those two may meet at some point, but I reckon it's going to take another Codd (or Joda) before it does.
- that's clearer to 90% of the dev team (my biased numbers, based on 50% of Java developers having decent knowledge of SQL and much less than that having the advanced SQL knowledge which I rank your suggestion at)Sounds to me like you'll get the solution that matches the skills you have then. Is that what you really want, if a better one is available?
- that doesn't require investigating the if of your suggestion (JDBC support)Agreed, but only because my JDBC knowledge isn't what it could be. I'd also be surprised if it doesn't support access to a named view, since they were designed to be equivalent to Tables.
- the Op is using DAOs, so it's possible, if profiling does show this is hampering performances, to change that with no impact on the client code that calls the DAO.There's no doubt that a database solution is much higher level than a programming one; but, as I said, it's what they were designed to do. And tinkering around with program optimization has the feel of a "hacker's solution" to me. Not that there's any particular problem with that - I do it quite often when I have no control over my source - but I also try to keep in mind what the "actual" problem is.
Winston

Design Pattern for execution queue

Anyone know of any good design patterns for using a JMS Queue and MDB's
          as async
          execution queue which maintains execution order by some key


Enforced ordering on redelivery will be supported in the
          next release, but only if the application clamps the pipe-line
          size down to its minimum and the MDB pool size down to one.
          I don't think enforced ordering is supported in the current release.
          We are looking at least partially addressing the general design
          pattern below in the release after next. I don't think I can
          get away with being more specific. (Sorry.) Currently, I
          think something along the line of Larry's solution is the only way to
          accomplish it. Interestingly, the recent thread started
          by "[email protected]" on correlating requests and responses
          seems to be somewhat related.
          Tom, BEA
          Larry Presswood wrote:
          > Well you are both correct however we have something which works
          > however it does involve some threading primitives which generally is not
          > a good idea
          > inside wlas but seems to work.
          >
          >
          > Generally have a singleton on the server which has slots for each key
          > with message
          > numbering for each message and force a wait if message for key is out of
          > order
          > during fifo processing rules. IE do what things you can do in parallel
          > but gate for
          > the last step.
          >
          > I think there is a general remote execution pattern out there.
          >
          > The general problem to solve is this:
          >
          > In a messaging system you want to process messages for each key/session
          > in order however
          > with a large number of sessions its possible to parallel messages for
          > different sessions
          >
          > Otherewise you can either create custom queues or a topic with a
          > selector and then
          > create custom consumers which does not behave as well from a resource
          > perspective
          > as MDB's do.
          >
          >
          >
          >
          >
          >
          >
          > Nick Minutello wrote:
          >
          >>I may be completely wrong - but I think that Larry is referring to the inherant
          >>out-of-order message consumption that you get when using MDB pools to consume
          >>from a Queue.
          >>
          >>In short, the only design pattern here is to deploy the MDB to only one machine
          >>in the cluster - and set the pool size to 1.
          >>
          >>In-order execution is incompatible with the parallel execution that MDB's give
          >>you.
          >>
          >>-Nick
          >>
          >>
          >>
          >>Tom Barnes <[email protected]> wrote:
          >>
          >>
          >>>Hi Larry,
          >>>
          >>>Generally, I think it is best to have a seperate queue per key if the
          >>>
          >>>number of keys is small. This prevents starvation of a particular
          >>>message. For example when handling message-priority, low priority gets
          >>>
          >>>an MDB pool of size 1, high priority gets and MDB pool of size 10.
          >>>
          >>>Note that WebLogic JMS allows a queue to specify a sort-order keys based
          >>>on arbitrary message fields. Note that the in-flight message pipe-line
          >>>
          >>>between server and asynchronous clients is unsorted.
          >>>
          >>>Tom, BEA
          >>>
          >>>Larry Presswood wrote:
          >>>
          >>>
          >>>>Anyone know of any good design patterns for using a JMS Queue and MDB's
          >>>>
          >>>>
          >>>>as async
          >>>>execution queue which maintains execution order by some key
          >>>>
          >>>>
          >>>>
          >>
          >>
          >>
          >

Flex design pattern for BlazeDS transfer objects

Dear Community,
I have a question regarding the nature of objects transferd from BlazeDS backend to the Flex client.
According to some adobe docs all the presentation logic should be in flex and BlazeDS should provide only services.
The question is what kind of transfer objects should be used? with what level of abstraction?
To make it more clear let's talk about a simple forum application like adobe forums.
I have created a Forum service, which returns a Forum transfer object, which has a List of Threads, with each thread having a List of Messages.
Flex gets the Forum transfer object and does all the presentaiton work.
This is a very nice seperatin of concerns architecture BUT there are two major performance issues:
- when the forum becomes bigger the transfer object will be huge
- the flex will use huge client resources to create the presentation of the forum transfer object.
So my question is what is your strategy/ design pattern for such a problem.
An obvious answer would be create services that include the presentation logic and use transfor objects like ThreadListPage which will include only the first 10 threads.
Thanks in advance

I think you are going to get a few varied types of answers to a general question like this, but I will comment on a few things. First, you should only be transmitting the data that you need to use or display to the user at the time. If this forum was implemented in Flex (I wish) you wouldn't transfer the text for all the threads. You might not transfer the thread text at all (just the subjects), you'd make calls back to the server to fetch that data when and if you need it.
Also, I think you are overestimating the resources required for the Flex "presentation layer". If you think about it, these workstations we have here are pretty idle most of the time when you're at a website. Nowadays there's plenty of processing power just sitting there waiting, so as long as your design isn't flawed the CPU or memory are rarely going to be a bottleneck with Flex.
The way I design, BlazeDS (or GraniteDS etc) should mostly just be "serving data". There is some flexibility available, for example I don't see a problem with putting certain types of business rules (such as a limit on the number of results that can be recieved in a search) within server side code, and validation rules on the Flex side. So there's not too many "industry standards" in Flex yet beyond maybe what's done in the various standard architectures, at least not that I'm aware of.
You might find it beneficial to look into some of the various frameworks/architectures available like Cairngorm, Mate, Swiz, and so on. Learning how they work (looking at examples) would probably answer some of your questions too.

What is the best design pattern for this problem?

No code to go with the question. I am trying to settle on the best design pattern for the problem before I code. I want to use an Object Oriented approach.
I have included a basic UML diagram of what I was thinking so far.
Stated simply, I have three devices; Module, Wired Modem, and Wireless Modem.
In the Device Under Test parent class, I have put the attributes that are variable from device to device, but common to all of them.
In the child classes, I have put the attributes that are not variable to each copy of that device. The attributes are common across device types. I was planning to use controls in the class definition that have the data set to a default value, since it doesn't change for each serial number of that device. For example, a Module will always have a Device Type ID of 1. These values are used to query the database.
An example query would be [DHR].[GetDeviceActiveVersions] '39288', 1, '4/26/2012 12:18:52 PM'
The '1' is the device type ID, the 39288 is the serial number, and the return would be "A000" or "S002", for example.
So, I would be pulling the Serial Number and Device Type ID from the Device Under Test parent and child, and passing them to the Database using a SQL string stored in the control of the Active Versions child class of Database.
The overall idea is that the same data is used to send multiple queries to the database and receiving back various data that I then evaluate for pass of fail, and for date order.
What I can't settle on is the approach. Should it be a Strategy pattern, A Chain of Command pattern, a Decorator pattern or something else.
Ideas?

elrathia wrote:
Hi Ben,
I haven't much idea of how override works and when you would use it and why. I'm the newest of the new here.
Good. At least you will not be smaking with a OPPer dOOPer hammer if I make some gramatical mistake.
You may want to look at this thread in the BreakPoint where i trie to help Cory get a handle on Dynamic Dispatching with an example of two classes that inherit from a common parent and invoke Over-ride VIs to do the same thing but with wildly varying results.
The example uses a Class of "Numeric" and a sibling class "Text" and the both implement an Add method.
It is dirt simple and Cory did a decent job of explaining it.
It just be the motivation you are looking for.
have fun!
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Design pattern for unprotecting and reprotecting sheets with VBA?

Many macros can't run when a worksheet is protected, so when I develop an Excel workbook that has protected worksheets, I have to unprotect worksheets when macros are called and then reprotect the worksheets once the macro has completed.
The current design pattern I use for this is the following:
I look at each procedure individually and consider which sheets need to be unprotected for it to run. Then in each procedure I write:
Sub Test()
Dim bSheet1Protected as boolean
Dim bSheet2Protected as boolean
bSheet1Protected = Sheet1.ProtectContents
bSheet2Protected = Sheet1.ProtectContents
bSheet1Protected.Unprotect
bSheet2Protected.Unprotect
'''The rest of my code
if bSheet1Protected then Sheet1.Protect
if bSheet2Protected then Sheet2.Protect
End Sub
But I imagine that maybe there are better ways of doing this. What is your preferred design pattern for unprotecting and reprotecting sheets with VBA?

Hi JP3O,
I think it is a good practice to unprotect the worksheet before execute some code and protect it back after the code execute finished.
>>But I imagine that maybe there are better ways of doing this. What is your preferred design pattern for unprotecting and reprotecting sheets with VBA?<<
I am not able to find a better way since we always need to unproect the worksheet if some code didn't not executed successful when the worksheet is proected.
Regards & Fei
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Design Pattern for Controlling Uniqueness

Hi,
I'm looking for a good design pattern for controlling uniqueness. E.g. I have classes representig a particular database relation. The constructor has the database key(s) as parameter(s). For the other attributes there are corresponding setter and getter methods.
How can I make sure, that I have only one instance with key(s) foo in my system?
Of course I have some ideas but I'm not sure if that is the best thing I could do. So I could use a map, to map the keys to the tuples.
This map could be in another class foo2 which creates the objects of foo1 (which has only a protected or package-private constructor).
Or I could place the map into foo1 itself as a static variable, and add a static factory method. The constructors would then be protected or private. Are these solutions good? Which one to prefer?
How can I handle other unique attributes (not part of the key)?
The equals method for such a class could then test the keys only, since there is only one object with such a key in the system, right?
Thanks for any help.
Greets
Puce

The class could have only private constructors and a public static getter method, which would decide based on some collection of the object created so far, whether to create a new one or give an old one.

What is the best design pattern for top-down ws development..?

Hi,
What is the best design pattern for top-down development+ wsdl2service....?

elrathia wrote:
Hi Ben,
I haven't much idea of how override works and when you would use it and why. I'm the newest of the new here.
Good. At least you will not be smaking with a OPPer dOOPer hammer if I make some gramatical mistake.
You may want to look at this thread in the BreakPoint where i trie to help Cory get a handle on Dynamic Dispatching with an example of two classes that inherit from a common parent and invoke Over-ride VIs to do the same thing but with wildly varying results.
The example uses a Class of "Numeric" and a sibling class "Text" and the both implement an Add method.
It is dirt simple and Cory did a decent job of explaining it.
It just be the motivation you are looking for.
have fun!
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Design Pattern For Web Services.

I tried asking siomilar questions in WebService Forum but didn'y got any replies.
Can anybody tell me what should be the Design for Web Services.
I have understanding that there can be just 1 Interface/Implementation class for each Web Service, and which will have 1 end point.So for evry such Interface we will have to have 1 Web Service.
Can someone please clarify wheather I'm correct or not ?
I guess that If my application has many Interfaces and I have to expose the application as Web Service.Then I will have to expose all methods from one Interface and then expose this new Interface as Web Service.
Is this how WS will work.
Any pointers to design PATTERNS for Web Service will be highly appreciated.
Thanks
Rahul

I don't know if anyone has documented new patterns specifically aimed at web services but the old ones definitely apply. Like you were alluding to, there is a letter-envelope decoupling of interface and implementation with the XML WSDL interface and coded implementation.

Design pattern for IFS

Hi,
I am new to Oracle IFS. I just want to know Is there any proven design pattern for IFS application development.

The class could have only private constructors and a public static getter method, which would decide based on some collection of the object created so far, whether to create a new one or give an old one.

Design Pattern for simple AIA processes

I have been using AIA Foundation Pack v2.4 with SOA Suite 10.1.3.4 for a while now and have developed a variety of interfaces using the standard AIA model of:
Source Adapter (ESB)
Requester ABCS (BPEL)
Enterprise Business Service (ESB)
Provider ABCS (BPEL)
Target Adapter (ESB)
I can see the value in usng this model but we are coming up with requirements for more specific Application to Application Integrations where we may just be interfacing some reference data. Therefore there is no available EBO and it is also overkill to develop 5 separate processes to satisfy a simple integration that could be developed with a simple ESB process.
Are there any best practices or preffered design models for implementing this kind of simple interface but still make use of some of the functionality of the AIA Foundation Pack, such as CAVS, Error Handling and setting dynamic endpoints etc..
We are also looking to utilise the Service Registry so we can define and manage the differnet services that we have developed.
I'd be interested to hear peoples thoughts.
Regards
Stuart

In the process of attacking daFei (a truly pointless excercise) everybody forgot to answer the OPs question.
Here's my take: composition will work better for this. There are several approaches you could use. One is to make a basic concrete Command and put the minimal base properties in it and let the other Command classes wrap other commands without copying.
Another approach would be to make this class a holder for all the possible attributes. The advantage is that in the above situatiuon (and your current situation, I beleive) one command can be created from another where they share properties that are not in the root set of attributes but these specialized properties will be lost in the copy. You can deal with this through a number of hacks but none are especially pretty. The downside is that you create a kind cyclic dependency by doing this.
Lastly and people will probably balk at this: you can put the properties in a map and encapsulate this inside each of your command classes. Then copying one from the other is just a matter of cloning the map or just wrapping the same instance, depending on what you want. This addresses theissue described in the paragraph above without creating cyclic dependencies. The downside is that you lose some type checking but you can mitigate to a large degree this by using static literals to get an put values and only access the map through methods specific to each property.

Design pattern for quiz module

Hello fellow developers.
I am making/refactoring a module in a jee mobileplatform. It's a quiz module where the enduser participates via sms. Now, I am trying to redesign the module and I am thinking about using the state pattern for this, where the user can be in i.e the following states: StartQuizState(welcomemessage and first question), NextQuestionState, NoAnswerState(the user sent an empty or no valid response), QuizFinishedState(sum up the points etc), and maybe a BonusState if the user makes x points within a specific time limit.
I was wondering if anyone had any comments on my choice of pattern for this module :)
Thanks in advance for any comments,
Best regards,
Eivind

Good morning Saish, sorry for my late response.
First of all - thanks again for showing such interest in my "discussion", and my deepest apologies for my grammatical error hehe, I was tired and wrote a little bit too fast. Normally I take great pride in writing correctly :)
I would also like to say that many, many times before, these forums, and others, have helped me when stuck in a programming problem or other problems related to software. So without all those people out there willing to spend their free time answering questions from people like me, a lot of us wouldn't be able to solve whatever problem we might have, and basically the general experience amongst inexperienced programmers would evolve much slower. So Saish, thanks to people like you there are a lot of happy programmers out there. It is very important for those of us working with development, to share whatever knowledge we might have.
Anyway back to the discussion:)
I totally agree, the state is absolutely the Quiz, not the contestant of the quiz. I just read a Head first design patterns (a great book by the way!), and I was a bit to hung up on using patterns instead of looking for a solution that works. So what I have done so far, refactoring my solution:
I have the following models:
- Quiz
- Contestant
- Answer
- QuizManager
Quiz Object
The Quiz model that represents the actual quiz, which contains a list of Question objects, and Answer objects. The quiz has a int constant QUIZ_STATE, and the possible states:
private static final int START_QUIZ_STATE = 0;
private static final int FINISH_QUIZ_STATE = 1;
private static final int NEXT_QUESTION_STATE = 2;
private static final int REPEAT_QUESTION_STATE = 3;
private int quizState = START_QUIZ_STATE;
As you can see the quizState defaults to START_QUIZ_STATE. The first thing I do when the contestant enters, is to check the state of the quiz, if he already is an contestant, if the quiz is finished etc.
Then I continue and process the quiz based on the state of the quiz (this time everything in one class - a quizmanager).
Contestant Object
Contestant model containing what questions are already answered, number of points and so on.
Answer Object
The Answer object is created if the contestant sends an answer and his answer corresponds with the alternatives in the Answer object. E.g if the answer alternatives are a) 100 kilometers and b) 20 kilometers, and the contestant sends an answer c, it is considered as no answer, and the last question is repeated, if the contestant sends a, or b, his answered is compared with the current Answer alternative, and a new question is sent him.
I have some database tables for managing this module, and basically a Quiz is configured as an XML, where 1 xml is a quiz, and 1 quiz xml can contain many question and answer tags. These are read upon quiz start, and Quiz, Answer, and Question objects are created. Every time a new contestant enters, a new Contestant object is ofcoursed created.
All the logic takes place in the previously mentioned QuizManager. Any comments on the solution so far would be greatly appreciated.
If interesting to anyone I can post the classes when I am finished with the module, as a standalone java application without a database.
Regards,
Eivind

Design pattern for continuous record printing

The Java printing API requires that during the print process a program retain enough information so that it can draw any page that is requested at any time. The API makes a call to the print method in the Printable interface with a specified index and the program is supposed to handle it.
I've been able to successfully use this method quite well for some time but now I've encountered a more complex situation and I am hoping someone can help me design a way to do what I need.
I have a data conversion program that may process millions of database records. I'm writing a conversion report for it where a variety of notification messages will print, possibly hundreds of thousands of messages (I know a report that long isn't very useful but our clients have to print it and file it as a FDA requirment). Because of the potentially large quantities of records involved I don't want to retain all of that information to allow any page can print at any time. I won't have a print dialog so there will be no way to selectively print pages anyway. I want to open the report at the beginning of the conversion and then call functions to write report records. When a page fills up it should print and start another. At the end a close function should be called to tell the Printable to start returning NO_SUCH_PAGE to end the process.
Does anyone know a design pattern that will accomplish this? The behavior I'm seeing is that the Printable.print method gets called twice per page, once to determine if the page exists, then again to print the page. I could retain enough information to print the one page, but then I'm doing page counting that the API wasn't designed for and I'm afraid it will fail when I put it on other systems.

Have you thought about separating the two business functions of (1) executing the data conversion, and (2) generating the report(s)?
You could capture the information about the "report generating" conversion events in an XML file, and then generate your reports from this datastore. You may find some performance benefits in the conversion piece, and have greater flexibility when dealing with the XML information store.
I want to open the report at the beginning of the conversion and then call functions to write report records. Here you would write report records to an XML file, or many XML files. You also put a counter in the conversion program that will start the reporting program after a specified number of event have occured. This will allow you to generate reports as the conversion program is still running.
I could retain enough information to print the one page, but then I'm doing page counting that the API wasn't designed for and I'm afraid it will fail when I put it on other systems. You should try to avoid "page counting".
A

Choosing a design pattern for duplicate processes

Similar Messages

Maybe you are looking for