Slashdot Mirror


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"

8 of 82 comments (clear)

  1. Why patterns? by waffleman · · Score: 5, Interesting

    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?

    1. Re:Why patterns? by rossifer · · Score: 4, Insightful

      They are almost by design so generic [...] that they are appropriate for nothing

      I find them useful for communication. If my design is similar to a pattern (most patterns are only part of any solution) then I can use the name of the pattern to describe my design more quickly. Often, because a pattern will include several distinct elements, I am able to convey several nuances of a particular design with only one or two words.

      Explaining a design in terms of patterns is also a cool way of mentoring junior developers. You can back them out of the details of "this problem" and take a look at the more general situation, what the pattern suggests, and then go back to "this problem" and see how it fits in. Often you'll be able to elicit multiple "a-ha!'s" from the junior.

      Back to your point, I find that the best pattern authors understand that they must strike a useful balance between generality and specificity. You still have to design the solution, but the top-level "how the heck do I get started here" is what's described by the pattern. Fowler tends to be better than the GoF at this particular skill.

      Of course, getting the most utility out of patterns absolutely requires that you are an experienced designer (or are working with one). This means applying all of the classic design skills, including patterns, as appropriate to solve the problem (and that may mean no use of patterns for a particular problem).

      Regards,
      Ross

  2. YAWL by asphinx · · Score: 5, Informative

    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/.

  3. Huh? by TrappedByMyself · · Score: 4, Interesting

    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'?
  4. Open Source Solution by mudwump · · Score: 4, Informative

    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.

  5. Re:Why don't you DO YOUR JOB? by Tsar · · Score: 4, Insightful

    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.

  6. Agreeing with afformentioned posts... by Chabil+Ha' · · Score: 4, Informative

    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
  7. Examples by Velox_SwiftFox · · Score: 4, Funny

    Well, I've always thought a little icon of an envelope was pretty good for representing mail.