Cloud-Based Software Development Lifecycle:A Simplified Algorithm for Cloud Service Provider Evaluation with Metric Analysis

At present,hundreds of cloud vendors in the global market provide various services based on a customer’s requirements.All cloud vendors are not the same in terms of the number of services,infrastructure availability,security strategies,cost per customer,and reputation in the market.Thus,software developers and organizations face a dilemma when choosing a suitable cloud vendor for their developmental activities.Thus,there is a need to evaluate various cloud service providers(CSPs)and platforms before choosing a suitable vendor.Already existing solutions are either based on simulation tools as per the requirements or evaluated concerning the quality of service attributes.However,they require more time to collect data,simulate and evaluate the vendor.The proposed work compares various CSPs in terms of major metrics,such as establishment,services,infrastructure,tools,pricing models,market share,etc.,based on the comparison,parameter ranking,and weightage allocated.Furthermore,the parameters are categorized depending on the priority level.The weighted average is calculated for each CSP,after which the values are sorted in descending order.The experimental results show the unbiased selection of CSPs based on the chosen parameters.The proposed parameter-ranking priority level weightage(PRPLW)algorithm simplifies the selection of the best-suited cloud vendor in accordance with the requirements of software development.

Security Threat and Vulnerability Assessment and Measurement in Secure Software Development

Security is critical to the success of software,particularly in today’s fast-paced,technology-driven environment.It ensures that data,code,and services maintain their CIA(Confidentiality,Integrity,and Availability).This is only possible if security is taken into account at all stages of the SDLC(Software Development Life Cycle).Various approaches to software quality have been developed,such as CMMI(Capabilitymaturitymodel integration).However,there exists no explicit solution for incorporating security into all phases of SDLC.One of the major causes of pervasive vulnerabilities is a failure to prioritize security.Even the most proactive companies use the“patch and penetrate”strategy,inwhich security is accessed once the job is completed.Increased cost,time overrun,not integrating testing and input in SDLC,usage of third-party tools and components,and lack of knowledge are all reasons for not paying attention to the security angle during the SDLC,despite the fact that secure software development is essential for business continuity and survival in today’s ICT world.There is a need to implement best practices in SDLC to address security at all levels.To fill this gap,we have provided a detailed overview of secure software development practices while taking care of project costs and deadlines.We proposed a secure SDLC framework based on the identified practices,which integrates the best security practices in various SDLC phases.A mathematical model is used to validate the proposed framework.A case study and findings show that the proposed system aids in the integration of security best practices into the overall SDLC,resulting in more secure applications.

Optimal Sprint Length Determination for Agile-Based Software Development

A carefully planned software development process helps in maintaining the quality of the software.In today’s scenario the primitive software development models have been replaced by the Agile based models like SCRUM,KANBAN,LEAN,etc.Although,every framework has its own boon,the reason for widespread acceptance of the agile-based approach is its evolutionary nature that permits change in the path of software development.The development process occurs in iterative and incremental cycles called sprints.In SCRUM,which is one of the most widely used agile-based software development modeling framework;the sprint length is fixed throughout the process wherein;it is usually taken to be 1–4 weeks.But in practical application,the sprint length should be altered intuitively as per the requirement.To overcome this limitation,in this paper,a methodical work has been presented that determines the optimal sprint length based on two varied and yet connected attributes;the cost incurred and the work intensity required.The approach defines the number of tasks performed in each sprint along with the corresponding cost incurred in performing those tasks.Multi-attribute utility theory(MAUT),a multi-criterion decision making approach,has been utilized to find the required trade-off between two attributes under consideration.The proposed modeling framework has been validated using real life data set.With the use of the model,the optimal sprint for each sprint could be evaluated which was much shorter than the original length.Thus,the results obtained validate the proposal of a dynamic sprint length that can be determined before the start of each sprint.The structure would help in cost as well as time savings for a firm.

Quintessence of Traditional and Agile Requirement Engineering

Requirement gathering for software development project is the most crucial stage and thus requirement engineering (RE) occupies the chief position in the software development. Countless techniques concerning the RE processes exist to make sure the requirements are coherent, compact and complete in all respects. In this way different aspects of RE are dissected and detailed upon. A comparison of RE in Agile and RE in Waterfall is expatiated and on the basis of the literature survey the overall Agile RE process is accumulated. Agile being a technique produces high quality software in relatively less time as compared to the conventional waterfall methodology. The paramount objective of this study is to take lessons from RE that Agile method may consider, if quality being the cardinal concern. The study is patterned on the survey of the previous research reported in the coexisting literature and the practices which are being pursued in the area.

Software, Software Engineering and Software Engineering Research: Some Unconventional Thoughts

Software engineering is broadly discussed as falling far short of expectations. Data and examples are used to justify how software itself is often poor, how the engineering of software leaves much to be desired, and how research in software engineering has not made enough progress to help overcome these weaknesses. However, these data and examples are presented and interpreted in ways that are arguably imbalanced. This imbalance, usually taken at face value, may be distracting the field from making significant progress towards improving the effective engineering of software, a goal the entire community shares. Research dichotomies, which tend to pit one approach against another, often subtly hint that there is a best way to engineer software or a best way to perform research on software. This, too, may be distracting the field from important classes of progress.

Development and application of a model for analysis and design phases of Web-based system development

Despite a short history of the Web development, Web-related technologies are rapidly develop- ing. However, the Web application quality is improving slowly, which requires efficient methods for devel- oping Web systems. This study presents a model for Web-based software development for analysis and design phases based on the ISO/IEC 12207 standard. It describes the methods used to define processes and entities in order to reflect the contents in Web applications. It applies the methodology of Web-Road Map by KCC Information and Technology using this model to the public project. As a result, Web-Road Map is proven to be an efficient model to analyze and design Web-applications.