如何在c＃中存储数字唱板和指纹值以及如何获得该值 [英] how to store digital sing pad and fingerprint value in c# and how to get that value

问题描述

i am going to create a desktop application which needs to support finger print reader, this application need to support fingerprint registration and store it database , but must be need to create in desktop application, kindly help me out..

ex. i have new customer so i need the details his name, address and mobile no and his signature and his fingerprint so i want to digital sign pad and finger print authantication in c#.

推荐答案

软件开发生命周期中有几种可接受的模式。经典的5层瀑布仍然看起来有用，但我更喜欢4点螺旋，所以我们会住在那里。是的，我知道有许多很多其他建筑模式，但我们在这里减少。



迭代1：



1.分析。确定软件的最终目标并充分了解客户需求。你似乎有一个很好的，一般的起点，这似乎就在你身边。



2.设计。这是您开发模型的阶段，您将使用该模型来解决Analysis中确定的需求。许多软件工程师喜欢在这一步中使用UML，但我个人更喜欢使用psudo-code和doodling的神秘组合（我认为在纸上很好）。您应该在询问任何特定于代码的问题之前执行此操作，因为您应该确定在此阶段您将使用的语言。



3.实施。在这里，您可以使用您认为最适合的语言编写实现您在Design中设计的模型的代码。否则被称为橡胶与道路相遇的地方。



4.测试。确保代码实现与模型匹配，最终符合客户要求。



迭代2：



5.分析：现在我们已经完成了一次迭代，我们可以重新审视需求并决定是否需要满足其他要求，或者是否有任何要求与我们最初的想法不同。这可能是整个SDLC中最关键的一步，因为我们有机会抛弃预先设想的概念并正确识别我们软件带来的价值。如果你的要求没有改变，你可能做错了。



6.设计：决定需要对模型和设计做出哪些改变他们。不要为了这样做而抛弃结构。这可能是最艰难的一步，因为它很容易缠绕在轴上并开始微观优化。



7.实施：这基本相同。如果你不自由地评论你的代码并忽略所有的命名约定，那么回去说WTF我在这里做了什么就变得很常见了。



8。测试：你应该精炼到足以退出纯粹的内部测试并推送到Alpha版本。



等等...



这并不是一个讽刺的答案，只是为了说明你在哪里以及在开发的任何特定时刻你应该关注什么。你的问题很模糊，我认为这是有道理的。

There are several accepted patterns in the Software Development Life Cycle. The classic 5-tier waterfall does still see use, but I prefer a 4-point Spiral, so we'll live there in my answer. Yes, I know there are many, many, many other architectural patterns, but we're reducing here.

Iteration 1:

1. Analysis. Identify an end goal for the software and get a good sense of the client requirements. You seem to have a good, general starting point, and this appears to be where you are.

2. Design. This is the phase where you develop the model which you will use to address the requirements identified in Analysis. Many software engineers like to use UML for this step, but I personally prefer an arcane combination of psudo-code and doodling(I think well on paper). You should do this before asking any code-specific questions, as you should identify what languages you'll be using in this phase.

3. Implementation. This is where you write code that implements the model that you designed in Design, using the language that you identified as the best fit. Otherwise known as "where the rubber meets the road."

4. Testing. Make sure that the code implementation matches up against the model, and ultimately against customer requirements.

Iteration 2:

5. Analysis: Now that we've completed one iteration, we can revisit requirements and decide if other requirements will need to be met, or if any requirements are different than we initially thought. This is perhaps the MOST crucial step in the entire SDLC, because it is our chance to throw out pre-conceived notions and properly identify the value that our software will bring. If your requirements haven't changed at all, you're probably doing it wrong.

6. Design: Decide what changes need to be made to the model and design them. Don't throw out structures just to do it. This is probably the HARDEST step, because it becomes easy to get wrapped around the axle and start micro-optimizing.

7. Implementation: This is basically the same. If you don't comment your code liberally and ignore all naming conventions, it becomes pretty common to go back and say "WTF did I do here."

8. Testing: You should be refined enough to move out of pure internal testing and push to Alpha version.

AND SO ON...

This isn't meant to be a snarky answer, just to illustrate where you are and what you should really be focusing on at any given moment in development. Your question was vague enough that I felt it was warranted.

这篇关于如何在c＃中存储数字唱板和指纹值以及如何获得该值的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！