The first and most basic problem with documentation is that the consumer of software applications does not want to use the documentation included with a software product for one or more reasons. Studies, and papers, have been done on the effect that documentation has on a user's satisfaction with a software application; its ease of use, how quickly a user can learn to use the application, and on how documentation should be standardized. The premise of this thesis is that an improvement to the software maintenance processes can be achieved by limiting maintenance requests to "actual” problems with software, versus "perceived" problems caused by inadequate end-user documentation. After analyzing the literature within the computer science communities on the software maintenance process, and the literature within the educational and psychological communities on learning, retention, and the effect of software documentation on the end-user, a modification to the Foster Model was conceived. This model incorporates the concept of an Interactive Documentation Program (IDP), which allows for the end-user to utilize end-user directed and task-based documentation to improve their skills with the operation of commercially available off-the-shelf "office application" software as well as in-house developed software of a similar nature. To ascertain the viability of this concept, a world-wide survey of end-users is concerning their needs, desires, expectations, and complaints concerning end-user documentation was conducted. Combining the statistical results of the analysis of this survey with the concept of the IDP resulted in a new visuaUy-based and task oriented documentation paradigm called hypervideo.

Thesis (M.S.)--Virginia Polytechnic Institute and State University, 1988. / Vita. Abstract. Includes bibliographical references (leaves 80-82). Also available via the Internet.

Thesis (Ph. D.)--Northeastern University, 2008. / Title from title page (viewed March 9, 2009) College of Computer and Information Science. Includes bibliographical references (p. 101-106).

Thesis (M.S.)--Virginia Polytechnic Institute and State University, 1990. / Vita. Abstract. Includes bibliographical references (leaves 89-94). Also available via the Internet.

Thesis (Ph. D.)--University of Washington, 1996. / Vita. Includes bibliographical references (leaves [193]-203).

Dissertation--Universität Kiel, 2009. / Includes bibliographical references (p. [227]-244).

Thesis (Ph. D.)--University of Washington, 2005. / Vita. Includes bibliographical references (p. 135-143).

Thesis (Ph. D.)--Oregon State University, 2007. / Printout. Includes bibliographical references (leaves 216-223). Also available on the World Wide Web.

It is within highly integrated technology environments that information security is becoming a focal point for designing, developing and deploying software applications. Ensuring a high level of trust in the security and quality of these applications is crucial to their ultimate success. Therefore, information security has become a core requirement for software applications, driven by the need to protect critical assets and the need to build and preserve widespread trust in computing. However, a common weakness that is inherent in the traditional software development methodologies is the lack of attention given to the security aspects of software development. Most of these methodologies do not explicitly include a standardised method for incorporating information security into their life cycles. Meaningful security can be achieved when information security issues are considered as part of a routine development process, and security safeguards are integrated into the software application throughout its life cycle. This, in turn, will lead to users being more confident to use software applications, and to entrust today's computer systems with their personal information. To build better or more secure software, an improved software development process is required. Security of a software application must be based on the risk associated with the application. In order to understand this risk, the relevant information assets need to be identified together with their threats and vulnerabilities. Therefore, security considerations provide input into every phase of the Software Development Life Cycle (SDLC), from requirements gathering to design, implementation, testing and deployment. This research project presents a Secure Software Development Model (SecSDM) for incorporating information security into all phases of the SDLC, from requirements gathering to systems maintenance. The SecSDM is based on many of the recommendations provided by relevant international standards and best practices, for example, the ISO 7498-2 (1989) standard which addresses the underlying security services and mechanisms that form an integral part of the model.

No description available.