Software development and testing methodology used for subscriber digital concentrator ACK-2000

Software testing provides a means to reduce errors, cut maintenance and overall software costs. Numerous software development and testing methodologies, tools, and techniques have emerged over the last few decades promising to enhance software quality. While it can be argued that there has been some improvement it is apparent that many of the techniques and tools are isolated to a specific lifecycle phase or functional area. This paper presents a set of best practice models and techniques integrated in optimized and quantitatively managed software testing process (OptimalSQM), expanding testing throughout the SDLC. Further, we explained how can Quantitative Defect Management Model be enhanced to be practically useful for determining which activities need to be addressed to improve the degree of early and cost-effective software fault detection with assured confidence is proposed. To enable software designers to achieve a higher quality for their design, a better insight into quality predictions for their design choices, test plans improvement using Simulated Defect Removal Cost Savings model is offered in this paper.

The Internet of Things (IoT) represents a paradigm shift in the way we interact with technology and the world around us. As the number of IoT devices continues to proliferate across various domains, ranging from smart homes to industrial settings, the vulnerabilities associated with this interconnected ecosystem become increasingly pronounced. This research aims to dissect the multifaceted challenges that arise in securing the vast network of interconnected devices, recognizing that the traditional approaches to cybersecurity may not suffice in this evolving environment. The objectives of the study are to comprehensively analyze these constraints, ranging from insecure IoT device configurations to potential data breaches and privacy concerns. The method adapted for this study is the V Model is a software development and testing methodology that emphasizes a structured approach to the development process. When applied to Cybersecurity and the Internet of Things (IoT) the V Model can be effectively utilized to address the unique complexities associated with securing interconnected devices. The adoption of a “security-by-design” philosophy emerges as a crucial aspect of mitigating IoT-related risks. Incorporating security measures from the inception of device development helps establish a robust foundation. The research anticipates contributing valuable insights to the ongoing discourse on cybersecurity, offering actionable recommendations for stakeholders navigating the intricate landscape of IoT security.

Many undergraduate IT programs recognize that their graduates will find jobs as software developers. As such, software development (analysis and design) courses are often a core requirement of IT undergraduate degree programs. This paper presents an analysis and comparison of the content of software development courses at several colleges and universities. In particular, the software development methodologies presented in the courses are examined. The comparison is based on two main criteria; the development methodologies presented through the textbook assigned to the class, and the development methodologies presented through the class lectures.A software development methodology is "a recommended collection of phases, procedures, rules, techniques, tools, documentation, management, and training used to develop a system" (Avison 2003). There are hundreds of software development methodologies. An ongoing debate has existed for several years as to what methodology is best. Prior research has shown that no methodology is best all the time and that practitioners are modifying methodologies to suit their needs. This research shows that IT software development courses have not been modified to reflect current trends in the practical application of development methodologies and students may not be learning the tools and techniques that they need to become successful practitioners. Key inadequacies and the associated pedagogical significance are discussed.

On Testing Embedded Software

This paper describes the design and development of the file configuration and ground sampling distance graphical user interface application for an unmanned aerial vehicle system. It begins with describing the undergraduate capstone project at University of Wisconsin-Stout and its industry project sponsor, Sentera Inc., a company developing sensors, software, and unmanned aerial vehicle systems primarily for agricultural applications. It then presents the needs, design and development, and the implementation of the software application. Agile testing methodology was utilized to improve the functionality of the application. This paper summarizes a capstone project experience with industry sponsor including system design concepts, development of software application, testing methodology, and other technical aspects of the system design leading to a successful undergraduate capstone project.

The process of software development life cycle (SDLC) is an important element of development phases to develop the application. In fact, there are needs to upgrade the sequence of methodology in software development. The SDLC methodology is the highest level of abstraction and is defined as a collection of problem-solving methods governed by a set of principles and common philosophies in solving targeted problems for extended project timeline teamwork as well as a decrease of a high team collaboration and understanding in the software development. Thus, the SDLC is very crucial in order for them to ensure the quality of skills is placed accordingly in the workflow. This research contributes to the development of a new approach in system development workflow with the aim to properly manage system development projects. It started by providing some background data related to the previous mode of operation in the teamwork samples as shared by the stakeholders of the transformation projects and the new proposed Analysis System Development Framework (ASDF) method team members. Then, the key findings related to themes of 1) input for User Requirement Specification (URS) and 2) System Requirement Specification (SRS), 3) proses for module, 4) process for database, 5) process for User Acceptance Testing (UAT) 6) output for Final Acceptance Testing (FAT) and empowerment for the whole level based on ASDF method. This research contributes mainly to the findings, more than previous research has found, that significantly support the perception that a high quality of skills in a teamwork results in better performance of software development.

Leveraging a service-oriented paradigm would significantly affect the way people build software systems. However, to achieve this ambitious vision a solid software development methodology should be in place, comprising specific, service-context patterns as well as appropriate supporting tools which altogether integrate methods and best practices into a stable development environment. This paper presents a structured approach to analyzing software development methodologies in light of the specific features of service-oriented applications. The proposed approach is based on a critical assessment of existing software development methodologies along three methodological dimensions, namely managing change in software development, specifying the software development process and targeting the stakeholder goals. For each of this dimension we first identify suitable software methodologies capable to meet the specific challenges and then discuss their contribution towards the definition of a service-oriented development methodology.

Successful implementations of Software Development Methodologies significantly improve software efficiency, collaboration and security. Most companies are moving away from traditional development methodologies towards DevOps for faster and better software delivery. DevOps, which is a primary need of the IT industry, brings development and operation teams together to overcome communication gaps responsible for software failures. It relies on different sets of automation tools to robotize the tasks of software development from continuous integration, to testing, delivery, and deployment. The existence of several automation tools in each development phase raises the need for an integrated set of tools to reduce development time. For this purpose, we used the DevOps-based hybrid model Integrated Tool Chain (ITC), along with three sample java-based projects or code repositories to quantify the results. This paper evaluates and compares measurement metrics of java projects using traditional development methodologies and DevOps, and the results are shown in tabular and graphical format. The latest Google and Stack Overflow Trends have also been included to retrieve the best performer development methodology. This comparative and evaluative performance analysis will be beneficial to young researchers that study the metrics of software development, while also they will be introduced to the automotive environment of DevOps, the latest emerging buzzword in software development.

The emergence of software offshore outsourcing phenomena hits every country positively and one of the offshore client/vendor attractng factor is CMM certification. CMM is a well recognized and globally accepted standard in software development to process control, quality improvement, and measurement of software firm's capability. Therefore, Pakistani software firms (SMEs) are striving to achieve the CMM certifications to earn profit from offshore clients. In fact, CMM certification is not easy to adopt for all level of firms. Pakistan software industry is at its initial stage, so it is not recommendable to jump for CMM by software firms (SMEs) directly. The present research paper suggests that these software firms (SMEs) should go for adaptation of agile development methodology for excellent performance on the foot steps of CMM. In this way, software firms (SMEs) can leads toward CMM after agile maturity. The authors used the eXtreme Programming (XP) as an example that proves Agile Development Methodology can well fit the CMM framework and software development firms (SMEs) can achieve their objectives to participate in offshore outsourcing phenonmena.

One of the main goals of Software Engineering is to produce software with quality. But with the increasing use of agile methodologies in software development, it is observed that the existing quality assurance models do not adapt easily to these methods. In this context, the objective of this research is to propose critical factors of success (CFS) and tools for software development and management environment using agile methods, focusing on quality. Thus, initially, a literature review was conducted in SCOPUS and SCIELO bases, identifying 21 CFS, which were grouped into three categories: Individual; Organizational; and Technical / Process. Based on these factors, a questionnaire was applied to specialists in software management and development, reaching the sample of 101 respondents, with the most important CFS belonging to the Personal category, which reinforces the need for investment in this area. After this field research, a case study was done in a public company that uses traditional methods, making it possible to propose a development and management environment of software, adding the best practices, tools and CFS with the purpose of improve the quality of delivery of the final product. It was also observed the applicability of the agile Scrum method, allied to Kanban, taking advantage of the best practices of both, and how much was relevant in the context of the company, demonstrating the importance of agile methods to improve the quality and productivity of the whole team, including customers and sponsors. In addition, the present work generates an CFS base for knowledge of the academic community.

The Marshall Space Flight Center's (MSFC) Payload Operations Center (POC) ground system has evolved over a period of about 10 years. During this time the software processes have migrated from more traditional to more contemporary development processes in an effort to minimize unnecessary overhead while maximizing process benefits. The Software processes that have evolved still emphasize requirements capture, software configuration management, design documenting, and making sure the products that have been developed are accountable to initial requirements. This paper will give an overview of how the Software Processes have evolved, highlighting the positives as well as the negatives. In addition, we will mention the COTS tools that have been integrated into the processes and how the COTS have provided value to the project.

Today, the most vital step is software testing, especially in product quality. Agile software development is exceedingly difficult and has contentious issues in literature and business. Since most Agile techniques place more emphasis on development than software testing activities, different people have varying opinions about how software testing fits into these methodologies. Agile places a high emphasis on frequent deliveries and tight client connections. However, software testing is complex because agile does not incorporate many destructive testing techniques typically required for a product of higher-quality. The study reveals industry-wide Agile testing procedures and the main problems that arise when Agile development is used. Additionally covered are the differences between manual and automated testing, best automation practices, and ways to lead different testing teams in an agile testing environment. This study covers every facet of the Agile software testing process. Agile development has shown that testing is not a distinct stage but rather a crucial component of software development along with the coding. The agile team employs an overall strategy to produce software products of the highest quality. As part of an agile team, testers collect customer samples of the desired behaviour and collaborate with the developer's team to help the coders translate these examples into executable specifications. Coding and testing are done iteratively and incrementally, developing every item until it is valuable enough to release in production. It addresses several testing modalities. The classification provided by its quadrants aids teams in determining and organizing the necessary tests. To increase quality assurance, this article will examine various and improved Agile Testing Processes and methodologies. Additionally, the topic of Agile development's software testing method is covered. Agile development processes can be improved and more advantageous by incorporating testing procedures.

AI technology brought into the field of healthcare is a matter of significant importance as it has contributed to a qualitative improvement of patient care, diagnostics as well as treatment planning. The integrity of the AI-driven healthcare applications including the accuracy, reliability, and safety aspects is what the whole game is about. Even a small matter of software bugs can have severe consequences such as a wrong diagnosis being made, the discharging of patients with the wrong medicines, or a data breach. The most common traditional testing techniques, such as manual testing and rule-based automation, are quite often unsatisfactory as they lack the proper adaptability level that is necessary to cope with the ever-increasing complexity of the newest AI-based healthcare applications. The deployment of AI in software testing has turned out to be an effective method to solve these challenges of ensuring the machine learning algorithm has proper test coverage, defect detection automation, and finally, the healthcare software systems more robust. Automated functional testing, performance testing, security testing, and usability testing are the AI-powered testing methodologies that are the gateway to the development of reliable software. Problematic topics are emphasized in this research such as AI-powered software testing methodologies and their impact on healthcare applications, and the challenges addressing widespread adoption. Forward-thinking is also addressed surrounding the creation of explainable AI (XAI) in testing, continuous integration with DevOps, and AI-powered real-time validation frameworks to ensure the reliability and security of AI-driven healthcare systems.

<p>In software development, one size does not fit all. Contingencies shape the alignment between the project and its environment, and between software development and project success. Yet the conditions favouring a particular software development methodology (e.g., waterfall or scrum) are not well understood. The current research aims to answer two questions: (1) What are the important factors in software development methodology (SDM) fit? (2) What is the role of SDM fit in project success? A review of the IT literature revealed two kinds of SDMs. On the one hand, there are traditional, plan-driven methodologies that seek compliance to a pre-established plan and existing processes. On the other hand, there are agile methodologies that seek to embrace the increasing changes and uncertainty involved in software development projects. The literature review established that there is no agreement on the contingencies associated with the use of each methodology, nor agreement on how to measure project success. Exploratory research was undertaken to identify contingencies in software development. Preliminary interviews of projects workers, using a card sort procedure, helped to identify key constructs and to generate and refine a set of measurement items. Then an international survey of software development project workers was conducted. Data analysis revealed two factors that are important in SDM fit: one is organizational culture; and the other is empowerment of the project team. The first factor encapsulates variables related to the project environment such as the level of entrepreneurship and methodology supported by top management. The second factor is related to the characteristics of the project and includes variables such as procedural empowerment and project uncertainty. No support was found for factors such as project size, criticality and the need for personnel supervision that are generally considered important contingencies. The current study also demonstrates that SDM fit is one of the predictors of project success, and affirms prior claims that one methodology does not fit all projects. The current research contributes to the SDM fit literature a contingency model that includes the impact of factors associated with the project and the project environment, on SDM fit and project success. The contingencies identified and evaluated by this research may assist practitioners to select the most appropriate methodology, and to achieve higher project success rates.</p>

This study presents MARTO (Modular Adaptive Real-Time Orchestrator), a cybersecurity framework designed to merge multi-source IDS log fusion with entropy-based adaptive scoring for anomaly detection. The framework incorporates protocol-aware entropy enhancement together with software testing methodologies such as trace simulation and toggleable logic for embedded validation. The Adaptive Threat Entropy Component (ATEC) strengthens flow scoring by incorporating session duration and protocol volatility. Experimental evaluations demonstrate MARTO’s capability to detect anomalous flows with improved transparency and reproducibility, addressing limitations observed in existing IDS frameworks.