Software Requirements Specification for Electronic Business Cards Page i

VTU Final Year Project

Software Requirements
Specification
for

DropMyCard.com

(Electronic Business Card)

Version 1.0

Prepared by

Madhukara H 4MT07IS015
Mohammed Azzan Patni 4MT07IS018
Rodney Vishwas D’souza 4MT07IS033
Asrar Ahmed 4MT08IS401

Copyright © 2011 DropMyCard.com | Department of Information Science & Engineering

Software Requirements Specification for Electronic Business Cards Page ii

Table of Contents

Table of Contents .......................................................................................................................... ii

1. Introduction ..............................................................................................................................1
1.1 Purpose ............................................................................................................................................ 1
1.2 Scope................................................................................................................................................ 1
1.3 Overview .......................................................................................................................................... 1
2. Overall Description ..................................................................................................................2
2.1 Product Perspective ......................................................................................................................... 2
2.2 Product Functions ............................................................................................................................ 2
2.3 User Classes and Characteristics ..................................................................................................... 2
2.4 General Constraints ......................................................................................................................... 2
2.5 Assumptions..................................................................................................................................... 2
3. System Requirements ..............................................................................................................3
3.1 External Interface Requirements .................................................................................................... 3
3.2 Hardware Requirements .................................................................................................................. 3
3.3 Software Requirements .................................................................................................................... 3
3.4 Functional Requirements ................................................................................................................. 3
3.5 Design Constraints ........................................................................................................................... 4
3.2 Performance Requirements .............................................................................................................. 4
4. System Requirements ..............................................................................................................4

Copyright © 2011 DropMyCard.com | Department of Information Science & Engineering

Software Requirements Specification for Electronic Business cards Page 1

1. Introduction
We all know the scenario, you meet someone (man, woman, clown) at a gathering of
professionals (conference, party) and all goes well. You reach for your pocket which is where
you keep your business cards. Oh no! You’re all out...

Or let us pick another scenario where you just got back from your gathering of professionals and
you want to connect with all of the people that you met. So you pull out your stack of cards and
you go through your social network of choice searching for each one by one. Why?

How about solving both problems at once? Instead of giving your new friend your printed
business card how about you, save a tree and, give them your virtual one. This action
automatically places them in your online contact list and if they have a profile on
dropmycard.com you both are connected. No more searching or fumbling in the dark!

The E-Business card is well suited for professionals, Businessmen who have to share a lot of
business cards. Instead using the E-Business card Contacts can be shared instantly in a cost
effective and time efficient method.

1.1 Purpose

The system establishes connectivity between the sender and the receiver by carrying out the
processes of exchanging or sharing contacts thereby making it easy to access the systems
services. The system on the whole acts as a business application package which allows one to
manage contacts, messages, to-do lists, reminders and much more with the Social Networking
websites.

1.2 Scope
This system is a Web Based Application and can be within a local area network or can be put on
internet for public use. The Electronic Business Card (E-business Card) is a cost efficient and
fast means of sharing contacts to one or more users or a group of users at a given time. This
system can work on intranet. Multiple users can work at a time.

1.3 Overview
The main objective of this system is to develop a user-friendly system which is used to share
contacts from one user to another. User accounts can be created and access privileges can be set
for normal and special users by the administrator. Only the intended users can receive the
relevant messages. All information related to all users will be stored in database.

Copyright © 2011 DropMyCard.com | Department of Information Science & Engineering

Software Requirements Specification for Electronic Business cards Page 2

2. Overall Description

2.1 Product Perspective

• To provide users a device free contact sharing, online.
• To provide friendly interfaces to everyone who access it.
• The product supports, sharing of contacts performing delivery of messages,
• To provide a profile for each user, that can be viewed globally.
• Helps in reducing cost and avoids use of paper.

2.2 Product Functions

• Primary function is to share and exchange contacts.
• Users must set up accounts within the system.
• Each user gets a public profile that can be viewed by public or guest.
• Users can request for exchange of contacts with other users and then send messages to
each other.
• All user details will be stored in a database.
• The sent messages and requests will be stored in the database.
• Search query facility will be provided so as to search for a user available in the System.
• Email alerts could be sent in accordance to any updates.

2.3 User Classes and Characteristics

The users using the product would be:

• Administrator, Professionals and Businessmen.

• Every user must be authenticated to before Enjoying the services.
• There is an authorization system which limits the user’s access to various resources.
• The users can access the application with just the basic knowledge of internet. Users
need not bother about its technical specifications or functionalities.

2.4 General Constraints

• All Users are required to register themselves by submitting their profile to the website.
• A guest can only see a public profile of a person as a business card and cannot send any
messages to the user or see his/her private information.
• Only those Users, who are connected to each other with terms to share their contacts can
send and receive messages to each other.
• The Users must be authenticated before servicing their request.
• The accounts of the user will be deleted from the database when he/she would be
reported to be indulged in an illicit scenario.

2.5 Assumptions
• No unauthorized impairment of services is possible.
• The system will be up and running all the time.
• The users have the basic knowledge of accessing the system.
• Data integrity should be maintained during exchange of contacts.

Copyright © 2011 DropMyCard.com | Department of Information Science & Engineering

Software Requirements Specification for Electronic Business cards Page 3

3. Specific Requirements

3.1 External Interface Requirements

3.1.1 User Interface

The application provides the following services:

• Login.
• Logout.
• Register for new account.
• Password recovery.
• View Profiles.
• Request for exchange of contact.
• Accept / Deny Request.
• Add / Delete Contacts.
• Send Private Messages.
• Add / Delete To-do Lists.
3.1.2 Communication Interface

• Internet.
• Local Area Network.

3.2 Hardware Requirements

• Intel Pentium IV processor 1.6 GHz
• Hard Disk space: 20GB
• Ram: 256MB
• Input/output devices

3.3 Software Requirements

• Server Operating system: Linux
• Front end: HTML5, Jquery, PHP.
• Back end: MySQL and APACHE server.

3.4 Functional Requirements

1. Administrator:
o The administrator is a type of user who creates accounts for all users and sets
privileges for them.
o He/she validates all account requests.
2. Normal User:
o Professionals or Businessmen are normal users.
o Their privileges restrict them to only viewing and forwarding notices.
o No modification of notices can be done by these users.
o They can view notices which are relevant only to them.

Copyright © 2011 DropMyCard.com | Department of Information Science & Engineering

Software Requirements Specification for Electronic Business cards Page 4

3. Guest
o Visitors, who can look at the public profile.
o Their privileges restrict them to only viewing
o Can Register for the Website.

3.5 Design Constraints

• The user interface must be attractive and simple to use with guided navigation.
• Security is a major concern as contacts online and across the network and the internet are
vulnerable to spam and other cyber crimes.
• The information furnished by all users must be verified.

3.6 Performance Requirements

• Maintainability: The web application has to be designed in such way so that it can meet
the needs or the requirements of the user. Maintainability is really important because
change is an inevitable consequence of changing business environment.

• Usability: The application should be usable, without undue effort and it should have
appropriate user interface and adequate documentation.

4. Non Functional Requirements

• The website should load very fast and easily.
• Should have cross browser support functionality.
• The user interface should not be complicated but simple.
• Should have easy navigation, from any page to any other page.

Copyright © 2011 DropMyCard.com | Department of Information Science & Engineering