|
|
That's such a bad idea...
|
|
|
|
|
Does it have a death ray on board?
Asking for a friend. Yeah, a friend ...
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Traditionally, large satellites are configured on the ground for specific tasks that cannot be changed after launch, even if market demands evolve.
I don't agree with that. When I worked for a major satellite manufacturer, the satellites would often launch with just basic capabilities and the final operational software would be uploaded once it was in orbit. That way, the software could continue to be developed while the satellite hardware was dealt with, decoupling the launch schedule from the software development schedule.
The whole point of a communication satellite that has a 15 to 20 year (or more) lifetime is that it can be configured as requirements change and as hardware fails on the satellite -- that was the part I was working on, testing different end-of-life failures of the high power amplifiers and being able to switch to spares -- one of many things that can be reconfigured once in orbit.
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
So what you are saying is that satellites are nothing more than orbiting JavaScript libraries. 
When you are dead, you won't even know that you are dead. It's a pain only felt by others.
Same thing when you are stupid.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
Marc Clifton wrote: while the satellite hardware was dealt with
IF the thing explodes while on its way, you did not have to check-in the last version of the code. 
|
|
|
|
|
about time
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
|
It's a shame it'll go offline, every few weeks, after each mandatory winio update.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Speaking in code: Grave - Oscar - Chart - Yankee. (12)
|
|
|
|
|
Speaking in code:
Grave - CRYPT
Oscar - O
Chart - GRAPH
Yankee Y
CRYPTOGRAPHY
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Yes of course, well done!
|
|
|
|
|
Hi All,
Can someone recommend a strategy for managing and development of projects that are Hardware & Software. Its just that AGILE doesn't seem to be applicable for hardware. The big thing is with agile is that it can change right up to delivery which is fine for software but not for hardware which is physical a change will require a re-spin of the board (unless you want to ship a board with tombstone resistors and bodge wires (or ![Green Alien | [Alien]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/alien.gif) preserve us as I have done once a (small)BGA upside down with wires on the balls to pads)).
|
|
|
|
|
A guess would be kanban.
Kanban is what came out of the Japanese just in time production line system - given your example, if something changes regarding hardware then the processes that depend on that new hardware are going to have to wait until that hardware is ready.
Although my preferred development strategy for all projects is MUYBM (Make up your bloody mind! )
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Yes and no, kanban is a method to optimally handle logistics for production (supply, ressources, ...). If kanban is implemented, you do not have to wait.
|
|
|
|
|
|
On not, 'Waterfall' 'it's not the 80's we have gone beyond that, it is so dated' (but it works!!) 
|
|
|
|
|
So check the links at the bottom of the article, there are plenty of methods to use.
Pick the one with the fanciest name.
|
|
|
|
|
The places where agile "works" are the places where it is implemented as a continuous waterfall-cycle 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Well - I know you need to attract and keep the new crop of developers, so kumbaya programming techniques must be adopted. At all costs! At any costs!
Thus, I suggest you adapt the hardware development to the Agile . . .
| 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 |
|
|
|
|
|
Can you use FPGA or flash EPROM/firmware and turn the hardware problem into a software one?
|
|
|
|
|
Hecky thump!, this beast I'm working on has FPGA's, SODIMM PC104's, it's just that the sort of Agile approach means it's not really getting anything done. 
|
|
|
|
|
Well yes - the point of Agile is to look busy while not getting anything done.
|
|
|
|
|
They've tried to use a software strategy for Hardware/embedded see a problem here... 
|
|
|
|
|
Waterfallish Agile.
Waterfall for the hardware part. Agile for the software part.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
