Re: Web Payment Software Design Patterns

Brent,  I'm interested in the common technical transaction patterns that
show up in application source code structure, at this level:
http://www.martinfowler.com/articles/writingPatterns.html
http://en.wikibooks.org/wiki/Introduction_to_Software_Engineering/Architecture/Design_Patterns

When I said "high-level comparison of the mechanics of transactions" I
didn't mean as high level as use cases.  I meant "developers' technical
guide" level.

Joseph



On Sun, Nov 2, 2014 at 11:25 AM, Brent Shambaugh <brent.shambaugh@gmail.com>
wrote:

> Joseph,
>
> Here is a large body of information I produced earlier this year. It has a
> lot of links that may relate to what you are seeking.
>
> https://www.w3.org/community/webpayments/wiki/WebPaymentsUseCases_r1
>
> Sent from my iPhone
>
> On Nov 2, 2014, at 9:45 AM, Joseph Potvin <jpotvin@opman.ca> wrote:
>
> RE: "What would happen within this column, and in what order, will need to
> be the same for each payment method, I reckon."
>
> Oops. Correction: "Some essentials for what would happen within this
> column will be the same for each payment method, but their order and
> various optional features and functions can differ."
>
> Joseph
>
> On Sun, Nov 2, 2014 at 9:45 AM, Joseph Potvin <jpotvin@opman.ca> wrote:
>
>> Has anyone on this list come across (or co-produced) a high-level
>> comparison of the mechanics of transactions within the different payments'
>> software systems: debit card, credit card, automated clearing house (incl.
>> direct deposit), wire transfer, giro, ripple, blockchain systems? What I
>> have in mind are comparable class diagrams and activity (swimlane) diagrams
>> for each.
>>
>> I think what I'm imagining is something like a "Web Payment Software
>> Design Patterns" collection.
>>
>> If a functional systems comparison isn't available presently, does anyone
>> else on this list think such a collection would be useful? For my own work,
>> such a diagrammatic taxonomy will be useful. If it's not yet started, I'll
>> do so.
>>
>> It seems to me that a comparable set of system-level diagrams in this
>> form would be useful towards advancing common undestanding about the
>> contibutions and limitations of a W3C specification on web payments. For
>> example, in the various activity diagrams, the generic "browser" would
>> occupy one of the swimlanes. What would happen within this column, and in
>> what order, will need to be the same for each payment method, I reckon. For
>> the various class diagrams, there would be a package that expresses the
>> scope of the W3C specification, which contains a set of classes with their
>> respective sets of attributes.
>>
>> Useful?  Not useful?
>>
>> --
>>
>>
>> Joseph Potvin, M.Phil. MCPM
>> Doctoral Candidate, Project Management
>> Université du Québec
>>
>> Chair, OSI Management Education Working Group
>>
>> Coordinator, The FLOW Syllabus
>> http://wiki.opensource.org/bin/Projects/flow-syllabus
>>
>> The Open Source Initiative
>>
>> Operations Manager | Gestionnaire des opérations
>> The Opman Company | La compagnie Opman
>> jpotvin@opman.ca
>> Mobile: 819-593-5983
>>
>
>
>
>


-- 
Joseph Potvin
Operations Manager | Gestionnaire des opérations
The Opman Company | La compagnie Opman
jpotvin@opman.ca
Mobile: 819-593-5983