Lifeline Report
Lifeline Report
Lifeline Report
SYSTEM DESIGN
ASP.NET has many advantages over other platforms when it comes to creating Web applications. Probably the most significant advantage is its integration with the Windows server and programming
tools. Web applications created with ASP.Net are easier to create, debug and deploy because those tasks can all be performed within a single development environment, C#. Back end :SQL Server 2005 SQL Server 2005 (codenamed Yukon), released in October 2005, is the successor to SQL Server 2000. It included native support for managing XML data, in addition to relational data. For this purpose, it defined an xml data type that could be used either as a data type in database columns or as literals in queries. XML columns can be associated with XSD schemas; XML data being stored is verified against the schema. XML is converted to an internal binary data type before being stored in the database. Specialized indexing methods were made available for XML data. XML data is queried using XQuery; SQL Server 2005 added some extensions to the T-SQL language to allow embedding XQuery queries in T-SQL. In addition, it also defines a new extension to XQuery, called XML DML, that allows query-based modifications to XML data. SQL Server 2005 also allows a database server to be exposed over web services using TDS packets encapsulated within SOAP (protocol) requests. When the data is accessed over web services, results are returned as XML.
5. TESTING
Stress Test: Test has been done to intentionally break the unit. This helps in learning about the strength and limitations about the strength and limitations of the program by examining a manner in which a program unit breaks.
Structure Test: Structure test is done to test the internal logic of the program and traversing particular execution paths. The major activity involved in structure test is to decide which paths to exercise, deriving test data to exercise those paths, determining the test coverage.
data or test data that we will derive results for. Here we will compare the results from the software with the results that are derived. This will check for the validation of the software. In case there are problems with the software we will create a deficiency list and will record all problems there.
5.2.Test Procedure
This section describes a detailed test procedure including test tactics and test cases for the system. In this section all software specification is described. We will describe the methods for all the different tests to be performed and will also declare the expected outputs.
In this method of testing we will test the smallest unit of software called modules. We will be testing all the important paths to find any errors within the boundary of module. So here white box test is applied. We will be testing the parts of the software rather than the entire software. The modules are as follows.
Expected results for Registration Module The recipient is registered successfully if username and password are provided and also proper values are entered in all the textboxes provided.
In this method of testing, we will implement the software LIFE LINE at the actual site and will run it. So we will be testing the product on actual site network. Here Top-Down model is used to test. We will start the test with home page, after the home page we will be testing each and every sub component or functions of software.
software components should work properly. In case we come across any errors we will record them in the error document and these errors will be fixed later.
expected results.