Voicemail Synopsis
Content
MCSP – 060 SYNOPSIS OF
VOICE EMAIL
Submitted by MASRAT AKHTER Enrolment no. 098150586 UNDER THE GUIDANCE Of MR. Syed Waseem Aslam Shah Submitted to the school of computer and information sciences in partial fulfillment of the requirements for the degree of Masters of Computer Applications (MCA) Year of Submission
INDIRA GANDHI NAIONAL OPEN UNIVERSITY, Maidan Garhi New Delhi - 110068
SCHOOL OF COMPUTER AND INFORMATION SCIENCES IGNOU, MAIDAN GARHI, NEW DELHI – 110 068 II. PROFORMA FOR THE APPROVAL OF MCA PROJECT PROPOSAL
(Note: All entries of the Performa of approval should be filled up with appropriate and complete information. Incomplete Performa of approval in any respect will be summarily rejected.)
Enrolment No.: ......................... Project Proposal No :………………….. (for office use only) Study Centre: ........…………… Regional Centre:…RC Code:….. E-mail:…….………...................... Mobile/Tel No.: …..…………… 1. Name and Address of the Student ……………………………………………………………... ……………………………………………………………... 2. Title of the Project .………..……………………………………………………. 3. Name and Address of the Guide …..…………………………………………………………. ……………………………………………………………… Ph.D* 4. Educational Qualification of the Guide (Attach bio-data also) (*in Computer Science / IT only) 5. Working / Teaching experience of the Guide** ………………………………………………………………………………………. (**Note: At any given point of time, a guide should not provide guidance for more than 5 MCA students of IGNOU) 6. Software used in the Project …………………………………………………………….. M.Tech.* B.E*/B.Tech.* MCA Msc
7. If already pursued BCA/BIT from IGNOU, Mention the title of the project (CS-76) and the s/w used……………………………………………………………….. 8. Project title of the Mini Project (MCS-044) and the s/w used………………………………………………………………..
9. Is this your first submission?
Yes
No
Signature of the Student Date: …………………
Signature of the Guide Date: …………………….
For Office Use Only
Name………………………… …………………………….. Signature, Designation, Stamp
of the Project Proposal Evaluator
Approved
Not Approved
Date: ………………………………
Suggestions for reformulating the Project:
Preface
Table of Contents
Preface
Table of Contents
TITLE OF THE PROJECT 1. INTRODUCTION
Abstract Project Objectives Scope of the project
2. PROJECT CATEGORY 3. HARDWARE AND SOFTWARE REQUIREMENTS
4.1Hardware Requirements 4.2 Software Requirements
5. PERT Chart AND GANTT CHART 6. ANALYSIS (DFD AND ER DIAGRAMS)
6.1 Data Flow Diagrams 6.2 Context Level DFD 6.3 Level – 1 DFD 6.4 Entity Relationship Diagram
7. COMPLETE STRUCTURE OF THE PROJECT
7.1 Modules and their description 7.2 Data Structure 7.3 Process Logic of modules 7.4 Implementation Methodology 7.5 List of Reports likely to be generated.
8. OVERALL NETWORK ARCHITECTURE 9. IMPLEMENTATION OF SECURITY MECHANISM 10. FUTURE SCOPE AND FURTHER ENHANCEMENT OF THE PROJECT
11. BIBLIOGRAPHY
Title Of The Project:-
\
VOICE BASED EMAIL
INTRODUCTION;
ABSTRACT
For most people today, the preferred means of communication is by email. Most people use computers to check their email, which means that if they are away from a computer or are using a computer without Internet access, they cannot check their email. Voice Based Email System provides, a way for you to check your email and even send email. The Voice Based Email System will check your email and read whatever message we want in our INBOX aloud . Voicemail systems began as a replacement for earlier analog answering machines, but developed many new features over time due to their digital storage of messages. Voicemail systems can now be used to route calls and messages to the proper recipient. Voice-mail (also known as voice message or voice bank) is a computer based system that allows users and subscribers to exchange personal voice messages; to select and deliver voice information; and to process transactions relating to individuals, organizations, products and services, Simple voice-mail systems function as a remote answering machine using a touch-tones as the user interface. More complicated systems may use other input devices such as voice or a computer interface. Simpler voice-mail systems may play the audio message through the phone, while more advanced
systems may have alternative delivery methods, including email or text message delivery, message transfer and forwarding options, and multiple mailboxes.
PURPOSE OF PROJECT
This document contains a description for “VOICE BASED EMAIL" enhancement. This document will contain the functional requirements of the project and how the developers will enhance the project to achieve all the objectives. The SRS will serve as a guide for the client and the developers.
SCOPE OF THE PROJECT
A well-implemented voicemail system can provide benefits to the customer and the business. Customers should be provided with the option to immediately leave a message at any time, rather than wait on hold or be forced to navigate the system. This demonstrates a respect for the value of her time -- provided, of course, that their message gets to the right person regardless, and receives a prompt reply. This efficiency allows you to lower your staff expenses while maintaining customer satisfaction. A grammar defines the set of valid expressions that a user can say or type when interacting with a voice application. Each interactive dialog in an application references one or more grammars using one or more grammar elements. VoiceXML provides you with several choices when integrating grammars into your voice application: Reference a 'builtin' grammar by setting the type attribute of the field element.
Define your own grammar using the Nuance Grammar Specification Language (GSL)
OBJECTIVES
Minimizing the manual records kept at different locations. There will be more data integrity. Facilitating desired information display, very quickly, by retrieving information from users. Facilitating various statistical information which helps in decision-making? To reduce manual efforts in activities that involved repetitive work. Updating and deletion of such a huge amount of data will become easier.
Project Category:-
“Web based Application Program”
System Requirement Specifications
Hardware Requirements: PIV 2.8 GHz Processor and Above RAM 2GB and Above HDD 40 GB Hard Disk Space and Above
Software Requirements: WINDOWS OS (XP / windows 7 / 2003 Server / 2008 Server) Visual Studio .Net 2008 Enterprise Edition Internet Information Server 7.0 (IIS) Visual Studio .Net Framework (Minimal for Deployment) version 3.0 SQL Server 2005 Enterprise Edition
Project Evaluation Review Technique (PERT)
A PERT chart is a project management tool used to schedule, organize, and coordinate tasks within a project. It tells about the running project and its current status. It includes activities, their estimated times of completion and actual time that they took. It is a pictorial representation of the various activities carried out during the project. A PERT chart presents a graphic illustration of a project as a network diagram consisting of numbered nodes (either circles or rectangles) representing events, or milestones in the project linked by
labelled vectors (directional lines) representing tasks in the project. The direction of the arrows on the lines indicates the sequence of tasks.
Activities Start A B C D E F
Names Requirement Analysis Logical Design Physical Design Coding Testing Implementation
Estimated Activities Start A Event No. 1 2 Events SRS DFD’& B 3 Flowchart UI & Algorithm C 4 Design Forms & D E 5 6 Reports Testing Required F
Start 1 2 A (30)
Time(days) 30
7
21
30 7
7
System
7
D (30)
B (7) 3
4 C (21)
5
6
6
F (7)
E (7)
Gantt Charts
This is a project planning tool that can be used to represent the timing of task required to complete a project. It is a standard format for displaying a schedule graphically .It consist of a horizontal bar chart wit time as the horizontal axis. Individual operations are displayed as horizontal bars in the chart, indicating the time at which the job begins and ends. Many variations on the Gantt chart exist to display additional kind of information. A Gantt chart is constructed with a horizontal axis representing the total time span of the project, broken down into increments (for example, days, weeks, or months) and a vertical axis representing the tasks that make up the project (for example, if the project is outfitting your computer with new software, the major tasks involved might be: conduct research, choose software, install software). Horizontal bars of varying lengths represent the sequences, timing, and time span for each task. Using the same example, you would put "conduct research" at the top of the vertical axis and draw a bar on the graph that represents the amount of time you expect to spend on the research, and then enter the other tasks below the first one and representative bars at the points in time when you expect to undertake them. The bar spans may overlap, as, for example, you may conduct research and choose software during the same time span. As the project progresses, secondary bars, arrowheads, or darkened bars may be added to indicate completed tasks, or the portions of tasks that have been completed. A vertical line is used to represent the report date. Gantt charts give a clear illustration of project status, but one problem with them is that they don't indicate task dependencies - you cannot tell how
one task falling behind schedule affects other tasks. The PERT chart, another popular project management charting method, is designed to do this. Automated Gantt charts store more information about tasks, such as the individuals assigned to specific tasks, and notes about the procedures. They also offer the benefit of being easy to change, which is helpful. Charts may be adjusted frequently to reflect the actual status of project tasks as, almost inevitably; they diverge from the original plan.
3/6 ANALYSIS DESIGN CODING TESTING
2/7
3/7 3/8
4/8
4/9
28/9 4/10
Expected date for completion of activities Actual date for completion
ANALYSIS (DFD AND E-R DIAGRAMS)
DFD Diagrams:
Login DFD Diagram:
Login Master
Open Login form
Enter User Name and Password
Yes
Check User
Yes
User Home Page
No
Verify Data
1st Level DFD A1; Userid , Password , Designation
UML DIAGRAM
Class Diagram:
E-R DIAGRAMS
COMPLETE STRUCTURE
Modules and their description The project is mainly divided into 4 modules 1). User registration and Authentication The user registration and authentication module is meant for registering the user and authenticating the user with valid credentials to access the voice based mail facility.
2). Text based Mail Module
This module is used to send , read, delete mails from the database This module also provides the facility of attaching the files with the email. 3). Voice Based Mail Module
The voice based module is used to read the mail in the inbox and is employed using microsoft speec h recognition and speech synthesis API's.
4). Steganography module This module stegnates the outgoing mail or the attachment that is enclosed with the email and is also employed in de-stegnating the mail 5) Spam checker module
This module is used to check the junk mails and redirect them in the junk folder and is based on the detection of keywords
OVERALL NETWORK ARCHITECTURE
The presentation tier In the presentation layer, the code-behind mechanism for ASP.NET pages and user controls is a prominent example of a layered design. The markup file defines the look and layout of the web form and the code behind file contains the presentation logic. It's a clean separation because both the markup and the code-behind layers house specific sets of functionality that benefit from being apart. Designers don't have to worry about messing up code to make user interface changes, and developers don't have to worry about sifting through the user-interface to update code.
The data tier You also see sub-layers in the data tier with database systems. Tables define the physical storage of data in a database, but stored procedures and views allow you to manipulate data as it goes into and out of those tables. Say, for example, you need to denormalize a table and therefore have to change its physical storage structure. If you access tables directly in the business layer, then you are forced to update your business tier to account for the changes to the table. If you use a layer of stored procedures and views to access the data, then you can expose the same logical structure by updating a view or stored procedure to account for the physical change without having to touch any code in your business layer. When used appropriately, a layered design can lessen the overall impact of changes to the application.
The business tier And of course, this brings us to the topic of business objects and the Data Access Layer (also known as the DAL), two sub-layers within the business tier. A business object is a component that encapsulates the data and business processing logic for a particular business entity. It is not, however, a persistent storage mechanism. Since business objects cannot store data indefinitely, the business tier relies on the data tier for long term data storage and retrieval.
Thus, your business tier contains logic for retrieving persistent data from the data-tier and placing it into business objects and, conversely, logic that persists data from business objects into the data tier. This is called data access logic.
Three tiered .NET application with sub-tiers
SYSTEM SECURITY
INTRODUCTION The protection of computer based resources that includes hardware, software, data, procedures and people against unauthorized use or natural Disaster is known as System Security. System Security can be divided into four related issues: Security Integrity Privacy Confidentiality SYSTEM SECURITY refers to the technical innovations and procedures applied to the hardware and operation systems to protect against deliberate or accidental damage from a defined threat. DATA SECURITY is the protection of data from loss, disclosure, modification and destruction. SYSTEM INTEGRITY refers to the power functioning of hardware and programs, appropriate physical security and safety against external threats such as eavesdropping and wiretapping. PRIVACY defines the rights of the user or organizations to determine what information they are willing to share with or accept from others and how the organization can be protected against unwelcome, unfair or excessive dissemination of information about it. CONFIDENTIALITY is a special status given to sensitive information in a database to minimize the possible invasion of privacy. It is an attribute of information that characterizes its need for protection. SECURITY SOFTWARE
System security refers to various validations on data in form of checks and controls to avoid the system from failing. It is always important to ensure that only valid data is entered and only valid operations are performed on the system. The system employees two types of checks and controls:
SDLC METHDOLOGIES
The following diagram shows how a spiral model acts like:
FIG:- SPIRAL MODEL
A COMPLETE DATABASE AND TABLES DETAIL WITH PRIMARY AND FOREIGN KEYS, AND PROPER CONSTRAINTS IN THE FIELDS
FUTURE SCOPE AND FURTHER ENHANCEMENT OF THE PROJECT
This Project plays a vital role in the development life cycle (SDLC) and it describes the complete requirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.
BIBLIOGRAPHY
FOR .NET INSTALLATION www.support.mircosoft.com FOR DEPLOYMENT AND PACKING ON SERVER www.developer.com www.15seconds.com FOR SQL www.msdn.microsoft.com FOR ASP.NET Asp.Net 3.5 Unleashed www.msdn.microsoft.com/net/quickstart/aspplus/default.com www.asp.net www.fmexpense.com/quickstart/aspplus/default.com www.asptoday.com www.aspfree.com www.4guysfromrolla.com/index.aspx Software Engineering (Roger’s Pressman
VOICE EMAIL
Submitted by MASRAT AKHTER Enrolment no. 098150586 UNDER THE GUIDANCE Of MR. Syed Waseem Aslam Shah Submitted to the school of computer and information sciences in partial fulfillment of the requirements for the degree of Masters of Computer Applications (MCA) Year of Submission
INDIRA GANDHI NAIONAL OPEN UNIVERSITY, Maidan Garhi New Delhi - 110068
SCHOOL OF COMPUTER AND INFORMATION SCIENCES IGNOU, MAIDAN GARHI, NEW DELHI – 110 068 II. PROFORMA FOR THE APPROVAL OF MCA PROJECT PROPOSAL
(Note: All entries of the Performa of approval should be filled up with appropriate and complete information. Incomplete Performa of approval in any respect will be summarily rejected.)
Enrolment No.: ......................... Project Proposal No :………………….. (for office use only) Study Centre: ........…………… Regional Centre:…RC Code:….. E-mail:…….………...................... Mobile/Tel No.: …..…………… 1. Name and Address of the Student ……………………………………………………………... ……………………………………………………………... 2. Title of the Project .………..……………………………………………………. 3. Name and Address of the Guide …..…………………………………………………………. ……………………………………………………………… Ph.D* 4. Educational Qualification of the Guide (Attach bio-data also) (*in Computer Science / IT only) 5. Working / Teaching experience of the Guide** ………………………………………………………………………………………. (**Note: At any given point of time, a guide should not provide guidance for more than 5 MCA students of IGNOU) 6. Software used in the Project …………………………………………………………….. M.Tech.* B.E*/B.Tech.* MCA Msc
7. If already pursued BCA/BIT from IGNOU, Mention the title of the project (CS-76) and the s/w used……………………………………………………………….. 8. Project title of the Mini Project (MCS-044) and the s/w used………………………………………………………………..
9. Is this your first submission?
Yes
No
Signature of the Student Date: …………………
Signature of the Guide Date: …………………….
For Office Use Only
Name………………………… …………………………….. Signature, Designation, Stamp
of the Project Proposal Evaluator
Approved
Not Approved
Date: ………………………………
Suggestions for reformulating the Project:
Preface
Table of Contents
Preface
Table of Contents
TITLE OF THE PROJECT 1. INTRODUCTION
Abstract Project Objectives Scope of the project
2. PROJECT CATEGORY 3. HARDWARE AND SOFTWARE REQUIREMENTS
4.1Hardware Requirements 4.2 Software Requirements
5. PERT Chart AND GANTT CHART 6. ANALYSIS (DFD AND ER DIAGRAMS)
6.1 Data Flow Diagrams 6.2 Context Level DFD 6.3 Level – 1 DFD 6.4 Entity Relationship Diagram
7. COMPLETE STRUCTURE OF THE PROJECT
7.1 Modules and their description 7.2 Data Structure 7.3 Process Logic of modules 7.4 Implementation Methodology 7.5 List of Reports likely to be generated.
8. OVERALL NETWORK ARCHITECTURE 9. IMPLEMENTATION OF SECURITY MECHANISM 10. FUTURE SCOPE AND FURTHER ENHANCEMENT OF THE PROJECT
11. BIBLIOGRAPHY
Title Of The Project:-
\
VOICE BASED EMAIL
INTRODUCTION;
ABSTRACT
For most people today, the preferred means of communication is by email. Most people use computers to check their email, which means that if they are away from a computer or are using a computer without Internet access, they cannot check their email. Voice Based Email System provides, a way for you to check your email and even send email. The Voice Based Email System will check your email and read whatever message we want in our INBOX aloud . Voicemail systems began as a replacement for earlier analog answering machines, but developed many new features over time due to their digital storage of messages. Voicemail systems can now be used to route calls and messages to the proper recipient. Voice-mail (also known as voice message or voice bank) is a computer based system that allows users and subscribers to exchange personal voice messages; to select and deliver voice information; and to process transactions relating to individuals, organizations, products and services, Simple voice-mail systems function as a remote answering machine using a touch-tones as the user interface. More complicated systems may use other input devices such as voice or a computer interface. Simpler voice-mail systems may play the audio message through the phone, while more advanced
systems may have alternative delivery methods, including email or text message delivery, message transfer and forwarding options, and multiple mailboxes.
PURPOSE OF PROJECT
This document contains a description for “VOICE BASED EMAIL" enhancement. This document will contain the functional requirements of the project and how the developers will enhance the project to achieve all the objectives. The SRS will serve as a guide for the client and the developers.
SCOPE OF THE PROJECT
A well-implemented voicemail system can provide benefits to the customer and the business. Customers should be provided with the option to immediately leave a message at any time, rather than wait on hold or be forced to navigate the system. This demonstrates a respect for the value of her time -- provided, of course, that their message gets to the right person regardless, and receives a prompt reply. This efficiency allows you to lower your staff expenses while maintaining customer satisfaction. A grammar defines the set of valid expressions that a user can say or type when interacting with a voice application. Each interactive dialog in an application references one or more grammars using one or more grammar elements. VoiceXML provides you with several choices when integrating grammars into your voice application: Reference a 'builtin' grammar by setting the type attribute of the field element.
Define your own grammar using the Nuance Grammar Specification Language (GSL)
OBJECTIVES
Minimizing the manual records kept at different locations. There will be more data integrity. Facilitating desired information display, very quickly, by retrieving information from users. Facilitating various statistical information which helps in decision-making? To reduce manual efforts in activities that involved repetitive work. Updating and deletion of such a huge amount of data will become easier.
Project Category:-
“Web based Application Program”
System Requirement Specifications
Hardware Requirements: PIV 2.8 GHz Processor and Above RAM 2GB and Above HDD 40 GB Hard Disk Space and Above
Software Requirements: WINDOWS OS (XP / windows 7 / 2003 Server / 2008 Server) Visual Studio .Net 2008 Enterprise Edition Internet Information Server 7.0 (IIS) Visual Studio .Net Framework (Minimal for Deployment) version 3.0 SQL Server 2005 Enterprise Edition
Project Evaluation Review Technique (PERT)
A PERT chart is a project management tool used to schedule, organize, and coordinate tasks within a project. It tells about the running project and its current status. It includes activities, their estimated times of completion and actual time that they took. It is a pictorial representation of the various activities carried out during the project. A PERT chart presents a graphic illustration of a project as a network diagram consisting of numbered nodes (either circles or rectangles) representing events, or milestones in the project linked by
labelled vectors (directional lines) representing tasks in the project. The direction of the arrows on the lines indicates the sequence of tasks.
Activities Start A B C D E F
Names Requirement Analysis Logical Design Physical Design Coding Testing Implementation
Estimated Activities Start A Event No. 1 2 Events SRS DFD’& B 3 Flowchart UI & Algorithm C 4 Design Forms & D E 5 6 Reports Testing Required F
Start 1 2 A (30)
Time(days) 30
7
21
30 7
7
System
7
D (30)
B (7) 3
4 C (21)
5
6
6
F (7)
E (7)
Gantt Charts
This is a project planning tool that can be used to represent the timing of task required to complete a project. It is a standard format for displaying a schedule graphically .It consist of a horizontal bar chart wit time as the horizontal axis. Individual operations are displayed as horizontal bars in the chart, indicating the time at which the job begins and ends. Many variations on the Gantt chart exist to display additional kind of information. A Gantt chart is constructed with a horizontal axis representing the total time span of the project, broken down into increments (for example, days, weeks, or months) and a vertical axis representing the tasks that make up the project (for example, if the project is outfitting your computer with new software, the major tasks involved might be: conduct research, choose software, install software). Horizontal bars of varying lengths represent the sequences, timing, and time span for each task. Using the same example, you would put "conduct research" at the top of the vertical axis and draw a bar on the graph that represents the amount of time you expect to spend on the research, and then enter the other tasks below the first one and representative bars at the points in time when you expect to undertake them. The bar spans may overlap, as, for example, you may conduct research and choose software during the same time span. As the project progresses, secondary bars, arrowheads, or darkened bars may be added to indicate completed tasks, or the portions of tasks that have been completed. A vertical line is used to represent the report date. Gantt charts give a clear illustration of project status, but one problem with them is that they don't indicate task dependencies - you cannot tell how
one task falling behind schedule affects other tasks. The PERT chart, another popular project management charting method, is designed to do this. Automated Gantt charts store more information about tasks, such as the individuals assigned to specific tasks, and notes about the procedures. They also offer the benefit of being easy to change, which is helpful. Charts may be adjusted frequently to reflect the actual status of project tasks as, almost inevitably; they diverge from the original plan.
3/6 ANALYSIS DESIGN CODING TESTING
2/7
3/7 3/8
4/8
4/9
28/9 4/10
Expected date for completion of activities Actual date for completion
ANALYSIS (DFD AND E-R DIAGRAMS)
DFD Diagrams:
Login DFD Diagram:
Login Master
Open Login form
Enter User Name and Password
Yes
Check User
Yes
User Home Page
No
Verify Data
1st Level DFD A1; Userid , Password , Designation
UML DIAGRAM
Class Diagram:
E-R DIAGRAMS
COMPLETE STRUCTURE
Modules and their description The project is mainly divided into 4 modules 1). User registration and Authentication The user registration and authentication module is meant for registering the user and authenticating the user with valid credentials to access the voice based mail facility.
2). Text based Mail Module
This module is used to send , read, delete mails from the database This module also provides the facility of attaching the files with the email. 3). Voice Based Mail Module
The voice based module is used to read the mail in the inbox and is employed using microsoft speec h recognition and speech synthesis API's.
4). Steganography module This module stegnates the outgoing mail or the attachment that is enclosed with the email and is also employed in de-stegnating the mail 5) Spam checker module
This module is used to check the junk mails and redirect them in the junk folder and is based on the detection of keywords
OVERALL NETWORK ARCHITECTURE
The presentation tier In the presentation layer, the code-behind mechanism for ASP.NET pages and user controls is a prominent example of a layered design. The markup file defines the look and layout of the web form and the code behind file contains the presentation logic. It's a clean separation because both the markup and the code-behind layers house specific sets of functionality that benefit from being apart. Designers don't have to worry about messing up code to make user interface changes, and developers don't have to worry about sifting through the user-interface to update code.
The data tier You also see sub-layers in the data tier with database systems. Tables define the physical storage of data in a database, but stored procedures and views allow you to manipulate data as it goes into and out of those tables. Say, for example, you need to denormalize a table and therefore have to change its physical storage structure. If you access tables directly in the business layer, then you are forced to update your business tier to account for the changes to the table. If you use a layer of stored procedures and views to access the data, then you can expose the same logical structure by updating a view or stored procedure to account for the physical change without having to touch any code in your business layer. When used appropriately, a layered design can lessen the overall impact of changes to the application.
The business tier And of course, this brings us to the topic of business objects and the Data Access Layer (also known as the DAL), two sub-layers within the business tier. A business object is a component that encapsulates the data and business processing logic for a particular business entity. It is not, however, a persistent storage mechanism. Since business objects cannot store data indefinitely, the business tier relies on the data tier for long term data storage and retrieval.
Thus, your business tier contains logic for retrieving persistent data from the data-tier and placing it into business objects and, conversely, logic that persists data from business objects into the data tier. This is called data access logic.
Three tiered .NET application with sub-tiers
SYSTEM SECURITY
INTRODUCTION The protection of computer based resources that includes hardware, software, data, procedures and people against unauthorized use or natural Disaster is known as System Security. System Security can be divided into four related issues: Security Integrity Privacy Confidentiality SYSTEM SECURITY refers to the technical innovations and procedures applied to the hardware and operation systems to protect against deliberate or accidental damage from a defined threat. DATA SECURITY is the protection of data from loss, disclosure, modification and destruction. SYSTEM INTEGRITY refers to the power functioning of hardware and programs, appropriate physical security and safety against external threats such as eavesdropping and wiretapping. PRIVACY defines the rights of the user or organizations to determine what information they are willing to share with or accept from others and how the organization can be protected against unwelcome, unfair or excessive dissemination of information about it. CONFIDENTIALITY is a special status given to sensitive information in a database to minimize the possible invasion of privacy. It is an attribute of information that characterizes its need for protection. SECURITY SOFTWARE
System security refers to various validations on data in form of checks and controls to avoid the system from failing. It is always important to ensure that only valid data is entered and only valid operations are performed on the system. The system employees two types of checks and controls:
SDLC METHDOLOGIES
The following diagram shows how a spiral model acts like:
FIG:- SPIRAL MODEL
A COMPLETE DATABASE AND TABLES DETAIL WITH PRIMARY AND FOREIGN KEYS, AND PROPER CONSTRAINTS IN THE FIELDS
FUTURE SCOPE AND FURTHER ENHANCEMENT OF THE PROJECT
This Project plays a vital role in the development life cycle (SDLC) and it describes the complete requirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.
BIBLIOGRAPHY
FOR .NET INSTALLATION www.support.mircosoft.com FOR DEPLOYMENT AND PACKING ON SERVER www.developer.com www.15seconds.com FOR SQL www.msdn.microsoft.com FOR ASP.NET Asp.Net 3.5 Unleashed www.msdn.microsoft.com/net/quickstart/aspplus/default.com www.asp.net www.fmexpense.com/quickstart/aspplus/default.com www.asptoday.com www.aspfree.com www.4guysfromrolla.com/index.aspx Software Engineering (Roger’s Pressman
