Welcome to the InfoSci Platform
Functional Requirements - Email Management

Functional Requirements - Email Management

Len Asprey, Michael Middleton
Copyright: © 2003 |Pages: 6
ISBN13: 9781591400554|ISBN10: 1591400554|EISBN13: 9781591400684
DOI: 10.4018/978-1-59140-055-4.ch013
Cite Chapter Cite Chapter

MLA

Len Asprey and Michael Middleton. "Functional Requirements - Email Management." Integrative Document and Content Management: Strategies for Exploiting Enterprise Knowledge, IGI Global, 2003, pp.330-335. https://doi.org/10.4018/978-1-59140-055-4.ch013

APA

L. Asprey & M. Middleton (2003). Functional Requirements - Email Management. IGI Global. https://doi.org/10.4018/978-1-59140-055-4.ch013

Chicago

Len Asprey and Michael Middleton. "Functional Requirements - Email Management." In Integrative Document and Content Management: Strategies for Exploiting Enterprise Knowledge. Hershey, PA: IGI Global, 2003. https://doi.org/10.4018/978-1-59140-055-4.ch013

Export Reference

Mendeley
Favorite

Abstract

In Chapter 4, we indicated that there were various technology options available to organizations for capturing email as a record of a business transaction. We briefly examined the characteristics of two options for capturing email: • Direct capture of email using an email management system; and • End-user-invoked capture of email by saving an email to a DMS. In this chapter, we examine the functional requirements that may be appropriate when compiling a specification for managing email using either the direct capture method or save to DMS. The objectives are as follows: • Consider requirements for managing email that evidences a business transaction or activity. • Consider some technology solution options. • Review the functionality that might apply when defining requirements for capturing email as a record of a business transaction or activity.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.