|
OriginalGriff wrote: Winner Stays On (used on some pool tables in UK pubs... You are obviously not as old as you claim to be. "Winner Stays On" was used on Foosball tables in UK pubs, long before a pool table ever landed on these shores. They then stole our space and our WSO rule. Hopefully, one day someone will realise that, (just like Grey Squirrels), they are a serious threat to our way of life!
|
|
|
|
|
I refuse to even admit that WendyBall exists!
"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!
|
|
|
|
|
OriginalGriff wrote: I refuse to even admit that WendyBall exists! Ahhhh. I forgot, where you live, they don't do the 'real' game! Although, as a Man U supporter, I'm tempted to make the jump right now!
|
|
|
|
|
We are in discussion with a external company for an integration request.
The external company's services are built as a closed-ended product with no intention for 3rd party integrations. But now they've agreed to open up the services through APIs.
We have reached the understanding at the management level and now I'm supposed to write the requirements. Can I call this as an RFC? I'm just wondering it make sense to call this as an "RFC" when the product is external, belonging to some other company.
Don't want them to feel like
Please suggest.
|
|
|
|
|
Call it RFEC - Request for External Company
|
|
|
|
|
I think this is what an RFC is (Request for Comments).
A Structured RFC Process[^]
I would look more at SDD - software design document or SRD - software requirements document for external companies, perhaps. You don't need a request document anymore since you already have a working agreement (I am guessing).
Edit: SRSD - software requirements specification document may also be of help: Software Requirements Specification (SRS Document) | Perforce[^]
modified 6-Oct-20 7:50am.
|
|
|
|
|
thanks mate!
I guess RFS is more closer for the needs.
The Lounge[^]
|
|
|
|
|
Yes. Request For Cooperation
|
|
|
|
|
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
|
|
|
|