Submitted in partial fulfillment of the requirements For the degree of Bachelor of Engineering in Information Technology
2|Page
Declaration
This is to certify that i) The project comprises my original work towards the degree of bachelor of Engineering in Information Technology at Shantilal shah Engineering College, under the Gujarat Technological University, Ahmedabad and has not been submitted elsewhere for a degree.
ii) Due acknowledgement has been made in the text to all other material used.
3|Page
CERTIFICATE
This is to certify that the Project entitled " SENDING ONLINE BULK EMAIL SYSTEM " submitted by SHAH ATUL N. (080430116056), SAURABH VASHISTHA (080430116064) towards the partial fulfillment of the requirements for the degree of Bachelor of Engineering in Information Technology of Shantilal Shah Engineering College, Bhavnagar, under the Gujarat Technological University, Ahmedabad is the record of work carried out by them under my supervision and guidance. In my opinion, the submitted work has reached a level required for being accepted for examination. The results embodied in this project, to the best of my knowledge, haven't been submitted to any other university or institution for award of any degree.
4|Page
ABSTRACT
Bulk email is an email that is sent to countless recipients. The number of recipients of this bulk e-mails could vary from hundreds to thousands for each email. Companies are the ones who commonly use Bulk e-mailing to direct merchandises and market services to consumers. Bulk E-mail system is the system in which sender can send e-mail to countless recipients. The main aim of this project is to reduce the cost of sending mails for advertising of products and services. Bulk E-Mail system allows the sender to reach the audience globally so communication can take place globally; this is helpful for companies to sell their products and services. Instead of doing Email to every recipient separately, sender can reach to the countless recipients in single E-mail. Business can be expanded not only internally but globally throughout the world. Thats why Bulk E-mail system is preferred now-a-days in spite of its drawbacks.
5|Page
ACKNOWLEDGEMENT
On the completion of this Project Report on Sending online Bulk E-Mail system I am very much thankful to all my guide teacher of Shantilal Shah Engineering College, Bhavnagar, Lect. Mrs. Beena Thanki and Head of Department Mr. S.B. Parmar who has always helped and guided me in every possible way during the making of this report.
I would like to thank all my mentors and Information and Technology Department during this period for giving their precious time to me and helping me in completing my Project report.
6|Page
CONTENTS
Declaration Certificate Abstract Acknowledgement iii iv v vi
1 )Introduction 1.1 Objective of the Work . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 1.2 Scope of the Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Technology Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 1
2 )Project Management 2.1 Project Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 2.2 Milestone and Deliverables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 2.3 Roles and Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.4 Project Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.5 Risk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4 )System Design 4.1 Context Diagram . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 4 4.2 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.2.1 First Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.2.2 Second Level . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . 4 4.3 Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . 4 4.4 E-R Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 4.5 Use-Case Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
111
9|Page
CHAPTER NO: 1 INTRODUCTION: Objective of the Work Scope of the Work Technology Used Hardware-Software used
Introduction Bulk email is an email that is sent to countless recipients. The number of recipients of this bulk e-mails could vary from hundreds to thousands for each email. Companies are the ones who commonly use Bulk e-mailing to direct merchandises and market services to consumers. Bulk emails are used individuals and businesses, even though it is in general, it is thought of as a tool for direct marketing utilized by companies. Any person might use a bulk e-mail mail photos, send a birth announcement or mail invitations. Bulk e-mailing must vary by individual and are commonly mailed to people whom he or she knows.
i)
10 | P a g e
ii)
i)
Java has had a profound effect on the Internet. This is because; Java expands the Universe of objects that can move about freely in Cyberspace. In a network, two categories of objects are transmitted between the Server and the Personal computer. They are: Passive information and Dynamic active programs. The Dynamic, Self-executing programs cause serious problems in the areas of Security and probability,
SYSTEM REQUIREMENT
SOFTWARE Technology Framework Development Tool Front End Back End Operating System Java J2EE Apache Tomcat 6.0.18. server Java Sql server 2005 Windows Xp, windows vista, windows 2000
14 | P a g e
HARDWARE R.A.M Processor H.D.D 512 MB Minimum 2.0 GHZ Minimum 80 GB Preferable
Project Planning Milestone and Deliverables Roles and Responsibilities Project Schedule Risk Management i) Project planning
Planning is a software engineering task that bridges the gap between system level requirements engineering and software design. Requirements engineering activities result in the specification of softwares operational characteristics (function, data, and behavior), indicate software's interface with other system elements, and establish constraints that software must meet. Requirements analysis allows the software engineer (sometimes called analyst in this role) to refine the software allocation and build models of the data, functional, and behavioral domains that will be treated by software. Planning provides the software designer with a representation of information, function, and behavior that can be translated to data, architectural, interface, and component-level designs. Finally, the requirements specification provides the
15 | P a g e
16 | P a g e
Requirement Gathering & Analysis Project Planning System Design System Implementation Testing Documentation
ii)
Management needs information. As software is intangible, this information can only be provided as documents that describe the state of the software being developed. Without this information, it is impossible to judge progress
17 | P a g e
Design Analysis
Shah,
Saurabh
18 | P a g e
Documentation
iv)
PROJECT SCHEDULE:
Activities Prior tool Study report Project Synopsis Requirements and DFD SRS iteration-1 SRS Final Database + Screen Code for System
19 | P a g e
v)
Risks occur due to two main sources: people and paper. Projects tend to generate a significant number of (electronic) documents that contain project risks. Another categories are old project plans, your company Intranet and specialised websites. 2. Consider Both Threats and Opportunities Project risks have a negative connotation: they are the "bad guys" that can harm your project. However modern risk approaches also focus on positive risks, the project opportunities. These are the uncertain events that
20 | P a g e
5) Risk Management Plan There are four stages to risk management planning. They are:
Risk Identification Risks Quantification Risk Response Risk Monitoring and Control
Risk Identification In this stage, we identify and name the risks. The best approach is a workshop with business and IT people to carry out the identification. Use a combination of brainstorming and reviewing of standard risk lists.
22 | P a g e
23 | P a g e
Risk Response There are four things you can do about a risk. The strategies are:
Avoid the risk. Do something to remove it. Use another supplier for example. Transfer the risk. Make someone else responsible. Perhaps a Vendor can be made responsible for a particularly risky part of the project. Mitigate the risk. Take actions to lessen the impact or chance of the risk occurring. If the risk relates to availability of resources, draw up an agreement and get sign-off for the resource to be available. Accept the risk. The risk might be so small the effort to do anything is not worth while. A risk response plan should include the strategy and action items to address the strategy. The actions should include what needs to be done, who is doing it, and when it should be completed.
Risk Control The final step is to continually monitor risks to identify any change in the status, or if they turn into an issue. It is best to hold regular risk reviews to identify actions outstanding, risk probability and impact, remove risks that have passed, and identify new risks.
24 | P a g e
Requirement Of the System Feasibility Study Features Of the System Main Module Of the System System Requirement Study and Assumption
i)
25 | P a g e
Hardware requirement:
Hardware
CPU
Any Intel EMT64 or AMD x64 chip. Minimum 1.4GHz. Recommended 2GHz or faster.
26 | P a g e
Memory (RAM)
Total will vary depending on Total will vary depending on selected components. See selected components. See Table 5.2. Table 5.2. VGA or higher resolution. 1024x768 recommended for SQL Server graphical tools. Microsoft mouse or compatible pointing device. VGA or higher resolution. 1024x768 recommended for SQL Server graphical tools. Microsoft mouse or compatible pointing device.
Monitor
Pointing device
ii)
FEASIBILITY STUDY
The basic idea behind feasibility study is to determine whether the project is feasible or not. A feasibility is conducted to identify a best system that meets all the requirements. This includes an identification ,description, an evaluation of the proposed systems and selection of the best system for the job . The requirements of the system are specified with a set of constraints such as system objectives and the description of the out puts. It is then duty of the analyst to evaluate the feasibility of the proposed system to generate the above results. Three key factors are to be considered during the feasibility study. 1) ECONOMIC FEASIBILITY
27 | P a g e
28 | P a g e
Address Book Management Sign up form Sign Up response Personalization Template management Email editor Actions HTML and Text emails Test sending/previewing Sending
29 | P a g e
iv)
1. Login Page: There should be a login page for the existing user where theusername and password are verified and then if he is a valid user, he is allowed for further advancements. 2. Inbox Reply/Forward/Delete: The logged in users should be able to see the lists of new mails aswell asthe existing ones.
3. Compose Mail: User should be able to compose mails and send them to the other users.The user should be able to reply to mails, forward mails and alsodelete mails from his mailboxes. The deleted mails should be moved to the Thrashmailbox. 4. Organize Mails: The user should be able to organize his mails into the existing folders. 5. Attach files: The user should be able to attach files to the mails and send them to the desired users. 6. Save as Draft:
30 | P a g e
10.Visitor Module: Visitor is nothing but all the people who visits this application online. They can know the information of all the products, which are for sale under this application. 11.Customer Management
Single Point Relationship Management Contact Management Drill down customer history Outlook Integration Calendar
31 | P a g e
v)
Address Book Management: This Bulk email system offer multiple address books so that you can segment your audiences or a way of easily selecting the attributes you want for each mailing. It should be easy to import and export both the contact details and history of each name. Many systems also allow you to hold additional data fields (although the number may be limited) which can be useful for capturing information such as organisation name or for holding a database reference number. Sign up form: The system should provide you with a sign up form for your website and if it allows multiple address books then it should allow a sign up form for each one. You should be able to personalise the sign up form to include as little or as much data capture as you want (subject to the number of data fields available). Some systems allow you to have a drop down list in the sign up which makes data management easier. Sign Up response: The system should allow you to write a reply email which is sent when somebody subscribes on the website form. You should be able to set a sign up response for each address book. Personalisation: You should be able to capture the name and details of sign ups (with separate fist and last name fields) and then use those details to personalize the email with both Dear firstname and with fields in the body of the email. Good systems also allow you to set a default alternative for each field so that if the data is missing the field isnt left blank, for example rather
32 | P a g e
Template management: HTML emails can be complex and should be well designed. The system should allow you to build a template for each email you plan to send and hold the template for reuse. If you are having an email designed for you can you import it?
Email editor: Systems should either come with, or allow you to integrate, an email editor known as a WYSIWYG editor. These should contain basic standard editing options for formatting and controlling the content of your email as well as options for managing images and links. In some systems the email is built using an external tool such as Dreamweaver and imported into the email system. You need to consider the skills and training requirements of the users before taking this option. Actions: Many systems have pre-built actions for you to insert into your email. These include unsubscribe, forward, cant read, and add to safe list. HTML and Text emails: Although more than 80% of users in the UK can now receive HTML emails that still leaves 20% of your audience who cant and a few who chose not to. Bulk emails should always be offered in HTML and text formats. Systems should offer 2-part send, where the system works out what the recipients email client/application can read and only delivers this. Test sending/previewing: Systems should offer a simple preview pane and the option to test send the email to multiple addresses. Sending: When the email is ready the system should allow you to easy chose which segment or address book to send to. Some systems allow you to present a delivery time.
33 | P a g e
Reporting: Good reporting tools allow you to see how many emails were sent, who opened it, who clicked on what, how many forwards, bounces and unsubscribes happened. Bounce Management: Hard bounces (emails which failed to find the recipient) and soft bounces (received but not delivered i.e. recipients inbox full) should be recognised and listed. Good systems allow you to set a number of delivery tries for each which prevents you being seen as a spammer. Unsubscribe management: This is critical. The system should prompt you to add an unsubscribe to every email and may offer an unsubscribe/change you details form for your website. Best practice is for the system to automatically block any user who unsubscribes so that they cannot accidentally be sent another email. Check whether the system blocks unsubscribes against newly imported lists. Usability: Although this isnt a technical specification it is essential that you chose a system that you find easy to use. Bear in mind that you may want to devolve emails to other departments and need to consider their skill and technical ability.
CHAPTER NO: 4
SYSTEM DESIGN
i.
System Design
The basic goal of system design is to plan a solution for the problem. This phase is composed of several systems. This phase focuses on the detailed implementation of the feasible system. It emphasis on translating design specifications to performance specification. System design has two phases of development logical and physical design. During logical design phase the analyst describes inputs (sources), outputs (destinations), databases (data stores) and procedures (data flows) all in a format that meets the user requirements. The analyst also specifies the user needs and at a level that virtually determines the information flow into and out of the system and the data resources. Here the logical design is done through data flow diagrams and database design. The logical design is followed by physical design or coding. Physical design produces the working system by defining the design specifications, which tell the programmers exactly what the candidate system must do. The programmers write the necessary programs that accept input from the user, perform necessary processing on accepted data through call and produce the required report on a hard copy or display it on the screen. CONTEXT DIAGRAM
admin
35 | P a g e
Login
confirmation
user
ii.
The DFD is also know as a data flow graph or a bubble chart. DFDs are the model of the proposed system. They clearly should show the requirements on which the new system
36 | P a g e
Log In
Successful Login
User_Info
Read or Delete
Manage Emails
Email Details
Email Messages
Emails
Log In
Successful Login
User_Info
37 | P a g e
Read or Delete
Manage user
Email Messages
Emails
Size 15 15 15
Constraint
Allow Null
38 | P a g e
User Profile
Field Name User Name Data Type Vchar Size 15 Constraint Foreign Key Allow Null
39 | P a g e
Recipients
Field Name User Name Package Name Package Id Type Of Package Package Duration Price Of Package Data Type Vchar Vchar Number Vchar Number Number Size 15 10 10 10 5 5 Primary Key Constraint Foreign Key Allow Null
Function
Field Name Data Type Size Constraint Allow Null
40 | P a g e
Compose Mail
Field Name User Name Compose Mail Id Package Id Text Field Data Type Size Vchar Number Vchar Vchar 15 10 10 50 Constraint Foreign Key Foreign Key Foreign Key Allow Null
Inbox
Field Name User Name Inbox Id Inbox Mail Data Type Vchar number number Size 15 10 20 Constraint Foreign Key Foreign Key Allow Null
41 | P a g e
SPAM
Field Name User Name SPAM Id SPAM Mail Data Type Vchar number number Size 15 10 10 Constraint Foreign Key Foreign Key Allow Null
Trash
Field Name User Name Trash Id Trash Mail Data Type Vchar Number number Size 15 10 10 Constraint Foreign Key Foreign Key Allow Null
Draft
Field Name User Name Draft Id Draft Mail Data Type Vchar number number Size 15 10 10 Constraint Foreign Key Foreign Key Allow Null
Sent Item
42 | P a g e
43 | P a g e
Screen -Shot
44 | P a g e
Chapter 5
Planning, Implementation and Testing
45 | P a g e
Comments: The comments should describe what is happening, how it is being done, what parameters mean, which global are used and which are modified, and any restrictions or bugs. We have adopted the following standards for comments: Every program should begin with a comment block, which describes the scripts purpose; any arguments used (if applicable), and return values (if applicable), inputs-outputs, and name of script. Comments may also be used in the body of the progarm to explain individual sections or lines of code. It is also used to describe variable definition or declaration. Each part of the project has a specific comment layout.
5.4 Testing
When a system is developed, it hopes that it performs properly. In practice, however some errors always occur. The main purpose of testing an information system is to find the errors and correct them.
47 | P a g e
Acceptance Testing
Chapter 6
Conclusion and Future Enhancement
We think it will be a memorable experience for us .There will be lots of difficulties in our way to male proposed system, hope all will be right with our faculties and our class-mates. This site will provide good interface to people to sell their old items which is useful to others. Also we have removed whole commission part which will be good for attract enough customers for ONSHOP24x7. The future of this project seems to be bright. We are try to make this website as light as possible. We will try to reach as much customers as possible and also make our site as good as possible with changing technologies.
48 | P a g e
CONCLUSION Rather than send bulk emails from Outlook or other desktop email systems, charities should be using specialist tools. This article outlines the options available, features to look for, and gives an overview of the most commonly used tools in the sector.
FUTURE ENHANCEMENT: Bulk E-mail is preferred in this modern world for a successful email campaign marketing. To remove this drawback there are lots of management software has some basic functions like e-mail templates, tracking system, contact list management functions. Have a good software package to handle both text and HTML messages. The surveillance system is designed to measure e-mail campaign response rate is important.
49 | P a g e