Вы находитесь на странице: 1из 4

Multi Mailer's Accessing System

Title of the Project: Multi Mailer's Accessing System Project Architecture: N-Tire/MVC Architecture SDLC Methodologies: Waterfall/Spiral Model Course: Roll No: Name of the Student: Technology And Language: Internal Guide: E-Mail ID: Mobile No (Student): Abstract of the Project: Introduction:
The Multi Mailer's Accessing System is a web-based application that automates all possible services deals with identifying multiple users with in the same login and enabling them to send and receive mails. The current environment requires a login for each user to handle all mails related information.

MS.Net 3.5 With Visual C#

Functional Requirements:
The Multi Mailer's Accessing System application proposed to be implemented the services for Users. The services that this system should support for these users are summarized below:

This system should provide the users with the convenience such as registering new users, view and manage the information about the users, view the following reports y Every user willing to use the mail server application should be existing as a user before they can send or receiving mails. y Each user is needed to specify the user name, password and date of creation. y A unique user-id is created or generated automatically and is associated with each user by the system. y Mail Organization deals the organization of mails. When the users are created, a directory with the user-id as its name should be created along with Inbox, Compose and Address list. y Message Composition deals with composing messages. y Message Address list is responsible for having all the massages, which have been stored in the users address. Once the user creates all the contents of the file are displayed in the view file. y Message Inbox will help the user to store the messages in the Inbox. All the new arrived messages will be stored in this inbox, not only the new messages but also old messages are also stored in it.

Non-Functional Requirements:
y y y y Secure access of confidential data (users details). SSL (Secure Sockets Layer) can be used. 24 X 7 availability Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension

Existing System:
Present system is Intranet based and in the present System we can communicate within the certain premises only. Limitations of the Existing system are following

y y y

There is no common interface for maintaining different mail servers in single web application For Mail receiving Every time we need to submit User Credentials Individual application portal Decreases performance.

The increasing complexity, producing the reports as desired is not possible, and protracted time-scales of modern systems design and development have made working to a standardized Multi mailers system both essential and mandatory.

Proposed Systems:
To overcome all the difficulties of the existing system the management has proposed automated the whole system and the development of the new automated system contains the following activities, which try to automate the entire process keeping in view of the database integration approach. y y y y y y y y y y It provides complete activity as automated system. It is not limited to a single system because it is aimed to develop for web based environment. User friendliness (Graphical User Interface) is provided in the application. Provide Interactive interface through which a user can interact with different areas of application easily. The system makes the overall task much easier and flexible. It can be accessed over the Internet/Intranet. There is no risk of data mismanagement at any level while the project development is under process. It provides high level of security using session technique. It provides role based authentication to the different users like Normal Users. Deploy the application on a single system and make is available on all the systems within the network, thereby reducing the maintenance cost of software.

Modules:
After looking at the functional requirements it is identified that we can divide the system into mainly following modules: y User administration. y Mail organization. y Message composition. y Message Address list y Message Inbox. y Message Deletion. y Authentication Module Authentication Module: The Authentication module is the security module provides Credentials i.e. valid username, password to the persons who are logging in this project.

Users of the System:


This system should be designed to support the following users: y Normal users

Environment:
y Servers: y y y Operating System Server: - Microsoft Windows XP/2000 or Higher Data Base Server: Microsoft SQL Server 2005/2008

Clients: Microsoft Internet Explorer (Client Browser)

y y y y y

Development Tools: Microsoft Visual Studio .Net 2008/2010 Documentation Tools: MS Office 2007/2010 Drawing Tools: IBM Rational Rose Enterprise, MS Office Visio 2007 User Interface: ASP.NET With AJAX Code Behind: VC#.NET

Requirements:
y Hardware Requirements: Number 1 Description PC With Minimum 20 GB Hard-Disk And 1GB RAM

y Software Requirements: Number 1 2. 3. 4. Description Windows XP/2000 Or Higher With MS-Office 2007/2010 MS-SQL Server 2005/2008 Ms-Visual Studio .Net 2008/2010 MS-Internet Explorer

Milestones: No. Milestone Name Requirements Specification Milestone Description Remarks

Technology Familiarization

Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of the technology needed to implement the project.

Attempt should be made to add some more relevant functionality other than those that are listed in this document.

Database Creation

A database of at least 10 entries of users with at least 1 should application admin.

High-level and Detailed Design Development of Front End Functionalities.

Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario. Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options

The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective. It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself. The scenarios should map to the requirement specification

During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.

Integrating the Front-end with the Database

Integration Testing

Final Review

The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing. The system should be thoroughly tested by running all the test cases written for the system (from milestone 5). Issues found during the previous milestone are fixed and the system is ready for the final review.

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled

The following steps will be helpful to start of the project:


y y y y y Study and be comfortable with technologies such as: ASP.Net with C#, and SQL Server. Gather some knowledge of product hierarchies and maintenance before starting the design. Create a user database with different access levels. Start with creating the login screen. Create menus for navigation and group the functionalities as sub menus. Create the help-pages of the application in the form of FAQ. This will helps user.