Intranet Email System: Team Members Project Mentor

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 34

Intranet Email System

National Institute of Technology Kurukshetra

Department of Computer Application

Team members
Amit Kumar (411088) Deepak Kumar Saini(411061) Amit Kumar (411021)

Project mentor
Monika Saini Asst. professor

Context
Introduction Proposed system Advantages of proposed system

Feasibility study
Software Requirement Specification Functional requirement Technical requirement Scope of The project Context Diagram Data Flow Diagram Class-diagram Sequence Diagram

Introduction

The email system is developed for communication between the people on the network.

The intranet email system provides a means by which people can communicate with each others, reply to each others queries and send mails to each others on the local network.
Before the member can start sending mails they have to register with at this site and as soon as they register they will be provided with a unique email address. This system is very secure because it use on local System . Any other person cannot steal the important information. This system is free of cost because no need of internet when we used it. It is very useful for a organization.

Proposed system

Registration of users. Update profile. Inbox. Sent mail. Compose mail. Save important data in draft.

Advantages of proposed system


User can interact with any one on the network through mailing system. Proposed system is intranet enabled. No need of internet . Secured system for information transfer. You can access system only from particular intranet network.

Feasibility study
Feasibility is the determination whether or not a project is worth doing. The process followed in making this determination is called feasibility study. Two important tests of feasibility are described below: Technical Feasibility Operational Feasibility

Technical Feasibility
This is concerned with specifying equipment and software that will Successfully satisfy the user requirement. It is considered that it should produce outputs in a given time. It should give quick response under certain condition. The hardware should be able to process certain volume of transactions at faster speed.

Operational Feasibility
The project has been designed considering all future scopes that can come into the consideration in the near future and also considering that the organization can make some changes in its working environment or operational structure, or it can add some new skill that can be essential in near future. At this level the project is almost operationally feasible because the system has been designed so efficiently that a person having little knowledge of computers can handle the system very well.

Software Requirement Specification


A complete specification of the software requirement is essential to the success of Software development efforts. No matter how will design and well coded, a poorly specified program will disappoint the user and bring grief to the developers the requirement analysis task is a process of discovery and refinement. SRS is conducted with the following objectives in mind: Identify the customers need. Evaluate the system concept for feasibility. Perform economic and technical analysis.

Software Requirement Specification


Allocate functions to hardware, software, people, database, and Other system elements. Establish cost and schedule constraints. Create a system definition that forms the foundation for all Subsequent work.

Functional requirement
1.

Registration:Purpose: to register the user(any person) Input: click on submit button at the registration page Processing: store all valid data Output: message indicates that you are registered successfully.

2. Login:

Purpose: login authenticate user Input: valid user name and password

Processing: check user name and password from the database


Output: mail page will be open.

Functional requirement
3. Inbox:

Purpose: interface to the user to check his/her email.


Input: No input required Processing : It figure out the email selected by user to be Read or delete and update the database query according to query Output: provides a message in the email format

4. Sent Mail:

Purpose: To Check the sent mail

Input: No input
Processing: Store the sending mail in database Output: Display the sent mail information

Functional requirement
5. Update profile:5(a). Change Password
Purpose: To change the password of user Input: old and new password Processing: verify old password from database if password is valid than update user password Output: New password confirmed

5(b). Change Picture:


Purpose: To change the picture of the user Input: new image from browse the local disk Processing: update user profile from database Output: update the user profile and new image

Functional requirement
6. Attach file:

Purpose: attach a file click .zip or .rar Input: click on browse button Processing: Uploading the File Output: file has attached

7. Draft:

Purpose: To save own message by user Input: No input

Processing: To Store the important mails in database


Output: show the draft mails in specific format

Technical requirement:
1. Hardware requirement:

Pentium IV Processor 128 Mb RAM 40 GB Hard disk 32 bit PCI Ethernet Card

II. Software Requirement:


Operating System: Windows xp/7(client/server) Web-server: Tomcat Server Front-End: HTML , CSS , j-query Communication Architecture: Servlet Database : MYSQL Client Browsers: Internet Explorer , Mozilla and Firefox

Scope of The project


It is designed to provide a communication channel inside an organization between different clients on the network. It accepts the mails from authorized users providing security. This enhances communications among the members of the organization in a reliable, costeffective and secure way.

Context Diagram

The Context Diagram shows the system under consideration as a single high-level process and then shows the relationship that the system has with other external entities (systems, organizational groups, external data stores, etc.).
Compose mail Sent mail Draft Profile

User

Attach file Receiving Mail

Email System

Data Flow Diagram


Data Flow Diagram (DFD) is a graphical technique that depicts information flow and transfers that are applied as data moves from input to output. The data flow diagram may be used to represent a system or software at any level of abstraction. The basic notation to create a DFD is: A rectangle is used to represent an external entity that is, a system element (e.g. hardware, person and another program) or another System that produces information for transformation by the software or receives information produced by the software.

Data Flow Diagram


An arrow represents Data Flow between the data items. An open rectangle represents data store stored information that is used by the software, i.e. temporary repository of data. Data flow diagram level 1 Data flow diagram level 2

Admin

Validate Process info

Update user info User Account info

User Data flow diagram level 1

Enter username and password Display Inbox

Log in

Retrieve user & Mail info Display sent mail info

Update password

Draft
Retrieve draft

User detail

Compose Change password


Update password

Data Flow Diagram level 2


1)Registration :USER User Account info

Enter user info

Validate Process user info 2) Log in :User Lo g in Log in form

Update user info

Allow to access account

Accept details Of Authenticate user User Account info

3) Inbox :Retrieve user info

User Details

Data entry operator

Display Inbox

Update /delete/new mail

Validate /process user info

4) Sent Mail :Data entry operator Display sent mail info


Retrieve user info

User detail
Delete/update mail info

Validate/ Process user info

Update mail info

5) Compose Mail :Data entry operator User Account info

Enter destination id , subject& massage

Validate /process user info

Update mail info

6) Change password :Data entry operator Display Profile

Retrieve user info

User info Validate /process user info

Enter old password, new password and Retype password

Update mail info

ER Diagram:
An entity relationship diagram is a graphical representation of an organizations data storage requirements. Identify the data that must be captured, stored and retrieved in order to support the business activities performed by an organisation. Identify the data required to derive and report on the performance measures that an organization should be monitoring.

Fname

name
user

Lname Dob

Password Gender username Country username

Fname

lname name

password

Admin To manage
username Log in Have sent dob password username To delete

ER DIAGRAM

state Mob no.

Work on

Delete Account
Sent mail Receiver id subject Msg msg Compose mail

To change confirm Change password New password Old password Change picture New picture

Have mail Inbox

Sender id msg

To view profile

subject

To save Mail

To send
To

msg subject

Draft

Subject

Attach file

Use case diagram


Use case diagram identify the functionality provides by the system (use cases), identifies users who interact with the system (actor) and provides association between users and use cases. A use case diagram is set of use cases, actors and relationships between actors use cases The basic components in use case diagram are: 1. Use case 2. Actor 3. Association

Admin use case


Log in

Send Mail

Delete user

Change password
Admin

Log out

User use case


Log in Compose Mail

Attach file

Sent Mail
draft Change password user Change image Log out

Overall use case

Log in

Compose Mail
Attach file Sent Mail draft

Change password
user Change image Delete user Log out Admin

Class-diagram
A class diagram is graphical notation that shows set of classes, interfaces, collaboration and their relationship graphically. Graphically it is a collection of vertices and arcs, classes and interfaces are represented as vertices on relationships as arcs connecting classes together.

User
First Name String Last Name String Gender String Age Number Address String City String Email_id String Password String Re-type pwd String Pin code Number Mobile Number Log_in() Change_password() Send_Mail() Save_Mail() Receive mail()

Admin
Username String Password String Delete_user() Send_mail() Change_pwd()

Delete User
Username String To_delete()

Log in
Username String Password String

Inbox
Sender id String Subject String Msg Content String Store _Mail() Delete_Mail()

Authentication() Log_out() Validate()

Draft
Subject String Msg Content String

Change password
Old password String New Password String Confirm pwd String Change_pwd()

Compose Mail
Sender id String Msg content String Subject String File_attach() Send _Mail()

To _save() To_Send()

Class diagram

Sequence diagram
A sequence diagram is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a message sequence chart. A sequence diagram shows object interactions arranged in time sequence. It depicts the objects and classes involved in the scenario. Sequence diagram shows, as parallel vertical lines, different processes or objects that live simultaneously and as horizontal arrows, the messages exchanged between them, in the order in which they occur.

You might also like