[Type the document title] [Year



By SHAH ATUL N (Enroll No-080430116056) SAURABH VASHISTHA (Enroll No-080430116064)


[Type the document title] [Year]


Submitted in partial fulfillment of the requirements For the degree of Bachelor of Engineering in Information Technology

By SHAH ATUL N (Enroll No-080430116056) SAURABH VASHISTHA (Enroll No-080430116064)



[Type the document title] [Year]


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.

SHAH ATUL N (Enroll No-080430116056). SAURABH VASHISTHA (Enroll No-080430116064).


[Type the document title] [Year]

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.

Guided By: Mrs. Beena Thanki

Mr. S.B. Parmar Head of Department



[Type the document title] [Year]


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. That‘s why Bulk E-mail system is preferred now-a-days in spite of its drawbacks.


[Type the document title] [Year]


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.

SHAH ATUL N. (Enroll No-080430116056) SAURABH VASHISTHA (Enroll No-080430116064)


[Type the document title] [Year]

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

1.3.1 Hardware-Software used . . . . . . . . . . . . . . . . . . . . . . . . . . 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

3 )System Analysis and Requirement

3.1 Requirement Of the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2 Feasibility Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

[Type the document title] [Year]
3.3 Features Of the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.4 Main Module Of the System . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .3 3.5 System Requirement Study and Assumption . . . . . . . . . . . . . . . . . .3

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

5 ) Conclusion and Future Enhancement

5. Screen Shot…………………………………………………………………………….33 6. Coding……………………………………………………………………………………….43 7. System Design
7.1 Context Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 7.2 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 7.2.1 First Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 7.2.2 Second Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 7.3 E-R Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 7.4 Use-Case Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

[Type the document title] [Year]

8. Planning, Implementation and Testing
8.1 Implementation Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 8.2 Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 8.3 Coding Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 8.4 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

9. Conclusion and Future Enhancement . . . . . . . . . . . . . . . Appendix References
6 ) References



[Type the document title] [Year]

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.


Objective of the Work

10 | P a g e

[Type the document title] [Year]
 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.  This bulk e-mail system could be utilized to reach existing clients, as well as contact potential clients. Through this system lots of companies can make numerous bulk email versions and send each one's e-mail message to a specific group of people.  This system helps in direct email marketing, bulk email marketing, online marketing research, bulk email newsletter sending, email newsletter promotion, mass email newsletter advertising, customer relationship management and collaborative working etc. Bulk email system has elicited system great enthusiasm and customer appreciation from users all over the world. ii) Scope of the Work This online bulk email sending system is a big support for people who has to send e-mail to countless recipients. Any organization or an individual will benefit a lot from the services provided by this website. Bulk e-mail system has following advantages:  It allows to reach global audience with minimum effort  It is cheap to launch an email campaign when compared to other marketing channels  It is extremely affordable  The cost to send out emails is minimal  It has the ability to distribute information to a wide range of specific, potential customers at a pretty low cost  In terms of sending and responses is more immediate in comparative to traditional mailing
11 | P a g e

[Type the document title] [Year]
 You will be able to get the prompt response without any stretch of time  It is relatively easy and cost effective to test different email creative and messaging  E-mail messages are easy to track  Advertisers can generate repeat business iii) Technology Used The proposal has to be described in a detailed form to get an overview and an understanding of the functionalities of the technical approach. This provides the technical description of the characteristics of a proposal. J2EE: Java Enterprise Edition is a programming platform— part of the Java Platform-for developing and running distributed multi-tier architecture Java applications, based largely on modular software components running on an application server. HTML, XML: Hyper Text Mark up Language and Extensible mark up Language are the predominant mark up languages for web pages. It provides a means to describe the structure of text-based information in a document and to supplement that text with interactive forms, embedded images, and other objects. JAVASCRIPT: A client side scripting language used to create dynamic web content and user interface. i) Java Database Connectivity: JDBC is a Java API for executing SQL statements. (As a point of interest, JDBC is a trademarked name and is not an acronym;
12 | P a g e

[Type the document title] [Year]
nevertheless, JDBC is often thought of as standing for Java Database Connectivity. It consists of a set of classes and interfaces written in the Java programming language. JDBC provides a standard API for tool/database developers and makes it possible to write database applications using a pure Java API. Simply put, JDBC makes it possible to do three things: Establish a connection with a database. Send SQL statements. Process the results. SQL Structured Query Language (SQL) is the language used to manipulate relational databases. SQL is tied very closely with the relational model. In the relational model, data is stored in structures called relations or tables. SQL statements are issued for the purpose of: - Data definition:  Defining tables and structures in the database (DDL used to create,  Alter and drop schema objects such as tables and indexes). - Data manipulation:  Used to manipulate the data within those schema objects (DML Inserting, Updating, Deleting the data, and Querying the Database). iv) HARDWARE-SOFTWARE USED i) TOOLS & DEVELOPMENT ENVIRONMENT Apache Tomcat 6.0.18 Server: Apache Tomcat is a Servlet container developed by the Apache Software Foundation (ASF). Tomcat implements the Java Servlet and the Java Server Pages (JSP) specifications from Sun Microsystems, and provides a "pure Java" HTTP web server environment for Java code to run.
13 | P a g e

   ii)

[Type the document title] [Year]
 The Apache web server for communication between the other components of the E-mail system and the users. For security reasons, all communication between the users and the a E-mail system is conducted using SSL.  For this purpose, Apache provides a very reliable, fast and robust SSL implementation as a plug-in module.  User requests arrive at the Apache Web-Server, where they are directly processed or forwarded to the respective component (i.e. the mail server or JSP-Server).


How java is important to the internet?

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,


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

[Type the document title] [Year]
Other Javascript, hibernation, struts, html, xml

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 software‘s 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

[Type the document title] [Year]
developer and the customer with the means to assess quality once software is built.  Planning may be divided into five areas of effort:  Problem recognition  Evaluation and synthesis  Modeling  Specification  Review  Initially, the analyst studies the System Specification (if one exists) and the Software Project Plan. It is important to understand software in a system context and to review the software scope that was used to generate planning estimates. Next, communication for analysis must be established so that 34problem recognition is ensured. The goal is recognition of the basic problem elements as perceived by the customer/users.  Problem evaluation and solution synthesis is the next major area of effort for analysis. The analyst must define all externally observable data objects, evaluate the flow and content of information, define and elaborate all software functions, understand software behavior in the context of events that affect the system, establish system interface characteristics, and uncover additional design constraints. Each of these tasks serves to describe the problem so that an overall approach or solution may be synthesized.

16 | P a g e

[Type the document title] [Year]

July-August September October November-December January(start) February

Requirement Gathering & Analysis Project Planning System Design System Implementation Testing Documentation


Milestone and Deliverables

 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

[Type the document title] [Year]
and cost estimates and schedules cannot be updated. When planning a project series of milestones are established. Milestone: Milestone is an end-point of the software process activity.  At each milestone there should be formal output, such as report, that can be represented to the management. The weekly report is submitted to our project Guide, which include day to day work report.  Milestone report need not be large document; they are the short report of achievements in software project activity.  Milestone represents the end of the distinct, logical stage in the project. Deliverables:  Deliverable is a project report that is delivered to the administrator of our project.  Deliverables are delivered to the administrators of our organization at the end of the some major project phase such as specification, design, etc.  Deliverables are usually milestones. .

iii) Roles and Responsibility:
  The roles and responsibilities of this project are divided into two partners. All the phases of the project such as identifying the problem, analysis, solution, planning, designing, coding and implementation should be done by both the partners.

Design Analysis

Done by:Atul Vashistha



Done by:Atul Shah, Saurabh Vashistha

18 | P a g e

[Type the document title] [Year]
Coding Testing:Testing, Testing Done by: Atul Shah, Saurabh Vashistha Unit Testing, Module Done by: Atul Shah, Saurabh Integration, Interface Vashistha


Each phase is documented by: Atul Shah, Saurabh Vashistha



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

Date 20-09-2011 30-09-2011 15-10-2011 20-10-2011 20-12-2011 20-01-2012

[Type the document title] [Year]
Midway Testing Testing report Final Project Documentation 20-02-2012 08-03-2012 21-04-2012


PROJECT RISK MANAGEMENT: 1. Identify the risks

 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

[Type the document title] [Year]
beneficial to your project and organisation. These "good guys" make your project faster, better and more profitable. 3. Analyze risks  Risk analysis occurs at different levels.  Looking at the effects, you can describe what effects take place immediately after a risk occurs and what effects happen as a result of the primary effects or because time elapses.  A more detailed analysis may show the order of magnitude effect in a certain effect category like costs, lead time or product quality.  Another angle to look at risks, is to focus on the events that precede a risk occurrence, the risk causes. List the different causes and the circumstances that decrease or increase the likelihood.  Another level of risk analysis is investigate the entire project. Each project manager needs to answer the usual questions about the total budget needed or the date the project will finish. If you take risks into account, you can do a simulation to show your project sponsor how likely it is that you finish on a given date or within a certain time frame. A similar exercise can be done for project costs. The information you gather in a risk analysis will provide valuable insights in your project and the necessary input to find effective responses to optimise the risks. 4. Plan and implement risk response:  Implementing a risk response is the activity that actually adds value to your project. You prevent a threat occurring or minimise negative effects. Execution is key here. The other rules have helped you to map, prioritise and understand risks. This will help you to make a sound risk response plan that focuses on the big wins.  If you deal with threats you basically have three options, risk avoidance, risk minimisation and risk acceptance. Avoiding risks means you organise your project in such a way that you don't encounter a risk anymore. This could mean changing supplier or adopting a different
21 | P a g e

[Type the document title] [Year]
technology or, if you deal with a fatal risk, terminating a project. Spending more money on a doomed project is a bad investment  The biggest category of responses are the ones to minimise risks. You can try to prevent a risk occurring by influencing the causes or decreasing the negative effects that could result. If you have carried out rule 7 properly (risk analysis) you will have plenty of opportunities to influence it. A final response is to accept a risk. This is a good choice if the effects on the project are minimal or the possibilities to influence it prove to be very difficult, time consuming or relatively expensive. Just make sure that it is a conscious choice to accept a certain risk.  Responses for risk opportunities are the reverse of the ones for threats. They will focus on seeking risks, maximising them or ignoring them (if opportunities prove to be too small).

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

[Type the document title] [Year]
 There are different sorts of risks and we need to decide on a project by project basis what to do about each type.  Business risks are ongoing risks that are best handled by the business. An example is that if the project cannot meet end of financial year deadline, the business area may need to retain their existing accounting system for another year. The response is likely to be a contingency plan developed by the business, to use the existing system for another year.  Generic risks are risks to all projects. For example the risk that business users might not be available and requirements may be incomplete. Each organisation will develop standard responses to generic risks.  Risks should be defined in two parts. The first is the cause of the situation (Vendor not meeting deadline, Business users not available, etc.). The second part is the impact (Budget will be exceeded, Milestones not achieved, etc.). Hence a risk might be defined as "The vendor not meeting deadline will mean that budget will be exceeded". If this format is used, it is easy to remove duplicates, and understand the risk.  Risk Quantification Risk need to be quantified in two dimensions. The impact of the risk needs to be assessed. The probability of the risk occurring needs to be assessed. For simplicity, rate each on a 1 to 4 scale. The larger the number, the larger the impact or probability. By using a matrix, a priority can be established.

23 | P a g e

[Type the document title] [Year]
Note that if probability is high, and impact is low, it is a Medium risk. On the other hand if impact is high, and probability low, it is High priority. A remote chance of a catastrophe warrants more attention than a high chance of a hiccup.

 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

[Type the document title] [Year]


Requirement Of the System Feasibility Study Features Of the System Main Module Of the System System Requirement Study and Assumption



25 | P a g e

[Type the document title] [Year]
 Microsoft Visual Studio 2005 or 2008 or later version and Microsoft SQL Server 2005 or later version  1024 x 768 screen resolution recommended  Internet Explorer of later version  To include your e-mail messages in the catalog, you must have either Microsoft Outlook 2000 or later, or Microsoft Outlook Express 6.0 or later.  Full preview of Microsoft Office documents in the results view requires Office XP or later  Minimum Pentium 500 MHz processor (1 GHz recommended)  Windows XP or later or Windows Server 2003 Service Pack 1

Hardware requirement:


Minimum Requirements 32- Minimum Requirements Bit x64


Pentium III-compatible processor or faster. 1GHz minimum. Recommended 2GHz or faster.

Any Intel EMT64 or AMD x64 chip. Minimum 1.4GHz. Recommended 2GHz or faster.

26 | P a g e

[Type the document title] [Year]
512MB minimum, 2GB or more recommended. Report Server will use a maximum of 3GB (with /3GB switch in boot.ini). 512MB minimum, 2GB or more recommended. Maximum is the OSspecified maximum.

Memory (RAM)

Hard disk space

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.


Pointing device



 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

[Type the document title] [Year]
 Economic analysis is most frequently used for evaluation of the effectiveness of the system. More commonly knows as cost/benefit analysis the procedure is to determine the benefit and saving that are expected from a system and compare them with costs, decisions is made to design and implement the system.  This part of feasibility study gives the top management the economic justification for the new system. This is an important input to the management the management, because very often the top management does not like to get confounded by the various technicalities that bound to be associated with a project of this kind. A simple economic analysis that gives the actual comparison of costs and benefits is much more meaningful in such cases.  In the system, the organization is most satisfied by economic feasibility. Because, if the organization implements this system, it need not require any additional hardware resources as well as it will be saving lot of time. 2) TECHNICAL FEASIBILITY  Technical feasibility centers on the existing manual system of the test management process and to what extent it can support the system. According to feasibility analysis procedure the technical feasibility of the system is analyzed and the technical requirements such as software facilities, procedure, inputs are identified. It is also one of the important phases of the system development activities. The system offers greater levels of user friendliness combined with greater processing speed. Therefore, the cost of maintenance can be reduced. Since, processing speed is very high and the work is reduced in the maintenance point of view management convince that the project is operationally feasible. 3) BEHAVIOURAL FEASIBILITY  People are inherently resistant to change and computer has been known to facilitate changes. An estimate should be made of how strong the user is likely to move towards the development of computerized system. These are various levels of users in order to ensure proper authentication and authorization and security of sensitive data of the organization.

28 | P a g e

[Type the document title] [Year]
iii) FEATURES OF BULK E-MAIL SYSTEM:  Create, target, personalize, send and track compelling email messages.  When Bulk E-mail sender is integrated with E-mail tracker the mail sender lets you control and compare the effectiveness of your email campaigns by monitoring who opens your emails, when, from what country and most importantly, which links they click.  The service provides the ability to check how many sent emails were opened and how many links in a message were clicked.  But the email tracker goes beyond these features by actually showing the email address of each user who clicks a link, the time at which they visited your site and the page they landed on. This function is very useful for determining who is ready to buy a product, and makes it easy to follow up with another email or a phone call.  It allows to reach global audience with minimum effort  It is cheap to launch an email campaign when compared to other marketing channels.  It is extremely affordable. MainFeatures included in this “sending online bulk E-mail system‖          

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

[Type the document title] [Year]
    Reporting Unsubscribe management Bounce Management Usability



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

[Type the document title] [Year]
The user should be able to save the incomplete mails in the Draft mailbox and these can be completed later and can be sent to others. 7. Record Sent mails: There should be a provision for keeping a record of the mails that have been sent by the user in a separate mailbox called Sent mailbox. 8. Trash mailbox: This mailbox keeps a record of the deleted mails from the othermailboxes such as Inbox, Sent, and Draft. If further mails are deleted from this, the mailsshould be permanently deleted from the users‘ accounts. 9. Security and Authentication: The security and authentication is as follows: - Login as buyer or seller or administrator. - Change password. - Forgot Password. - Registration for buyer / seller

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

[Type the document title] [Year]
   

Email Task Manager Mailing Generation Document Library

 


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 isn‘t left blank, for example rather

32 | P a g e

[Type the document title] [Year]
than Dear (blank) the system would send to ―Dear Supporter‖ where Supporter has been set as a default.

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‖, ―can‘t 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 can‘t 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

[Type the document title] [Year]

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 isn‘t 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.



Context Diagram Data Flow Diagram Data Dictionary E-R Diagrams
34 | P a g e

[Type the document title] [Year] Use-Case Diagrams


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


35 | P a g e

[Type the document title] [Year]
Log-in details of new/old accnts

Bulk e-mail system

Mail System (database





Data Flow Diagram
 A graphical tool used to describe and analyze the moment of data through a system manual or automated including the process, stores of data, and delays in the system. Data Flow Diagrams are the central tool and the basis from which other components are developed.  The transformation of data from input to output, through processes, may be described logically and independently of the physical components associated with the system.

 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

[Type the document title] [Year]
should be built. Later during design activity this is taken as the basis for drawing the system‘s structure charts. Data Flow diagram for bulk E-mail system

Level – 1 DFD User

Email Id & Password

Log In
Successful Login

Email Id & Password


Read or Delete

Manage Emails
Email Details

Email Messages


Level – 1 DFD Admin

Email Id & Password

Log In
Successful Login

Email Id & Password


37 | P a g e
Read or Delete

Manage user

Email Messages


[Type the document title] [Year]

Field Name First Name Middle Name Last Name

Data Taye Vchar Vchar Vchar

Size 15 15 15


Allow Null

Data dictionary: Admin

38 | P a g e

[Type the document title] [Year]
Mobile No Gender Birthday User Name Email Id Password Security Question Recovery Email Country Name State Name Number Char Date Vchar Vchar Number Vchar Vchar Vchar Vchar 15 1 8 15 15 10 25 15 5 5 Yes Primary Key Primary Key Primary Key Primary Key Yes Yes Yes

User Profile
Field Name User Name Data Type Vchar Size 15 Constraint Foreign Key Allow Null

39 | P a g e

[Type the document title] [Year]
Company Id Company Name Company Address Company Cont.No Type Of Business Type Of Package Time Duration Of package Number Vchar Vchar Number Vchar Vchar Number 10 15 25 15 15 10 5 Primary Key

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

Field Name Data Type Size Constraint Allow Null

40 | P a g e

[Type the document title] [Year]
User Name Compose Mail Id Inbox Id Draft Id Sent Item Id SPAM Id Trash Id Vchar Number Number Number Number Number Number 15 10 10 10 10 10 10 Foreign Key Primary Key Primary Key Primary Key Primary Key Primary Key Primary Key

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

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

[Type the document title] [Year]

Field Name User Name SPAM Id SPAM Mail Data Type Vchar number number Size 15 10 10 Constraint Foreign Key Foreign Key Allow Null

Field Name User Name Trash Id Trash Mail Data Type Vchar Number number Size 15 10 10 Constraint Foreign Key Foreign Key Allow Null

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

[Type the document title] [Year]
Field Name User Name Sent Id Sent Mail Data Type Vchar number number Size 15 10 20 Constraint Foreign Key Foreign Key Allow Null

43 | P a g e

[Type the document title] [Year]

Screen -Shot

44 | P a g e

[Type the document title] [Year]

Chapter 5
Planning, Implementation and Testing

5.1 Implementation Environment
The implementation of our website is under the environment of JAVA. The dynamic page will be run on web browser like Mozilla Firefox 4.0 or greater, Microsoft Internet Explorer 6.0 or greater, and Google Chrome 10 or greater

5.2 Security Features
 User require their account in this site to use the bulk email marketing facility.  During the user(compnay)registration process website presents the terms and conditions as follows:  User should have a valid Bank Account or should be able to pay through approved credit cards like MasterCard or Visa.  User should be able to make the payment before the emails are actually delivered to the recipient.  User should have a right to choose the scheme and package as per there requirements.  Application should be feasible to users and provide secure transmition.  There will be an administrator, who has all the access rights to see all the details about user, corporate, employees, services and accounting.

45 | P a g e

[Type the document title] [Year]
And also have all the add, edit and delete permission of its mail content to be mailed.

5.3 Coding Standards
 CODING STANDARDS The coding standard is the well-defined and standard style of coding. With the help of the coding standard any person can go into any code and figure out what's going on and new people can get up to speed quickly. A coding standard sets out standard ways of doing several things such as the way variables are to be named, the code is to be laid out, the comments are to be described, the work of function are to carried out etc.  Naming Conventions  The name of variable that We have used in programs represents the content or purpose or role of the variable.  We have defined the each variable with the length of seven to eight characters.  Variable names consist of a data type used in it. If it is a string then the prefix of the variable is ‘string’ else if integer then ‘int’.  Variable Declarations  We have placed the local variable declarations at the beginning of the each program.
46 | P a g e

[Type the document title] [Year]
 Block of declarations has aligned.  For multiple declarations We have used new declaration on the next line.

 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

[Type the document title] [Year]

Unit Testing Module Testing Sub-Sytem Testing System Testing

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

[Type the document title] [Year]

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

Sign up to vote on this title
UsefulNot useful