Best Online Examples of Workflow Patterns?
g8orade writes "In his bestselling book, The World is Flat, Thomas Friedman lists workflow management software in the top 5 Flatteners. During my work for a shipping startup, I have analyzed our software's many UI weaknesses, particularly related to workflow management, and am currently searching for the best online examples of various UI application patterns / widgets that address managing transaction flows. What are the best examples you know of that are commonly viewable on the web?"
"Our software UI is Oracle (9i) Forms compiled to run with Java, through the web. We're using RT for our internal ticket tracking and it has many of the features listed. Also, we're evaluating several commercial document management systems as bolt-ons or companions to our in-house application. Here are some patterns we'd like to improve:
- Queue with count beside it. Example: 'Unshipped orders (5)'
- Screen for UI building of a search and ability to save the search as a queue
- List of queues showing all transaction counts and their various states
- Transaction list / table screen (should have an many possible features as a standard spreadsheet: pick your columns, column order, sort order, clickable column headings, export to various formats, print view, etc.)
- Detail view screen (one transaction, may include too many fields to display at once, requiring tabs, scrolling up and down, left to right, etc., should have a good printable view)
- Contact database built-in or connection to one from another system
- Auto messaging of various statuses to contacts and lists of contacts, above
- Full web accessibility and security model to allow our suppliers and clients access to their own queues for 'pull queries', in addition to what we email them.
- Ability to create a list of values for a field, then incorporate that into the query for a queue.
- Journal of a transaction
- Screen showing progression of a transaction
- Screen showing Parent / child parts of a transaction"
... in the article (just posted) is incorrect.
The correct link is http://www.patternlanguage.com/
Seriously, could someone explain to me why patterns are what is needed here? From my experience, user interface design takes a deep understanding of customer requirements. Applying patterns would seem (imo) like an entrapping short cut that ultimately would be a waste of time. Any thoughts?
Have a look at the YAWL project of the Business Process Modelling Group at the Queensland University of Technology. YAWL stands for Yet Another Workflow Language and is based on petri nets. The BPM group claims it can model any workflow pattern. Link: http://www.yawl.fit.qut.edu.au/.
Are we talking about globalization or software design? WTF?
I get the weird feeling that you're trying to solve your problems by throwing more processes, tools, and abstract concepts to the mix.
Just learn about use cases, flow charts, and screen mock-ups and your world will be simple and happy.
Help me take back Slashdot. When did 'News for Nerds' become 'FUD and Conspiracy Theories for Extremist Nutjobs'?
Is that what he's asking? I had to CTRL-F and search for a "?" to make sure you weren't pulling my leg.
body massage!
I have looked fairly extensively for a nice open source version of a workflow type program. One that I am currently watching is http://pentaho.org/. This is a very impressive package of not only workflow but business intellegence and reporting.
Afraid I have to agree with the AC, g8orade. You haven't even posted on /. since May '02 (and haven't answered anyone else's "Ask Slashdot" question, like, ever) and you're expecting everyone here to do your googling for you? Again?
I, for one, do not welcome our lazy, buck-passing overlords.
It has a worfklow engine that may be too abstract as a starting place for you, but the OfBiz app itself may already be doing pretty much everything you want anyway. It's java, open source, and been around for years, though not easy to tweak or get stably up and running.
So.. this would be how you get a beowulf cluster of slashdotters to do your job.
Impressive.
Here's a link you might follow to get you onto the right foot. It seems to me that all of your 'needs' only *need* some research. Jakob Nielsen's usibility guidlines are a good headstart. My own suggestion would be KISS.
We're all hypocrites. We all have hidden parts, it's the contrast between them that make us more a hypocrite than others
Well, I've always thought a little icon of an envelope was pretty good for representing mail.
Well the classic MVC combined with Observer does the job for most UI designs, especially in terms of web transactions that fall under the Oberver Observable mould. Java provides a rich set of Observer implementations: java.util.Observer and Java Beans' PropertyChangeListener. If you want to a really good implementation that removes a lot of the deficiencies in the above, use Impresario developed at ArchSynergy and Dr Sandeep Mitra. If you would need details on this let me know.
I found an excellent resource for this. They cover a new example each work day. Some of the examples are truly brillant.
I started it and tried to read it but found it a slow read. His points were not very interesting and I really thought it was just badly written.
Read the book, AssHat! Friedman is NOT a developer and not even software savvy, so when he titles something "workflow", you have to read what he says, and what he says is "web apps".
Bad news is that every "Web 2.0" marketer is going to interpret Friedman's words in the most convenient way. Like the Far Side cartoon with two bears at the cave door fighting off humans: "Seems like there's more and more of these each year!"
Go to the person who is most likely the creator of the whole idea of UI testing and design. Jeff Raskin. All others came after him. His writings, ideas etc are still maintained by his family on his home page.
http://jef.raskincenter.org/home/
Including his work on the Humane Interface.
I'm sorry, I'm to tired to be witty at the moment so this message will have to do.
Shop as usual. And avoid panic buying.
I have to disagree, Joe. Bits are easier to move than atoms, if there's connectivity; the advances in telecommunications that Friedman cites have created that connectivity. It is this development that enables many types of bit-moving knowledge work to be done globally, not cheap energy.
But, even if it was cheap energy, rising prices would only slow down globalization, not stop it. Rising oil prices in a market-driven global economy would only result in more dollars available for R&D into energy alternatives, driving more innovation and eventually solutions. Energy would continue to be available.
Because it makes for an interesting discussion.
Nah, I disagree man. I'd like to know more about what the UI problems with workflows are ... I'm a really big project-management-software hater and am intrigued to see if there are any experiments with alternative UI's.
It happens to be (about to be) my job too, so you can accuse me of self interest too. But hey - interesting discussion. Better than some halfarsed regurgitated press release, eh?
Dave
I write a blog now, you should be afraid.
I've found this useful: http://is.tm.tue.nl/research/patterns/
I have discovered a wonderful
... (1) how many bottles of Scotch the Brass are willing to
... they'll get much less than 40 hrs in 5 days.
... I'll probably fell sorry for them and take
... now we're talk'n about a 40+ hr per 5 day ... but not much more.
... now we're talk'n about
give me outside the contract.
One bottle
Two bottles
them out to dinner.
A bottle a day
week workflow
5 bottles of Sake and dinner each day
a regular 72 hr workflow in 5 days.
The key to a Samurai's heart is through the stomach.
Cheers!
From there, we (the users) can initiate a number of processes. An engineering "Test Order", for example, will require management/supervisor approval, finally requiring that an engineer submit a "Test Report", which also goes through an approval process, and so forth. If someone is on vacation, it gets re-routed to the responsible person. If an engineer bounces the request because he doesn't have the parts, the request goes back to someone else, etc.
These types of systems eliminate walking paperwork around the office for various signatures -- trying to find someone, playing phone tag, etc.
You should check Thomas Malone and his Coordination Theory, he has an open source project on business processes