|
|
Anyone who arrived too late to catch AirAsia flight QZ8501?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Ah, so the only way to win...
Whoa! I'm getting deja vu all over again!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
See above (3)
PooperPig - Coming Soon
|
|
|
|
|
This[^] song was on the radio this morning and now I am hooked to it.
|
|
|
|
|
Well, you write pretty well for being a bird...
|
|
|
|
|
But of course - he has all the quills he ever need for that...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Hey, it's not bad! 
|
|
|
|
|
Sir, let's have a song duel!
I challenge your song with that[^]! 
modified 5-Jan-15 6:32am.
|
|
|
|
|
Joan Jett meets Robert Palmer meets Giorgio Moroder in Hell ?
«A man will be imprisoned in a room with a door that's unlocked and opens inwards ... as long as it does not occur to him to pull rather than push» Wittgenstein
|
|
|
|
|
I'd rather be phishing!
|
|
|
|
|
How do i create Proof of Concept for my new Web Application Project. I never Created any POC so far. But my Client asked me for POC before start to develop. I don't know how to Start? what contents should i Cover ?
Any Idea?
The Project is about to Stock Management.
Born To Learn
|
|
|
|
|
Maybe your client meant a prototype? What new concept you have here that need a proof?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Difference between the both(POC and Prototype)?
Born To Learn
|
|
|
|
|
PoC - When you have an idea of how to do something, but not sure if it will work, so you build some working model than can prove (or not) you idea...Once I had an idea how to 'clean' scanned images using math (standard deviation) and made a software to prove it...
Prototype - It's a working minified/simplified version of your product (software), that show the main functions and your ability to create it at the same time...Again, I once made software for WiFi modem and the company created the board (almost manually) and printed on a 3D printer a prototype of the case to show how it will look like...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
|
can you Refer some Sample Template of POC
Born To Learn
|
|
|
|
|
Wikipedia knows it all: Proof of concept. 
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
A Proof of Concept is all about showing that an idea can work - not that it does, or it's complete, but that it can be done.
The big difference between a PoC and a Prototype is that even the worst Sales department can't sell a PoC...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: even the worst Sales department can't sell a PoC...
I see what you did there.
Your time will come, if you let it be right.
|
|
|
|
|
I've had sales departments sell prototypes before - and it's a nightmare, because you have to support the damn things for years despite them not being production ready. 
But...a PoC is so obviously not ready to be used that no-one will buy it! One of mine was a huge pile of electronics housed in cardboard boxes with mains leads running out the back. (We did cut ventilation slots in the boxes to prevent them catching fire, and checked the slots with the British Standard Finger to make sure we didn't electrocute customers) No way was the customer going to buy that! (But he was willing to talk about £2M worth of software development off the back of it, since it clearly could do what he wanted it to, if in a rather "fire-hazard" kind of way...)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I think you are looking at a PROTOTYPE rather than a PoC, I would mock up a couple of screens with dummy data without any database connectivity, make the UI as good as possible as that is what is going to sell the idea.
You need to be a little careful here as the client may just keep asking you to add bits to the prototype until you find you have built the app (this has happened to me) and then will argue the cost once it is done.
I would also get the client to make a commitment to the cost of building the prototype. You may lose the client and save you business.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I think in these cases (see the various cautions in other posts on this thread), you best protect yourself by making sure you have a clear understanding of what the client expects.
1. presentation: does the client expect to see a certain UI mock-up, use of visual themes/styled, etc. ?
2. functionality: does the client expect to observe your app connecting to an existing database and performing CRUD operations ? Expect to see accessing internet/cloud and saving/reading/scraping, etc. ?
3. algorithms/performance: does the client expect to see you processing some data in a certain amount of time in a particular way with particular results.
4. Ui features ?
By knowing, as precisely as possible, what the client expects before approving/hiring/paying, you can then estimate what your time costs are in preparing the prototype, and negotiate with the client. Ideally, you are in a position to state what you will, or won't do, for a certain fee prior to any longer-term contractual agreement.
Of course, in the real-world things are not so clear-cut, and, in the past, I have negotiated a flat fee for a certain period of my time (full-time, paid by the month) specifically to prototype, with the understanding that the client, or I , can cancel at the end of each month.
Flexibility may be necessary on your part, weighed against how much you trust the client, what you know of the client's dealings with other developers. I once worked eighteen-months full-time based on a handshake with a CEO, no contract ... that's rare.
I tend to think of POC and Prototype ideas like this:
1. Proof-of-Concept: answers questions which ask: "Can this be done ?"
2. Mock-Up/Sketch/WireFrame: purely visual representation of a UI, or of a WorkFlow, or some form of Diagram of state behavior of an Application.
3. Interactive Prototype: working simulation of UI interactivity possibly using mock data, mock database, etc.
4. Functional Prototype: working simulation of the basic functioning of an application including accessing real database, processing real data, etc.
Your mileage may vary
«A man will be imprisoned in a room with a door that's unlocked and opens inwards ... as long as it does not occur to him to pull rather than push» Wittgenstein
|
|
|
|
|
BillWoodruff wrote: Your mileage may vary
And objects in the mirror may be closer to Proof of Concept than they appear...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Aye, and, understanding the particular spherical aberrations, or generic concavity, or convexity, in the Client's mirror, as well as your very own: aye, there's the game
«A man will be imprisoned in a room with a door that's unlocked and opens inwards ... as long as it does not occur to him to pull rather than push» Wittgenstein
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
