Software Life Research Articles

Accounting for purchased software based on Turkish accounting standards

The first accounting record is made via determination of added and non-added costs of software purchased. Then amortization transaction must be accounted with respect to software useful life is limited or unlimited. Amortization cannot be done if the useful life of software is unlimited. In this article, it will be explained determination of useful life of software is limited or unlimited with the examples based on IAS 38. Before amortization of software purchased, it must be examine whether it is using in production period or not. Usage of software in production period is development activity and it have to be capitalize and other activities have to be expensed. Depreciation is recorded accordingly.In this article it is explained reasons of almost none revaluation. It is also explained that if revaluation is necessary, how it can be done. New account names are proposed because account names are not appropriate for concept of Turkish accounting standards.

Abstract P4-02-02: Targeted molecular characterization of serum derived cell free DNA from metastatic breast cancer patients treated with first-line tamoxifen

Abstract Background: Evaluation of cell-free DNA (cfDNA) is a very attractive tool to serve as "liquid biopsy" to define and establish mutational changes in circulating tumor DNA (ctDNA) non-invasively during therapy. Aim: To identify tumor specific mutations in serum cfDNA associated with resistance against tamoxifen in metastatic breast cancer. Materials & Methods: Ten metastatic ER-positive breast cancer patients treated with first-line tamoxifen of whom blood sera was available at start therapy, during treatment and at disease progression were selected. DNA was isolated from normal (nDNA) and primary tumor (ptDNA) tissue and from sera (cfDNA). DNA was analyzed with next generation sequencing by the ion-PGM system (Life Technologies) for a panel of 45 cancer genes. This panel included the most frequently mutated genes for breast, colon, prostate and ovarian cancer reported in the Catalogue Of Somatic Mutations In Cancer (Cosmic database, Release 67; cancer.sanger.ac.uk/). In total 1242 exons (∼255kb) were sequenced with 200 to 5000x reads depth coverage. The panel analyzed all exons for 39 genes and only hotspot exons for 6 oncogenes. Variant Caller software (Life Technologies; version 4.16) was applied to detect non-synonymous and stop-gain single nucleotide variants (SNVs) within the sequenced DNA. Hotspot mutations detected in PIK3CA exons 9 and 20 were validated with snapshot multiplex assays. Results: Variant Caller analyses revealed in total 252 SNVs within the 40 DNAs from tumor tissue and/or serum analyzed which were not detected in normal tissue. Of these, 229 SNVs were novel and not yet reported in the Cosmic database. Mutations were detected for 10 genes in both ptDNA and cfDNA, which enabled us to characterize ctDNA in serum of nine out of ten patients. The discovered mutations were already reported in Cosmic for PIK3CA, TP53, and NF1, but not for CDH1, APC, SMAD4, MLL, AKAP, CREBBP and MLL2. The PIK3CA, TP53 and APC mutations were observed in tumor and sera for 2, 3 and 2 patients, respectively. Mutations in the other genes, except MLL, were unique for individual patients. The mutation for MLL was seen in almost all patients at low frequencies (1-5%). The hotspot mutations in PIK3CA were confirmed with snapshot assays in the sequenced samples and in additional sera. In four patients, Cosmic reported mutations in BRCA1, KAT6B, MAP3K1, MLL2, PTCH1 and PTEN occurred in ctDNA at disease progression while they were not found in the primary tumor nor in preceding sera. The mutation frequencies ranged from 3% for BRCA1 and MAP3K1 to 6% for MLL2. Moreover, mutations for MED12 (3%) and MLL3 (4%), not yet reported in Cosmic, were each observed in two sera at disease progression for two additional patients. The remaining SNVs are currently verified for their authenticity and occurrence in ptDNA and/or ctDNA. Conclusion: Molecular characterization of tumor and serum derived DNA with targeted next generation sequencing enabled us to identify ctDNA in serum and to detect mutations at disease progression that might play a role in resistance to first-line tamoxifen. Citation Format: Maurice Jansen, Corine Beaufort, Jean Helmijr, Ronald van Marion, Niels Krol, Kim Monkhorst, Marian van Fessem, Ron van Schaik, Marcel Smid, Marion Meijer van Gelder, Maxime Look, Anita Trapman, Diana Ramirez-Ardila, Irene Lurkin, Ellen Zwarthoff, John Martens, John Foekens, Winand Dinjens, Stefan Sleijfer, Els Berns. Targeted molecular characterization of serum derived cell free DNA from metastatic breast cancer patients treated with first-line tamoxifen [abstract]. In: Proceedings of the Thirty-Seventh Annual CTRC-AACR San Antonio Breast Cancer Symposium: 2014 Dec 9-13; San Antonio, TX. Philadelphia (PA): AACR; Cancer Res 2015;75(9 Suppl):Abstract nr P4-02-02.

Software Engineering and Software Quality Management

As the rapid development of social informatization, software reliability and security are highly required. Only applying high-quality software products can increase work efficiency. Quality is the life of software. How to enhance the quality of software products and how to use effective quality management method is an urgent need. This paper discuss the key point of software engineering and software quality management, and this is the basis of software quality ensurance model.

Review: Naked City: The Death and Life of Authentic Urban Places, the Urban Wisdom of Jane Jacobs, Code/Space: Software and Everyday Life

Review: Naked City: The Death and Life of Authentic Urban Places, the Urban Wisdom of Jane Jacobs, Code/Space: Software and Everyday Life

Interated Model based on Software Engineering Environment and Life Cycle

Interated Model based on Software Engineering Environment and Life Cycle

Particle Swarm Optimization with CrossOver Operator for Prioritization in Regression Testing

Software Testing is continuous process of development and maintenance in life of software. In maintenance phase, regression testing gets exercisedwith additional resources/time for performance. The prioritization of test cases helps to reduce the cost-time of regression testing. Hence, completing Regression Testing effectively and on schedule is challenge for software tester. In this research paper, the Particle Swarm Optimization (PSO) technology has been studied and used with the blend of Genetic Algorithm (GA) and the hybrid prioritized algorithm has been proposed. The Particle Swarm Optimization is an optimization algorithm based on heuristic search which can be used to solve time-constraint environment of Test Case Prioritization and the concept of Genetic Algorithm will further help in diversifying the solution within whole search space. For finding the effectiveness of hybrid prioritization algorithm: the efficiency %, saving %, reduction % and APFD/APCC has been calculated.

Analysis of Life-Cycle Fatigue for a Car’s Front Sub-Frame

This paper based on the data of enterprise’s bench test, first set up the finite element analysis model for the front sub-frame by using the of professional finite element analysis software and fatigue life analysis software, then got the distribution information (such as the situation and the cycles) for the front sub-frame after analyzing, with these messages not only easily found out the danger area, but also provided reference for bench test improving, once more found a method that can forecast the life for mechanical products.

Multi up-gradation software reliability growth model with imperfect debugging

Due to demand of new features and highly reliable software system, the software industries are speeding their up-gradations/add-ons in the software. The life of software is very short in the environment of perfect competition. Therefore the software developers have to come up with successive up gradations to survive. The reported bugs from the existing software and Features added to the software at frequent time intervals lead to complexity in the software system and add to the number of faults in the software. The developer of the software can lose on market share if it neglects the reported bugs and up gradation in the software and on the other hand a software company can lose its name and goodwill in the market if the reported bugs and functionalities added to the software lead to an increase in the number of faults in the software. To capture the effect of faults due to existing software and generated in the software due to add-ons at various points in time, we develop a multi up-gradation, multi release software reliability model. This model uniquely identifies the faults left in the software when it is in operational phase during the testing of the new code i.e. developed while adding new features to the existing software. Due to complexity and incomplete understanding of the software, the testing team may not be able to remove/correct the fault perfectly on observation/detection of a failure and the original fault may remain resulting in the phenomenon known as imperfect debugging, or get replaced by another fault causing error generation The model developed is validated on real data sets with software which has been released in the market with new features four times.

TOWARD SOFTWARE ENGINEERING PRINCIPLES BASED ON ISLAMIC ETHICAL VALUES

Software is the core for Computer-based applications which became an essential part for critical control systems, health and human life guard systems, financial and banking systems, educational and other systems. It requires qualified software engineers professionally and ethically. L.R and survey results show that software engineering professionals facing several ethical related problems which are costly, harmful and affected high ratio of people. Professional organizations like ACM, IEEE, ABET and CSAC have established codes of ethics to help software engineering professionals to understand and manage their ethical responsibilities. Islam considers ethics an essential factor to build individuals,communities and society. Islamic Ethics are set of moral principles and guidance that recognizes what is right behavior from wrong, which are comprehensive, stable, fair, and historically prove success in building ethically great society. The 1.3 billions of Muslims with 10s of thousands of software engineers should have an effective role in software development and life, which requires them to understand and implement ethics, specially the Islamic ethics in their work. This paper is a frame-work for modeling software engineering principle. It focuses mainly on adopting a new version of software engineering principle based on Islamic ethical values.

The Case for Frame-Based Software Engineering

Frame technology adapts generic components into custom information structures. Its facility for maximizing reuse and minimizing redundancy has demonstrated dramatic improvements across software's life cycle.

Using the learning curve to maximize IT productivity: A decision analysis model for timing software upgrades

Information technology managers often feel pressure from stakeholders to continually upgrade their firm's software as soon as the software vendor releases a new version. However, this may not be ideal as the software's life cycle and the organization's learning curves are not necessarily aligned. If the firm upgrades its software too early, it may not achieve productivity gains and may lose investments from prior upgrades. If it upgrades too late, it may miss gaining important productivity gains offered by the new version. We present an approach to timing software upgrades that will maximize organization productivity gains. We use the learning curve as the theoretical basis for our mathematical model.

Evaluation method of Web site structure based on Web structure mining

The structure of Web site became more complex than before. During the design period of a Web site, the lack of model and method results in improper Web structure, which depend on the designer’s experience. From the point of view of software engineering, every period in the software life must be evaluated before starting the next period’s work. It is very important and essential to search relevant methods for evaluating Web structure before the site is completed. In this work, after studying the related work about the Web structure mining and analyzing the major structure mining methods (Page-rank and Hub/Authority), a method based on the Page-rank for Web structure evaluation in design stage is proposed. A Web structure modeling language WSML is designed, and the implement strategies for evaluating system of the Web site structure are given out. Web structure mining has being used mainly in searth engines before. It is the first time to employ the Web structure mining technology to evaluate a Web structure in the design period of a Web site. It contributes to the formalization of the design documents for Web site and the improving of software engineering for large scale Web site, and the evaluating system is a practical tool for Web site construction.

The Possible Irreducibility of Artificial Software Life

I argue that the characterization of reducibility as is too weak to be credible. I propose an improved version -- computability -- and show that it is indeed a stronger criteria, in that there may be specifications for which there exist programs but where there is no systematic way to build such a program from the specification. This undermines the assumption that just because software life would run on a computer that it must be reducible to a computer program as the result of an intentional plan. This, in turn, opens the way to the possibility that an intentionally irreducible program might arise (e.g. by evolution).

Experiences with C++ and object-oriented software development

Object-oriented is a very hot topic and buzzword both in academia and industry. There are object-oriented analysis and design techniques, object-oriented languages and databases, and so on. Many people see the letters "OO", attach a "G" to the front, and a "D" to the back and deem it to be "GOOD"---without much consideration for what it means in the software life cycle.This paper discusses the on-going (3+ years) object-oriented re-design and re-implementation in C++ of a commercial CASE tool. Specifically, why an object-oriented approach was chosen and the implications and collective experiences of this approach. In addition to the anticipated benefits, much of what we experienced was unforeseen and unexpected.