Global Project: Should we start developing the SIT-USE?
Software Immune Testing: Unified Software Engine (SIT-USE)
Toward Software Immune Testing Environment
Would you like to be part of the funding proposal for SIT-USE?
Would you like to participate in the development of the SIT-USE?
Would you like to support the development of HR SIT-USE?
Keywords: Funding Proposal or Funding, Participation, Support
If you answer yes to any of the questions, don't hesitate to get in touch with me at
[email protected] and write in the subject – The keyword(s)
Despite much progress and research in software technology, testing is still today's primary quality assurance technique. Currently, significant issues in software testing are:
1) Developing and testing software is necessary to meet the new economy market. In this new market, delivering the software on time is essential to capture the market. Software must be produced on time and be good enough to meet the customer's needs.
2) The existing software requirements keep changing as the project progresses, and in some projects, the rate of requirement changes can grow exponentially as the deadline approaches. This kind of rapid software change imposes significant constraints on testing because once a software program changes, the corresponding test cases/scripts may have to be updated. Furthermore, regression testing may have to be performed to ensure that those parts that are supposed to remain unchanged are indeed unchanged.
3) The number of test cases needed is enormous; however, the cost of developing test cases is extremely high.
4) Software development technologies, such as object-oriented techniques, design patterns (such as Decorator, Factory, Strategy), components (such as CORBA, Java's EJB and J2EE, and Microsoft's. NET), agents, application frameworks, client-server computing (such as socket programming, RMI, CORBA, Internet protocols), and software architecture (such as MVC, agent architecture, and N-tier architecture), progress rapidly, while designing and programming towards dynamic and runtime behavior. Dynamic behavior makes software flexible but also makes it difficult to test. Objects can now send a message to another entity without knowing the type of object that will receive the news. The receiver may be just downloaded from the Internet with no interface definition and implementation. Numerous testing techniques have been proposed to test object-oriented software. However, testing technology is still far behind software development technology.
5) Conventional software testing is generally application-specific, rarely reusable, and is not extensible. Even within a software development organization, software development, and test artifacts are developed by different teams and are described in separate documents. These make test reuse difficult.
As a part of this research, we plan to work toward an automated and immune software testing environment that includes 1. Unified Component-Based Testing (U-CBT); 2. Unified Built-In Test (U-BIT); 3. Unified-End-to-End (U-E2E) Testing; 4. Unified Agent-Based Testing U-ABT); 5. Unified Automatic Test Case Generators (U-ATCG); and 6. Unified Smart Testing Framework (U-STF). The development of this environment is based on the software stability model (SSM), knowledge map (KM): Unified Software Testing (KM-UST), and the notion of software agents. An agent is a computational entity evolving in an environment with autonomous behavior, capable of perceiving and acting on this environment and communicating with other agents.
You are invited to join Unified Software Engineering (USWE)
https://www.linkedin.com/groups/14289019/
It could help improve the detection and prevention of software vulnerabilities. Few factors:
1. Research and feasibility: Conduct thorough research to understand existing approaches, tools, and techniques related to software immune testing. Evaluate the feasibility of developing a unified software engine and consider the potential challenges and limitations that may arise.
2. Market demand and competition: Assess the market demand for a software immune testing tool. Investigate if similar tools or solutions already exist and analyze their features and limitations. Consider whether there is a need for a unified software engine like SIT-USE and how it would differentiate itself from existing solutions.
3. Resources and expertise: Determine if you have the necessary resources, including skilled developers, researchers, and domain expertise, to undertake the development of SIT-USE. Developing a robust and effective software testing tool requires significant time, effort, and expertise in areas such as software security, testing methodologies, and programming.
4. Collaboration and partnerships: Consider collaborating with experts or organizations specializing in software security or immune system-inspired testing. Partnering with experts in the field can provide valuable insights, guidance, and potential support for the development process.
5. Sustainability and maintenance: Evaluate the long-term sustainability and maintenance of the software immune testing tool. Consider factors such as updates, bug fixes, support, and staying up-to-date with emerging security threats and technologies.
Good luck
- Badges
- Science topic
- Similar topics
- Mathematics
- Statistics
- Regression