Recommended approach to sofware development

A set of guideline for an organized, disciplined approach to software development, based on data collected and studied for 46 flight dynamics software development projects. Methods and practices for each phase of a software development life cycle that starts with requirements analysis and ends with acceptance testing are described; maintenance and operation is not addressed. For each defined life cycle phase, guidelines for the development process and its management, and the products produced and their reviews are presented

Does OO sync with the way we think?

Given that corrective-maintenance costs already dominate the software life cycle and look set to increase significantly, reliability in the form of reducing such costs should be the most important software improvement goal. Yet the results are not promising when we review recent corrective-maintenance data for big systems in general and for OO in particular-possibly because of mismatches between the OO paradigm and how we think

A Neural Network Decision Method for Software Maintenance Life Cycle Identification

The software maintenance life cycle concept is a powerful model in helping software maintenance planning. The operationalization of the life cycle concept requires a heuristic decision method. Although the heuristic decision method works most of the time, the method requires integration of different tools and sometimes leads to errors. In this paper, we propose a neural network decision method, which combines data smoothing and maintenance stage identification into one unit

Cost of Quality in Software Products: An Empirical Analysis

Computer software has emerged as a major worldwide industry, estimated at $450B for 1995 of which$225B is attributable to US firms [Boehm, 1987]. Yet, in many organizations, costs and schedules for software projects are largely unpredictable, and product quality is often poor [DeMarco and Lister, 1993]. This underscores the need to study both the quality of the software product and the life-cycle cost incurred in the development and maintenance of the products. Increasing expenditure in software has caught the attention of researchers. Identifying software productivity factors and estimating software costs continue to be important research topics [Mukhopadhyay and Kekre, 1992; Banker et al., 1993]. Researchers have adopted both empirical and theoretical approaches to better understand the process of software development and maintenance. Though software cost continues to be an important research question, competition in the software industry and the increased role of software in everyday life have also made development cycle time and quality important research issues. The quality of software has been studied mainly from defect analysis and software maintenance perspectives. Empirical research has analyzed tradeoffs between software quality and maintenance, and examined drivers of software maintenance costs [Banker, et al., 1993]. Practitioners in the software industry are still faced with the challenge of understanding the key tradeoffs in a software project in order to deliver quality products to customers on time and without cost overruns. This underscores the need to study the various factors that influence the life-cycle cost and quality in software products. Moreover, the effect of the process used in a software project on the outcome of the project in terms of cost to the software developer and quality of the product has not been examined rigorously. Thus in this research, we propose to model the life-cycle cost and quality of software products based on the factorsrelated to product, people, process and technology deployed in the software project

RT-Syn: A real-time software system generator

This paper presents research into providing highly reusable and maintainable components by using automatic software synthesis techniques. This proposal uses domain knowledge combined with automatic software synthesis techniques to engineer large-scale mission-critical real-time software. The hypothesis centers on a software synthesis architecture that specifically incorporates application-specific (in this case real-time) knowledge. This architecture synthesizes complex system software to meet a behavioral specification and external interaction design constraints. Some examples of these external constraints are communication protocols, precisions, timing, and space limitations. The incorporation of application-specific knowledge facilitates the generation of mathematical software metrics which are used to narrow the design space, thereby making software synthesis tractable. Success has the potential to dramatically reduce mission-critical system life-cycle costs not only by reducing development time, but more importantly facilitating maintenance, modifications, and extensions of complex mission-critical software systems, which are currently dominating life cycle costs

DESIGN OF LIFE CYCLE COST (LCC) ANALYSIS CSHARP BASED SOFTWARE TO INCREASE THE EFFECTIVENESS AND EFFICIENCY IN MACHINE MAINTENANCE

Globalisation era is era where technology becomes primary need for every sector in industry. Technology that usually used by manufacturer are robot, machine, information system/ technology, etc. Those technology can help the company to minimize defect and control the production time which is one of quality control system scope. One of quality control aspect is maintenance management which often become an issue in a company because it spend a lot of money. Thus, in this era most of company are challenged to find a method that make maintenance more efficient and effective, minimize cost and complexity. The method that suitable with this case is life cycle cost analysis. Unfortunately, most of company lack of industrial engineer in their maintenance department that cause life cycle cost can not be applied in those company, whereas life cycle cost analysis is method that can help the company to get the optimum lifespan of machine or equipment, and how many maintenance crew that needed in every maintenance activity for each machine which drive to the minimum overall cost that has to be paid during the lifespan of machine or equipment. The aim of this research is to build an application or software that can help the company and maintenance department to perform life cycle cost analysis. With this application, it is expected that many companies can push down their expenses and make the machine perform better. Keywords: Life Cycle Cost, LCC, Csharp, Application, Software, Maintenance

DATABASE DEVELOPMENT LIFE CYCLE

A software development life cycle model (SDLC) consists of a set of processes (planning, requirements, design, development, testing, installation and maintenance) defined to accomplish the task of developing a software application that is functionally correct and satisfies the user’s needs. These set of processes, when arranged in different orders, characterize different types of life cycles. When developing a database, the order of these tasks is very important to efficiently and correctly transform the user’s requirements into an operational database. These SDLCs are generally defined very broadly and are not specific for a particular type of application. In this paper the authors emphasize that there should be a SDLC that is specific to database applications. Database applications do not have the same characteristics as other software applications and thus a specific database development life cycle (DBDLC) is needed. A DBDLC should accommodate properties like scope restriction, progressive enhancement, incremental planning and pre-defined structure.Software Development, Database, DBMS, lifecycle model, traditional lifecycles

Studying the lives of software bugs

For as long as people have made software, they have made mistakes in that software. Software bugs are widespread, and the maintenance required to fix them has a major impact on the cost of software and how developers' time is spent. Reducing this maintenance time would lower the cost of software and allow for developers to spend more time on new features, improving the software for end-users. Bugs are hugely diverse and have a complex life cycle. This makes them difficult to study, and research is often carried out on synthetic bugs or toy programs. However, a better understanding of the bug life cycle would greatly aid in developing tools to reduce the time spent on maintenance. This thesis will study the life cycle of bugs, and develop such an understanding. Overall, this thesis examines over 3000 real bugs, from real projects, concentrating on three of the most important points in the life cycle: origin, reporting and fix. Firstly, two existing techniques are compared for discovering the origin of a bug. A number of improvements are evaluated, and the most effective approach is found to be combining the techniques. Furthermore, the behaviour of developers is found to have a major impact on the accuracy of the techniques. Secondly, a large number of bugs are analysed to determine what information is provided when users report bugs. For most bugs, much important information is missing, or inaccurate. Most importantly, there appears to be a considerable gap between what users provide and what developers actually want. Finally, an evaluation is carried out on a number of novel alterations to techniques used to determine the location of bug fixes. Compared to existing techniques, these alterations successfully increase the number of bugs which can be usefully localised, aiding developers in removing the bugs.For as long as people have made software, they have made mistakes in that software. Software bugs are widespread, and the maintenance required to fix them has a major impact on the cost of software and how developers' time is spent. Reducing this maintenance time would lower the cost of software and allow for developers to spend more time on new features, improving the software for end-users. Bugs are hugely diverse and have a complex life cycle. This makes them difficult to study, and research is often carried out on synthetic bugs or toy programs. However, a better understanding of the bug life cycle would greatly aid in developing tools to reduce the time spent on maintenance. This thesis will study the life cycle of bugs, and develop such an understanding. Overall, this thesis examines over 3000 real bugs, from real projects, concentrating on three of the most important points in the life cycle: origin, reporting and fix. Firstly, two existing techniques are compared for discovering the origin of a bug. A number of improvements are evaluated, and the most effective approach is found to be combining the techniques. Furthermore, the behaviour of developers is found to have a major impact on the accuracy of the techniques. Secondly, a large number of bugs are analysed to determine what information is provided when users report bugs. For most bugs, much important information is missing, or inaccurate. Most importantly, there appears to be a considerable gap between what users provide and what developers actually want. Finally, an evaluation is carried out on a number of novel alterations to techniques used to determine the location of bug fixes. Compared to existing techniques, these alterations successfully increase the number of bugs which can be usefully localised, aiding developers in removing the bugs