User Requirements for Wireless.

In most IT system development processes, the identification or elicitation of user requirements is recognized as a key building block. In practice, the identification of user needs and wants is a challenge and inadequate or faulty identifications in this step of an IT system development can cause hu...

Full description

Saved in:
Bibliographic Details
Main Author: Sørensen, Lene
Other Authors: Skouby, Knud Erik
Format: eBook
Language:English
Published: Aalborg : River Publishers, 2015.
Series:River Publishers series in communications.
Subjects:
Online Access:Click for online access
Table of Contents:
  • Cover; Title Page; Foreword; Contents; Preface; List of Abbreviations; List of Figures; List of Tables; Introduction; References; 1. Designing Mobile Applications for Children; 1.1 Introduction; 1.2 JamMo, the Product of UMSIC Project; 1.2.1 JamMo for 3-6Years Old; 1.2.2 JamMo for 7-12Years Old; 1.3 Toward Social Inclusion; 1.4 Design, Requirements, and Development; 1.5 Impact; 1.6 Lessons; 1.6.1 Lessons for Educator; 1.6.1.1 What worked well with target children and teachers?; 1.6.1.2 Music educational experiences; 1.6.2 Lessons for Mobile Application Developer.
  • 1.6.2.1 Challenges related to software and hardware1.7 Conclusions; References; 2. Designing Mobile Applicationsfor the Construction Industry; 2.1 Introduction; 2.2 Information Technology and Construction Industry; 2.3 TheWork Environment and Users; 2.3.1 Advantages of Using Mobile Applications; 2.4 Mobile Application for Data Collection; 2.4.1 Quality Control; 2.4.2 Fault Reports; 2.4.3 Production Status; 2.4.4 Storage Information; 2.5 Lessons Learned; 2.6 Conclusions; References; 3. Innovation for the "Bottom of the Pyramid"-Mobile for Development Experiences of Farmer Net, Sri Lanka.
  • 3.1 Introduction3.2 Organizational History and FarmerNet; 3.3 FarmerNet and the Impetus for Innovation; 3.4 Idea Generation to Prototype Development-theInnovation Process; 3.4.1 Stage I-Idea Scoping; 3.4.2 Stage II-Concept Development; 3.4.3 Stage III-Prototype Development; 3.5 Ensuring Social Mission; 3.6 Conclusion; Bibliography; References; 4. Conflicting Interests in User Requirements for Customization and Personalization; 4.1 Introduction; 4.2 Who Requires What?; 4.3 Who is "The User"?; 4.4 Customization and Personalization; 4.5 Personalized PSB News; 4.6 The Case Study; 4.7 Conclusion.
  • 5.3.12 Attackers5.4 Likely Threats; 5.4.1 Loss of Device; 5.4.2 Identity Theft; 5.4.3 DoS Attacks; 5.4.4 Unauthorized Use; 5.4.5 Malicious Code; 5.4.6 Surveillance; 5.4.7 Unintended Disclosure; 5.4.8 Unwanted Persistence of Data; 5.4.9 High Technology Crime/Harassment; 5.4.10 Tricking/Attacking Individual Users; 5.4.11 Insider Attacks; 5.4.12 Security as Business; 5.4.13 Strong Security as a Problem; 5.5 How to Secure; 5.5.1 Trusted Components and Data Minimization; 5.5.2 Use Security Policies (Based on Risk Assessment); 5.5.3 Reliable "Delete"-Complete Destruction of Data.