用于处理扫描问卷的 .Net 组件?

发布于 2024-07-06 14:06:36 字数 488 浏览 12 评论 0原文

我希望将扫描作为从桌面应用程序(反馈管理应用程序)中的纸质调查问卷收集反馈的一种方式。

调查问卷使用勾号或十字标记以及自由文本来完成。 调查问卷是使用应用程序设计器设计的。

我正在寻找一个组件,它可以挑选出答案并允许我将它们与问题编号联系起来,以便我可以将反馈保存到数据库中,进行汇总和分析。

看看一些调查软件公司,他们似乎通过现成的扫描软件提供扫描功能,例如 Remark http: //www.gravic.com/remark/officeomr/。 除了成本问题之外,是否有理由更喜欢像 Remark 这样的东西而不是通过使用组件来(某种程度上)推出自己的东西?

对于您使用 .Net 组件以及 Remark 类型软件的经验,我们将不胜感激。

非常感谢

AbsFabs

I am looking to incorporate scanning as a way of collecting feedback from paper questionnaires in my desktop application (a feedback management app).

Questionnaires are completed using tick or cross marks as well as free text. The questionnaires are designed using the applications' designer.

I am looking for a components that will pick out the responses and allow me to tie them back to question numbers so I can save the feedback to the database, aggregate and analyse it.

Looking at some survey software companies, they appear to offer scanning capability with off the shelf scanning software like Remark http://www.gravic.com/remark/officeomr/. Outside of the question of cost, is there a reason to prefer something like Remark to (kind of) rolling your own by using a component?

Would appreciate your ideas as to your experience with .Net componets for this as well as Remark type software.

Many thanks

AbsFabs

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

旧伤还要旧人安 2024-07-13 14:06:36

最终成本是这里的重要因素,并且有多种形式。

  • 获取组件的成本与构建自己的
  • 组件的成本与维护组件的成本与持续的许可/合同成本
  • 尝试解决所购买组件中的缺点等的时间成本
  • 实际上

,任何优点或缺点都与成本有关。 主要的权衡是采购成本与灵活性。 第三方解决方案几乎总是更便宜,但永远不会像您自己构建的解决方案那样灵活。 您必须为通过自己的解决方案获得的收益分配某种价值,并将其与商业解决方案的价格进行权衡。 (您当然可以为自己这样做的学习经验赋予价值)。

我不知道您是否在为营利性公司、非营利性公司工作,或者这是否是一个学术项目。 但无论如何,在经济效率较低的解决方案上花费时间或金钱都会花费您的金钱或机会(能够继续到另一个项目,或在这个项目上投入更多)。

我对Remark没有个人经验,但多次面临这个决定。 根据我的经验,我通常发现来自信誉良好的开发人员的、完全满足我需要的商业组件比本土解决方案更有价值。 您将获得经过良好测试的代码,这些代码将直接放入您的应用程序中,让您继续迎接下一个挑战。

Ultimately cost is the big factor here, and it takes many forms.

  • Cost to aquire a component vs building your own
  • Cost to maintain your component vs ongoing license/contract costs
  • Cost of your time trying to workaround shortcomings in a purchased component
  • etc

Really, any pro or con ties back to cost. The major tradeoff is aquisition cost vs flexibility. A 3rd party solution will almost always be cheaper, but is never truly as flexible as a solution you build yourself. You have to assign some kind of value to what you'll gain by doing your own solution, and weigh that against the price of the commercial solution. (And you can certainly assign value to the learning experience of doing this yourself).

I don't know if you're working for a for-profit company, a non-profit, or if this is an academic project. But in any case, spending time or money on an economically less efficient solution will cost you money or opportunity (being able to move on to another project, or put more into this one).

I have no personal experience with Remark, but have faced this decision many times. In my experience, I typically find that a commercial component from a reputable developer that does exactly what I need is a better value than a home-grown solution. You'll get well tested code that will drop right into your app, letting you move on to the next challenge.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文