Welcome to PNB ATM

Submitted by:Date of Issue: Date of Submit:

Authorized Signature:-..

ACKNOWLEDGEMENT

Making an E-Project is always a monumental effort. Making an E-Project a

really takes many dedicated people and it is our great pleasure to acknowledge the contribution of entire group.

Our respected Madam .

did a great job, co-coordinating all aspect of

this complex E-Project a number of other individuals at Institute also provided valuable assistance. We would like them all to know how much we appreciate their efforts.

Suggestions for improvements of this E-Project will be most welcome.

Saharanpur, Date

Table of Contents.
1. Hardware and Software Requirement 2. Customer Requirement Specification 3. Synopsis 4. DFD 5. GUI Standards Document and Interface Design Document. 6. Testing 7. Maintenance

Hardware/ Software Requirements

Hardware
A minimum computer system that will help you access all the tools in the courses is a Pentium 166 or better 512 Megabytes of RAM or better

Software
ASP.NET 3.5 Sql Server 2005

SOFTWARE DEVELOPMENT LIFE CYCLE

FEASIBILITY STUDY

A feasibility study is a preliminary study undertaken to determine and document a projects viability. The results of this study are used to make a decision whether to proceed with the project, or table it. If it indeed leads to a project being approved, it will before the real work of the proposed project starts-be used to ascertain the likelihood of the projects success. It, for example, can decide whether an order processing be carried by a new system more efficiently than the previous one.

Reasons to do a Feasibility Study

Below the reasons to conduct a Feasibility Study: Gives focus to the project and outline alternatives Narrows count of alternative solutions Surfaces new opportunities through the investigative process Identifies reasons not to proceed Provides quality information for decision making Provides documentation that the existing and proposed system was thoroughly investigated

Within a feasibility study, three areas must be reviewed

 Technical Operational Economical Technical Feasibility:

The technical issues usually raised during the feasibility stage of the investigation includes the following Does the necessary technology exist to do what is suggested? Will the proposed system provide adequate management while automating Online Extension Management System of a Company? Can the system be upgraded if developed? Are there technical guarantees of accuracy, reliability, ease of access and data security? Operational Feasibility:

Proposed systems are useful if they can be turned out in the information system that will meet the organizations operating requirements. Some of the important issues raised are to test the operational feasibility of a project includes the following Is there efficient support for computerization of existing manual system? Will the system be used and work properly if it is being developed and implemented? Will there be any resistance from the user that will use the Online Extension Management System?

Economical Feasibility:

A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the developed cost in creating the system is evaluated against the ultimate benefit derived from the new system. Financial benefits must equal or exceed the costs.

SYSTEM ANALYSIS

After the feasibility, the next step is to analyze the problem and understand its context.

Analysis is a detailed study of the various operations performed by the system and their relationship with in and outside the system. This phase serves the purpose of understanding the exact requirements of the customer and to document them properly.

The first activity in this phase is studying the existing system and other is to understand the requirements and domain of the new system.

System Analysis has to ensure that as far as possible all the requirements of the software are elicited and analyzed clearly specified in the document describing the SRS (Software Requirement Specification).Due to this System Analysis phase consists of three basic activities:

1. Problem or Requirement Analysis 2. Requirement Specification 3. Requirement Validation Problem or Requirement Analysis: starts with some general Statement of need or a high level Problem Statement. During Analysis the problem domain and the environment are modeled in an effort to understand the system behavior, constraints on the system, its input and outputs, etc.

Requirement Specification: in which the focus is on clearly specifying the requirements in a document. Issues, such as representation, specifications, languages and tools are addressed during this activity.

Requirement Validation: is that what have been specified in the SRS are indeed all the requirements of the software and making sure that the SRS is of good quality.

DATA FLOW DIAGRAM Extension Management System Context Diagram

User

Admin

Login Request

Login

Login Req

Login Acknowledgement

Acknowledgement Request ATM System EM

ATM Login Database Acknowledgement

Various Snapshot and Coding

using System; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI;

using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.SqlClient;

public partial class _Default : System.Web.UI.Page { SqlConnection con; SqlDataAdapter da; DataTable _dt;

protected void Page_Load(object sender, EventArgs e) { con = new SqlConnection("Data Source=ASTHA-PC;Initial Catalog=ATM;Integrated Security=True;User Instance=False");

} protected void btnReset_Click(object sender, EventArgs e) { txtUsername.Text = string.Empty; txtPassword.Text = string.Empty; } protected void btnSubmit_Click(object sender, EventArgs e) {

if(txtUsername.Text!=string.Empty && txtPassword.Text!=string.Empty) { da = new SqlDataAdapter("Select RoleId from Login where UId=@uname and Password=@pwd ", con); da.SelectCommand.Parameters.Add("@uname", SqlDbType.NChar).Value=txtUsername.Text; da.SelectCommand.Parameters.Add("@pwd", SqlDbType.NChar).Value=txtPassword.Text; _dt = new DataTable(); da.Fill(_dt); object[] obj = _dt.Rows[0].ItemArray; string role = obj[0].ToString(); if (role =="1") { Session["Uid"] = txtUsername.Text; Response.Redirect("~/User/WelcomeScreen.aspx"); } else if (role == "2") { Session["Uid"] = txtUsername.Text; Response.Redirect("~/Admin/WecomeAdmin.aspx"); } else {

} }

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI;

using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Xml.Linq;

public partial class MasterUser : System.Web.UI.MasterPage { protected void Page_Load(object sender, EventArgs e) {

} protected void DepositButton_Click(object sender, ImageClickEventArgs e) { Response.Redirect("~/User/Deposit.aspx"); } protected void WithDrawButton_Click(object sender, ImageClickEventArgs e) { Response.Redirect("~/User/WithDraw.aspx"); } protected void ButtonLogout_Click(object sender, ImageClickEventArgs e) { Session.Abandon(); Response.Redirect("~/Login.aspx"); } protected void ButtonChangePwd_Click(object sender, ImageClickEventArgs e)

{ Response.Redirect("~/User/ChangePwd.aspx"); } }

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI;

using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.SqlClient; using System.Windows.Forms;

public partial class Deposit : System.Web.UI.Page { SqlConnection con; DataTable _dt; SqlDataAdapter _da; int _count = 0; int amount; string dt = ""; SqlCommand cmd; int chk; string Username;

protected void Page_Load(object sender, EventArgs e) { con = new SqlConnection("Data Source=ASTHA-PC;Initial Catalog=ATM;Integrated Security=True;User Instance=False"); txtDate.Text = DateTime.Today.ToString(); txtDate.Enabled = false; Username = Session["Uid"].ToString(); cmd = new SqlCommand("select Balance from Account where UId=@uid", con); cmd.Parameters.Add("@uid", SqlDbType.NChar).Value = Username;

_da = new SqlDataAdapter(cmd); _dt = new DataTable(); _da.Fill(_dt); } protected void btnDeposit_Click(object sender, EventArgs e) { object []obj =_dt.Rows[0].ItemArray; int bal=Convert.ToInt32(obj[0]);

amount=Convert.ToInt32(txtDeposit.Text);

bal = bal + amount; string _date = DateTime.Today.ToShortDateString(); con.Open(); int i=-1; if(txtDeposit.Text!=null && amount>=25000) { if (_count < 6 && DateTime.Today.ToShortDateString()==_date) { try {

string insert = "insert into Account values('" + Username + "','" + amount + "','" + null + "','" + bal + "','" + _date + "')"; cmd = new SqlCommand(insert, con); //cmd.Parameters.Add("@uname", SqlDbType.NChar).Value = Username;

//cmd.Parameters.Add("@dep", SqlDbType.VarChar).Value = txtDeposit.Text; //cmd.Parameters.Add("@date", SqlDbType.DateTime).Value = txtDate.Text; i = cmd.ExecuteNonQuery(); _count++; } catch (Exception ex) {

} else { _count = 0; }

} con.Close(); if (i > 0) { MessageBox.Show("Successfully deposit......");

} } }

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI;

using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.SqlClient; using System.Windows.Forms;

public partial class ChangePwd : System.Web.UI.Page { string Username; SqlConnection con; SqlCommand cmd; int res = 0;

protected void Page_Load(object sender, EventArgs e) { con = new SqlConnection("Data Source=ASTHA-PC;Initial Catalog=ATM;Integrated Security=True;User Instance=False"); } protected void btnClear_Click(object sender, EventArgs e) { txtOldPwd.Text = string.Empty; txtNewPwd.Text = string.Empty; txtConsirmPwd.Text = string.Empty; } protected void btnChange_Click(object sender, EventArgs e)

{ Username = Session["Uid"].ToString(); con.Open(); if(txtNewPwd.Text==txtConsirmPwd.Text) { try { cmd = new SqlCommand("update Login set Password=@Pwd where Uid=@uid", con); cmd.Parameters.Add("@Pwd", SqlDbType.NChar).Value = txtNewPwd.Text; cmd.Parameters.Add("@uid", SqlDbType.NChar).Value = Username;

res = cmd.ExecuteNonQuery(); } catch(Exception ex) {

} if(res>0) { MessageBox.Show("Your Password has been changed now..!!!!!!"); } con.Close();

} }

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq;

using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Xml.Linq;

public partial class Admin_MasterAdmin : System.Web.UI.MasterPage { protected void Page_Load(object sender, EventArgs e) {

} protected void CreateButton_Click(object sender, ImageClickEventArgs e) { Response.Redirect("~/Admin/CreateUser.aspx"); } protected void ChangePwdButton_Click(object sender, ImageClickEventArgs e) { Response.Redirect("~/User/ChangePwd.aspx"); } protected void Logout_Click(object sender, ImageClickEventArgs e) { Session.Abandon();

Response.Redirect("~/Login.aspx"); } protected void WithDrawReport_Click(object sender, EventArgs e) { Response.Redirect("~/Admin/WthDrawReport.aspx"); } }

using using using using using using using using using using using using using

System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Xml.Linq; System.Data.SqlClient;

public partial class Admin_DepositReport : System.Web.UI.Page { SqlConnection con; DataTable _dt; SqlDataAdapter _da; SqlCommand cmd;

protected void Page_Load(object sender, EventArgs e) { con = new SqlConnection("Data Source=ASTHA-PC;Initial Catalog=ATM;Integrated Security=True;User Instance=False"); } protected void btnShow_Click(object sender, EventArgs e) { string Username = Session["Uid"].ToString(); cmd = new SqlCommand("select top 5 Deposit from Account where UId='@uid' order by Date desc", con); cmd.Parameters.Add("@uid", SqlDbType.NChar).Value = Username; _da = new SqlDataAdapter(cmd); _dt = new DataTable(); _da.Fill(_dt); GridView1.DataSource = _dt; GridView1.DataBind(); GridView1.Visible = true; } protected void CalDeposit_SelectionChanged(object sender, EventArgs e) { txtDate.Text = CalDeposit.SelectedDate.ToShortDateString(); } }

TESTING AND DEBUGGING

Introduction: Software testing is a critical element of software quality assurance and represents ultimate review of specification, design and coding. In fact, testing is the one step

in the software engineering process that could be viewed as destructive rather than constructive. Testing a program consists of providing the program with a set of test inputs (or test cases) and observing if the program behaves as expected.

If the program fails to behave as expected, then the conditions under which a failure occurs are noted for debugging and correction. The following are some commonly used terms associated with testing

A failure is a manifestation of an error (or defect or bug). But, the mere presence of an error may not necessarily lead to a failure.

A fault is an incorrect intermediate state that may have been entered during program execution, e.g. a variable value is different from what it should be. A fault may or may not lead to a failure.

A test case is the triplet [I, S, O], where I is the data input to the system, S is the state of the system at which the data is input, and O is the expected output of the system.

A test suit is the set of all test cases with which a given software product is to be tested.

Unit Testing:

Unit testing focuses verification effort on the smallest unit of the software design, the module.

1. White box testing: This type of testing ensures that

All independent paths have been exercised at least once. All logical decision has been exercised on their true and false side. All loops are executed at their boundaries and within their operational bounds. To follow the concept of white box testing we have tested we have tested each form we have created independently to verify that

Data flow is correct. All condition are exercised to check their validity. All loops are executed on their boundaries.

Integration Testing:

The objective of integration testing is to ensure that components link and work together, and the focus is on the effectiveness of functional interactions and

compatibility at the interfaces of the components. Integration testing is carried out based on the control flow of units, and their dependency.

1. Integration Approach: We have used combined approach for integrating different part of software. The Top-Down strategy has been used for upper level modules and Bottom-Up strategy has been used for sub-ordinate levels.

Each time a thoroughly tested module was added to the system, the Regression Testing was performed to confirm that added module is not adding any unwanted changes.

New Test Cases Software under Testing Output

Existing Test Cases Comparator

Result of Testing

Regression Testing

Validation Testing:

Validation Testing succeeds when software function in a manner that can be reasonably expected by the customer software validation is achieved through a series of Black-box testing that demonstrate conformity with the requirements.

1. Black Box Testing:

focuses on the functional requirements of the

software. Black-box Testing helps to find errors as Incorrect or missing functions Interface Errors Errors in the data structures Performance Errors Initialization and termination Errors System Testing:

System Testing is actually a series of different tests whose primary purpose is to fully exercise the computer-based system as a whole.

The aim of the System testing is to ensure that the system as a whole gives intended result.

IMPLEMENTATION A crucial phase in project development is the successful implementation of the new system. Implementation means the process of converting a new or a revised system design in to an operational one.

Implementation involves creating computer compatible files, training the operating staff.

Once a proposed system has been designed it must be implemented. It involves the Hardware and Software acquisition, Software development, testing of the programmed and procedure and a variety of the installation activities.

It also involves the education and training of end users and specialists who will operate a system. Though implementation can be difficult in process it is vital in ensuring the success of any newly developed system.

MAINTENANCE

Software maintenance traditionally denotes the process of modifying a software product after it has been delivered to the customer. Maintenance is inevitable for almost any kind of product. Most products need maintenance due to wear and tear caused by use. On the other hand, software products do not need maintenance of this count, but need maintenance on account of the following three main reasons:

Corrective Maintenance:

Corrective maintenance of a software product may be necessary either to rectify some bugs observed while the system is in user or to enhance the performance of system.

Adaptive Maintenance:

A software product might need maintenance to support the new features that the users want or to change different functionalities of the systems, or when they need the product to interface with new hardware or software.

Perfective Maintenance:

A software product needs maintenance to support the new features that the users want or to change different functionalities of the system according to customer demands.

EMS Maintenance:

EMS is developed in .NET, which is platform dependent so there is need of adaptive maintenance. EMS also needs Corrective and perfective maintenance, because it is a new system and has very high scope of extension.

Conclusion:

EMS is a secured system, as all measures are taken into account so that Unauthorised person could not access the system.

BIBLIOGRAPHY

Websites:
http://www.homeandlearn.co.uk http://www.msdn.microsoft.com http://www.google.com (For various search) http://www.spidernet.com