Phases Of Software Development Life Cycle Research Articles

Towards formalising installation and reconfiguration tasks of AADL architecture

Software applications are becoming more and more distributed rendering their deployment which consists essentially of the installation and dynamic reconfiguration activities crucial and important phase in software development lifecycle. Although, several approaches for software deployment exist in the literature, most of them deal with specific technologies and offer limited models. In this paper, we focus on the formalisation of the most important deployment tasks of software systems using bigraphical reactive systems BRS. We aim to give a complete semantic framework for AADL specifications, including the installation of software application on execution platform and its dynamic reconfiguration. AADL offers necessary tools to define both software and execution platform characteristics in the same description. For this purpose, our model allows the specification of software architecture configuration by a suitable pair of bigraphs, the first one models software components and their interconnections, and the second one models the execution platform. Thus, software entities installation on hardware ones is achieved by composing the two designed bigraphs. Besides, reconfiguration activity is formalised in terms of BRS reactions rules.

A Methodological Framework for Software Safety in Safety Critical Computer Systems

Software safety must deal with the principles of safety management, safety engineering and software engineering for developing safety-critical computer systems, with the target of making the system safe, risk-free and fail-safe in addition to provide a clarified differentaition for assessing and evaluating the risk, with the principles of software risk management. Problem statement: Prevailing software quality models, standards were not subsisting in adequately addressing the software safety issues for real-time safety-critical embedded systems. At present no standard framework does exist addressing the safety management and safety engineering priniciples for the development of software safety in safety-critical computer systems. Approach: In this study we propose a methodological framework involving safety management practices, safety engineering practices and software development life cycle phases for the development of software safety. In this framework we make use of the safety management practices such as planning, defining priniciples, fixing responsibilities, creteria and targets, risk assessment, design for safety, formulating safety requirements and integrating skills and techniques to address safety issues early with a vision for assurance and so on. In this framework we have also analysed integration of applicability of generic industrial heirarchy and software development heirarchy, with derived cyclical review involving safety professionals generating a nodal point for software safety. Results: This framework is applied to safety-critical software based laboratory prototype Railroad Crossing Control System (RCCS) with a limited complexity. The results have shown that all critical operations were safe and risk free. Conclusion: The development of software based on the proposed framework for RCCS have shown a clarified and improved safety-critical operations of the overall system peformance.

안전한 웹 애플리케이션 개발을 위한 취약점 분석 및 위협 완화

Recently, as modern Internet uses mashups, Web 3.0, JavaScript/AJAX widely, the rate at which new vulnerabilities are being discovered is increasing rapidly. It can subsequently introduce big security threats. In order to efficiently mitigate these web application vulnerabilities and security threats, it is needed to rank vulnerabilities based on severity and consider the severe vulnerabilities during a specific phase of software development lifecycle (SDLC) for web applications. In this paper, we have first verified whether the risk rating methodology of OWASP Top 10 vulnerabilities is a reasonable one or not by analyzing the vulnerability data of web applications in the US National Vulnerability Database (NVD). Then, by inspecting the vulnerability information of web applications based on OWASP Top-10 2010 list and CWE (Common Weakness Enumeration) directory, we have mapped the web-related entries of CWE onto the entries of OWASP Top-10 2010 and prioritized them. We have also presented which phase of SDLC is associated with each vulnerability entry. Using this approach, we can prevent or mitigate web application vulnerabilities and security threats efficiently.

Study and Analysis of Defect Amplification Index in Technology Variant Business Application Development through Fault Injection Patterns

Software reliability for business applications is becoming a topic of interest in the IT community. An effective method to validate and understand defect behaviour in a software application is Fault Injection. Fault injection involves the deliberate insertion of faults or errors into software in order to determine its response and to study its behaviour. Fault Injection Modeling has demonstrated to be an effective method for study and analysis of defect response, validating fault-tolerant systems, and understanding systems behaviour in the presence of injected faults. The objectives of this study are to measure and analyze defect leakage; Amplification Index (AI) of errors and examine “Domino” effect of defects leaked into subsequent Software Development Life Cycle phases in a business application. The approach endeavour to demonstrate the phasewise impact of leaked defects, through causal analysis and quantitative analysis of defects leakage and amplification index patterns in system built using technology variants (C#, VB 6.0, Java).

Flexible software reliability growth model with testing effort dependent learning process

A lot of importance has been attached to the testing phase of the Software Development Life Cycle (SDLC). It is during this phase it is checked whether the software product meets user requirements or not. Any discrepancies that are identified are removed. But testing needs to be monitored to increase its effectiveness. Software Reliability Growth Models (SRGMs) that specify mathematical relationships between the failure phenomenon and time have proved useful. SRGMs that include factors that affect failure process are more realistic and useful. Software fault detection and removal during the testing phase of SDLC depend on how testing resources (test cases, manpower and time) are used and also on previously identified faults. With this motivation a Non-Homogeneous Poisson Process (NHPP) based SRGM is proposed in this paper which is flexible enough to describe various software failure/reliability curves. Both testing efforts and time dependent fault detection rate (FDR) are considered for software reliability modeling. The time lag between fault identification and removal has also been depicted. The applicability of our model is shown by validating it on software failure data sets obtained from different real software development projects. The comparisons with established models in terms of goodness of fit, the Akaike Information Criterion (AIC), Mean of Squared Errors (MSE), etc. have been presented.

A Cost Benefit Analysis Tool (CBAT) for the Management of User Interface Design and Evaluation Tasks

A user interface cost benefit analysis is an examination of the estimated costs associated with user interface design and evaluation tasks against the potential benefits to the software product. The Cost Benefit Analysis Tool (CBAT) is a human factors management tool written in SuperCard™. The tool is based on research by Mayhew (1993) and Mantei and Teorey (1988). CBAT supplements previous research efforts by the addition of more user interface tasks during typical software development lifecycle phases. The main cost benefit form is completed by means of electronic worksheets which are used to estimate both the costs and the benefits used in the overall analysis. Both cost and benefit estimates can be tailored to individual organizational needs. The tool provides the capability to print out data used to perform the cost benefit analysis and on-line help is provided for all worksheets. Future enhancements to CBAT are suggested in the following areas: additional user interface cost tasks and benefit estimates, the saving of analysis data into individual files, the inclusion of a graphic scheduling capability, and improvements to the software performance and flexibility.