When many people think of software companies, they think of the large organizations that have become so well known in the marketplace. However, a flow of offerings are also coming from smaller organizations, including very small entities (VSEs), which have 25 or fewer employees. Moreover, most products and services from big software vendors depend on third-party components and other forms of collaboration involving VSEs or small units within large organizations. Thus, small and very small organizations-which include most software startups-are the global software industry's dominant force and are crucial to its competitiveness and innovation.Software process is a leading research area for software-engineering academics. And managing software process is a big challenge for practitioners. Large organizations typically have used traditional softwareprocess-improvement (SPI) models such as CMMI and ISO/IEC 15504 (also called Software Process Improvement and Capability Determination [SPICE]). Smaller organizations generally haven't done so for many reasons, such as the perception that these efforts were developed by and for larger organizations, are costly, require much documentation and bureaucracy, and don't clearly establish software processes.For many small and very small software companies, implementing software-development management controls and structures is a major challenge. At a time when software quality is a key to competitive advantage, organizations are using only a few of the most popular ISO/IEC systems and softwareengineering standards. Research shows that small and very small companies often have difficulty relating ISO/IEC standards to their business needs and justifying their application to their business practices. Most don't see their net benefit; lack expertise; or can't afford the necessary employees, cost, and time.In 2011, driven by VSEs' increasing importance and growing need for systems and software life cycle profiles and guidelines, the International Organization for Standardization and the International Electrotechnical Commission jointly published a set of ISO/IEC 29110 standards and guides. Other initiatives are devoted to small entities-some from Latin America, such as Competisoft, and others from Europe, such as ITmark. But ISO/IEC 29110 is becoming the widely adopted standard.

We also analyzed the characteristics of super-spreaders, factors associated with mortality, and hospital response to infection. Results: The first mortality by MERS-CoV in Korea was infected by the first super-spreader in Korea. The lessons after the outbreak were as follows:-A higher index of alerting system to find the source-patient earlier.-Appropriate numbers of Airborne Infection Isolation Rooms (AIIRs) should be constructed and maintained.-Proper training on putting on and take off of Personal Protective Equipment.-Well-trained health care workers to care for patients infected with highly contagious pathogens must be fostered.-Crowded and narrow hospital rooms should be converted to visitor controlled, larger-spaced hospital rooms. Conclusion: Multiple potential factors were associated with the super-spreading events: misdiagnosis, delayed hospital admission, inter-hospital transfers without accurate information , and also behaviors such as ignoring instructions regarding infection control, and poor environmental conditions. Institutional and health care systems' preparedness is required to prevent such outbreaks.

By identifying a set of core competencies, this study aimed to provide the specific knowledge and skills required by medical staff to respond to CRBN emergencies. A blended approach may be a suitable delivery method, allowing medical staff to attend the same training sessions despite different time zones and locations. The study output provides a CBRN training scheme that may be adapted and used at the European Union level.

No abstract

No abstract

No abstract

No abstract

No abstract