Talk:The Software Cycle

From iA wiki

The main purpose of this page is to interconnect a number of programming and software concepts together into one page. There are a number of concepts and resources out in the world which need to be gathered here to make better use of this space. There are 'bloatware', 'staleware' and other concepts which exist which would apply here. The basic concept is that there is a life cycle to a piece of software.. from the idea and planning stages to the collection of programming skills which form a useful application to user feedback and program rewrites etc etc.. For example, a mature piece of program often finds itself at the end of it's useful cycle and is redesigned to integrate further (or lesser) use, tweaked etc etc.. Some software finds that the technology base it relies on is either so flooded with competant competition or is obsoleted that it is dropped as a project. -- rack

This seems extremely user-oriented to me. I don't think programmers really use these terms. There are software engineering procedures specified in ISO standards and the like that cover all of the steps of the software development lifecycle... User Requirements, High-Level Design, Software Design Documents, different methodologies etc etc. Perhaps there should be a page for the software development lifecycle as well as "the software cycle"? -- Amw

The reason its user-oriented is that users need to know that Alpha and Beta-level programs can often not be trusted and may corrupt files on their computer. Occasionally, developers communicate poorly with their users, interested only in their interaction with the program they create. Hopefully, making people more aware of these basic precepts will help. Webfork