Among the first casebooks in the field, Software and Internet Law presents clear and incisive writing, milestone cases and legislation, and questions and problems that reflect the authors' extensive knowledge and classroom experience. Technical terms are defined in context to make the text accessible for students and professors with minimal background in technology, the software industry, or the Internet.
Always ahead of the curve, the Fourth Edition adds coverage and commentary on developing law, such as the Digital Millennium Copyright Act's Safe Harbor, the Electronic Communications Privacy Act, and the Stored Communications Act.
Hard-wired features of Software and Internet Law include:
The Fourth Edition responds to this fast-changing field with coverage of :
Using Software in Qualitative Research is an essential introduction to the practice and principles of Computer Assisted Qualitative Data Analysis (CAQDAS). The book will help you to choose the most appropriate package for your needs and get the most out of the software once you are using it. This book considers a wide range of tasks and processes in the data management and analysis process, and shows how software can help you at each stage. In the new edition, the authors present three case studies with different forms of data (text, video and mixed methods data) and show how each step in the analysis process for each project could be supported by software. The new edition will be accompanied by an extensive companion website with step-by-step instructions produced by the software developers themselves. Software programmes covered in second edition include the latest versions of: * NVivo * ATLAS.ti * DEDOOSE * TRANSANA * HyperResearch * QDA Miner Ann Lewins and Christina Silver are leading experts in the field of CAQDAS and have trained thousands of students and researchers in using software. Reading this book is like having Anna and Christina at your shoulder as you analyse your data!
Many approaches have been proposed to enhance software productivity and reliability. These approaches typically fall into three categories: the engineering approach, the formal approach, and the knowledge-based approach. The optimal gain in software productivity cannot be obtained if one relies on only one of these approaches. Thus, the integration of different approaches has also become a major area of research.
In clear, easy-to-grasp language, the author covers many of the topics that you will need to know in order to win your dream job and be the first in line for a promotion.
I N T R O D U C T I O N How to Perform Software Metrics is a plain-english, simplified version of IEEE Std 1061 Standard for a Software Metrics Methodology. This how to guide defines the standard for software quality metrics methodology. It is meant for people involved with the purchase, development, use, assistance, maintenance or review of soft-ware. The standard is especially directed at those measuring or reviewing the quality of software. S C O P E How to Perform Software Metrics supplies a methodology for founding quality requirements and recognising, implementing, analysing and validating process and product software quality metrics. This methodology applies to all software at all stages of any software life-cycle structure. Sections 1 through 4 provide, scope, definitions, and background information which is the basis of this standard; all parts of Section 5 are compulsory. Appendices A through D are incorporated for illustrative and reference reasons only. This how to guide does not assign specific metrics. However, the appendices include models of metrics together with a finalised example of the use of this standard. O B J E C T I V E S The objectives of How to Perform Software Metrics are to provide definitive software metrics reference to the following categories of person: - Purchasing/project managers to identify, state and priori-tise the quality requirements for a system. - System developers to identify definite features that should be assembled into the software in order to meet the quality requirements. - Quality audit/assurance/control company and a system developer to review whether the quality requirements are being met. - System maintainers to aid in change management during product development. - User to help in distinguishing the quality requirements for a system Contribution to IS Quality. Software metrics form an indispensable part of any software process improvement program. Without the means to measure improvements (or otherwise) in software quality, it cannot be determined whether process improvement is being achieved. This how to guide is an valuable aid for project and quality managers to address the important process of keeping software metrics. It is is an easy to use checklist, as defined by IEEE Std 1061, and template to achieve this end.
The Disc Shop Articles
The Disc Shop Books