Cato CRM Software Requirements Specification - Draft

Software Requirements Specification for the Cato Institute Customer Relationship Management System
Table of Contents
Software Requirements Specifications
1. Introduction............................................................................................................................ 3
1.1 Purpose.......................................................................................................................................3
1.2 Project Scope.............................................................................................................................3
2. Overall Description .............................................................................................................. 3
For 2.1 Product Perspective..................................................................................................................3
2.2 Non-Functional requirements ..................................................................................................4
2.2.1 Data conversion ....................................................................................................................4
2.2.2 Training...................................................................................................................................4
2.2.3 Product roll-out strategy.......................................................................................................5
2.2.4 Product support .....................................................................................................................5
Cato Customer Relationship Management Database 2.2.5 Interoperability .......................................................................................................................5
2.2.6 Project Management ............................................................................................................5
2.2.7 User Documentation and Support ......................................................................................6
2.2.8 Stakeholder Acceptance ......................................................................................................6
3. Required Function Features.............................................................................................. 7
Prepared by Manuela Fortenberry 3.1 Constituent Management .........................................................................................................7
3.1.1 Contact management ...........................................................................................................7
3.1.2 Constituent Search ...............................................................................................................7
3.1.3 Relationships among Constituents.....................................................................................9
3.1.4 Interest Codes .......................................................................................................................9
The Cato Institute 3.1.5 Contact chronology...............................................................................................................9
3.1.7 Views and Screens .............................................................................................................12
3.2 Query Management and Reporting ......................................................................................12
3.2.1 Query Management ............................................................................................................12
3.2.2 Reporting ..............................................................................................................................13
3.3 List Management .....................................................................................................................14
November 12, 2007 3.4 Events Management ...............................................................................................................15
3.5 Fundraising...............................................................................................................................17
3.6 Subscriptions and Publication Management.......................................................................19
3.7 Cato’s Systems Integration....................................................................................................20
3.7.1 Microsoft Outlook integration ............................................................................................20
3.7.2 Wealth Prospect Integration..............................................................................................20
3.8 CRM User Management.........................................................................................................21
3.8.1 User Security .......................................................................................................................21
3.8.2 User Permissions ................................................................................................................21
3.8.3 Record Audit Trail ...............................................................................................................21
3.9 Additional Database Requirements ......................................................................................21
3.9.1 Sort Order.............................................................................................................................21
3.9.2 Bulk data modification ........................................................................................................21
3.9.3 System values management.............................................................................................22
3.9.4 User Interface ......................................................................................................................22
3.9.5 Document Storage..............................................................................................................22
3.9.6 Document Management.....................................................................................................22
3.9.7 Text Pasting .........................................................................................................................22
3.9.8 Tickler Feature.....................................................................................................................23
3.9.9 Interface with third party list vendors ...............................................................................23
3.9.10 Remote Access ...................................................................................................................23
3.9.11 Bar code Ability....................................................................................................................23
3.9.12 Robust duplicate checking capability...............................................................................23
4. Requested System Features ........................................................................................... 24
5. CRM Users............................................................................................................................ 25
Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document. 1
Software Requirements Specification for the Cato Institute Customer Relationship Management System Software Requirements Specification for the Cato Institute Customer Relationship Management System
5.1.1 User Classes and Characteristics ....................................................................................25

5.1.2 Description of Cato CRM Users........................................................................................25
6. Operating Environment .................................................................................................... 26
7. User Management .............................................................................................................. 26
8. Communications Interfaces ............................................................................................ 27
9. Other Nonfunctional Requirements .............................................................................. 27 1. Introduction
10. Performance Requirements............................................................................................. 27
11. Security Requirements ..................................................................................................... 27
Appendix A: Glossary ............................................................................................................. 27 1.1 Purpose
Appendix C: Issues List.............................................................. Error! Bookmark not defined.
The Cato Institute is a non-profit public policy research organization with approximately 130
employees. The purpose of implementing a new Customer Relationship Management (CRM)
application is to replace the existing CRM, Siebel, which Cato has determined to be inadequate for
its needs.
1.2 Project Scope
The Cato Institute requires a well-functioning CRM that will assist it in attracting potential
Sponsors, retaining current Sponsors, administering financial contributions, and managing
Sponsor and other constituent information. Goals:
• Increase financial contributions to Cato
• Increase constituent participation in Cato activities
• Increase Cato’s public visibility and involvement.
2. Overall Description
2.1 Product Perspective
A new Customer Relationship Management application (CRM) will replace Siebel, the existing
CRM.
The following Departments at Cato will use this application:

• Development
• External Affairs
• Web Services
• Marketing
Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document. 2 Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document. 3
• Information Technology The vendor will provide initial user training to Cato staff members to be determined by Cato
• Conference management and the vendor. The training will be performed at Cato's headquarters building.
• Policy
• Government Relations Following final implementation, the vendor will provide training such as refresher, job-specific and
• Media Relations new hire training, as needed.
Cato currently uses the following Siebel modules and screens to support its business functions
2.2.3 Product roll-out strategy
(these are names of the modules and screens in Siebel, not necessarily their functions):
• Individuals (individual people, contacts) Must provide a test implementation for a mutually agreed upon period before implementation.
• Organizations (the organizations with which the individuals are affiliated, mostly)
• Correspondence (currently used as a mailing and list history)
2.2.4 Product support
• Campaigns/Offers (e.g. direct mail campaigns and their corresponding codes)

Must be able to provide support after implementation for a specified period of time. Support must
• Events/Attendees include non-technical support (e.g., assisting users with application functionality) and technical
• Activities (correspondence between Cato and individuals: email, letters, proposals, etc.) support (e.g., correcting system errors). The vendor will offer a Service Level Agreement (SLA)
• Categories/Values (issues of interest and other attributes and designations) that describes the cost, response time, hours of operation, method of contact, and penalties for
• Orders (this includes contributions and Sponsor subscriptions). lack of service. Support will be provided via telephone and email, among other methods, such as
• Products (descriptions of subscriptions, publications, contributions, etc.) remote administration.
• Mail Management (an add-on module to facilitate mailings and list management)
2.2.5 Interoperability
• Notes (free form text about an individual and/or organization; usually research)
• Attachments (of all kinds: photos, clippings, web pages, documents, video and audio, etc.) 2.2.5.1 The product will provide an application programming interface (API). This protocol may
• Calendar (limited use in Siebel) be Web-based (e.g., SOAP) or COM based. The product will include detailed instructions
• Relationships (between/among individuals) regarding interoperability requirements, including function calls, data models, etc.
Note: These modules may have a different labels or names with the new vendor’s product. 2.2.5.2 The product must be compatible with Cato’s current information and IT structure, to
include
2.2 Non-Functional requirements • Cato’s Windows and SQL servers
• Network architecture
2.2.1 Data conversion • Operating systems
• Software applications
The system will provide an automated means to convert existing records from the present Siebel
database into the new application. 2.2.6 Project Management
2.2.2 Training
2.2.6.1 The Vendor must assign a manager to the project for the entire length of the project, 3. Required Function Features
and include initial contract, analysis, data conversion, application testing, training, implementation,
and follow-up support.
3.1 Constituent Management
2.2.6.2 Vendor will provide status of project progress to Cato representative on a regular basis,
i.e. regular meetings, regular emails and reports. Vendor will also notify Cato in a timely manner 3.1.1 Contact management
of any unusual or unforeseen circumstances that occur outside regularly scheduled meetings or
reports. Priority: High
1. The system will have the ability to store an unlimited number of records
2.2.7 User Documentation and Support 2. The system will include the ability to store and display a photograph in a prominent fashion in
the constituent's record.
The vendor will provide Cato with user documentation and support in some or all of the following
3. The application must provide an area where users can enter detailed, free-form notes about an
forms, among others:
individual that are not readily captured in structured form. Notes must be queriable, without the
• Printed user manual
need for knowledge of SQL. The system will have no artificial limit on the amount of information
• On-line user manual
stored as notes for each constituent. The system shall provide an unlimited number of notes fields.
• On-line help screens
These fields shall also be printable in their entirety. The notes need to be fully searchable, in more
• Email and phone support
than one way (not just within a particular note - we need to be able to search for a word or phrase
• Web-based support that is in any note on any constituent or a particular group of notes or constituents). Also needed
are indications of when the notes were written, who wrote the notes, and the ability to sort on
2.2.8 Stakeholder Acceptance
various fields.
The system must be acceptable to all Cato stakeholders before the vendor contract is signed. The
Cato stakeholders include, but are not limited to the following:
3.1.2 Constituent Search
• President: Ed Crane
• Executive Vice President: David Boaz Priority: High
• Vice President: Lesley Albanese The ability to search quickly and easily for constituents will include, but not be limited to, the
• Vice President of Finance: Bill Erickson following list of indexed fields:
• Director of Management Information Systems: Alan Peterson • last name
• Conference Director: Linda Hertzog • first name
• job title
• organization affiliation
• street address
• city
• state
• zip code
• country
3.1.3 Relationships among Constituents
• record ID
• primary phone number Priority: High
• email address The system shall show relationships among constituents and other entities, such as schools,
• comments (contents of the Siebel Comments field) associations, businesses, and personal and family relationships. It should have the ability to
• Sponsor level toggle between organization records and associated individual records, or among associated
• Nickname (if it exists) individuals and/or among affiliates have the ability to track a “knows” or “relationship” kind of link
• Record number between/among people so we can show who knows whom, etc. and link events the people
attended, including “gathered at retreat” etc.
Search results will display differentiating criteria including, but not limited to, last name, first name,
state, zip code, and Sponsor level. User will be able to, after locating the desired constituent, have
3.1.4 Interest Codes
the ability to quickly and easily navigate (or drill down) to more detailed information about the
Priority: High
constituent. Individual and Organization constituent records will be presented in this detailed view
The system shall be able to indicate the various interests a constituent has:
or screen with even more detailed information just a click or two away. The following fields will be
• It can have several codes and several levels - perhaps a tiered category/value system,
visible without navigating to a separate tab or form:
such as that in Siebel.
• name
• An unlimited number of different issues of interest or other types of codes, attributes and
• preferred address
designations
• organization affiliation
• The ability to right click or drill down (or hover) on an issue code (or event code, etc.) and
• title
view a text explanation of the code; i.e., where it came from (for example, Forum Trade =
• multiple salutations "people who are interested in trade and who should be invited to trade forums and related
• Sponsor and/or Prospect status fields events, but they or we don’t want to send them all the trade studies").
• a photograph
• home phone 3.1.5 Contact chronology
• home fax
Priority: High
• office phone
A chronological listing of all modes of contact with our constituents:
• office fax
• Invitations sent
• preferred e-mail address
• Publications sent
• alternate e-mail address(es)
• Event attendance
• date the record was first entered
• Correspondence sent and received (letters, emails, phone calls, etc.)
• date the record was last changed.
• Address change requests, etc.
From an organization record, we should be able to see and drill down to the records of the
• Contributions
individual constituents associated with that organization.
• Visits to and from • Ability to enter new constituents in the database WITHOUT being forced to link them to an
• Tickler/to-do items with ability to assign tasks organization record
• Publication claims • No middle initial field
• Ability to see/change constituent email addresses and street addresses from Contributions
Other considerations: entry screen
• When a mailing is sent from Cato through the system, this event should automatically • Next Record/Previous Record navigation capability
show up in the chronology • Calculated Fields:
• Ability to filter the list by date, transaction type, transaction amount, etc. o Date of first contribution
• Ability to sort the list various ways by date, transaction type, transaction amount, etc. o Cumulative dollars given
• Ability to search the chronology list various ways (including searching all chronologies) o Number of contributions
• Ability to add attachments and brief comments to each item o Most recent contribution
• Built-in or easy add-in address verification; zip+4 addition; five-digit zip option; CASS
3.1.6 Field Specifications certification, etc.
Priority: High • Ability, while entering contributions, to see a Sponsor’s past contributions with one click and
• Salutation - Automatic fill-in of salutation based on rules. without exiting the contribution entry screen
• There should be at least two salutation fields (informal and formal) for each constituent • Mark certain records as to who "owns” them. If an address change or bad address comes
• Multiple seasonal addresses, including date ranges in, notify the "owner.” Not all records would be marked as such.
• Ability to mark one address as the “preferred address” • Type in the zip code, get city/state; have the ability to overwrite
• Robust opt-in/opt-out/exclude information capability. Certain constituents who are • Copy addresses from one record to another (org or not)
otherwise entitled to particular publications or benefits might not want to receive them. • A multiple-value field or capability that allows users to mark constituent records with one of
Also available in the query function. various valid and invalid address codes.
• Ability to attach/link an individual to an already-existing organization. Paste the • Change the address of a group of constituents that have identical addresses
organization's preferred address into a newly-added individual record. • Ability to mark someone "Do not email" but still have their email on file. Etc.
• State default is uppercase • "Soft correspondence" similar to soft credits (save letters/correspondence when an
• Zip code should be 10 characters organization’s contact person leaves).
• No state or zip code for non-US addresses (for non-US addresses, postal code will be • A display that indicates the presence of various constituent attributes. This information
stored in the city field with the city) should appear in the main information screen that shows after selecting a constituent after
• Ability to add a new organization on the fly from within an individual’s record. doing a lookup or search. The system shall provide the ability to click on the attribute to
• Ability to add constituents to the database with a minimum of available information, such as view the underlying information. Those attributes are:
a name or an e-mail address. o Issues
• Ability to record constituents' preference of how they would like to receive invitations, o Subscriptions
publications, etc. Preference may vary between invitations (may prefer e-mail or web) and o Contributions
publications (may prefer mail). o Event Attendance
o Notes • Ability to store queries in easily accessible format, such as hierarchical or searchable
o Attachments • Add a code to a group or list of records (query update)
• Prefix and suffix fields should be drop-down fields of predefined choices • Ability to exclude records based on invalid address codes and opt-out/opt-in info
preferences
• Ability to exclude other lists (i.e., exclude records which are on a particular list or that have
3.1.7 Views and Screens
a particular code, from the results of a query)
• Ability to keep track of which codes (in addition to which people) are sent a publication or
Priority: High
event invitation. (i.e., save query criteria with the results of the query)
The system will provide multiple views and interfaces depending upon security, job requirements,
• Ability to query on the date when a record was added to the system and/or what/when their
preference or group membership, as appropriate. These screens will be developed jointly
most recent contact/touch with Cato was (attended an event, bought a publication,
between the vendor and Cato staff. Some examples (not an inclusive list):
donated, etc.) (e.g. needed for catalog mailing)
• Individual constituent information
• Ability to query on event records in various ways:
• Organization information
o type of event (monetary conference, city seminar, etc.)
• All subscriptions
o date range
• All contributions
o geographic region where the event was held
• Events
• Ability to search indirect criteria (e.g. other employees of a company)
• Contribution batch entry
• Require a mechanism to query and have results show both individuals and organizations
• Subscription entry
(or, more accurately, records for which there is no person's name - such as libraries) when
• Sponsor summary page
querying for mailings
• Data entry and modification
• 2nd home query capability - query to include non-preferred addresses.
• Ability to output the results of a query into various formats (including, but not limited to)
3.2 Query Management and Reporting o MS Word merge files

o CSV files
o TXT delimited files
3.2.1 Query Management o DBF files
o PDF files
Priority: High
o HTML files
The system will provide the following query capabilities:
o XLS files
• Query on any field in the database
• Query on all data without users being required to know Structured Query Language (SQL)
3.2.2 Reporting
• Additional capability to query on all data by building queries using SQL
• Join tables to query composite data Priority: High
• Group, sort and filter on any field in the database The system will provide the following reporting capabilities:
• Ability to save unlimited numbers of queries • Create reports based on saved queries
• Create reports based on ad hoc queries • To be able to create a flexible temporary group/tag a group of people that goes beyond a
• Create reports using Microsoft Business Intelligence. search criterion. For example: we use the results of a query, but also want to add three
• Save reports and report formats for future use and modification individuals that don’t fit the criteria and also remove another five that do. Ability to store this
• Organize saved reports and queries for rapid access list and to query it and query against it in the future.
• Format reports for clear presentation
3.4 Events Management
• Organize reports and queries for rapid accessibility.
• Export reports to various formats, including (but not limited to) Microsoft Excel, comma- Priority High
delimited files, PDF, HTML, DBF, Word, etc. as appropriate The application will permit users to enter all data pertaining to events depending on the user's
• Sort certain reports by Sponsor level highest to lowest database security level. Robust events management capabilities should include, but are not
• Require common standardized reports to include, but not limited to: limited to:
o Detailed Sponsor Profile (including the ability to print many profiles at once instead • Comprehensively manage and track invitations/registrations/attendance/fees at Cato
of one at a time) events.
o Sponsor List (this is a recent contributions report, which shows demographic
• Ability to enter associated guests at an event (tables, etc.)
information and the last four transactions for each Sponsor, filtered by Sponsor
• Notes (overall event notes and individual participant notes)
criteria.
• Ability to produce nametags, table tents, seating charts, etc.
o Side-by-Side Report (this is a report showing the Sponsors' year's contributions and
• Location(s), start/end dates/times of each event
current year's contributions, for comparison and follow-up)
• Ability to differentiate among types of event attendees (speaker, moderator, attendee,
o One-page Sponsor Profile Summary: info sheet with photo and summary
etc.)
information about the Sponsor which can be printed on color printer, for fundraising
• Ability easily to print a detailed formatted attendance roster for distribution at an event,
trips.
or at any other time
o Daily Cash Report: today's contributions to match up with accounting
• Ability to export the attendees of an event in various formats (e.g., to print envelopes for
o Various direct mail analysis reports (for contributions or subscriptions )
follow-up mailings)
o Sponsor Snapshot Report (shows how many people we have listed as Sponsors on
• Link each attendee and event record to information/attachments about that particular
any given date range in the past)
event.
o Various Sponsor renewal reports
• Ability to track Policy Forum attendance (this is something we cannot currently do)
• Ability to store an issue or multiple issues of interest for each event. When a constituent
3.3 List Management becomes a participant of that event, his list of issues now includes the one(s)
associated with the event.
Priority: High • Track info about events including a roster (whether or not it is assembled from a list
The Cato Institute requires the ability to manage lists. Those functions include: taken from the database)
• Subdivide/query update • A separate interface for manually entering registrations that come over the phone or fax
• Add to/list browser or through the mail
• Ability to integrate web-based registrations with no redundant data entry
• Ability to track how a person responded/registered for an event (fax, phone, email, mail, 3.5 Fundraising
online)
Priority: High
• Ability to show how an invitation was sent to an individual (mail, email, fax, etc.).
The system shall provide the ability to process fundraising tasks and store information. It shall
The data in the events area are to include, but are not limited to:
interface with the CRM’s query and reporting modules.
• Event Registration
o Attendee's contact information (to be extracted from the contact information
System shall have the ability to store the following required information for financial contributions:
within the CRM)
• Ability to track all information about a contribution:
o Event name
o First name and last name
o Event date
o Organization, if this is a corporate or foundation contribution
o Event location
o Campaign name (for example; 2007 direct mail, mailing "B")
o Special requests
o Offer name (basically, the piece of paper that they return, or the reason that
o Attendance
they are giving us the money: it could be a direct mail code such as 7B5 or 6F2
• Yes (type of attendee: speaker, attendee, etc.)
or "Renewal" for a renewal card, or "CPR" for the little envelope inside the Cato
• No (no-show, cancellation)
Policy Report or "Web" if the contribution comes via the web site or store.)
o Fees
o Check number
• Paid
o Payment type (cash, check, Visa, stock, in kind, etc.)
• Not Paid
o Other address fields: title, organization, street, city, state, zip, etc. from the
• Fees outstanding
constituent's record
• Complimentary
o Created on date (date this contribution record was created/entered)
o Information about an attendee's guest (First Name, Last name, Address, Phone,
o Contribution date (date the contribution goes into the bank)
etc.) Link to existing constituent records, if they exist.
o Contribution amount
• Participants’ travel and accommodation requirements
o Order number (unique record number for this contribution)
• Participants’ dietary requirements
o Fund (what the money is earmarked for, if applicable. There are lots of options
• Hotel rooming lists
here)
• Catering
o Sponsor’s renewal month
• Speakers lists
o Level before (the person's Sponsor level immediately before receiving this
• Excursion lists contribution, if this is his annual gift)
• AV requests o Level after (the person's Sponsor level as a result of receiving this contribution,
• Catering if this is his annual gift)
• Budget o Letter number (the number of the renewal notice we have sent him that resulted
• Conference brochures in his sending us this gift: 1, 2, 3 or blank
o Gift year
o Postmark date (the first part of each calendar year)
o Customer note (short, free-form text field) o Ability to manage “match-back” procedures
o Individual/Corporate/Foundation contribution designation o Ability to inform and bill the purchaser of gift Sponsorships for their gifts at
o Sponsor renewal date renewal time.
o Corporate renewal date
o Sponsor level 3.6 Subscriptions and Publication Management
o Corporate level
Priority: High
o Attachment (scan of check, etc.)
The system shall manage Cato’s print and audio subscriptions of its constituents. It shall interact
• Some information I would like to capture but currently cannot:
with Cato’s online Bookstore which accepts and processes subscription requests (or have future
o Person who created the contribution record
connectivity capability). It shall let authorized Cato users run reports to review which subscriptions
o Person who edited record
are expiring and send reminder notices to subscribers.
o Email address of the Sponsor
• Ability to associate each publication order or subscription order (or Sponsor contribution
• Additional requirements:
resulting in a premium) to a corresponding PDF file, audio file or other media, including a
o Ability to enter contributions in batch format, and enter individual contributions
link to Cato's web page for the particular study.
on an ad hoc basis
• Ability to associate the Cato policy scholar who is responsible for the publication to the
o Ability to change data entry errors in contributions directly without using an
corresponding Cato web page
accounting-type reversing entry
• Ability to associate the Cato staff member responsible for writing the press release for the
o Corporate or foundation contributions under organization record.
publication to the corresponding Cato web page.
o Corporate or foundation contributions would be viewable under each contact's
• Ability to associate the author of the publication to the corresponding Cato web page
record, also known as a “soft credit.” (In this context, a "contact" is an individual
• Ability to indicate the policy issues/research areas that the publication has associated with
constituent that Cato designates as the Organizations contact person)
it
o Payment methods
• Ability to capture the various pieces of information about the subscriptions that Cato
o Sponsor direct mail tracking/reporting
publishes:
o Renewal and thank you letter storage/automated (see chronology)
o start and end date of subscription
o Basic, Sponsor specific pledge management – ability to track pledges (promised
o amount paid for subscription, if appropriate
of money forthcoming) that shows how much is coming, when and the ability to
o renewal information for reporting
apply grants against a receivable
o Brief comment for each transaction
o Ability to check off/indicate the acknowledgement letter the Sponsor should
o Which direct mail or renewal campaign and offers (codes) offer codes
receive; while entering the contribution.
o Subscriber's subscription history
o Ability to perform ad hoc reporting with the CRM’s reporting module.
• Ability to add future subscriptions (new publications not yet published by Cato)
o Create a “receivable” when someone sends in a matching gift form
o Ability to flag (notice) who the recently-new (and about-to-renew) Sponsors are • Ability to track campaign success rates (DM or renewal, others)
so that we don't exchange their names for direct mail purposes • Ability to track claims for missing issues
o Ability to process and keep track of list rentals and exchanges (excluding • Ability to track publications mailed:
previous lists, excluding new Sponsors, etc.) o individual (see Chronology)
Software Requirements Specification for the Cato Institute Customer Relationship Management System
o overall (the mailing itself, not just what one constituent received)
• Ability to inform and bill the purchaser of gift subscriptions for their gifts at renewal time.
• Ability to inform gift recipients of their gift subscriptions
• Regulation magazine: mechanism(s) for keeping track of updates to the comp list
o Keep track of position
o Keep track of individual
o Keep track of Fortune 500-type list (external link?)
o Date last updated, search on that
3.7 Cato’s Systems Integration
Priority: High
The system shall provide the ability to capture and import constituent-entered information from
Cato’s web pages (with ability to edit the info before the info is added to the database).
• “My Cato" (future)
• Event registrations
• Contributions
• Recurring payments
• Address changes
• Contact preferences
• Issues of interest
3.7.1 Microsoft Outlook integration
Priority: High
The system will allow users to send e-mail correspondence directly from the constituent record
Microsoft Outlook 2003 by clicking on the Sponsor’s email address, or similar functionality. Such
an email created this way will become part of the constituent's chronology.
3.7.2 Wealth Prospect Integration
Priority: Medium
The system shall provide the ability to integrate a prospect wealth and information application.
These applications permit Cato to locate potential Sponsors and Sponsor upgrades and record
financial and demographic information about its Sponsors and prospects.
Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document. 20

Cato CRM Software Requirements Specification - Draft

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cato CRM Software Requirements Specification - Draft

Uploaded by

Copyright:

Available Formats

Software Requirements Specification for the Cato Institute Customer Relationship Management System

5.1.1 User Classes and Characteristics ....................................................................................25

1.2 Project Scope

2.1 Product Perspective

The following Departments at Cato will use this application:

• Media Relations new hire training, as needed.

• Campaigns/Offers (e.g. direct mail campaigns and their corresponding codes)

3.2 Query Management and Reporting o MS Word merge files

previous lists, excluding new Sponsors, etc.) o individual (see Chronology)

3.7 Cato’s Systems Integration

3.7.1 Microsoft Outlook integration

3.7.2 Wealth Prospect Integration

You might also like