Contect Management System (Report) - Abhishek Jaiswal
Contect Management System (Report) - Abhishek Jaiswal
Project Report
on
CONTACT MANAGEMENT SYSTEM
Submitted By
ABHISHEK JAISWAL
Enrolment no: - 1713104024
Bachelor of Computer Application
Under Guidance of
Ms. Nikita
Thank you
PAGE INDEX
1 Introduction
1.1 Introduction to system
1.2 Scope of System
1.3 FIELD STUDY OF CONTACT MANAGEMENT
2 Analysis
2.1 Fact Finding Techniques
3 System Designing
3.2 Study and Factors of contect
3.4 File Dessign or Data Dictionary
6 Bibliography
ABSTRACT
Much of our daily communication activity involves managing interpersonal communications
and relationships. Despite its importance, this activity of contact management is poorly
understood. We report on field and lab studies that begin to illuminate it. A field study of
business professionals confirmed the importance of contact management and revealed a major
difficulty: selecting important contacts from the large set of people with whom one
communicates. These interviews also showed that communication history is a key resource for
this task. Informants identified several history-based criteria that they considered useful. We
conducted a lab study to test how well these criteria predict contact importance. Subjects
identified important contacts from their email archives. We then analyzed their email to extract
features for all contacts. Reciprocity, recency and longevity of email interaction proved to be
strong predictors of contact importance. The experiment also identified another contact
management problem: removing ‘stale’ contacts from long term archives. We discuss the design
and theoretical implications of these results.
1.1 INTRODUCTION
Theorizing about asynchronous communication has been dominated by comparisons with face-
to-face communication . Early asynchronous theories emphasized media differences arguing
that asynchronous communication differs from face-to-face communication because of the
absence of non-verbal information afforded by gaze and gesture. However, the emphasis on
media differences leaves other crucial aspects of asynchronous communication unexamined,
particularly those that stem from its persistent nature. We explore those persistent aspects of
asynchronous communication in this paper. Research on email, voicemail, and Usenet has
revealed various critical features of asynchronous, technologically mediated interpersonal
conversations. These conversations consist of multiple messages exchanged over a fairly
extended period of time: days, weeks, or even months. This extension of conversations over
time implies that people are typically engaged in multiple conversations at any given time. And
each conversation often involves multiple people. These properties lead to significant problems
of conversation management. People find it difficult to keep track of the content and status of
their multiple conversations, as well as the identity, contact information, and expertise of all
their conversational partners. Maintaining knowledge of one’s contacts is a significant problem
in its own right we refer to this problem as contact management. Contact management is clearly
complex. A major problem is that people are exposed to an unmanageable number of potential
contacts. This is exacerbated by widespread use of distribution lists . It would be both onerous
and unnecessary to store detailed information about all these potential contacts. As a result,
individuals must decide:
(a) which of these potential contacts are important enough to retain information about; and
(b) what sorts of information to retain about these chosen contacts.
2.1 Problems: Contact Selection, Data Entry, Tool Diversity However, contact management
has a number of associated difficulties. At first glance, the main problem informants had was
the number of contacts they needed to manage. We estimate that this number varied from a low
of several hundred to well into the thousands, although reliable
estimation was hard given the large number of contact management tools people typically used,
and the fact that there was often duplication between these. Upon further examination, though,
deeper problems concerned: (a) the need to make an explicit decision that someone was a
valuable contact; (b) the diversity of tools used; and (c) data entry.
2.2 Contact Selection. When someone calls you on the phone, leaves you voicemail, sends you
email, or hands you a business card, what do you do? Do you record their contact information
or not? The difficulty is that it is hard to anticipate whether, and to what extent, you will need
to communicate with that person in the future. Whether someone is an “important contact” only
becomes clear over time. The ease of electronic communication, especially the ability to
broadcast messages to large numbers of people at little cost, exacerbates this problem: you may
be cc’ed on messages, get email from various distribution lists, or receive mass mailings. To be
safe, our informants often “over-saved” information, leading to huge rolodexes, overflowing
booklets of business cards, and faded post-it notes scattered around their work areas. Despite
this strategy, participants were still exposed to many more contacts than they recorded
information about. One reason for this was the laborious nature of recording contact
information.
2.3 Data Entry. Informants made it clear that contact information is costly to acquire and
especially hard to maintain. They often wanted to record various types of addressing
information for a particular contact: work, home, and mobile phone numbers, fax number, email
address, postal address, instant messaging alias, as well as the IM system it was good for, and so
on. And, as we mentioned earlier, some people found it important to include detailed personal
and social information that was useful in maintaining an effective relationship with that contact.
2.4 Diversity of Tools. All the informants used ad hoc combinations of tools, with some people
evolving highly complex and idiosyncratic systems. For example, Mary, the freelance
researcher, had over 1000 people in her email address book, a 60 page Word document
containing over 1200 people, over 400 people in her PDA, as well as miscellaneous people in
Christmas card lists. Ollie, a corporate research scientist, kept 7 different address books, using 2
PDAs, Microsoft Outlook, and 4 independent email address books. He also wrote key work
numbers on his office blackboard. One reason why these complex systems evolved was that
informants seldom ‘cleaned up’ their contact information. People were loath to delete any
contact information. This seemed to be motivated both by the effort of data entry, along with the
belief that even little used contact information may be relevant at some future time.
2.5 Criteria for Determining Contact Importance Returning to the basic decision people face –
is this an important contact? – we sought to find out how our informants dealt with this issue.
Informants responded with a surprising consensus. Since they could not make this decision at
first exposure, they relied largely on the history of their prior interactions. Further individual
factors, such as communication style seemed to affect the number and type of contacts selected.
In our interviews, we probed informants to identify specific aspects of interaction history and
communication style that were critical in determining important contacts. We asked people to
walk us through their contact management tools and explain why particular contacts had been
included.
3.6 Results
Characteristics of Extracted Contacts and the Selection Process Before testing our hypotheses,
we present some general observations about the characteristics of the original archives and the
set of contacts our users rated as important. We also present some observations about the
selection process.
Several design suggestions follow from these results. First, our regression analysis is a model for
identifying important contacts in email, and this could be implemented directly as an algorithm.
The ability to automatically identify important contacts from communication archives might be
used in a number of applications, allowing us to improve messaging applications, support
reminding and provide social recommendation. Messaging applications are currently poorly
integrated with contact management tools, but future systems could exploit information about
important contacts in a variety of ways. These might include alerting, filtering and prioritization
of incoming email or voicemail messages based on the sender’s importance. Tighter integration of
contact information with messaging logs could be also used to manage relationships with contacts,
e.g. reminding the user when they haven’t talked to an important contact in a long time. We have
implemented contact-based alerting and reminding in a social network based user interface to
communication and information . Finally social recommendation systems might be able to exploit
information about a register of important contacts to either direct a user query or guide information
access. Other design implications concern contact management tools directly. We could improve
address book utility by using our algorithm to automatically recommend that a potentially
important contact should be added to the address book, based on their communication history. But
even if we provide ways to better identify significant contacts, data entry is still a major problem.
One possible way to address this would be to identify contact information from other sources, such
as Internet home pages containing addresses. We may also be able to mine other types of records
such as phone and voicemail logs, or use reverse lookup to provide detailed addresses for contacts.
Having general techniques for populating address books is clearly important. One unexpected
finding from our research was that 72% of important contacts came from outside the user’s
organization. While this may depend on the specific user population, it suggests that corporate
address books or intranets have limited utility as a way to provide detailed addresses for contacts.
✓ Hardware Specification
✓ Software Specification.
REFERENCES
1. Donath, J., Karahalios, K., & Viegas, F. (1999). Visualizing conversations. In HICSS-32,
IEEE, 583592.
2. Erickson, T. (1999). Persistent Conversation: Discourse as Document. In HICSS-32, IEEE
Press, 514.
3. Granovetter, M. (1973). The Strength of Weak Ties. American Journal of Sociology 78,
6, 1360-1380.
4. Haythornthwaite, C., Wellman, B., & Mantei, M. (1995). Work Relationships and Media
Use: A Social Network Analysis. Group Decision and Negotiation, 4, 193-211.
5. Millen, D. and Henderson, D. (2000). PhoneMan – The Benefits of Personal Call
Histories, In CHI2000, New York, ACM, 155-156.