Showing papers on "Software as a service published in 1984"
CACI1
TL;DR: A sample software development plan is presented discussing the various areas that a software development manager should address in preparing his project's plan, and various considerations and suggestions are presented for each of the management subject areas.
Abstract: The lack of comprehensive planning prior to the initiation of a software development project is a very pervasive failing. This paper walks through a sample software development plan discussing the various areas that a software development manager should address in preparing his project's plan. Various considerations and suggestions are presented for each of the management subject areas. How the user/customer can use the developer's plan to aid in monitoring of his software's evolution is also presented. Detailed planning of a software development project is necessary to the successful completion of the project.
19 citations
TL;DR: In the past, software systems have often been viewed (at least by Business Schools) as simply tools for management, but much of the software system's worth is dependent on how effectively it can be used.
Abstract: In the past, software systems have often been viewed (at least by Business Schools) as simply tools for management. Thus, the majority of the attention paid to software systems has generally revolved around building systems that can be used more effectively by the user[1]. Other projects funded by the 1984 SIGBDP research program support this statement ("Human Computer Interaction for Management Tasks", "Information System Support for Group Decision Making", and "Critical Success Factors of Decision Support Systems"). This is a perfectly legitimate view of data processing. Much of the software system's worth is dependent on how effectively it can be used.
9 citations
TL;DR: It is argued that the number of lawsuits involving software that is delivered late, over budget, and does not do what it is supposed to do is rising and indicates that this country has a software crisis.
Abstract: DeMarco's observationis are derived in part from a multiyear survey ot over 200 projects. Based on this survey, he concludes that 15 percent ot all software projects never deliver anything and that overruns of one to two hundred percent are commoni. DeMarco, whose survey encompassed mostly small projects (on the order ot 10 to 25 mani-moniths of effort) that were primarily nongoverinmental in sponsorship,* is not alone. The General Accountinig Office, in an investigation of government software contracting practices, concluded that \"many development contracts are successful, but some result in unsatisfactory or useless software.\"' Concern is rising regarding the software industry, particularly with respect to the dependency of our military systems on softw are. 3-7 Further-more, the number of lawsuits involving software that is delivered late, over budget, and does not do what it is supposed to do is rising. 8-9 The nine references cited-only a sample of the growing number of such literature indicate, in our opinion, that we have a software crisis in this country. Without a doubt, there are nmany successful projects; howexver, our experience in the software industry and acquaintanice with current authors of literature on this topic lead us to believe that there are many more unlsuccesstful software projects. For this reason, we present in this article some suggestions for addressing the software cIrisis. Some of these sug-
5 citations
01 Oct 1984
TL;DR: The purpose of this project was to select and apply commercially available software to paratransit management, and the selected software was Mircorim’s R:base 4000, which was used to automate this data base.
Abstract: The purpose of this paper is to select and apply commercially available software to paratransit management. While the focus was on database management software (DBMS), other popular applications programs such as spreadsheets, word processing, and graphics were also investigated. The specific management functions considered for automation included vehicle scheduling, client and vehicle record keeping, financial management, and report generation for billing and performance measurement. Using actual data from a paratransit system (Call-A-Ride) which operated in Barnstable County, Cape Cod, Massachusetts, prototype data was developed. The selected software was used to automate this data base. The final product was a User’s Manual which was intended to assist non-technical transit managers in applying generic software products to the specific problems of paratransit management. This paper will summarize the lessons learned during the course of this project. The paper will discuss the data base management software (DBMS) and focus on its application to the scheduling function. The software selected was Mircorim’s R:base 4000.
3 citations
26 Mar 1984
TL;DR: In this article, the authors describe the experiences of an instructor, experienced in management, teaching a software engineering project management course at a school that specializes in software education, where a "spiral approach" was used to provide for the parallel acquisition of management knowledge and experience, while building on recently acquired skills in software technology.
Abstract: This paper describes the experiences of an instructor, experienced in management, teaching a software engineering project management course at a school that specializes in software education. A "spiral approach" was used to provide for the parallel acquisition of management knowledge and experience, while building on recently acquired skills in software technology and developing confidence through the successful development of a software product. This paper describes the reason for selecting the approach, the course content, the observation of the students and the instructor, the advantages and disadvantages of the approach as applied, and conclusions. Course objectives were met and course evaluations by students indicated a much higher level of acceptance than previous traditional approaches. The observations indicated that the approach may extend beyond the classroom to the industrial setting where on the job training, career path planning, and management development are of concern.
2 citations
Journal Article•
1 citations
01 Jul 1984
TL;DR: The objective of this report is to provide an expanded analysis of the BRASS program to assess its applicability to the Combat Service Support Concept as envisioned for Army 21.
Abstract: : In addition to the development of the transitional logistics (TRANSLOG) programs, the need for short term support for detailed analyses of current or near term specific logistical problems focused on, but not limited to, Class V will continue to arise. Allied to robotics is computer automation which will be required throughout the system. Transitional problems may address specific hardware and related software, such as the Standard Army Ammunition System (SAAS) Level 4, through the integration of computers with outside communications nets and internal control of robots. The objective of this report is to provide an expanded analysis of the BRASS program to assess its applicability to the Combat Service Support Concept as envisioned for Army 21. To meet the requirements of this expanded analysis, the following tasks were prescribed.
1 citations
16 May 1984
TL;DR: In a system' s development phase, information on design strategy must be communicated to the programmer, and as the coding and testing progresses, some design adjustments may be made, and this new informationmust be communicated up and down the line.
Abstract: In a system' s development phase, information on design strategy must be communicated to the programmer. As the coding and testing progresses, some design adjustments may be made, and this new information must be communicatedup and down the line. Finally, when the system is in production, the design documents and code are all made to agree, and we can quit worrying about documentation, right? Not jusv yet.
1 citations
Proceedings Article•
01 Jan 1984
1 citations
Journal Article•
TL;DR: Guidance is provided for managers of small fixed-route, fixed-schedule services who are considering the purchase of a microcomputer and the necessary software for management information purposes as mentioned in this paper.
Abstract: Guidance is provided for managers of small, fixed-route, fixed-schedule services who are considering the purchase of a microcomputer and the necessary software for management information purposes. The major management related functions of such services, which require the tabulation and analysis of data, are reviewed in detail and categorized into six groups: (a) administrative, (b) planning, monitoring, and evaluation, (c) operations management, (d) materials and equipment ordering and inventory, (e) maintenance, and (f) financial management. Following this review, source forms for the actual collection of the data are proposed and management reports for each function are suggested. Reference is also made to a set of criteria and standards to assist managers in the selection of the type of microcomputer and the required peripherals and software. To illustrate the use of these criteria and standards, three alternative hardware and software systems are formulated. Each system is intended to aid in all information management functions, to accommodate the processing of the data that have been entered from the source forms, and to generate the necessary reports. Each system consists of "off-the-shelf" software (including a data-base manager and some application programs and report generation capabilities). The hardware includes the most popular and widely used mircrocomputers and printers. Each system can be purchased for a total cost of approximately $10,000 to $12,000.