Is there an NCPDP [National Council for Prescription Drug Programs] implementation reference standard - especially one written in a .NET language?
NCPDP publishes several different standards for different purposes and there can be no single answer to this question. To which are you referring?
Mark
Related
There seems to be quite a few different ways to tackle parsing ETW events (TraceProcessing, TraceEvent, ETW2JSON, etc.). I'm interested specifically in the trade offs between the TraceProcessing library and the TraceEvent library.
Are they intended for different usecases?
Did TraceProcessing come about as a follow on to or evolution of TraceEvent?
Why would one choose the TraceProcessing library instead of TraceEvent library?
(I am a developer at Microsoft who works on the TraceProcessor project.)
I have a little more familiarity with TraceEvent than with ETW2JSON, but the same answer applies in both cases.
Each was developed by different organizations within Microsoft to best support our own performance and diagnostic investigations. In some cases, we took design inspiration or cues for TraceProcessor from other libraries, but largely we developed it for our specific use cases and according to our own design philosophies.
Those differences mean that each library has its own principles about performance, API design/consistency, and broad-based ETW support vs. well-developed first-class support for certain specific things.
TraceEvent does have .NET/CLR support, but focuses mostly on being a manged wrapper around the C++ ETW APIs. It does have support for other events, but very limited.
All in all, TraceEvent is great for first-class .NET/CLR data and the "basics" elsewhere.
TraceProcessor gives strong first-class support to the types of system and diagnostic data that you could see in other tools like XPerf and WPA. We’ve pushed for a clean, consistent, performant API across the library and emphasized strong typing to present each type of data in the most natural shape.
Some years ago was many information about Code Contracts. I did not have time to learn it and found this time only now :)
But when I try to use it, I see, that Visual Studio 2017 does not support it, CC tool is updated last time more than 3 years ago...
So, Code Contracts is closed for now?
Sadly, Code Contracts is no longer supported.
The good news is that C#8 is going to include a new nullable reference types feature that will handle a large portion of the invariants and pre- and post-conditions for which Code Contracts was used. This will assist with detecting and avoiding possible null-reference exceptions.
The bad news is that there is no built-in support for other types of contracts, and nothing like it has been announced for the future.
Correctness guarantees will have to come from third-party tools, or another language will have to be used (e.g., Ada Spark).
OpenFOAM (the latest versions at the time of writing) provides three types of test filter for large eddy simulation applications:
simpleFilter
laplaceFilter
anisotropicFilter
Considering there are various anisotropic filters proposed in the literature, could anyone tell us which reference was used in the code implementation of the anisotropicFilter, as such information is not available through the code guide?
The answer was kindly provided by Henry Weller in response to a feature ticket:
The anisotropic filter was not implemented with reference to any
literature.
Can you suggest some good real live and not too simplistic implementations based on Caliburn Micro where the source code is available to study approaches to common problems and "best practises"?
Have you had a look at the Caliburn.Micro contest winners for 2010? I don't know if they are too simple for your needs, and how up to date the projects are in relation to changes in the framework since they were submitted, but you could try there.
I'm not sure what common problems and best practices you are referring to over and above the samples that Rob provides on the CodePlex site.
My organization has recently been wrestling the question of whether we should be incorporating different middleware products / concepts into our applications. Products we are looking at are things like Pegasystems, Oracle BPM / BPEL, BizTalk, Fair Isaac Blaze, etc., etc., etc.
But I'm having a hard time getting a handle on all this. Before I go forward with evaluating the usefulness (positive or negative) of these different products I'm trying to get an understanding of all the different concepts in this space. I'm overwhelmed with an alphabet soup of BPM, ESB, SOA, CEP, WF, BRE, ERP, etc. Some products seem to cover one or more of those aspects, others focus on doing one. The terms all seem very ambiguous and conflated with each other.
Is there a good resource out there to get a handle on all these different middleware concepts / patterns? A book? A website? An article that sums it up well? Bonus points if there is a resource that maps the various popular products into which pattern(s) they address.
Thanks,
~ Justin
I've spent the last 3-4 years blogging on the topics you mentioned (http://www.UdiDahan.com) as well as writing my own lightweight ESB (http://www.NServiceBus.com) and many more years working and consulting in this space. The main conclusion that I've come to is that strong business analysis and technologically-agnostic architecture is needed - no tool or technology can prevent a mess by itself.
There is the Enterprise Integration Patterns book which provides a good catalog of the technical patterns involved but doesn't touch on the necessary business analysis. I've found that Value Networks (http://en.wikipedia.org/wiki/Value_network_analysis) can be used as a good start for identifying business boundaries to which IT boundaries can be then aligned, resulting in the benefits of SOA, and the use of an ESB across those boundaries is justified.
CEP, WF, and BRE should be used within a boundary and not across them.
ERP packages tend to cross boundaries and, as such, should be integrated piecemeal into the boundaries mentioned - DDD anti-corruption layers can be used to insulate custom logic from those apps.
Hope that helps.
IBM and Oracle have SOA certifications. Since they're the leaders in the marketplace (Gartner Magic Quadrant), I would read about how they define SOA and ESBs (along with methodology and the components needed to support SOA like Governance, Registry, etc etc). It'll give you the high level overview that you're looking for and the use cases "all this middleware" is trying to solve.