At the University of Pretoria we had two teams develop the same project - the one using a waterfall based development method and the other using Scrum as an agile development process. The project was to add client based secure group chat functionality to the Linphone chat application without making any changes to the server -- i.e. the server did not have any group chat functionality itself. The result was interesting. The waterfall team committed more thought into the software architecture and came up with a distributed architecture without a single point of failure - even if the group creator./owner went off-line, the remaining group members could still continue with the group chat. In the Scrum based project all communication for a group went via the group owner node and hence there was a single point of failure. On the other hand, the Scrum based project came up with a more intuitive and more usable user interface for the application, most probably due to the short client feedback cycles.
I know a couple where the husband wanted to write a software system but could not get the go-ahead from his employer to do it. He then used his honeymoon leave to write the system (sending his wife on honeymoon), wrote the system, resigned and sold the system to his ex employer. They are happily married (20 odd years later).I know a couple where the husband wanted to write a software system but could not get the go-ahead from his employer to do it. He then used his honeymoon leave to write the system (sending his wife on honeymoon), wrote the system, resigned and sold the system to his ex employer. They are happily married (20 odd years later).
"That's one of the reasons they like Windows and OS X (all the fighting over those is kept behind the scenes, for the most part)."
That's one of the differences between open and not open. Looks to me a bit like wanting a non-opensource Linux. Mac is close to that (shackles and all).
Unlike non-profit organizations which are generally accountable to society or a subset thereof, companies are only accountable to shareholders. If the choice is between "do good" and "increase shareholder value" they are obliged to follow the latter. "Do good" acts are tus only done if they are aligned with optimizing shareholder value. This holds for any corporate and I do not like it if certain corporates (e.g. Google) try and create a perception that they are a "do no evil company". It is only that that image can provide a lot of shareholder value, but trust -- NOOOOOO
If the poster had given the name, the focus might have been on how to safe that particular project whilst the question is more general (and more important). What infrastructure has open source got in place to safe abandoned software projects in general?
Absolutely love this on today's BBC article on Windows 7.
"We were able to shave 400 milliseconds off the shutdown time by slightly trimming the WAV file shutdown music.
"It's indicative of really the level and detail and scrutiny on Windows 7."
This is a brilliant career path. No more work - just a now and then donate some bone marrow to people who would be willing to pay a lot of money as it is a life or death situation!!
There do seem some subtle effects on SUSE, though.
If you install version 11.0 on a machine which has Windows pre-installed (because you couldn't buy the Laptop without the Microsoft tax), it no longer gives yo a pref=configured option to remove the Windows. The only way, it seems, to remove Windows now is to go through a manual partitioning process which may be a bit daunting for the average home user. In versions prior to the Microsoft partnership, there was a convenient option to do a clean install removing all existing partitions including an MS partition.
Fritz
All our documentation was in LaTeX and we moved in 2001 over to XML DocBook. The reason for this is that we are able to process the information so much easier through standard XML tools. DocBook is quite big and polluted with all sorts of domain specific aspects, but we restrict ourselves to a relatively small subset and do automatic course note generation from a knowledge repository of little docbook documents. We still render via LaTeX as the LaTeX rendering is more mature than the FOP rendering.
This is the worst form of rape. First you persecute them or even burn them on the stake, then you let them work for you by declaring them a saint or erecting a statue. I would be turning in my grave if this happened to me.
We have developed the Use-Case, Responsibility Driven Analysis and Design (URDAD) methodology which BA's use to document business processes in a technology neutral way. The technology-neutral business process is then mapped onto an implementation across IT systems and manual work flow steps, i.e. it is deployed within an implementation architecture infrastructure. Changes in the implementation architecture or technologies do not require redesign of the business processes, but merely updating the implementation mapping for the technology neutral business process.
Furthermore, the business process across levels of granularity is designed by BAs across different specialist domains, all working on the business model for the organization as a whole.
You can download a paper at www.solms.co.za -> downloads -> research papers -> urdad.pdf. You will have to register with the site, though. Alternatively you are welcome to send me an e-mail, and I will send you an email with the paper.
Here is a link to the officially published paper: Solms, Fritz (2007), "Technology Neutral Business Process Design using URDAD", Frontiers in Artificial Intelligence and Applications, vol. 161, IOS Press, pp. 52-70, ISBN 978-1-58603-794-9
Slashdot Mirror
At the University of Pretoria we had two teams develop the same project - the one using a waterfall based development method and the other using Scrum as an agile development process. The project was to add client based secure group chat functionality to the Linphone chat application without making any changes to the server -- i.e. the server did not have any group chat functionality itself. The result was interesting. The waterfall team committed more thought into the software architecture and came up with a distributed architecture without a single point of failure - even if the group creator./owner went off-line, the remaining group members could still continue with the group chat. In the Scrum based project all communication for a group went via the group owner node and hence there was a single point of failure. On the other hand, the Scrum based project came up with a more intuitive and more usable user interface for the application, most probably due to the short client feedback cycles.
I know a couple where the husband wanted to write a software system but could not get the go-ahead from his employer to do it. He then used his honeymoon leave to write the system (sending his wife on honeymoon), wrote the system, resigned and sold the system to his ex employer. They are happily married (20 odd years later).I know a couple where the husband wanted to write a software system but could not get the go-ahead from his employer to do it. He then used his honeymoon leave to write the system (sending his wife on honeymoon), wrote the system, resigned and sold the system to his ex employer. They are happily married (20 odd years later).
This post just emphasises again that we need engineering standards and measures for software.
I also prefer PostgreSQL, but clearly you have a lot more oportunities to fix things on MySQL :)
Red Hat -> Suse -> Gentoo -> Arch -> Gentoo
Or you can start with a clean desktop and not have to remove anything. Try XMonad :)
Until you either open-source it or until you have enabled the organization to maintain the software by themselves :)
"That's one of the reasons they like Windows and OS X (all the fighting over those is kept behind the scenes, for the most part)." That's one of the differences between open and not open. Looks to me a bit like wanting a non-opensource Linux. Mac is close to that (shackles and all).
Unlike non-profit organizations which are generally accountable to society or a subset thereof, companies are only accountable to shareholders. If the choice is between "do good" and "increase shareholder value" they are obliged to follow the latter. "Do good" acts are tus only done if they are aligned with optimizing shareholder value. This holds for any corporate and I do not like it if certain corporates (e.g. Google) try and create a perception that they are a "do no evil company". It is only that that image can provide a lot of shareholder value, but trust -- NOOOOOO
Try XMonad on Gentoo or Arch :)
Except by pointing out general places where orphaned OSS projects can be advertized for adoption :)
If the poster had given the name, the focus might have been on how to safe that particular project whilst the question is more general (and more important). What infrastructure has open source got in place to safe abandoned software projects in general?
It is not that mis-leading ... They did say the horns most probably evolved as a form of sexual display!!
Or not use KDE at all, sticking with XFCE or XMonad or any of the other lightweight window managers.
What I love is that this is the main if not only concrete enhancement listed in the BBC article.
I guess it is important on that platform since one needs to reboot regularly?
Absolutely love this on today's BBC article on Windows 7. "We were able to shave 400 milliseconds off the shutdown time by slightly trimming the WAV file shutdown music. "It's indicative of really the level and detail and scrutiny on Windows 7."
Damn, where to start??&^%#@#@
This is a brilliant career path. No more work - just a now and then donate some bone marrow to people who would be willing to pay a lot of money as it is a life or death situation!!
There do seem some subtle effects on SUSE, though. If you install version 11.0 on a machine which has Windows pre-installed (because you couldn't buy the Laptop without the Microsoft tax), it no longer gives yo a pref=configured option to remove the Windows. The only way, it seems, to remove Windows now is to go through a manual partitioning process which may be a bit daunting for the average home user. In versions prior to the Microsoft partnership, there was a convenient option to do a clean install removing all existing partitions including an MS partition. Fritz
All our documentation was in LaTeX and we moved in 2001 over to XML DocBook. The reason for this is that we are able to process the information so much easier through standard XML tools. DocBook is quite big and polluted with all sorts of domain specific aspects, but we restrict ourselves to a relatively small subset and do automatic course note generation from a knowledge repository of little docbook documents. We still render via LaTeX as the LaTeX rendering is more mature than the FOP rendering.
This is the worst form of rape. First you persecute them or even burn them on the stake, then you let them work for you by declaring them a saint or erecting a statue. I would be turning in my grave if this happened to me.
Aahh -- but then there is religion ....
We have developed the Use-Case, Responsibility Driven Analysis and Design (URDAD) methodology which BA's use to document business processes in a technology neutral way. The technology-neutral business process is then mapped onto an implementation across IT systems and manual work flow steps, i.e. it is deployed within an implementation architecture infrastructure. Changes in the implementation architecture or technologies do not require redesign of the business processes, but merely updating the implementation mapping for the technology neutral business process.
Furthermore, the business process across levels of granularity is designed by BAs across different specialist domains, all working on the business model for the organization as a whole.
You can download a paper at www.solms.co.za -> downloads -> research papers -> urdad.pdf. You will have to register with the site, though. Alternatively you are welcome to send me an e-mail, and I will send you an email with the paper.
Here is a link to the officially published paper:
Solms, Fritz (2007), "Technology Neutral Business Process Design using URDAD", Frontiers in Artificial Intelligence and Applications, vol. 161, IOS Press, pp. 52-70, ISBN 978-1-58603-794-9
Fritz
SCO shares have recovered significantly after having filed for patent infringement regarding the latest Microsoft business strategies.