Description
A fixed deposit (FD) is a financial instrument provided by Indian banks which provides investors with a higher rate of interest than a regular savings account, until the given maturity date . It may or may not require the creation of a separate account. It is known as a term deposit or time deposit in Canada, Australia, New Zealand, and the US, and as a bond in the United Kingdom.
Fixed Deposit Management System
This project is focused on the fixed deposit management system with the environments as Visual Basic as Front end and Oracle as back end. This project has four modules with their details as said below.
Description :
Fixed Deposit Management System takes care of part of financial activities of the Company such as Deposits Received, Loan Issued and Repayment, Maturity Repayments, Generation of interest warrants, Deposit Receipts.
• •
Deposits Master Module-Tracks the Deposits received from the customer. Payments Master Module-Maturity Repayment, to the Customer against their Deposits and interest payments from the Customer against the Loans are manipulated.
•
Loans Master Module-The provision of Loans sanctioned based on the deposits are maintained.
•
Depositors ID, Loan Number, Transaction Date, and Transaction Number are generated automatically through these modules. Reports related to outstanding Loans, Interest Details, Terminated Deposits, Tax Statements are generated through the System.
CONTENTS
CHAPTER 1. 2. 3. INTRODUCTION
INDEX SOFTWARE PROJECT PLAN SOFTWARE REQUIREMENTS SPECIFICATION 3.1 Functional Requirements 3.2 Performance Requirements 3.3 interface Requirements 3.4 Operational Requirements 3.5 Resource Requirements 3.6 Security Requirements 3.7 Design Requirements 3.8 Quality and Reliability Requirements
PAGE NO 1 2 4-10
4.
SYSTEM ANALYSIS 4.1 Data Flow Diagram 4.2 Entity Relationship Diagram
11-19
5.
SYSTEM DESIGN 5.1 Input Design 5.2 Table and Database Design 5.3 Output Design 5.4 Front End Design 5.5 Back End Design
20-44
6. 7. 8. 9.
TESTING CONCLUSIONS SCREEN SHOTS & REPORTS BIBLIOGRAPHY
45 47 48 67
CHAPTER-1 INTRODUCTION
This project is designed and developed for Brigade Corporation Ltd. formerly as Brigade Solutions – Chennai to take care of part of financial activities of the Company such as Deposits Received, Loan Issued, Repayment, Maturity Repayments, and Generation of interest warrants and Deposit Receipts. This company wants to maintain all the transactions in the database for accounting and future reference.
The database system must provide for the safety of the information stored, despite system crashes or attempts at unauthorized access if data are to be shared among several users, the system must avoid possible anomalous results.
In “Fixed Deposit Management System” maintaining the details of various customers, employees are kept in a database and also can be retrieved easily when the admin access it.
The difficulty in the present system is everything is maintained through papers. So maintaining records for a long time and handling large volumes data is impossible. This project is developed using Visual Basic Language under windows platform and Oracle.
CHAPTER 2 SOFTWARE PROJECT PLAN The project contains five modules Customer Master Module Deposits Master Module Payments Master Module Loans Master Module Reports
? ? ? ? ?
Customer Master Module To do transactions with the company the details of the customer should be maintained. This module helps to add, modify and remove the customer details.
Deposits Master Module This module helps to Track the Deposits received from the customer. With this module the end user can add, modify, remove the customer details and deposit schemes.
Payments Master Module With the help of this module, the end user can do the process like Maturity Repayment to the Customer against their Deposits and interest payments from the Customer against the Loans.
Loans Master Module This module provides the facilities to maintain loan sanctions based on the deposits of the customers.
Reports
Reports related to outstanding Loans, Interest Details, Terminated Deposits, Tax Statements are generated through the System.
The end user can add, modify or remove transaction entries based on their rights. The administrator is a user giving rights to the end user is having the capability of changing passwords of other users.
CHAPTER 3 SOFTWARE REQUIRMENTS SPECIFICATION 3.1 Functional Requirements: The main aim in this stage is to assess what kind of a system would be suitable for a problem and how to build it. The requirements of this system can be defined by going through the existing system and its problems. They discussing (speak) about the new system to be built and their expectations from it. involved would be The steps
Problem Recognition The difficulty in the present system is everything is maintained through papers. So maintaining records for a long time and handling large volumes data is impossible. Evaluation and Synthesis The system has to be designed only after complete evaluation of the existing one, upon which we can see that a lot depends on the medium of communication. In the proposed system the information related to the
customers, deposits and reports are very quickly and effectively handled. So this has to be used such that there is no waste of time.
Specification The specifications from the deposits, loan and customers had be to taken. This division provided the required format for the Fixed Deposit Management System. The appearance of forms, and their field names, the different screens are desired, the stages of this database etc., were all given. The system has been build following all the specifications.
3.2 Performance requirements All the requirements relating to the performance characteristics of the system must be clearly specified. There are two types of performance requirements – static and dynamic.
Static Requirements are those that do not impose constraint on the execution characteristics of the system. These include requirements like the number of terminals to be supported, and number simultaneous users to be supported, number of files, and their sizes that the system has to process. These are also called capacity of the system. Dynamic requirements specify constraints on
execution behavior of the system. These typically include response time and throughput constraints on the system.
The processing speed, respective resource consumption throughput and efficiency measure performance. For achieving good performance few
requirements like reducing code, less use of controls, minimum involvement of
repeated data etc., are to be followed. Each real-time system, software what provides required function but does not conform to performance of software requirements is acceptable. These requirements are used to test run time performance of software with the context of an integrated system.
3.3 Interface requirements Software Interfaces These interface requirements should specify the interface with other. Software which the system will use or which will use the system, this includes the interface with the operating system and other applications. The message content and format of each interface should be given.
Hardware interface Hardware interface is very important to the documentation. If the software is executive on existing hardware or on the pre-determined hardware, all the characteristics of the hardware, including memory restrictions, should be specified. In addition, the current use and load characteristics of the hardware should be given.
3.4 operation requirements
Operational study is an important phase in the phase in the software development process. It enables the developer to have an assessment of the
product being developed. It refers to the feasibility study of the product in terms of outcomes of the product, operational use and technical support required for implementing it.
Operational study should be performed on the basis of various criteria and parameters. The various operational studies are:
? Economic ? Operational ? Technical 1. Economic: It refers to the benefits or outcomes we are deriving from the product as compared to the total cost we are spending for developing the product. If the benefits are more or less the same as the older system, then it is not feasible to develop the product.
2. Operational: It refers to the feasibility of the product to be operational. Some products may work very well at design and implementation but may fall in the real time environment. It includes the study of additional human resource required and their technical expertise.
3. Technical: It refers to whether the software that is available in the market fully supports the present application. It studies the pros and cons of using particular software for the development and its feasibility. It also studies the additional training needed to be given to the people to make the application work.
3.5 Resource Requirements Hardware Specification Processor Processor Speed RAM Hard disk Key board Software Specification Database Front end Editor : : : Oracle 10 G Visual Basic, Microsoft Office : : : : : Intel Core 2 Duo based system 2.66 Ghz 2 GB 360 GB 104 keys
3.6 Security Requirements Software requirements specification plays an important role in the creating quality software solutions. Specification is basically a representation process.
Requirements are represented in a manner that ultimately leads to successful software implementation.
Requirements may be specified in a variety of ways. However there are some guidelines worth following:• • • • Representation format and content should be relevant to the problem Information contained within the specification should be nested Diagrams and other notational forms should be restricted in number and consistent in use. Representations should be revisable.
3.7 Design Requirements Software design is a process through which the requirements are translated into a representation of software. One of the software requirements have been
analyzed and specified, the s/w design of the system is in modular form i.e., the s/w is logically partitioned into components that perform specific functions and sub functions. The design phase leads to modules that exhibit independent
function characteristics. It even leads to interfaces that reduce the complexity of the connections between modules and with the external environment. The design phase is of main importance because in this activity, decisions ultimately affect the success of s/w implementation and maintenance.
3.8 Quality and reliability requirements The software requirements specification is produced at the culmination of the analysis task. The function and performance allocated to the software as a part of system engineering are refined by establishing a complete information description, a detailed functional and behavioral description, and indication of performance requirements and design constraints, appropriate validation criteria and other data pertinent to requirements.
CHAPTER 4 SYSTEM ANALYSIS 4.1 Data Flow Diagram
Master Customer Master
Transaction
Reports
Deposit Master
Payment Master
Loan Master
Customer Master
Add Customer
Modify Customer
Delete Customer
Loan Master
Add Loan Details
Modify Loan Details
Delete Loan Details
Deposit Master
Add Deposit Details
Modify Deposit Details
Delete Deposit Details
Payment Master
Add Payment Details
Modify Payment Details
Delete Payment Details
4.2 Entity Relationship Diagram
Depositors_ID
Depositors _Address2
Depositors _Firstnam e Depositors _lastname Depositors _lastname
Depositors _Address3
Depositors _Address4
Customer
Pincode
Contact_n o
Dateofbirth
Deposit_Scheme_Id
Maturity_days
Deposit_scheme _Name
Validfrom_sche me
Rate_of_Intere st
Validto_scheme
Deposits
Depositors_ID
Repayment _amount
Deposit_S cheme_Id
Interestrec eived_Dat e
Repayment_date
Interestrece ived_amou nt
Payment
Deposit_ amount
Deposit_date
Transaction _id
Depositors_ID
Transaction_N umber
Loan_Number
Loan_amount
Transaction_Date
Loan
CHAPTER 6 SYSTEM DESIGN 5.1 Input Design Input design is the process of converting user-originated information to computer-based format. The goal of designing input data is to make data entry easier and error free as possible. An input format should be easy to understand.
In this application inputs are nothing but the information about different entities. Every entity has different fields i.e., customer master have some properties like Customer_id, Customer_firstname and so on. By taking these inputs from the user, we do the process to decide whether to save the messages, send the content to the destination or pacing any restrictions. The output design relays on input, which is used to the output. Hence input design needs some special attention.
5.2 Table and Database Design
TABLE NAME: Customer_Master, it contains all details about administrators. The following table explains all the fields.
Field Name Depositors_ID Depositors _Firstname Depositors _lastname Depositors _lastname Depositors _Address2 Depositors _Address3 Depositors _Address4 Pincode Contact_no Dateofbirth
Data Type
VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2
Date
Size 14 25 25 25 25 25 25 6 10 8
TABLE NAME: Deposits_Master, it contains all details about administrators. The following table explains all the fields.
Field Name Deposit_Scheme_Id Deposit_scheme_Name Rate_of_Interest Maturity_days Validfrom_scheme Validto_scheme
Data Type
VARCHAR2 VARCHAR2 Number Number Date Date
Size 14 25 5,2 5 8 8
TABLE NAME: Payments_Master, it contains all details about administrators. The following table explains all the fields.
Field Name Depositors _id Deposit_Scheme_Id Repayment_date Repayment_amount Interestreceived_Date Interestreceived_amount Deposit_amount Deposit_date Transaction_id
Data Type VARCHAR2 VARCHAR2 Date Number Date Number Number Number VARCHAR2
Size 14 14 8 8,2 8 8,2 8,2 8,2 14
TABLE NAME: Loan_Master, it contains all details about administrators. The following table explains all the fields.
Field Name Depositors_ID Loan_Number Transaction_Date Transaction_Number Loan_amount
Data Type
VARCHAR2 VARCHAR2
Date
VARCHAR2 Number
Size 14 14 8 14 8,2
5.3 Output Design
Output reflects image of the purpose. The output design involves designing forms layout, making lists, making well designed reports etc., and reports are main outputs of the proposed system. Here the outputs are: list of customers, list of outstanding loans and so on.
System Design System design is the process of applying various techniques and principles for the purpose of definition a system in sufficient details to permit its physical realization.
Software design is the kernel of the software engineering process. Once the software requirements have been analyzed and specified, the design is the first activity. The flow of information during this process is as follows.
The Process Software design is the process through which requirements are translated into a representation of software.
5.4 Front End Design
Visual Studio.Net
Visual Studio .NET is a complete set of development tools for building
? ASP Web applications ? XML Web services ? desktop applications ? mobile applications
Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same integrated development environment (IDE), which allows them to share tools and facilitates in the creation of mixed-language solutions. Visual Basic Visual Basic has been updated to include many new and improved language features that make it a powerful object-oriented programming language. These features include inheritance, interfaces, and overloading, among others. Visual Basic also now supports structured exception handling, and custom attributes. In addition, Visual Basic supports multithreading. Multithreading is the ability to assign individual tasks to separate processing threads.
C# Visual C#, pronounced C sharp, is a new object-oriented programming language that is an evolution of C and C++, providing a simple and type-safe language for developing applications. C++ Managed Extensions for C++ and attributed programming are just some of the enhancements made to the C++ language. Managed Extensions simplify the task of migrating existing C++ applications to the new .NET Framework. Attributes, like C++ keywords, are used in your source files and interpreted by the compiler. Attributes are designed to provide a quick and efficient method to simplify COM programming with Visual C++. JScript JScript has been updated to be a class-based, object-oriented scripting language that maintains full backwards compatibility with previous versions of JScript. JScript now provides class-based objects, typed variables, true compiled code, and cross-language support through Common Language Specification (CLS) compliance. The primary role of JScript is development of Web sites with ASP.NET and customization of applications with Script for the .NET Framework.
Types of forms used in .Net Web Forms Web Forms are an ASP.NET technology that you use to create programmable Web pages. Web Forms render themselves as browser-compatible HTML and script, which allows any browser on any platform to view the pages. Using Web Forms, you create Web pages by dragging and dropping controls onto the designer and then adding code, similar to the way that you create Visual Basic forms Windows Forms Windows Forms is the new platform for Microsoft Windows application development, based on the .NET Framework. This framework provides a clear, objectoriented, extensible set of classes that enables you to develop rich Windows applications. Additionally, Windows Forms can act as the local user interface in a multitier distributed solution. The .NET Framework Overview The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:
•
To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.
•
To provide a code-execution environment that minimizes software deployment and versioning conflicts.
•
To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party.
•
To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.
•
To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.
•
To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.
The .NET Framework is a multi-language environment for building, deploying, and running XML Web services and applications.
? Common Language Runtime Despite its name, the runtime actually has a role in both a component's runtime and development time experiences. While the component is running, the runtime is responsible for managing memory allocation, starting up and stopping threads and processes, and enforcing security policy, as well as satisfying any dependencies that the component might have on other components. At development time, the runtime's role changes slightly; because it automates so much (for example, memory management), the runtime makes the developer's experience very simple, especially when compared to COM as it is today. In particular, features such as reflection dramatically reduce the amount of code a developer must write in order to turn business logic into a reusable component.
? Unified programming classes The framework provides developers with a unified, object-oriented, hierarchical, and extensible set of class libraries (APIs). Currently, C++ developers use the Microsoft Foundation Classes and Java developers use the Windows Foundation Classes. The framework unifies these disparate models and gives Visual Basic and JScript programmer’s access to class libraries as well. By creating a common set of APIs across all programming languages, the common language runtime enables cross-language inheritance, error handling, and debugging. All programming languages, from JScript to C++, have similar access to the framework and developers are free to choose the language that they want to use.
? ASP.NET ASP.NET builds on the programming classes of the .NET Framework, providing a Web application model with a set of controls and infrastructure that make it simple to build ASP Web applications. ASP.NET includes a set of controls that encapsulate common HTML user interface elements, such as text boxes and drop-down menus. These controls run on the Web server, however, and push their user interface as HTML to the browser. On the server, the controls expose an object-oriented programming model that brings the richness of object-oriented programming to the Web developer. ASP.NET also provides infrastructure services, such as session state management and process recycling that further reduce the amount of code a developer must write and increase application reliability. In addition, ASP.NET uses these same concepts to enable developers to deliver software as a service.
Visual Basic.Net New in Visual Basic Web Development: Visual Basic and C# include support for Web Forms and XML Web services. Web Forms allow you to easily and quickly create the browserbased interface for ASP.NET Web applications. XML Web services allow you to package a Visual Basic or C# method and make it accessible on the Web. New in Data: ADO.NET provides scalable, high-performance data access for all Visual Studio Applications based on the .NET Framework. You can access data directly in the data source or create an in-memory cache — a dataset — for working with disconnected data. You can also work directly with XML as relational data or by creating and editing XML files directly. Windows Forms and Controls: You can use Windows Forms and controls to create the presentation layer of a distributed application. Windows Forms provides a clear, object-oriented, extensible set of classes that enable you to develop rich Windows applications. New in Projects: You can use the Project templates in this version to easily create various types of Windows and ASP.NET Web applications and controls. Project templates set necessary references for you, import namespaces, and add default items to your projects.
Components and Component Authoring: You can use nonvisual components and associated features to incorporate resources such as message queues, event logs, and performance counters into your applications. This version also offers RAD support for component creation via the Component Designer and framework classes that help you create controls and components.
New in Debugging: You can now debug projects that are part of the same solution but written in different languages, perform remote debugging, and implement trace functionality throughout your code to retrieve finely tuned output.
Extensibility and Automation: Visual Studio .NET includes a programmable object model that provides access to the underlying components and events of the integrated development environment (IDE). This model allows you to extend the functionality of the IDE, automate repetitive tasks, and integrate the IDE with other applications.
(ActiveX Data Objects)ADO. Net
ADO.NET is an evolutionary improvement to Microsoft ActiveX Data Objects (ADO). It represents a standards-based programming model that facilitates the development of distributed applications, especially Web applications.
Features
? Access Data Sources with High-Performance Data Components
ADO.NET provides high-performance .NET data providers for direct access to databases and other data sources. Data providers give you precise control over SQL commands and stored procedures that can return data or scalar values or perform other database operations. Data reader objects provide an extremely fast way to return readonly data from a data source.
? Work with Disconnected Data To make most efficient use of database and server resources, you can create datasets that act as a relational cache for data drawn from a data source. (A data source is typically a database, but can also be XML or any source for which a .NET data provider is available.) You can define data adapters that fill the dataset and propagate dataset changes back to the data source using stored procedures or SQL statements.
? Create Datasets with Strongly Typed Access With ADO.NET you can create a dataset based on an XML schema, producing a typed class in which tables and columns become first-class objects in the object model. Typed access makes code easier to read, is less error prone, and is fully supported by IntelliSense in the Visual Studio Code Editor.
? Exchange Data as XML with Other Applications You can serialize data into and out of XML streams that can be exchanged with other XML-enabled applications or components by using either the built-in features of datasets or XML-specific methods. ADO.NET can easily create XML Web services with methods that return datasets as XML.
? Use Wizards for Configuring Data Access Wizards can be used to create and configure data adapters and connections. The Data Form Wizard helps you create a form that is bound to a dataset, creating type-appropriate data-bound controls. The Data Form Wizard can create simple forms bound to a single table or master-detail forms bound to related tables, and can display data one record at a time or in a data-bound grid.
Debugging Visual Studio .NET provides a single integrated debugger for all Visual Studio languages, including Visual Basic and C#. A new, unified interface combines features of the Visual C++ and Visual Basic 6.0 debuggers, as well as many new features.
? Cross-Language Debugging Using the integrated debugger, you can debug projects that are part of the same solution but are written in different languages. For example, you can debug a solution that contains a project consisting of a Visual Basic or Visual C# user interface application and a Visual C++ server application, and you can step back and forth between these projects, for example from Managed Extensions for C++ to Visual Basic and back to Managed Extensions for C++.
? Attaching to a Running Program You can attach the debugger to a program that is already running and debug the program. Attaching to a running program works the same way whether the program is
running on a host machine or a remote machine. The program does not need to be launched in the Visual Studio .NET integrated development environment (IDE).
? Remote Debugging You can attach to and debug a process that is running on a different computer from the one on which you are running Visual Studio. For example, if you are debugging a Windows Forms client application and an XML Web service it uses, you can run Visual Studio on the client and then attach to the server that is providing the XML Web service. You typically perform this kind of debugging for Web Forms projects or ASP.NET Web Service projects.
? Debugging Multithreaded Applications New for Visual Basic users is the ability to write and debug multithreaded applications. The Threads window can be used to view the threads that are running and to switch context.
? Debugging Multiple Programs You can debug multiple programs by attaching to running programs or by launching multiple programs from the Visual Studio IDE.
? Debugging ASP.NET Web Applications Configuring debugging for ASP.NET Web applications has been significantly improved. In most cases you can simply choose Start from the Debug menu and the debugger will automatically attach to the ASP.NET worker process for debugging Web
Forms, even if the ASP.NET worker process is running on a different server. Security configuration has been made easier by the addition of a debugger users group.
? .NET Framework Classes for Debugging and Code Tracing You can include instrumentation code in your Microsoft .NET application. Several .NET Framework classes are available for use both in debugging and in instrumenting your code.
Visual C++.NET Microsoft Visual C++ is the most productive C++ tool for creating the highest performance applications for Windows and the World Wide Web. Nearly all world-class software, ranging from the leading Web browsers to mission-critical corporate applications, is built using the Microsoft Visual C++ development system. Visual C+ + .NET brings a new level of productivity to C++, without compromising flexibility, performance, or control. New in c++.Net Managed Code and Targeting the .NET Framework
Provides links to Managed Extensions for C++ and Visual C# documentation.
Attributed Programming
Attributes are designed to provide an efficient and quick method to simplify COM programming in Visual C++. Attributes, like C++ keywords, are used in your source files and interpreted by the compiler. Attributes can modify the behavior of your existing code and even insert additional framework code to accomplish basic tasks, such as implementing an ActiveX control, creating a class factory, or formatting a database command. You can apply attributes to nearly any C++ object, such as classes, data members, and member functions, or you can insert attributes into your source code as stand-alone statements.
C++ Compiler, Linker, and C++ Language
Provides links and updated information about the compiler, linker, build tools, and C++ language features in Visual C++ .NET.
Libraries Provides links to new content in the Visual C++ libraries, including the Active Template Library (ATL), ATL Server, C Run-Time Library, Microsoft Foundation Class Library, OLE DB Templates, Shared Classes, and the Standard C++ Library.
5.5 Back End Design JDBC, accessing the database through applets and JDBC.API via an intermediate server resulted to new type of database model which is different from the client-server model. There are single tires, two tire and multi tire architectures are available.
Single Tier In a single tier the server and client are the same in the sense that a client program that needs information and the sour of this type of architecture is also possible in java, in case flat files are used to store the data. However this is useful only in case of small applications. The advantage with this type is the simplicity and portability.
Server and Client
Database Two Tier (Client – Server) In two tier architecture the database resides in one machine on the network. In this type of architecture a database management takes control of the database and provides
access to clients in a network.
This software bundle is also called as the server.
Software in different machines, requesting for information are called as the clients.
Server
Client Client
Database
Three Tier and N-Tier In the three-tier architecture, any number of servers can access the database that resides on server. Which in turn serve clients in a network. For example, you want to access the database using java applets, the applet running in some other machine, can send request to the server where it is down loaded. For this reason we will need to have a intermediate server which will accepts the request from applets and them to the actual database server. This intermediate server acts as a two-way communication channel also. This is the information or data from the database is passed on to the applet that is requesting it. This can be extended to make n tiers of servers, each server carrying to specific type of request from clients, however in practice only 3 tiers architecture is popular.
ORACLE
ORALCE is a relational database management system, which organizes data in the form or tables. Oracle is one of many database servers based on RDBMS model, which mangers a seer of data that attends three specific things data structures, data integrity and data manipulation. With oracle cooperative server technology we can realize the benefits of open, relational system for all the applications. Oracle makes efficient use of all systems resources, on all hardware architecture; to deliver unmatched performance, price performance and scalability. Any DBMS to be called as RDBMS has to satisfy DR. E.F. Codd’s rules.
DISTINCT FEATURES OF ORACLE • ORACLE IS PORTABLE
The oracle RDBMS is available on wide range of platforms ranging from PCs to super computers and as multi-user loadable module for Novel NetWare, if you develop application on system you can run the same application on other systems without any modifications.
•
ORACLE IS COMPATIBLE Oracle commands can be used for communicating with IBM DB2 main frame
RDBMS that is different from Oracle, which is Oracle compatible with DB2. Oracle RDBMS is a high performance fault tolerant DBMS, which is specially designed for online transaction processing and for handling large database applications.
•
MULTITHREADED SERVER ARCHITECTURE adaptable multithreaded server architecture delivers scalable high
Oracle
performance for very large number of users on all hardware architecture including symmetric multiprocessors (sumps) and loosely couples multiprocessors.
Performance is achieved by eliminating CPU, I/O, memory and operating system
bottlenecks and by optimizing the Oracle DBMS server code to eliminate all internal bottlenecks.
FEATURES OF ORACLE Most popular RDBMS in the market because of its ease of use • • • • • • Client/server architecture Data independence Ensuring data integrity and data security Managing data concurrency Parallel processing support for speed up data entry and online transaction processing used for applications DB procedure functions and packages.
Dr. E. F. CODD’s Rules These rules are used for valuating a product to be called as relational database management systems. Out of 12 rules, a RDBMS product should satisfy at least 8 rules must be satisfied.
RULE 0: FOUNDATION RULE: For any system that is to be advertised as or claimed to be relational DBMS. That system should manage database with in self, with out using an external language.
RULE 1: FOUNDATION RULE: All information in relational database is represented at logical level in only one way as values in tables.
RULE 2: GUARANTEED ACCESS: Each and every data in a relational database is guaranteed to be logically accessibility by using to a combination of table name, primary key value and column name.
RULE 3: SYSTEMATIC TREATMENT OF NULL VALUES Null values are supported for representing missing information and inapplicable information. They must be handled in systematic way, independent of data types.
RULE 4: DYNAMIC ONLINE CATALOG VASED RELATION MODEL The database description is represented at the logical level in the same way as ordinary data so that authorized users can apply the same relational language to its interrogation as they do to the regular data.
RULE 5: COMPREHENSIVE DATA SUB LANGUAGE A relational system may support several languages and various models of terminal use. However there must be one language whose statement can express all of the following: Data definition, view definitions, data manipulations, integrity, constraints,
authorization and transaction boundaries.
RULE 6: VIEW UPDATING Any view that is theoretically updatable if changes can be made to the tables that effect the desired changes in the view.
RULE 7: HIGH LEVEL UPDATE, INSERT and DELETE
The capability of handling a base relational or derived relational as a single operand applies not only retrieval of data also to its insertion, updating, and deletion.
RULE 8: PHYSICAL DATA INDEPENDENCE Application program and terminal activities remain physically unimpaired whenever any changes are made in either storage representation or access method.
RULE 9: LOGICAL DATA INDEPENDANCE Application program and terminal activities remain logically unimpaired whenever any changes are made in either storage representation or access method.
RULE 10: INTEGRITY INDEPENDENCE Integrity constraints specific to particular database must be definable on the relational data stored in the catalog, not in application program.
RULE 11: DISTRIBUTED INDEPENDENCE Weather or not a system support data base distribution, it must have a data sublanguage that can support distributed database without changing the application program.
RULE 12: NON SUB-VERSION If a relational system has low level language, that low language cannot use to subversion or by pass the integrity rules and constraints expressed in the higher level relation language.
ORACLE SUPPORTS THE FOLLOWING CODD’S RLES: 1. Information Rule
2. Guaranteed access – yes 3. Systematic treatment of null values - yes 4. Dynamic on line catalog-based relation model – yes 5. Comprehensive data sub language – yes 6. View updating – PARTIAL 7. High – level update, insert and Delete – Yes 8. Physical data independence – PARTIAL 9. Logical data independence – PARTIAL 10. Integrity Independence – PARTIAL 11. Distributed independences – Yes 12. Non – subversion – yes
TESTING
6.1 Unit Testing Unit testing focuses on verification effort on the smallest unit of software design that is called as module. Using procedural design description as a guide, important control paths are tested to uncover errors within the boundaries of the module. The unit test is normally called as white box testing and the testing can be conducted in parallel for multiple modules.
6.2 integration testing Integration testing is a systematic technique for constructing the program structure while conducting test to uncover errors associated with the interfacing. The objective is to take unit tested methods and build a program structure that has been dictated by design.
Top-down integration: Top down integrations an incremental approach to construction of program structure. Modules are integrated by moving downward through the control hierarchy, beginning with the main control program. Modules subordinate to the main program are incorporated in the structure either in the breath-first or depth-first manner.
Bottom-up integration: This method as the name suggests, begins construction and testing with atomic modules ie., modules at the lowest leveling the program structure. Because the modules are integrated in the bottom up manner the processing required for the modules subordinate to a given level is always available and the need for stubs is eliminated.
6.3 Validation Testing At the end of integration testing software ids completely assembled as a package. Validation testing is the next stage which can be defined as successful when the software functions in the manner reasonable expected by the customer. Reasonable expectations are those defined in the software requirements specifications. Information contained in those sections form a basis for validation testing approach.
6.4 Acceptance Testing A strategy for software testing integrates software test cases into a series of well planned steps that result in the successful construction of software. Software testing is a broader topic for what is referred to as Verification and Validation. Verification refers to the set of activities that ensure that the software correctly implements as specific function validation refers the set of activities that ensure that the software that has been built is traceable to customer’s requirements.
CHAPTER 7 CONCLUSION
This project is designed and developed for Brigade Corporation Ltd. formerly as Brigade Solutions – Chennai to take care of part of financial activities of the Company such as Deposits Received, Loan Issued, Repayment, Maturity Repayments, and Generation of interest warrants and Deposit Receipts. This company wants to maintain all the transactions in the database for accounting and future reference.
The database system must provide for the safety of the information stored, despite system crashes or attempts at unauthorized access. If data are to be shared among several users, the system must avoid possible anomalous results.
SCREEN SHOTS & REPORTS
doc_215273156.doc
A fixed deposit (FD) is a financial instrument provided by Indian banks which provides investors with a higher rate of interest than a regular savings account, until the given maturity date . It may or may not require the creation of a separate account. It is known as a term deposit or time deposit in Canada, Australia, New Zealand, and the US, and as a bond in the United Kingdom.
Fixed Deposit Management System
This project is focused on the fixed deposit management system with the environments as Visual Basic as Front end and Oracle as back end. This project has four modules with their details as said below.
Description :
Fixed Deposit Management System takes care of part of financial activities of the Company such as Deposits Received, Loan Issued and Repayment, Maturity Repayments, Generation of interest warrants, Deposit Receipts.
• •
Deposits Master Module-Tracks the Deposits received from the customer. Payments Master Module-Maturity Repayment, to the Customer against their Deposits and interest payments from the Customer against the Loans are manipulated.
•
Loans Master Module-The provision of Loans sanctioned based on the deposits are maintained.
•
Depositors ID, Loan Number, Transaction Date, and Transaction Number are generated automatically through these modules. Reports related to outstanding Loans, Interest Details, Terminated Deposits, Tax Statements are generated through the System.
CONTENTS
CHAPTER 1. 2. 3. INTRODUCTION
INDEX SOFTWARE PROJECT PLAN SOFTWARE REQUIREMENTS SPECIFICATION 3.1 Functional Requirements 3.2 Performance Requirements 3.3 interface Requirements 3.4 Operational Requirements 3.5 Resource Requirements 3.6 Security Requirements 3.7 Design Requirements 3.8 Quality and Reliability Requirements
PAGE NO 1 2 4-10
4.
SYSTEM ANALYSIS 4.1 Data Flow Diagram 4.2 Entity Relationship Diagram
11-19
5.
SYSTEM DESIGN 5.1 Input Design 5.2 Table and Database Design 5.3 Output Design 5.4 Front End Design 5.5 Back End Design
20-44
6. 7. 8. 9.
TESTING CONCLUSIONS SCREEN SHOTS & REPORTS BIBLIOGRAPHY
45 47 48 67
CHAPTER-1 INTRODUCTION
This project is designed and developed for Brigade Corporation Ltd. formerly as Brigade Solutions – Chennai to take care of part of financial activities of the Company such as Deposits Received, Loan Issued, Repayment, Maturity Repayments, and Generation of interest warrants and Deposit Receipts. This company wants to maintain all the transactions in the database for accounting and future reference.
The database system must provide for the safety of the information stored, despite system crashes or attempts at unauthorized access if data are to be shared among several users, the system must avoid possible anomalous results.
In “Fixed Deposit Management System” maintaining the details of various customers, employees are kept in a database and also can be retrieved easily when the admin access it.
The difficulty in the present system is everything is maintained through papers. So maintaining records for a long time and handling large volumes data is impossible. This project is developed using Visual Basic Language under windows platform and Oracle.
CHAPTER 2 SOFTWARE PROJECT PLAN The project contains five modules Customer Master Module Deposits Master Module Payments Master Module Loans Master Module Reports
? ? ? ? ?
Customer Master Module To do transactions with the company the details of the customer should be maintained. This module helps to add, modify and remove the customer details.
Deposits Master Module This module helps to Track the Deposits received from the customer. With this module the end user can add, modify, remove the customer details and deposit schemes.
Payments Master Module With the help of this module, the end user can do the process like Maturity Repayment to the Customer against their Deposits and interest payments from the Customer against the Loans.
Loans Master Module This module provides the facilities to maintain loan sanctions based on the deposits of the customers.
Reports
Reports related to outstanding Loans, Interest Details, Terminated Deposits, Tax Statements are generated through the System.
The end user can add, modify or remove transaction entries based on their rights. The administrator is a user giving rights to the end user is having the capability of changing passwords of other users.
CHAPTER 3 SOFTWARE REQUIRMENTS SPECIFICATION 3.1 Functional Requirements: The main aim in this stage is to assess what kind of a system would be suitable for a problem and how to build it. The requirements of this system can be defined by going through the existing system and its problems. They discussing (speak) about the new system to be built and their expectations from it. involved would be The steps
Problem Recognition The difficulty in the present system is everything is maintained through papers. So maintaining records for a long time and handling large volumes data is impossible. Evaluation and Synthesis The system has to be designed only after complete evaluation of the existing one, upon which we can see that a lot depends on the medium of communication. In the proposed system the information related to the
customers, deposits and reports are very quickly and effectively handled. So this has to be used such that there is no waste of time.
Specification The specifications from the deposits, loan and customers had be to taken. This division provided the required format for the Fixed Deposit Management System. The appearance of forms, and their field names, the different screens are desired, the stages of this database etc., were all given. The system has been build following all the specifications.
3.2 Performance requirements All the requirements relating to the performance characteristics of the system must be clearly specified. There are two types of performance requirements – static and dynamic.
Static Requirements are those that do not impose constraint on the execution characteristics of the system. These include requirements like the number of terminals to be supported, and number simultaneous users to be supported, number of files, and their sizes that the system has to process. These are also called capacity of the system. Dynamic requirements specify constraints on
execution behavior of the system. These typically include response time and throughput constraints on the system.
The processing speed, respective resource consumption throughput and efficiency measure performance. For achieving good performance few
requirements like reducing code, less use of controls, minimum involvement of
repeated data etc., are to be followed. Each real-time system, software what provides required function but does not conform to performance of software requirements is acceptable. These requirements are used to test run time performance of software with the context of an integrated system.
3.3 Interface requirements Software Interfaces These interface requirements should specify the interface with other. Software which the system will use or which will use the system, this includes the interface with the operating system and other applications. The message content and format of each interface should be given.
Hardware interface Hardware interface is very important to the documentation. If the software is executive on existing hardware or on the pre-determined hardware, all the characteristics of the hardware, including memory restrictions, should be specified. In addition, the current use and load characteristics of the hardware should be given.
3.4 operation requirements
Operational study is an important phase in the phase in the software development process. It enables the developer to have an assessment of the
product being developed. It refers to the feasibility study of the product in terms of outcomes of the product, operational use and technical support required for implementing it.
Operational study should be performed on the basis of various criteria and parameters. The various operational studies are:
? Economic ? Operational ? Technical 1. Economic: It refers to the benefits or outcomes we are deriving from the product as compared to the total cost we are spending for developing the product. If the benefits are more or less the same as the older system, then it is not feasible to develop the product.
2. Operational: It refers to the feasibility of the product to be operational. Some products may work very well at design and implementation but may fall in the real time environment. It includes the study of additional human resource required and their technical expertise.
3. Technical: It refers to whether the software that is available in the market fully supports the present application. It studies the pros and cons of using particular software for the development and its feasibility. It also studies the additional training needed to be given to the people to make the application work.
3.5 Resource Requirements Hardware Specification Processor Processor Speed RAM Hard disk Key board Software Specification Database Front end Editor : : : Oracle 10 G Visual Basic, Microsoft Office : : : : : Intel Core 2 Duo based system 2.66 Ghz 2 GB 360 GB 104 keys
3.6 Security Requirements Software requirements specification plays an important role in the creating quality software solutions. Specification is basically a representation process.
Requirements are represented in a manner that ultimately leads to successful software implementation.
Requirements may be specified in a variety of ways. However there are some guidelines worth following:• • • • Representation format and content should be relevant to the problem Information contained within the specification should be nested Diagrams and other notational forms should be restricted in number and consistent in use. Representations should be revisable.
3.7 Design Requirements Software design is a process through which the requirements are translated into a representation of software. One of the software requirements have been
analyzed and specified, the s/w design of the system is in modular form i.e., the s/w is logically partitioned into components that perform specific functions and sub functions. The design phase leads to modules that exhibit independent
function characteristics. It even leads to interfaces that reduce the complexity of the connections between modules and with the external environment. The design phase is of main importance because in this activity, decisions ultimately affect the success of s/w implementation and maintenance.
3.8 Quality and reliability requirements The software requirements specification is produced at the culmination of the analysis task. The function and performance allocated to the software as a part of system engineering are refined by establishing a complete information description, a detailed functional and behavioral description, and indication of performance requirements and design constraints, appropriate validation criteria and other data pertinent to requirements.
CHAPTER 4 SYSTEM ANALYSIS 4.1 Data Flow Diagram
Master Customer Master
Transaction
Reports
Deposit Master
Payment Master
Loan Master
Customer Master
Add Customer
Modify Customer
Delete Customer
Loan Master
Add Loan Details
Modify Loan Details
Delete Loan Details
Deposit Master
Add Deposit Details
Modify Deposit Details
Delete Deposit Details
Payment Master
Add Payment Details
Modify Payment Details
Delete Payment Details
4.2 Entity Relationship Diagram
Depositors_ID
Depositors _Address2
Depositors _Firstnam e Depositors _lastname Depositors _lastname
Depositors _Address3
Depositors _Address4
Customer
Pincode
Contact_n o
Dateofbirth
Deposit_Scheme_Id
Maturity_days
Deposit_scheme _Name
Validfrom_sche me
Rate_of_Intere st
Validto_scheme
Deposits
Depositors_ID
Repayment _amount
Deposit_S cheme_Id
Interestrec eived_Dat e
Repayment_date
Interestrece ived_amou nt
Payment
Deposit_ amount
Deposit_date
Transaction _id
Depositors_ID
Transaction_N umber
Loan_Number
Loan_amount
Transaction_Date
Loan
CHAPTER 6 SYSTEM DESIGN 5.1 Input Design Input design is the process of converting user-originated information to computer-based format. The goal of designing input data is to make data entry easier and error free as possible. An input format should be easy to understand.
In this application inputs are nothing but the information about different entities. Every entity has different fields i.e., customer master have some properties like Customer_id, Customer_firstname and so on. By taking these inputs from the user, we do the process to decide whether to save the messages, send the content to the destination or pacing any restrictions. The output design relays on input, which is used to the output. Hence input design needs some special attention.
5.2 Table and Database Design
TABLE NAME: Customer_Master, it contains all details about administrators. The following table explains all the fields.
Field Name Depositors_ID Depositors _Firstname Depositors _lastname Depositors _lastname Depositors _Address2 Depositors _Address3 Depositors _Address4 Pincode Contact_no Dateofbirth
Data Type
VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2
Date
Size 14 25 25 25 25 25 25 6 10 8
TABLE NAME: Deposits_Master, it contains all details about administrators. The following table explains all the fields.
Field Name Deposit_Scheme_Id Deposit_scheme_Name Rate_of_Interest Maturity_days Validfrom_scheme Validto_scheme
Data Type
VARCHAR2 VARCHAR2 Number Number Date Date
Size 14 25 5,2 5 8 8
TABLE NAME: Payments_Master, it contains all details about administrators. The following table explains all the fields.
Field Name Depositors _id Deposit_Scheme_Id Repayment_date Repayment_amount Interestreceived_Date Interestreceived_amount Deposit_amount Deposit_date Transaction_id
Data Type VARCHAR2 VARCHAR2 Date Number Date Number Number Number VARCHAR2
Size 14 14 8 8,2 8 8,2 8,2 8,2 14
TABLE NAME: Loan_Master, it contains all details about administrators. The following table explains all the fields.
Field Name Depositors_ID Loan_Number Transaction_Date Transaction_Number Loan_amount
Data Type
VARCHAR2 VARCHAR2
Date
VARCHAR2 Number
Size 14 14 8 14 8,2
5.3 Output Design
Output reflects image of the purpose. The output design involves designing forms layout, making lists, making well designed reports etc., and reports are main outputs of the proposed system. Here the outputs are: list of customers, list of outstanding loans and so on.
System Design System design is the process of applying various techniques and principles for the purpose of definition a system in sufficient details to permit its physical realization.
Software design is the kernel of the software engineering process. Once the software requirements have been analyzed and specified, the design is the first activity. The flow of information during this process is as follows.
The Process Software design is the process through which requirements are translated into a representation of software.
5.4 Front End Design
Visual Studio.Net
Visual Studio .NET is a complete set of development tools for building
? ASP Web applications ? XML Web services ? desktop applications ? mobile applications
Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same integrated development environment (IDE), which allows them to share tools and facilitates in the creation of mixed-language solutions. Visual Basic Visual Basic has been updated to include many new and improved language features that make it a powerful object-oriented programming language. These features include inheritance, interfaces, and overloading, among others. Visual Basic also now supports structured exception handling, and custom attributes. In addition, Visual Basic supports multithreading. Multithreading is the ability to assign individual tasks to separate processing threads.
C# Visual C#, pronounced C sharp, is a new object-oriented programming language that is an evolution of C and C++, providing a simple and type-safe language for developing applications. C++ Managed Extensions for C++ and attributed programming are just some of the enhancements made to the C++ language. Managed Extensions simplify the task of migrating existing C++ applications to the new .NET Framework. Attributes, like C++ keywords, are used in your source files and interpreted by the compiler. Attributes are designed to provide a quick and efficient method to simplify COM programming with Visual C++. JScript JScript has been updated to be a class-based, object-oriented scripting language that maintains full backwards compatibility with previous versions of JScript. JScript now provides class-based objects, typed variables, true compiled code, and cross-language support through Common Language Specification (CLS) compliance. The primary role of JScript is development of Web sites with ASP.NET and customization of applications with Script for the .NET Framework.
Types of forms used in .Net Web Forms Web Forms are an ASP.NET technology that you use to create programmable Web pages. Web Forms render themselves as browser-compatible HTML and script, which allows any browser on any platform to view the pages. Using Web Forms, you create Web pages by dragging and dropping controls onto the designer and then adding code, similar to the way that you create Visual Basic forms Windows Forms Windows Forms is the new platform for Microsoft Windows application development, based on the .NET Framework. This framework provides a clear, objectoriented, extensible set of classes that enables you to develop rich Windows applications. Additionally, Windows Forms can act as the local user interface in a multitier distributed solution. The .NET Framework Overview The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:
•
To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.
•
To provide a code-execution environment that minimizes software deployment and versioning conflicts.
•
To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party.
•
To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.
•
To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.
•
To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.
The .NET Framework is a multi-language environment for building, deploying, and running XML Web services and applications.
? Common Language Runtime Despite its name, the runtime actually has a role in both a component's runtime and development time experiences. While the component is running, the runtime is responsible for managing memory allocation, starting up and stopping threads and processes, and enforcing security policy, as well as satisfying any dependencies that the component might have on other components. At development time, the runtime's role changes slightly; because it automates so much (for example, memory management), the runtime makes the developer's experience very simple, especially when compared to COM as it is today. In particular, features such as reflection dramatically reduce the amount of code a developer must write in order to turn business logic into a reusable component.
? Unified programming classes The framework provides developers with a unified, object-oriented, hierarchical, and extensible set of class libraries (APIs). Currently, C++ developers use the Microsoft Foundation Classes and Java developers use the Windows Foundation Classes. The framework unifies these disparate models and gives Visual Basic and JScript programmer’s access to class libraries as well. By creating a common set of APIs across all programming languages, the common language runtime enables cross-language inheritance, error handling, and debugging. All programming languages, from JScript to C++, have similar access to the framework and developers are free to choose the language that they want to use.
? ASP.NET ASP.NET builds on the programming classes of the .NET Framework, providing a Web application model with a set of controls and infrastructure that make it simple to build ASP Web applications. ASP.NET includes a set of controls that encapsulate common HTML user interface elements, such as text boxes and drop-down menus. These controls run on the Web server, however, and push their user interface as HTML to the browser. On the server, the controls expose an object-oriented programming model that brings the richness of object-oriented programming to the Web developer. ASP.NET also provides infrastructure services, such as session state management and process recycling that further reduce the amount of code a developer must write and increase application reliability. In addition, ASP.NET uses these same concepts to enable developers to deliver software as a service.
Visual Basic.Net New in Visual Basic Web Development: Visual Basic and C# include support for Web Forms and XML Web services. Web Forms allow you to easily and quickly create the browserbased interface for ASP.NET Web applications. XML Web services allow you to package a Visual Basic or C# method and make it accessible on the Web. New in Data: ADO.NET provides scalable, high-performance data access for all Visual Studio Applications based on the .NET Framework. You can access data directly in the data source or create an in-memory cache — a dataset — for working with disconnected data. You can also work directly with XML as relational data or by creating and editing XML files directly. Windows Forms and Controls: You can use Windows Forms and controls to create the presentation layer of a distributed application. Windows Forms provides a clear, object-oriented, extensible set of classes that enable you to develop rich Windows applications. New in Projects: You can use the Project templates in this version to easily create various types of Windows and ASP.NET Web applications and controls. Project templates set necessary references for you, import namespaces, and add default items to your projects.
Components and Component Authoring: You can use nonvisual components and associated features to incorporate resources such as message queues, event logs, and performance counters into your applications. This version also offers RAD support for component creation via the Component Designer and framework classes that help you create controls and components.
New in Debugging: You can now debug projects that are part of the same solution but written in different languages, perform remote debugging, and implement trace functionality throughout your code to retrieve finely tuned output.
Extensibility and Automation: Visual Studio .NET includes a programmable object model that provides access to the underlying components and events of the integrated development environment (IDE). This model allows you to extend the functionality of the IDE, automate repetitive tasks, and integrate the IDE with other applications.
(ActiveX Data Objects)ADO. Net
ADO.NET is an evolutionary improvement to Microsoft ActiveX Data Objects (ADO). It represents a standards-based programming model that facilitates the development of distributed applications, especially Web applications.
Features
? Access Data Sources with High-Performance Data Components
ADO.NET provides high-performance .NET data providers for direct access to databases and other data sources. Data providers give you precise control over SQL commands and stored procedures that can return data or scalar values or perform other database operations. Data reader objects provide an extremely fast way to return readonly data from a data source.
? Work with Disconnected Data To make most efficient use of database and server resources, you can create datasets that act as a relational cache for data drawn from a data source. (A data source is typically a database, but can also be XML or any source for which a .NET data provider is available.) You can define data adapters that fill the dataset and propagate dataset changes back to the data source using stored procedures or SQL statements.
? Create Datasets with Strongly Typed Access With ADO.NET you can create a dataset based on an XML schema, producing a typed class in which tables and columns become first-class objects in the object model. Typed access makes code easier to read, is less error prone, and is fully supported by IntelliSense in the Visual Studio Code Editor.
? Exchange Data as XML with Other Applications You can serialize data into and out of XML streams that can be exchanged with other XML-enabled applications or components by using either the built-in features of datasets or XML-specific methods. ADO.NET can easily create XML Web services with methods that return datasets as XML.
? Use Wizards for Configuring Data Access Wizards can be used to create and configure data adapters and connections. The Data Form Wizard helps you create a form that is bound to a dataset, creating type-appropriate data-bound controls. The Data Form Wizard can create simple forms bound to a single table or master-detail forms bound to related tables, and can display data one record at a time or in a data-bound grid.
Debugging Visual Studio .NET provides a single integrated debugger for all Visual Studio languages, including Visual Basic and C#. A new, unified interface combines features of the Visual C++ and Visual Basic 6.0 debuggers, as well as many new features.
? Cross-Language Debugging Using the integrated debugger, you can debug projects that are part of the same solution but are written in different languages. For example, you can debug a solution that contains a project consisting of a Visual Basic or Visual C# user interface application and a Visual C++ server application, and you can step back and forth between these projects, for example from Managed Extensions for C++ to Visual Basic and back to Managed Extensions for C++.
? Attaching to a Running Program You can attach the debugger to a program that is already running and debug the program. Attaching to a running program works the same way whether the program is
running on a host machine or a remote machine. The program does not need to be launched in the Visual Studio .NET integrated development environment (IDE).
? Remote Debugging You can attach to and debug a process that is running on a different computer from the one on which you are running Visual Studio. For example, if you are debugging a Windows Forms client application and an XML Web service it uses, you can run Visual Studio on the client and then attach to the server that is providing the XML Web service. You typically perform this kind of debugging for Web Forms projects or ASP.NET Web Service projects.
? Debugging Multithreaded Applications New for Visual Basic users is the ability to write and debug multithreaded applications. The Threads window can be used to view the threads that are running and to switch context.
? Debugging Multiple Programs You can debug multiple programs by attaching to running programs or by launching multiple programs from the Visual Studio IDE.
? Debugging ASP.NET Web Applications Configuring debugging for ASP.NET Web applications has been significantly improved. In most cases you can simply choose Start from the Debug menu and the debugger will automatically attach to the ASP.NET worker process for debugging Web
Forms, even if the ASP.NET worker process is running on a different server. Security configuration has been made easier by the addition of a debugger users group.
? .NET Framework Classes for Debugging and Code Tracing You can include instrumentation code in your Microsoft .NET application. Several .NET Framework classes are available for use both in debugging and in instrumenting your code.
Visual C++.NET Microsoft Visual C++ is the most productive C++ tool for creating the highest performance applications for Windows and the World Wide Web. Nearly all world-class software, ranging from the leading Web browsers to mission-critical corporate applications, is built using the Microsoft Visual C++ development system. Visual C+ + .NET brings a new level of productivity to C++, without compromising flexibility, performance, or control. New in c++.Net Managed Code and Targeting the .NET Framework
Provides links to Managed Extensions for C++ and Visual C# documentation.
Attributed Programming
Attributes are designed to provide an efficient and quick method to simplify COM programming in Visual C++. Attributes, like C++ keywords, are used in your source files and interpreted by the compiler. Attributes can modify the behavior of your existing code and even insert additional framework code to accomplish basic tasks, such as implementing an ActiveX control, creating a class factory, or formatting a database command. You can apply attributes to nearly any C++ object, such as classes, data members, and member functions, or you can insert attributes into your source code as stand-alone statements.
C++ Compiler, Linker, and C++ Language
Provides links and updated information about the compiler, linker, build tools, and C++ language features in Visual C++ .NET.
Libraries Provides links to new content in the Visual C++ libraries, including the Active Template Library (ATL), ATL Server, C Run-Time Library, Microsoft Foundation Class Library, OLE DB Templates, Shared Classes, and the Standard C++ Library.
5.5 Back End Design JDBC, accessing the database through applets and JDBC.API via an intermediate server resulted to new type of database model which is different from the client-server model. There are single tires, two tire and multi tire architectures are available.
Single Tier In a single tier the server and client are the same in the sense that a client program that needs information and the sour of this type of architecture is also possible in java, in case flat files are used to store the data. However this is useful only in case of small applications. The advantage with this type is the simplicity and portability.
Server and Client
Database Two Tier (Client – Server) In two tier architecture the database resides in one machine on the network. In this type of architecture a database management takes control of the database and provides
access to clients in a network.
This software bundle is also called as the server.
Software in different machines, requesting for information are called as the clients.
Server
Client Client
Database
Three Tier and N-Tier In the three-tier architecture, any number of servers can access the database that resides on server. Which in turn serve clients in a network. For example, you want to access the database using java applets, the applet running in some other machine, can send request to the server where it is down loaded. For this reason we will need to have a intermediate server which will accepts the request from applets and them to the actual database server. This intermediate server acts as a two-way communication channel also. This is the information or data from the database is passed on to the applet that is requesting it. This can be extended to make n tiers of servers, each server carrying to specific type of request from clients, however in practice only 3 tiers architecture is popular.
ORACLE
ORALCE is a relational database management system, which organizes data in the form or tables. Oracle is one of many database servers based on RDBMS model, which mangers a seer of data that attends three specific things data structures, data integrity and data manipulation. With oracle cooperative server technology we can realize the benefits of open, relational system for all the applications. Oracle makes efficient use of all systems resources, on all hardware architecture; to deliver unmatched performance, price performance and scalability. Any DBMS to be called as RDBMS has to satisfy DR. E.F. Codd’s rules.
DISTINCT FEATURES OF ORACLE • ORACLE IS PORTABLE
The oracle RDBMS is available on wide range of platforms ranging from PCs to super computers and as multi-user loadable module for Novel NetWare, if you develop application on system you can run the same application on other systems without any modifications.
•
ORACLE IS COMPATIBLE Oracle commands can be used for communicating with IBM DB2 main frame
RDBMS that is different from Oracle, which is Oracle compatible with DB2. Oracle RDBMS is a high performance fault tolerant DBMS, which is specially designed for online transaction processing and for handling large database applications.
•
MULTITHREADED SERVER ARCHITECTURE adaptable multithreaded server architecture delivers scalable high
Oracle
performance for very large number of users on all hardware architecture including symmetric multiprocessors (sumps) and loosely couples multiprocessors.
Performance is achieved by eliminating CPU, I/O, memory and operating system
bottlenecks and by optimizing the Oracle DBMS server code to eliminate all internal bottlenecks.
FEATURES OF ORACLE Most popular RDBMS in the market because of its ease of use • • • • • • Client/server architecture Data independence Ensuring data integrity and data security Managing data concurrency Parallel processing support for speed up data entry and online transaction processing used for applications DB procedure functions and packages.
Dr. E. F. CODD’s Rules These rules are used for valuating a product to be called as relational database management systems. Out of 12 rules, a RDBMS product should satisfy at least 8 rules must be satisfied.
RULE 0: FOUNDATION RULE: For any system that is to be advertised as or claimed to be relational DBMS. That system should manage database with in self, with out using an external language.
RULE 1: FOUNDATION RULE: All information in relational database is represented at logical level in only one way as values in tables.
RULE 2: GUARANTEED ACCESS: Each and every data in a relational database is guaranteed to be logically accessibility by using to a combination of table name, primary key value and column name.
RULE 3: SYSTEMATIC TREATMENT OF NULL VALUES Null values are supported for representing missing information and inapplicable information. They must be handled in systematic way, independent of data types.
RULE 4: DYNAMIC ONLINE CATALOG VASED RELATION MODEL The database description is represented at the logical level in the same way as ordinary data so that authorized users can apply the same relational language to its interrogation as they do to the regular data.
RULE 5: COMPREHENSIVE DATA SUB LANGUAGE A relational system may support several languages and various models of terminal use. However there must be one language whose statement can express all of the following: Data definition, view definitions, data manipulations, integrity, constraints,
authorization and transaction boundaries.
RULE 6: VIEW UPDATING Any view that is theoretically updatable if changes can be made to the tables that effect the desired changes in the view.
RULE 7: HIGH LEVEL UPDATE, INSERT and DELETE
The capability of handling a base relational or derived relational as a single operand applies not only retrieval of data also to its insertion, updating, and deletion.
RULE 8: PHYSICAL DATA INDEPENDENCE Application program and terminal activities remain physically unimpaired whenever any changes are made in either storage representation or access method.
RULE 9: LOGICAL DATA INDEPENDANCE Application program and terminal activities remain logically unimpaired whenever any changes are made in either storage representation or access method.
RULE 10: INTEGRITY INDEPENDENCE Integrity constraints specific to particular database must be definable on the relational data stored in the catalog, not in application program.
RULE 11: DISTRIBUTED INDEPENDENCE Weather or not a system support data base distribution, it must have a data sublanguage that can support distributed database without changing the application program.
RULE 12: NON SUB-VERSION If a relational system has low level language, that low language cannot use to subversion or by pass the integrity rules and constraints expressed in the higher level relation language.
ORACLE SUPPORTS THE FOLLOWING CODD’S RLES: 1. Information Rule
2. Guaranteed access – yes 3. Systematic treatment of null values - yes 4. Dynamic on line catalog-based relation model – yes 5. Comprehensive data sub language – yes 6. View updating – PARTIAL 7. High – level update, insert and Delete – Yes 8. Physical data independence – PARTIAL 9. Logical data independence – PARTIAL 10. Integrity Independence – PARTIAL 11. Distributed independences – Yes 12. Non – subversion – yes
TESTING
6.1 Unit Testing Unit testing focuses on verification effort on the smallest unit of software design that is called as module. Using procedural design description as a guide, important control paths are tested to uncover errors within the boundaries of the module. The unit test is normally called as white box testing and the testing can be conducted in parallel for multiple modules.
6.2 integration testing Integration testing is a systematic technique for constructing the program structure while conducting test to uncover errors associated with the interfacing. The objective is to take unit tested methods and build a program structure that has been dictated by design.
Top-down integration: Top down integrations an incremental approach to construction of program structure. Modules are integrated by moving downward through the control hierarchy, beginning with the main control program. Modules subordinate to the main program are incorporated in the structure either in the breath-first or depth-first manner.
Bottom-up integration: This method as the name suggests, begins construction and testing with atomic modules ie., modules at the lowest leveling the program structure. Because the modules are integrated in the bottom up manner the processing required for the modules subordinate to a given level is always available and the need for stubs is eliminated.
6.3 Validation Testing At the end of integration testing software ids completely assembled as a package. Validation testing is the next stage which can be defined as successful when the software functions in the manner reasonable expected by the customer. Reasonable expectations are those defined in the software requirements specifications. Information contained in those sections form a basis for validation testing approach.
6.4 Acceptance Testing A strategy for software testing integrates software test cases into a series of well planned steps that result in the successful construction of software. Software testing is a broader topic for what is referred to as Verification and Validation. Verification refers to the set of activities that ensure that the software correctly implements as specific function validation refers the set of activities that ensure that the software that has been built is traceable to customer’s requirements.
CHAPTER 7 CONCLUSION
This project is designed and developed for Brigade Corporation Ltd. formerly as Brigade Solutions – Chennai to take care of part of financial activities of the Company such as Deposits Received, Loan Issued, Repayment, Maturity Repayments, and Generation of interest warrants and Deposit Receipts. This company wants to maintain all the transactions in the database for accounting and future reference.
The database system must provide for the safety of the information stored, despite system crashes or attempts at unauthorized access. If data are to be shared among several users, the system must avoid possible anomalous results.
SCREEN SHOTS & REPORTS
doc_215273156.doc