Showing papers on "Software as a service published in 1981"
01 Jan 1981
TL;DR: New programmers, some managers, and lots of users don't understand the advantages of a structured software life-cycle, so it is suggested that the millennium has finally arrived, and software people will soon live in a controlled world with rational practices.
Abstract: New programmers, some managers, and lots of users don't understand the advantages of a structured software life-cycle. However, only a single experience with coding while designing will convince any incipient software engineer that a controlled process is needed from the time of system concept though the last maintenance phase. Software Configuration Management has become almost a religion, and EDP auditors have even encountered a few systems that appear to have been specified, then designed, then implemented, then tested, and finally installed—all before maintenance and redefinition occurred. Perhaps the millennium has finally arrived, and software people will soon live in a controlled world with rational practices.If you are tempted to believe the foregoing prediction, read the latest issue of FORTUNE, the WALL STREET JOURNAL, or COMMERCE BUSINESS DAILY and note a few problems that may divert us from the path to Nirvana. Data Processing supports commercial, educational, industrial, and governmental activities that are frequently (and repeatedly) redirected. Under circumstances of a largely random environment with thorough business planning a rarity, a critical support activity can expect to be redirected frequently. New ideas will be sliced into partly-completely DP projects, and users “analytical analyses” will become DP systems as if by magic.
3 citations
TL;DR: The superset of documents which will be required under the new MIL-STD-SDS is described and the relationship of each document to the acquisition cycle, particularly the design reviews, and to each other is emphasized.
2 citations
01 Jan 1981
TL;DR: Software Configuration Management (SCM) is a management method that establishes a discipline for the software development process and provides visibility to that process that significantly improved the quality of their software products and reduced the costs.
Abstract: Have you or one of your programmers said: “The system ran yesterday; I only changed one line.” or “I spent my budget, but I'm not done.” or “I fixed that problem yesterday, but it's back now.” or “I thought it would be a nice feature for the operator, so I added it to the program.” or “Why was this line of code changed? Who did it and when?”?If these or other similar statements are familiar, then Software Configuration Management is a subject that should interest you. Software Configuration Management (SCM) is a management method that establishes a discipline for the software development process and provides visibility to that process.The step by step procedures used by a large software organization to resolve some of their development problems will be followed here. The result of their efforts was the formulation of a management method that significantly improved the quality of their software products and reduced the costs. It was learned later that other software organizations had gone through similar processes and arrived at similar results. This new tool is now known as Software Configuration Management.
2 citations