|
|
Yes, been there, done that, safety critical software to DO178 Level A (so that's aerospace software - flight software specifically).
Yes, formal requiremenymts and design (plus full traceability from requirements down through design, code and up through unit test, requirements test and validation). The most stringent part is verification - peer review of all artefacts, unit test with 100% coverage of statements, branches, decisions and as high as possible with MC/DC (modified condition/decision coverage). Oh, and coverage from source to object code because the (Ada) compiler isn't formally qualified.
Don't do that now, but still have close contact with it - it's expensive, but it's what's required by the standards...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Formality seldom survives the first missed deadline.
Software engineering is not a programmer's term; it is a manager's term.
|
|
|
|
|
It is often overseen that a users does not use software like she/he uses a car but uses the services that the software "produces" together with other components like devices, clouds, etc. So software is part of a production site that generates the IT-Services the user needs to run her/his tasks better and more efficiently.
So when looking for professionalism in IT-services the first and most important question is what quality of service the user needs to get the wanted benefit out of that IT-service. And the whole process to define, engineer, develop, deploy and run the production site that delivers the IT-service as "promised" is much more complex than the formal software engineering process delivers today. SO what we need is a formalized approach in Business Analysis that is also delivers quality criteria relevant to the user and not only functional specifications. This is far apart from being a trivial task.
Best regards
UP
|
|
|
|
|
Sure. In government or military contracts.
Mostly what we produce is a _huge_ pile of documentation showing how no taxpayers money was wasted (not including producing said huge pile of documentation).
The unstated aim is to move money from the public sector into the private. An actual working product at the end is pretty much an afterthought. Or if it's a working product, then it's not what the users want - rather what the users bosses they _said_ they wanted several years ago, which leads to the next contract.
That's not to say formal specs don't have their place. Many medical devices will have formal specs due to the risk that lives could be lost if there's a serious bug.
|
|
|
|
|
Government contractor here, and I can concur. A colleague of mine often points out that the the documentation we produce must produce stacks of paper that are tall enough that we can use them to build a fortress to protect ourselves when the auditors attack the castle.  I produced a 1000-page ATR just last month (I didn't actually print it out, though).
Having said that though, I should also mention that I am on a team that is introducing Agile methodology to this heavily waterfall-dominated workplace, and we are making some real headway. One of the keys that has helped us a lot is the use of quality tools: Jama for requirements development, JIRA for issue tracking, etc. Introducing these tools has really helped us to start enjoying the best of both worlds. (That 1000-pg ATR, for example, was automatically generated from our Jama repository.)
|
|
|
|
|
ALL MEN MUST DIE?
The warden of an overloaded prison decided to ease the situation in a somehow brutal way...
He told to the inmates, that from the next day he will line up the inmates from each section (between 20 to 30) in a way that they can see the inmates before them, but not those behind. The guards will but a black or white party-hat on the head of each inmate in a random way...
From back to front, each prisoner have to say what color the hat is on his own head. Those are guess wrong will be executed...
What the inmates can do?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Since you didn't add any other rules, why not take off their hat, look at it, and then give the answer?
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I asked the warden - touching the hat punishable by death...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
But the hat is on his head, so it is touching him. Therefore he is already touching the hat and all prisoners die immediately.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: and all prisoners die immediately.
That does fix the overcrowding issue.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I told - the warden is a brutal creature...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
The way I heard it, one guess is allowed to be wrong, if more than one then all prisoners die. You can't turn around, only see the prisoners in front, can only provide one answer.
Very difficult for many, quite simple for those of us who lived in the early days of serial communications and error-prone memory.
|
|
|
|
|
Assuming there is an equal number of black and white hats, the guy at the tail end of the queue can see every hat except his own. He can correctly guess the colour of his own. The guy in front of him uses that and the hats he can see to say what colour his hat is, and so on.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
The number of black and white hats is unknown...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Martyr's solution:
Tell the person in front of you their hat color. Take your guess and hope they can all thank you later.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
That will break on the first color change...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
No - each prisoner looks at the prisoner in front of them and reports his hat color to him - they can then do the same for the next prisoner and announce (correctly) their own hat color since it was told to them by the prisoner behind them. They can all be the same color or any number of identifiable colors.
Only fails if there are liars or blind prisoners - but picks up again.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: Those are guess wrong will be executed...
Then they should all refuse to guess! 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Alas - just after you left I asked the warden about that. He said it's guess or die.
(my answer to the unsaid is better, so there!)
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
The guy at the back can save the others but not himself. They agree a code - let's say if there's an even number of black hats in front of him he calls black, otherwise he calls white. That gives everyone in front of him enough information to work out what colour hat they're wearing e.g. second guy knows that there are an even number of black hats but knows that there are an odd number so can conclude that his own hat is black.
The guy at the back's chances are 50-50 (probably less if a sadistic guard heard the prisoners devising the code) but at least he's taking one for the team.
Solution 2 is build a time-machine; go back and vote for someone else. This is a very unhealthy country that they're living in.
Slogans aren't solutions.
|
|
|
|
|
|
Ask the guy behind you what color your hat is
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Paint their, *ahem* "appendages" with silver paint, drop their trousers, and look at the hat in the reflection.
To every problem, there's always an easy solution.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The Prisoners, realizing that the warden will be fired if they all die, all answer RED!
He kills them all, is fired for there are no prisoners, and they get their revenge!
Oh, and the guards end up working for walmart.
Or they all sneeze at the same time and all the hats FALL OFF Magically.
Or they tell the guy in front of them, and the last guy changes places with the second from last guy when the guards are not looking.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
