Cargando…

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...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: Sørensen, Lene
Otros Autores: Skouby, Knud Erik
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Aalborg : River Publishers, 2015.
Colección:River Publishers series in communications.
Temas:
Acceso en línea:Texto completo

MARC

LEADER 00000cam a2200000Mu 4500
001 EBOOKCENTRAL_ocn957125006
003 OCoLC
005 20240329122006.0
006 m o d
007 cr |n|---|||||
008 160827s2015 xx o 000 0 eng d
040 |a EBLCP  |b eng  |e pn  |c EBLCP  |d OCLCO  |d OCLCQ  |d CCO  |d OCLCO  |d OCLCF  |d MERUC  |d LOA  |d COCUF  |d K6U  |d STF  |d IDB  |d PIFAG  |d FVL  |d OCLCQ  |d ZCU  |d U3W  |d WRM  |d ICG  |d VT2  |d OCLCQ  |d WYU  |d TKN  |d DKC  |d OCLCQ  |d OCLCO  |d TYFRS  |d OCLCQ  |d SFB  |d OCLCQ  |d OCLCO  |d OCLCL 
019 |a 1372504350 
020 |a 9788793237612 
020 |a 8793237618 
020 |a 9781003339977  |q (electronic bk.) 
020 |a 1003339972  |q (electronic bk.) 
020 |a 9781000793321  |q (electronic bk. : PDF) 
020 |a 100079332X  |q (electronic bk. : PDF) 
020 |a 9781000796094  |q (electronic bk. : EPUB) 
020 |a 1000796094  |q (electronic bk. : EPUB) 
020 |z 9788793237209 
024 7 |a 10.1201/9781003339977  |2 doi 
029 1 |a CHNEW  |b 000960809 
029 1 |a CHVBK  |b 491676336 
029 1 |a DEBBG  |b BV044060938 
035 |a (OCoLC)957125006  |z (OCoLC)1372504350 
037 |a 9781003339977  |b Taylor & Francis 
050 4 |a QA76.59  |b .U847 2015eb 
072 7 |a SCI  |x 024000  |2 bisacsh 
072 7 |a TEC  |x 041000  |2 bisacsh 
072 7 |a TJK  |2 bicssc 
082 0 4 |a 004  |2 23 
049 |a UAMI 
100 1 |a Sørensen, Lene. 
245 1 0 |a User Requirements for Wireless. 
260 |a Aalborg :  |b River Publishers,  |c 2015. 
300 |a 1 online resource (135 pages) 
336 |a text  |b txt  |2 rdacontent 
337 |a computer  |b c  |2 rdamedia 
338 |a online resource  |b cr  |2 rdacarrier 
490 1 |a River Publishers Series in Communications 
588 0 |a Print version record. 
505 0 |a 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. 
505 8 |a 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. 
505 8 |a 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. 
504 |a References5. Security and Usability; 5.1 What is Usable Security?; 5.2 Background; 5.2.1 Usability Status; 5.2.1.1 Usability in mobile communication; 5.2.1.2 Usability in other systems; 5.2.2 Security Status; 5.2.2.1 Security of mobile communication system; 5.2.2.2 Internet security; 5.2.3 Security in the Future; 5.3 Stakeholders; 5.3.1 Individual Users; 5.3.2 Corporate Users; 5.3.3 Developers; 5.3.4 System Administrators; 5.3.5 Network Operators; 5.3.6 Manufacturers; 5.3.7 Service Providers; 5.3.8 Regulators; 5.3.9 Government Agencies; 5.3.10 Certification Authorities; 5.3.11 Insurers. 
505 8 |a 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. 
500 |a 5.5.4 User Authentication and Mutual Authentication in Most/All Transactions. 
520 |a 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 huge problems with the final product. The elicitation of user requirements as such changes according to age groups;, to gender,; to cultural settings,; and into time; and experience in the use of the system/software. User requirements, therefore, cannot be used between projects, IT systems, and different software. That makes the elicitation of user requirements an inherent part of any software development project and a resourceful activity as well. This book provides insights to the process of identifying user requirements and to different types by describing varying case studies in which technologies or software has been developed. A variety of user requirements are provided illustrating the effect of changing the targeted user group with respect to age,; to the context and the different technologies or software as well as to the difference in viewpoint on ways of involving users in the elicitation process. Cases and user requirement elements discussed in the book include: User requirements elicitation processes for children, construction workers, and farmers User requirements for personalized services of a broadcast company Variations in user involvement Practical elements of user involvement and requirements elicitation Usable security requirements for design of privacy. 
545 0 |a Lene Sørensen, Knud Erik Skouby 
590 |a ProQuest Ebook Central  |b Ebook Central Academic Complete 
650 0 |a Mobile apps. 
650 0 |a Wireless communication systems. 
650 6 |a Applications mobiles. 
650 6 |a Transmission sans fil. 
650 7 |a SCIENCE / Energy  |2 bisacsh 
650 7 |a TECHNOLOGY / Telecommunications  |2 bisacsh 
650 7 |a Mobile apps  |2 fast 
650 7 |a Wireless communication systems  |2 fast 
700 1 |a Skouby, Knud Erik. 
758 |i has work:  |a User requirements for wireless (Text)  |1 https://id.oclc.org/worldcat/entity/E39PCXWPbBhHWPbMdkgccjxQjd  |4 https://id.oclc.org/worldcat/ontology/hasWork 
776 0 8 |i Print version:  |a Sørensen, Lene.  |t User Requirements for Wireless.  |d Aalborg : River Publishers, ©2015  |z 9788793237209 
830 0 |a River Publishers series in communications. 
856 4 0 |u https://ebookcentral.uam.elogim.com/lib/uam-ebooks/detail.action?docID=4509479  |z Texto completo 
938 |a EBL - Ebook Library  |b EBLB  |n EBL4509479 
994 |a 92  |b IZTAP