The most commonly reported reason for avoiding oral administration was concern about possible drug interactions (63.6%) for self-injection, this was a dislike of needles or the injection process (66.7%). The most commonly reported reason for oral administration as the first choice was speed and ease of administration (76.2%) for self-injection, this was convenience (75.9%). Oral administration was the first-choice preference in the US (88.0% vs 38.0% in Europe). Self-injection was most often selected as second choice (51.8%), clinic injection as third (49.4%), and infusion as fourth (47.1%). Of 48 (56.5%) patients with a strong first-choice preference (ie point allocation ≥60), 66.7% chose oral administration.
#Atlasti psu software#
ATLAS.ti Scientific Software Development GmbH, 2004.Overall, 85 patients were interviewed (female, 60.0% mean age, 49.8 years). Faily, The webinos project, Proceedings of the 21st international conference companion on World Wide Web, DOI : 10.1145/2187980.2188024 Chernoff, The Use of Faces to Represent Points in k-Dimensional Space Graphically, Journal of the American Statistical Association, vol. Hyatt, Automated quality analysis of natural language requirement specifications, Proceedings of Fourteenth Annual Pacific Northwest Software Quality Conference, pp. Schwaber, Agile Project Management with Scrum, 2004. Sawyer, Concept mapping as a means of requirements tracing, 2010 Third International Workshop on Managing Requirements Knowledge, pp. Stary, Effects of a Tabletop Interface on the Co-construction of Concept Maps, Proceedings of the 13th IFIP TC 13 international conference on Human-computer interaction -Volume Part III. Antle, A Tangible Approach to Concept Mapping, AIP Conference Proceedings, pp. Landay, The designers' outpost, Proceedings of the 14th annual ACM symposium on User interface software and technology, UIST '01, pp. Katz, Concept mapping methodology: A catalyst for organizational learning, Evaluation and Program Planning, vol. Hanington, Universal Methods of Design: 100 Ways to Research Complex Problems, Develop Innovative Ideas, and Design Effective Solutions, Rockport, 2012. Clarke, How usable are your apis?, Making Software: What Really Works, and Why We Believe It. Dubberly, Using concept maps in product development Exposing the Magic of Design: A Practitioner's Guide to the Methods & Theory of Synthesis, pp.
Irani, Sensemaking for the rest of us, CHI 2008 Sensemaking workshop, 2008. Wessman, Making Sense of Product Requirements, 2010 18th IEEE International Requirements Engineering Conference, pp.
Card, The cost structure of sensemaking, Proceedings of the SIGCHI conference on Human factors in computing systems, CHI '93, pp. Fléchais, Persona cases, Proceedings of the 2011 annual conference on Human factors in computing systems, CHI '11, pp. Fléchais, The Secret Lives of Assumptions: Developing and Refining Assumption Personas for Secure System Design, Proceedings of the 3rd Conference on Human- Centered Software Engineering. Fléchais, A meta-model for usable secure requirements engineering, Proceedings of the 2010 ICSE Workshop on Software Engineering for Secure Systems, SESS '10, pp. Fléchais, Towards Tool-Support for Usable Secure Requirements Engineering with CAIRIS, International Journal of Secure Software Engineering, vol. Brown, SEURAT, Proceedings of the 13th international conference on Software engineering, ICSE '08, pp. Mistrik, Rationale-Based Software Engineering, 2008. Von-pilgrim, A survey of traceability in requirements engineering and modeldriven development. Finkelstein, An analysis of the requirements traceability problem, Proceedings of IEEE International Conference on Requirements Engineering, pp. Nuseibeh, Ariane 5: Who dunnit? IEEE Softw, pp. Atlee, Research Directions in Requirements Engineering, Future of Software Engineering (FOSE '07), pp.
0 kommentar(er)
