522 research outputs found

    Quality Assurance in Requirement Engineering

    Get PDF
    Requirement engineering is the most important process in software development life cycle. Quality assurance in requirement engineering has a great impact on the product quality. It checks whether the requirements meet the desired quality attributes i.e. adequacy, completeness, consistency etc. Quality Assurance of the requirement is important because the cost of requirements failure is very high. The proposed research is based on the survey of the quality assurance in requirement engineering. The major focus of this research paper is to analyze the quality parameters which assure the overcome of the issues related to the requirements. The research papers include brief overview of those parameters

    The First Hundred Years of the Bureau of Labor Statistics

    Get PDF
    [Excerpt] This volume reports on the first century of a government agency whose founders hoped that, by publishing facts about economic conditions, the agency would help end strife between capital and labor. The Bureau\u27s early work included studies of depressions, tariffs, immigrants, and alcoholism and many assignments to investigate and mediate disputes between labor and management. Most of these functions- especially those involving formulation of policy- passed on to other agencies. The Bureau today remains one of the Nation\u27s principal economic factfinders. In writing the book, Drs. Goldberg and Moye had full freedom to interpret events in accordance with their judgments as historians, without conformance to an official view of institutional history. Given the perspective made possible by passing years, the authors offer broader evaluations of the Bureau\u27s early history than of contemporary events

    Crashworthy Code

    Get PDF
    Code crashes. Yet for decades, software failures have escaped scrutiny for tort liability. Those halcyon days are numbered: self-driving cars, delivery drones, networked medical devices, and other cyber-physical systems have rekindled interest in understanding how tort law will apply when software errors lead to loss of life or limb. Even after all this time, however, no consensus has emerged. Many feel strongly that victims should not bear financial responsibility for decisions that are entirely automated, while others fear that cyber-physical manufacturers must be shielded from crushing legal costs if we want such companies to exist at all. Some insist the existing liability regime needs no modernist cure, and that the answer for all new technologies is patience. This Article observes that no consensus is imminent as long as liability is pegged to a standard of “crashproof” code. The added prospect of cyber-physical injury has not changed the underlying complexities of software development. Imposing damages based on failure to prevent code crashes will not improve software quality, but will impede the rollout of cyber-physical systems. This Article offers two lessons from the “crashworthy” doctrine, a novel tort theory pioneered in the late 1960s in response to a rising epidemic of automobile accidents, which held automakers accountable for unsafe designs that injured occupants during car crashes. The first is that tort liability can be metered on the basis of mitigation, not just prevention. When code crashes are statistically inevitable, cyber-physical manufacturers may be held to have a duty to provide for safer code crashes, rather than no code crashes at all. Second, the crashworthy framework teaches courts to segment their evaluation of code, and make narrower findings of liability based solely on whether cyber-physical manufacturers have incorporated adequate software fault tolerance into their designs. Requiring all code to be perfect is impossible, but expecting code to be crashworthy is reasonable

    Ethical and Unethical Hacking

    Get PDF
    The goal of this chapter is to provide a conceptual analysis of ethical, comprising history, common usage and the attempt to provide a systematic classification that is both compatible with common usage and normatively adequate. Subsequently, the article identifies a tension between common usage and a normativelyadequate nomenclature. ‘Ethical hackers’ are often identified with hackers that abide to a code of ethics privileging business-friendly values. However, there is no guarantee that respecting such values is always compatible with the all-things-considered morally best act. It is recognised, however, that in terms of assessment, it may be quite difficult to determine who is an ethical hacker in the ‘all things considered’ sense, while society may agree more easily on the determination of who is one in the ‘business-friendly’ limited sense. The article concludes by suggesting a pragmatic best-practice approach for characterising ethical hacking, which reaches beyond business-friendly values and helps in the taking of decisions that are respectful of the hackers’ individual ethics in morally debatable, grey zones

    Best Practices and Recommendations for Cybersecurity Service Providers

    Full text link
    This chapter outlines some concrete best practices and recommendations for cybersecurity service providers, with a focus on data sharing, data protection and penetration testing. Based on a brief outline of dilemmas that cybersecurity service providers may experience in their daily operations, it discusses data handling policies and practices of cybersecurity vendors along the following five topics: customer data handling; information about breaches; threat intelligence; vulnerability-related information; and data involved when collaborating with peers, CERTs, cybersecurity research groups, etc. There is, furthermore, a discussion of specific issues of penetration testing such as customer recruitment and execution as well as the supervision and governance of penetration testing. The chapter closes with some general recommendations regarding improving the ethical decision-making procedures of private cybersecurity service providers

    Platform Embedded Security Technology Revealed

    Get PDF
    Computer scienc
    corecore