IMS Final Report

8/3/2019 IMS Final Report

1/57

Project Report

On

INTRANET MAILING SYSTEM

Submitted to the

Rajasthan Technical University, Kota

In Partial fulfillment of the requirement for the degree of

MASTER OF COMPUTER APPICATIONS

Submitted by Submitted to

Nipun Kumar Jain Mr.Hemant Sahu

Mohit Mathur

Geetanjali Institute of Technical Studies, Udaipur

Affiliated to

Rajasthan Technical University, Kota

MCA-(2009-12)

(December-2011)


2/57

CERTIFICATE

This is to certify thatproject entitled INTRANET MAILING SYSTEM and submitted by

Nipun Kumar Jain and Mohit Mathur for the partial fulfillment of the requirements of MCAdegree of Rajasthan Technical University Kota embodies the bonafied work done by all under

my supervision.

Hemant Sahu

Associate Professor & Head

Department of MCA

Acknowledgement


3/57

It gives me immense pleasure to express my sincere thanks and gratitude to all those with whose

guidance, co-operation and sincerest counsel. I have been able to complete my project.

A large number of people have contributed to the evolution of this system and Id like to

thank everyone (Office management and our faculty members who have e-mailed me) that made

constructive suggestions for developing this system. The system designer, testing andmaintenance staff were very supportive and helpful and help to produce the system in record

time.

I am thankful and indebted to Mr. Hemant Sahu, Geetanjali Institute of Technical

Studies, Udaipur under whose guidance; I have completed my project work. Thanks to him from

the depth of my heart for his valuable suggestions and proper guidance through the project.

Table of Contents


4/57

1. Introduction

Objective

Scope

Purpose

2. Software & Hardware Requirements

Software Requirement

Hardware Requirement

3. Literature Survey and Introduction Methodology

4. SRS

5. Design and Development

Use Case

Activity Diagrams

Data Flow Diagram (DFD)

Class diagram

6. Testing and Implementation

7. Conclusion

8. System Design

Snapshot

Data Tables

9. References


5/57

Chapter 1

Introduction

Objective

The Objective of Internal Email and file sharing of an organization project is to

develop a system for an organization to inter communicate with each other.

It also includes file sharing that eliminates the need of servants as one can share file

across the system.

Employee of the organization will be able to view and download files and upload files.

Anyone who is registered can view and compose mail.

Registered person can check their sent items.

According to the initial study of the requirement following objectives need to be

met:

Acceptance of registration form.

Username and password is given to everyone.

Provide email and file sharing facility.

Backlogs handling.


6/57

.

Scope

The scope of the current application includes the transaction (monetary and non-

monetary) pertaining to the following functions:

Account Creation for Each Member

Composing and Sending E-mails

File Sharing

Scope of Administrator

Administrator can create personal account for each employee.

Administrator can add and delete the end users accounts.

Scope of Online End-User

Users compose and send e-mails.

Users can share file with other users.

Purpose

The purpose of project is to facilitate the computer based

communication between the various employees of particular organization.

The administrators of the Email & File Sharing System have authority to

register the user on this system, admin main task is to create and manageuser account. The system will allow users to send & receive Email and also

file sharing facility within a organization, Administrator will provide user id

and password for new user so he/she can registered himself/herself and use

the service of email and file sharing in a particular organization.


7/57

Chapter 2

Software & Hardware Requirements

Software Requirement

Following are the core technologies used in developing our website.

Server Technologies:

WAMP (Web Server)

WAMP (Windows, Apache, MySQL, PHP/Perl/Python).


8/57

WAMPs are packages of independently-created programs installed on computers that

use a Microsoft Windows operating system.

WAMP is an acronym formed from the initials of the operating system Microsoft

Windows and the principal components of the package: Apache, MySQL and one ofPHP, Perl or Python. Apache is a web server.

MySQL is an open-source database. PHP is a scripting language that can manipulate

information held in a database and generate web pages dynamically each time

content is requested by a browser.

Other programs may also be included in a package, such as phpMyAdmin which

provides a graphical user interface for the MySQL database manager, or the

alternative scripting languages Python or Perl.

Equivalent packages are MAMP (for the Apple Mac) and LAMP (for the Linux

operating system).

MySQL Server (Database Server)

We are listing the three main reasons why we have used Oracle instead of any other

prevailing database servers

SCALABLE

RELIABLE

SECURE

Software Technologies:

1. PHP

2. Ajax

3. JQuery


9/57

4. JavaScript

5. HTML

6. XML

7. CSS


10/57

Hardware Requirement

Processor Genuine Intel Pentium

Processor Speed 2.0GHz

Word Size 128 bits

RAM Size 128 MB

Hard Disk 10GB

Floppy Disk Drive 1.44 MB

Monitor 15 color SVGA Monitor

Cache Memory 256 KB Burst Cache

CD-ROM 52X CD ROM Drive

Keyboard Microsoft(111 keys)

Mouse Microsort(Optical Mouse)


11/57

Chapter 3

Literature Survey and Introduction of Methodology

Brief Description of the Current (Mannual) System

The current manual system follows

the traditional approach of delivering the records of information that is all paper based,

maintained on paper. And because of that paper based record management face lots of

problem and if record will misplaced then humble of problem has been occurred. So this

system will make work of management bit easy.

The query of clients is all verbally told to

the customers. For this there is a need of database of questions and answers, users and

admin the current system a lot of work has to be done in the absence of computerized

system.

Problems with Conventional (Mannual) System

Lack of immediate and accurate retrieval of information

Lack of validation

Lack of storage of information

Lack of consistency

Preparation of accurate and prompt report

Benefits of new automated system are described below

Quick answering of questions

Simple and Less time consuming

Less requirement of Staff and better management


12/57


13/57

Chapter 4

Software Requirement Specification (SRS)

Introduction to SRS

The purpose of SRS is that the requirement specification allows the

programmer to code the software in the same respect as the user wants him to make his software.

The requirements analysis is the phase used extensively throughout the project, as it is the whole

sole part of the project. Without the requirement analysis phase, nothing can be made in the

project. This phase tell us to make the project according to the users need.

Standards of SRS

We have tried to design the Website in such a way that user may not have

any difficulty in using this package and further expansion is possible without much effort. Even

though we cannot claim that this work to be ebirely exhaustive, the main purpose of this exercise

is perform each persons activity in computerized way rather than manually which is time

consuming. We are confident that this website package can be readily used by non-programming

personal avoiding human handled chance of error.

This project is used by following users

Employee of the specified department for Composing and viewing mails.

Employee of the specified department for uploading and downloading mails.

Admin can manage the users.


14/57

Online users can see the required news. Administrator can maintain daily updates. Administrator

is must be an authorized user.


15/57

Functional Requirement

Functional Requirements are those that refer to the functionality of

the system, i.e., what services it will provide to the user.

Login Form

Use Case Name Login Form

Trigger Both Admin and Registered user will use it to login.

Pre-condition Account must exist

Basic Path The login form is given on the form. User need to enter

his/her user name and password to go into his/her account.

now one will click on login button.

The system will validate the user that whether the user has

an account or not. If login is successful then the home page

of the user is shown else the error message is shown. If the

username and password is found of admin then the admin

home page is shown for manage user account.

Alternative Paths N/A

Post-condition N/A

Other None

Priority Essential

Change Profile


16/57

Use Case Name Change Profile

Trigger A Register user having a facility to edit profile and

save updated profile.


Basic Path Once the user logins successful , he will be able to

change profile and after desire change in profile

submit the profile and after validate by system the

server will save all the updated data in database


Post-condition N/A

Other None

Priority Essential

File Sharing

Use Case Name File Sharing

Trigger A registered user have facility to upload a file on

server and also download file from server so he


17/57

can easily share file between register user of a

system.


Basic Path Once user successfully login he click on file

sharing option and system will display appropriatepage having option download file and upload file

user wish to upload a file than he click on upload a

file than file uploaded another option is download

a file than click on download file option and

download a file from database server.


Post-condition N/A

Other None

Priority Essential


18/57

Compose mail

Use Case Name Compose mail

Trigger A register user can send a email to particular user

in a organization.


Basic Path A register user have facility to send a mail in

within a intranet system to appropriate register

user and email system have responsibility to save

and send to recipient .


Post-condition N/A

Other None

Priority Essential


19/57

Check Inbox

Use Case Name Check Inbox

Trigger A register user receive mail in inbox and facility to

view or delete mail.


Basic Path The user click on inbox option and system will

show desire page and user view the mail he has

a option that either he delete the mail after reading

or he has another option to send reply mail.


Post-condition N/A

Other None

Priority Essential


20/57

Manage Account

Use Case Name Manage Account

Trigger This use case will be used by admin to add new

user and delete existing user and save updated

information at web server


Basic Path Admin have facility to manage user account when

he click at this option system will display a page

where he can add new user and also delete existing

user and performing a desire task updated

information save in database.


Post-condition N/A

Other None

Priority Essential


21/57

Non-Functional Requirement

Secure access of confidential data (users details). SSL 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

1. Security

Description Priority

The system must be capable of supporting different types of users, who

have associated permissions within the system.

Essential

2. Documentation / Online Helps


A System Adminstration manual shall be provided that cover sall the

system adminstration functions of the system.

Essential

An Extensive online help facility shall be provided that covers all user

functions,is indexed and fully searchable.

Essential

3. Usability


A System shall provide a consistent user interface,menus and

commands across all parts of the application to assist new users in

gettingup of speed.

Essential

The system should provide meaningful error messages that give users

a clear prompts as to how to take corrective action..

Essential


22/57

4. Compliance with Standard


The System shall be store all dates in a format complaint with ISO

8601.

Dates Shall be formatted as YYYY-MM-DD where YYYY is the year

in the usual Gregorian calendar,MM is the month of the year between

01(january) and 12(December),DD is the day of the month between 01

and 31.

Time shall be formatted as hh:mm:ss where hh is the number of

complete hours that have passed since midnight(00-24),mm is the

number of complete minutes that have passed since the start hour(00-

59),ans ss is the numberr of the complete seconds since the start of the

nminute(0-60).

Essential

If the system uses an underlying relational database,it must cofirm to

the SQL standard ISO/ICE 9075.

Essential

5. Backup & Recovery


The System shall provide Backup & Recovery facilities for all data are

held within the underlying data base.

Essential


23/57

Chapter 5

Design and Development

Unified Modeling Language (UML)

(a) UseCase Diagram


24/57

(b) Activity Diagram

1. Login Activity Diagram

9


25/57

2.Change Profile Activity Diagram

Em ail SystemUser

Edit Profile Display Req uested Page

Edit in Profile form

Subm it Validate

[Incorrect][Correct]

Save Data


26/57

3. File Sharing Activity Diagram

E m a il S y s t e mU s e r

C l i c k o n F i le S h a r in gD i s p l a y F i le S h a r in g F o r m

U p lo a d F i le

D o w n lo a d F i le P r ov ide the f il e

S a v e T h e f ile

13


27/57

4.Compose Mail Activity Diagram


C l ic k o n C o m p o s e m a ilD i s p la y R e q u e s t e d p a g e

C o m p o s e m a il fo r m

S e n d m a il S a v e a n d S e n d to R e c ip ie n t

15


28/57

5.Manage Account Activity Diagram

Email SystemAdmin

Update User list Display User List form

Add User Delete user

Save Updated Record


29/57

5.Check Inbox Activity Diagram


C h e c k I n b o x D i s p l a y R e q u e s t e d F o r m

V ie w m a il

D e l e te m a il

R e p l y to

U p d a t e In b o x

S a v e a n d S e n d t o re c i p ie n t

(c) Sequence Diagram


30/57

1. Login

Class Description

Login form: boundary Allow the user to login to the system.

Login controller: controller This class controls the login usecase.

Login: entity That contain the detail of login records.

2.Registration


31/57

Class Description

User Registration form: boundary Allow the user to register to the system

User Registration controller: controller This class controls the valid User nformation

User: entity That contains the detail of user

3. Compose mail


32/57

Class Description

Compose form: boundary Allow the user to compose a mail.

Mailinfo controller: controller This class controls the compose mail use case.

Sendmail controller: entity That contain the detail about sent mail records.

4. Inbox


33/57

Class Description

Inbox form: boundary Allow the user to view received mails.

Inbox controller: controller This class controls the receiving mail usecase.

Inbox: entity That contain the detail about received mails.

5. Update Profile


34/57

Class Description

Profile form: boundary Allow the user to change into profile.

Profile controller: controller This class controls the Change profile use case.

Inbox: entity That contain the updated detail about user profile.

6. File Sharing


35/57

Class Description

File form: boundary Allow the user to upload/download the file.

File controller: controller This class controls the sharing of files usecase.

File: entity That contain the uploaded file detail.

7.Maintain User List


36/57

Class Description

User List form: boundary Allow admin to view/update the list of users.

User List controller: controller This class controls manage user account usecase.

User List: entity That contains the updated user list.


37/57

(d) Class Diagram

RegisteredUser

-User name-Password+user_login()+edit_profile()

MailInformation

+show_mail()+show_maildetail()+show_sentmail()

MailBox-filename+compose_mai

l()+add_attachment()+delete_mail()+share_file()

27

11..*

1..*

1..*1..*


38/57

(e) Data Flow Diagram

0 Level DFD


39/57

1 Level DFD


40/57

1 Level DFD

1 Level DFD


41/57

1 Level DFD


42/57

Chapter 6


43/57

Testing and Implementation

Testing Overview

The aim of testing process is to identify all defects in a software product. Testing

is any activity aimed at evaluating the software for quality results it produces and the quality ofresults it can handle. Testing a program consists of subjecting the program to attest cases and

observing if the program behaves as expected. If the program fails to behave as expected , then

the condition under , which failures occurs are noted for later debugging and correction. There

are many stages of testing depending on the complexity of the software.

Levels of Testing

Unit Testing

Integration Testing

System Testing

Acceptance Testing

The levels of Testing attempt to detect different types of faults. The relation of faults introducesin different phases and the different levels of testing are shown :

Employee Needs Acceptance

Testing

Requirement System

Testing

Design IntegrationTesting

Code Unit

Testing

Unit Testing


44/57

Unit Testing has been under taken when a module has been coded and

successfully reviewed. Unit testing is the testing of different units or modules of system in

isolation. Is programmers responsibility to think of the advantage of doing unit testing before

integration testing is that it makes debugging easier. If an error is detected when a module is

being tested along with several modules, it would be difficult to determine which module exactly

has an error.

Integration Testing

Once a program or module has been tested the module interface in order to ensure

that there are no errors in the parameter passing , when one module involves another modules.

During integration testing, different-different modules of the system are integrated in a planned

manner i.e. the order in which they are combined to realize the full system.

The various approaches of integration testing are :

Big Bang Approach

Top-Down Approach

Bootom-Up Approach

Mixed Approach

One of the above four approaches Mixed Approach has been used for the proposed system.A missed approach integration testing follows a combination of top down and bottom up testing

approach. In the top-down approach , testing can start only after the bottom level module is

ready. The mixed testing can start as a when modules become available.

For the proposed we have also extensively used regression testing. Regression testing is

the practice of running an old test suite after change to the system or after each bug fix ensures

no new bug has been introduced as a resukt of the change made or bug fixed.

System Testing


45/57


46/57

A walkthrough approach with friends and scenarios was applied for testing. Suggestions related

to presentation and report generation were incorporated.

Test Plan and Test Cases

The components which are developed are :

The online application submits

Approval of the online application

Issue against Approved applications

Report Generation

Since the whole project is not yet developed and only few components are carried out. The unit

testing was carried out by separately operating the components. The testing of online submission

part was carried out by checking the all form validation and checking the database after the form

submission. The approval part was carried out by testing the data which are inserted in the

database in the online submission part. The issue and report portion is also tested by the same

data which were processed in the testing of approval of the application portion.

Result

Testing is an essential stage of the software development life cycle. If it is performed

properly by following an organizations standards the end result will be more robust programs

going to the system integration testing and finally a system with low maintenance. Proper coding

and unit testing are basic steps to ensure that the system being built will work once it is put

together.


47/57

Chapter 7

Conclusion

System Evalution

Nowadays, all organization attaches great importance to the

communication system and has been the core projects in the construction of communication

system within organization.

In this paper, we determine the weight of evaluation index systems and use gray

correlation analysis to evaluate the Intranet Mailing System, this qualitative and quantitative

analysis methods are more scientific and objective for Communication within organization

systems evaluation.

Intranets play an important role in this vision by serving as the single, consolidated

interface through which employees access a companys intellectual assets.Implementation of

intranet improved our ability to manage knowledge and communicate information within the

department and to any user in the system.

Future Extension

Any organization may adopt it as it is flexible.

Chatting script can be integrated.

In future, employees can be divided on the basis of department.

File viewing and downloading can be restricted on the basis of department toprovide higher confidentiality.

Future Sope of Application

This application can be easily implemented under various

situations. We can add new features as and when we require. Reusability is possible as and when

require in this application. There is flexibility in all the modules.

Software Scope


48/57

Extensibility

This software is extendable in ways that its original developers may not

expect. The following principles enhance extensibility like hide data structure, avoid

traversing multiple links or methods, avoid case statements on object type and distinguish

public and private operations.

Reusability

Reusability is possible as and when require in this application. We can

update it next version. Reusable software reduces design, coding, and testing cost by

amortizing effort over several designs. Reducing the amount of code also simplifies

understanding, which increases the likelihood that the code is correct. We follow up both

types of reusability:

Sharing of newly written code with in a project.

Reuse of previously written code on new projects.

Understandability

A method is understandable if someone other than the creator of

the method can understand the code (as well as the creator after a time lapse). We usethe method, which small and coherent helps to accomplish this.

Cost-Effectiveness

Its cost is under the budget and make within given time period. It is

desirable to aim for a system with a minimum cost subject to the condition that it must

satisfy the entire requirement.


49/57

Chapter 8

System Design

Snapshots

Index Page

New Registration


50/57

User Management

Inbox


51/57

View Message

Compose Mail


52/57

Sent Mail

View Sent Mail


53/57

File Sharing

Edit User Profile


54/57

Database Design

1. Table1(admin_info):

Field name Data type Description Key inform

admin_id Int(11) Id of admin primary

User_name Varchar(30) Name of admin -

Password Varchar(20) Password for login -

2. Table2(file_info):


fielded Int(11) Field id primary

filename Varchar(max) Name of user -

uploadedDate datetimeDate on which file

added-


55/57

3. Table3(mail_info):


Maild Int(11) Maild primary

Sender Int(11) Name of sender -

Receiver Int(11) Name of receiver -

Subject Varchar(max) Subject of mail -

Message Varchar(max) Msg body -

Attachment Varchar(max) Attachment -

date datetime date -

4. Table4(User_Registration):


Userid Int(11) Userid Primary

Name Varchar(max) Name of user -

Username Varchar(max) Username for login -

Password Varchar(max) Password for login -

Address Varchar(max) Address of user -

Email Varchar(max) Email of user -

Department Varchar(max) Department of user -

Post Varchar(max) Post of employee -


56/57

Chapter 9

References and Bibliography

Web References

http://www.google.com

http://w3schools.com

www.sourceforge.com
http://www.google.com/http://w3schools.com/http://www.google.com/http://w3schools.com/


57/57

Bibliography

Silberschatz A., Database system Concepts, Mc Graw-Hill, 4th edition.

Ramakrishnan R. & Gehrke j., Database Management System, Mc Graw Hill, 2002

Kroenke, D.M, Database Processing: Fundamentals, Design and Implementation,

Prentice Hall, 1998.

Riordan R., Designing Relational Database System, Microsoft Press, 1999.

Hoffer, J.A. Modern System Analysis and Design, Addison Wesley Longman, India,

2001.

Thimbleby H., User Interface Design, Addison Wesley, U.K., 1990.

IMS Final Report

Documents

Transcript of IMS Final Report