|
It (and always was?) an RFP: Request For Proposal; in effect, asking someone for a "bid", recommendation, solution, something.
"The purpose of this RFP is to solicit ... etc."
I wrote an "external RFP" on behalf of a subdivision (due to politics), then due to politics, the project was brought in-house, and my RFP became an "internal" "Response to (my own) RFP". The RTRFP?
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
I think they are past the RFP process and now need to provide the external 3rd party with requested software design requirements. That is not contained in the RFP/RFP process, if I am not mistaken.
|
|
|
|
|
Then it's just a "User Requirements" document and no need to agonize over a "Request for Something". Just a friendly cover letter.
Then they say: "This is not acceptable." Then you go: "Propose something"; i.e. an RFP
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Great. Thanks for the input Gerry
|
|
|
|
|
|
At some point, you need to make contact with your "counter-part" in the other organization.
What you think "management" wants and what the people that do the actual work need can be 2 different things.
There's always some politics / turf disputes; depending on who you cultivate, the road is easy or rocky.
I usually start with: "Hi, I've been assigned to ... and I was told that ... and would like your thoughts, etc." Casual-like. Start as a serf; then become the master.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
It probably depends on what stage you are at - and the level of detail you are planning. You could go with:
BRD - Business Requirements Document - which would be a fairly high level description of what the business needs/expects.
TOR - Terms of Reference - would probably flesh out a bit more, such as scope, risks/contingencies, critical success factors, etc.
Specification - which would describe the nuts and bolts of the API content and how it will interact.
I guess in these 'Agile' days, the above are all frowned upon. You just need to put: "I want x,y,z" on a post-it note and stick it on a white board! 
|
|
|
|
|
5teveH wrote: You just need to put: "I want x,y,z" on a post-it note and stick it on a white board!
That is how I am used to it being done now days. 
I used to have to work on SDDs in the past, though. Ugh, not fun.
|
|
|
|
|
I was just having the same conversation with a product manager here.
Agile doesnt mean cutting off all analysis and shrinking it to a post it note.
It's completely screwed.
|
|
|
|
|
Great. Thanks for the reply, @SteveH. Quite useful.
5teveH wrote: I guess in these 'Agile' days, the above are all frowned upon. You just need to put: "I want x,y,z" on a post-it note and stick it on a white board
Precisely, What I did not want to follow. 
|
|
|
|
|
Arrrgh. apologies in advance
ITYWIWWIRRW
I'll tell you what I want, what I really really want
|
|
|
|
|
What ever you go for, please be aware to use the long form the very first time you use the acronyms to specify. Or at least don't forget to write down:
"if you don't know what RFC is... RTFM" 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
In summary, male otolaryngologist works alone, making sense of bugs. (13)
modified 6-Oct-20 7:45am.
|
|
|
|
|
Not sure about the "otolaryngologist" bit, but ...
In summary, (anag)
male TOM
otolaryngologist SETING?
works alone, SOLO
making sense of bugs.
ENTOMOLOGISTS
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Wow, that was quick. But wrong. Surprisingly, the answer is close, but every bit of the working is incorrect.
|
|
|
|
|
That's kinda a relief ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Building on OG's suggestion
In summary, otolaryngologist - Ear Nose Throat doctor or ENT
male - not sure about this
works alone - singular , not plural
making sense of bugs
Entomological
(of or relating to the biological science of entomology)
// TODO: insert something here
|
|
|
|
|
Got it! You're up tomorrow
In summary (next phrase is initials)
Male otolaryngologist (Ear, Nose + Throat) = ENT (man)
works alone (One Man Operated) = OMO
makes sense = LOGICAL
ENTOMOLOGICAL = of bugs
The contentious bit might be "OMO" I guess. "One man operated" used to be a common phrase, typically relating to public transport but not exclusively so. I remember when the old buses started to be phased out, the new ones all had "This is an OMO bus, please have your change ready" at the door. When political correctness started to take hold, it was sometimes expressed as "OMO / OWO" but now the terminology tends to be simply "single-crewed". But it was to comply with PC that I added the "male" prefix, so as not to lead people to ENTOWOLOGICAL
I'd hoped that even without the OMO bit there was enough there to get to the answer with confidence.
|
|
|
|
|
 Oh dear, didn't expect that. I'm only starting to get a glimmer of understanding these CC's.
I've never made one up before, will give it my best shot.
Feedback be definitely be welcomed (please) ...
// TODO: insert something here
|
|
|
|
|
yacCarsten wrote: Oh dear, didn't expect that.
Don't panic; it's not the Spanish Inquisition[^] after all
|
|
|
|
|
From where i can learn programming in discount please suggest me
|
|
|
|
|
|
We can't really answer that except in the broadest terms: we have no idea what is available near you so "in discount" (which I assume means "really, really cheap") isn't anything we can evaluate for you.
So in broad terms:
1) The best way to learn programming is via a course: that way if you don't understand, the tutor can rephrase and explain until you do. It is possible there may be free or subsidised courses near you but that would be up to you to check.
2) The next best way is via a book - Addison Wesley, Wrox, and Microsoft press so good ones - this needs you to read the whole thing from start to finish and complete every exercise yourself in order to get anywhere useful. Ignoring the exercises or hunting for internet solutions won't teach you anything!
3) The first worst way is to get a compiler and wing it. Guess what the language works like, guess what you have to do. About as effective as learning to drive by stealing a car and hoping it doesn't crash and burn.
4) The worst way is via YouTube: finding any development videos that aren't made by idiots is a major challenge. Most of 'em are produced by people who have no idea how to make a video, and even less idea how to code. Avoid, they are there for subscribers and monetization.
Needless to say, generally speaking the costs go the other way: a course is most expensive, youtube is cheapest. But you do get what you pay for ... most of the time! As mentioned there may be cheap / free courses available locally, and libraries often have access to nationwide book lists and can sometimes provide loans of technical books if asked really nicely.
You will need to decide on a lot of things before you launch into learning to code: Languages, frameworks, environments: there are a lot of them, and selecting the right ones can be difficult. I'd suggest learning C#, under .NET, for Console and later Winforms as the simplest "starter" set: it'll give you access to a lot of employment positions when you have some experience.
One thing to note: this is not going to be a quick process, regardless of which route you go. Learning how to code is hard work, and it takes time - there is a huge amount you need to know to be effective, and your "way of thinking" has be be expanded to be at all effective.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
What he said.
I have been programming since 1975 and I am still learning.
If you think it is going to be quick and easy, think again.
Good luck, if you "get it", it'll be fun!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Yes, very true.
Me, I have I never had any sort of "programming course" except for a tiny bit of COBOL, PASCAL and FORTRAN when I was studying to get an engineering degree in electronics (telecommunication).
Still, I have been programming since 1980 and like you I am still learning things. In fact, if I didn't I would have been out of the business a long time ago. 40 years of relentless evolution is something you can't ignore. If you do you might as will give it up as you will become obsolete in no time flat.
As to it being easy: no it is not. If you get the hand of it though it never becomes boring.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
