Address Book Application Requirements

Address Book Requirements

I. Introduction

This document describes the requirements for the ACS Address Book application. The Address Book application allows people to create address books for single individuals, groups of people, or the general public.

II. Vision Statement

People often keep address books containing their contacts. The address book application will allow people to store their contact information on a Web site, enabling them to access their contacts from anywhere they have access to the Web. Furthermore, because the address book application supports group and public address books, they will be able to share contact information with other people on the Web.

III. System/Application Overview

The address book will consist of two main interfaces: a user interface and an administrator interface. The user interface will allow people to view, add, and update address book records for themselves, groups, or the public. The administrator interface will allow administrators to see who has created an address book and what entries these people have entered into their address books.

IV. Use-Cases and User Scenarios

Creating A Private Address Book

Priscilla Popular's rolodex has grown too unwieldy for her to carry around. So, she decides that she needs to store her contact information somewhere else. Remembering that she already uses an ACS-backed web site every day, she decides to store her contact information online. This will enable her to look up information from anywhere she has Web access. She will also be able to do things like click on an e-mail address in her online address book and immediately send e-mail to that address from her favorite e-mail client. So, Priscilla Popular creates private address book entries for herself.

Creating A Group Address Book

April Mayflower runs the Americans for Thirty Days in February (ATDIF) organization. People in ATDIF often want to find out contact information about others in their group. Presently, they maintain a Microsoft Word ATDIF membership list. But, because ATDIF is a highly progressive group, it decides to setup a new, ACS-backed Web site. April Mayflower decides that her organization should store its contact information online where only other members of ATDIF may view it. So, she sets up a group-based address book for her ATDIF group. This restricts the address book to only members of ATDIF. It also offers improvements to ATDIF's old membership list because it is now sortable, searchable, and accessible on the Web.

Creating A Public Address Book

Tom Tom runs an ACS-backed Web site for drummers. He thinks that it would be nifty if every user of his site would be able to find contact information about other users--this would allow drummers to meet, get together, and jam. So, he creates a public address book for his site. This allows every registered user at his site to view contact information about other users.

Administrating the Address Book

Annie Admin's Web site uses ACS address books. By going to her site's administration pages, she is able to see who has created address book entries, how many entries people have entered, and what those entries are.

V. Related Links

VI.A. Requirements: Data Model

10 Data Model

10.1 address book

10.1.1 the address book should support user, group, and public scopes

10.1.2 address book entries should have a unique identifier

10.1.3 address book entries should support common contact fields

10.1.3.1 these fields include first name, last name, e-mails, addresses, phone numbers, notes, and birthdays

10.1.4 address book entries should support e-mail reminders for birthdays

10.2 address book fields

10.2.1 Address book fields should be customizable in their name, look, and sort order

VI.B. Requirements: Administrator Interface

20 Administrator Interface

20.1 The administrator should be able to see who has created address books

20.2 The administrator should be able to see how many address book entries people have created

20.3 The administrator should be able to see individual address book entries

VI.C. Requirements: User Interface

30 User Interface

30.1 Address Book Entries

30.1.1 The user should be able to add/edit address book entries

30.1.2 The user should be able to delete address book entries

30.1.3 The user should not be able to see address book entries outside of his current scope (user, group, public)

30.1.4 Only users with appropriate administrative rights within a scope may administrate address books for that scope

30.2 Address Book Fields

30.2.1 The user should be able to customize his address book fields

30.2.2 The user may decide which contact fields he wishes to see

30.2.3 The user may sort the order of his contact fields

30.2.4 The address book should provide functional, html links for e-mail and address information

30.2.4.1 If the user clicks on an e-mail address, he should be able to send e-mail to that address from an e-mail client (if this is setup on his computer)

30.2.4.2 The user may click on a link allowing him to view a map of a contact's address

30.3 Finding Address Book Contacts

30.3.1 The user should be able to search for contacts

30.3.2 The user should be able to sort contacts

30.4 Birthday Reminders

30.4.1 The user should be able to setup e-mail birthday reminders for his contacts

VII. Revision History

Document Revision #	Action Taken, Notes	When?	By Whom?
0.1	Creation	10/06/2000	Bryan Che

bryanche@arsdigita.com