Database Management System-Implementation and Applications In Computer Sciences-Project Report, Study Guides, Projects, Research of Applications of Computer Sciences
This report is for final year project to complete degree in Computer Science. It emphasis on Applications of Computer Sciences. It was supervised by Dr. Abhisri Yashwant at Bengal Engineering and Science University. Its main points are: Timeline, Implementation, Application, Centre, Test, Parameters, Compilation, Total, ASP
Download Database Management System-Implementation and Applications In Computer Sciences-Project Report and more Study Guides, Projects, Research Applications of Computer Sciences in PDF only on Docsity!
Table of contents
Work Summary
1. Timeline in vision
The project has been segmented into activities. These activities fall on the time line for completing these activities in planned appropriate intervals of time. Below is a list of project timeline activities and the timeline figure.
1.1. Activities
A – Test Application Design and Development B – Optimization Cases Study and Implementation C – Test Application Modules D – Run Test Centre Simulations E – Case Tool Development
Figure 1-1 Timeline in vision
*NOTE: For project over view and description see article 11.
2. 6
th
semester - 7
th
semester mid
Project work carried from 6th^ semester to 7 th^ mid consisted both study and implementation work, followed on the timeline. The work categorized into two fields, Study work and Implementation work. Below is the categorized list of activities carried during this period.
2.1. Study Work
Developer testing Overview of .Net platform Test strategy concept W3C recommendation on world wide wait Application Centre Test ER Modeling and Normalization ASP.net First two test case study
2.2. Implementation Work
ER model for the system ER model normalization DB implementation Test Application Prototype First two test case implementation
The study work focused on study of literature, research paper, documentations etc as to gain knowledge before implementing the task at hand. It focused more on acquiring knowledge of the subject under study. In implementation work different tasks were implemented in light of the study work carried earlier.
3. 7
th
semester mid - date
Activities carried out in this period are both study oriented and implementation oriented. The study work consists of studying the test cases at hand, their concepts and implementation techniques. The implementation work consists of
Detailed study work description
Below mentioned is detailed description of all the work carried out during the current period.
4. Application centre test parameters
Application Center Test (ACT) stress tests Web servers and analyze performance and scalability problems of Web applications. ACT simulates a large group of users by opening multiple connections to the server and rapidly sending HTTP requests. It also supports several other authentication schemes and the SSL protocol, making it ideal for testing personalized and secure sites.
Orienting to ACT is a major task as all the test cases are going to be simulated on ACT for a number performance counters. Based on the results optimization level and results can be evaluated. For the test cases at hand following are the parameters selected and studied.
(The following carry extracts from reference [5])
4.1. Application life time events
Number of Application events raised since application was started. This parameter lets us know how many events have been raised to see the performance of the server for different amount of events raised.
4.2. Compilation total
Number of .asax, .ascx, .ashx, .asmx, or .aspx source files dynamically compiled.
4.3. Request wait time
The number of milliseconds the most recent request was waiting in queue. More wait time means server is not efficient enough and hence delay in service time for the client.
4.4. Requests in application queue
The number of requests in the application request queue.
4.5. Requests succeeded
It is the number of requests that executed successfully. The more number of requests succeed the efficient the server is.
4.6. Requests timed out
IT is the number of requests that timed out. More time outs means requests waited long before and were not serviced. It refers to the inefficiency of the server.
4.7. Requests/sec
The number of request executed per second on the server. The more number of request executed refers to efficiency of server and web application.
4.8. HTML source size
Size of the HTML sent to the client. If the HTML size is large it will require more space at client end and also take longer time to download at client end. Another effect can be increase in network traffic.
4.9. Memory
Memory consumed by the application at server end. It depends on the construction of web application and requests being serviced by the server. If the application caches more data then more memory is consumed for fewer requests.
5. View state in ASP .net
5.1. Introduction
The web is a stateless medium that is a live connection is not maintained between server and client. State is not maintained between client requests by default. Techniques must be utilized to provide some form of state management for a web application. ASP.NET provides several mechanisms to manage state in a more powerful and easier to utilize. View state is used to represent the state of the page when it was last processed on the server. It is used to retain values across two successive request of the same page. View state is sent and received with the page but it carries no information regarding the display of the page at client end. View state allows the controls in a web page to retain their state.
View state is enabled by default so if you view a web form page in browser, a line similar to the following near the form definition is made in rendered HTML:
Page level state is maintained automatically by ASP.NET. It can be disabled if necessary by setting the EnableViewState property to false for either the controls whose state doesn't need to be maintained or for the page as a whole.
By default View state is enabled for every control in an ASP.NET application. Any data in view state automatically makes a round trip to the client. Because the round trips contribute to a performance overhead, it is important to avoid unnecessary use of view state.
On completing a web forms page it is necessary to review the controls in the page and consider what is being passed in the view state and whether it is really needed to pass all that information. To optimize Web page size view state should be disabled in the following cases:
When a page does not post back to itself When there are no dynamically set control properties When the dynamic properties are set with each request of the page
6. Session state in ASP .net
6.1. Introduction
An application might need to store and access complex information such as datasets or custom data objects which can’t be easily persisted to a
cookie or sent through a query string. Or the application might have stringent security requirements that prevent it from storing the client’s information in state or a custom cookie. In this situation one can use ASP .net’s built-in session state facility 1.
Session state is a way of state management that fulfills the storage requirements of sophisticated web applications.
6.2. How it works
A session key that is a unique 120 bit identifier is stored for each client session. Special algorithms are used to generate the key to ensure its uniqueness. This ID is the only information that is being transmitted between client and server. When the request with ID is received at the server end ASP .net looks up for the corresponding session and retrieves the serialized data from the state server and converts them to live objects. There are two methods to do this task.
Session ID may be transmitted in a special cookie which is created automatically when the session collection is used. This is the default methodology. This is shown in figure below^4 :
Figure 6-2-A Session ID with cookie
The session ID can be sent through a modified URL. This is called cookie less transmission. This is useful when client runs applications that do not support cookies. The cookie less methodology is shown in figure below^4 :
6.4. Session Mode
ASP.NET session state supports several different storage options for session variables. Each option is identified as a session-state Mode. The default behavior is to store session variables in the memory space of the ASP.NET worker process. However, it can also be specified that session state be stored in a separate process, in a SQL Server database, or in a custom data source. If it is not desired to keep session state enabled for application, the session mode can be set to off.
6.5. Advantages / disadvantages
Session state is the most flexible and, in general, the most efficient. ASP.NET has enhanced session state to address some of the problems associated with it in previous versions of ASP, including the abilities to host session state out of process (or in a database) and to track session state without using cookies. Keeping data in session state at server end keeps the data safe as it is not transmitted to client. Since data is not transmitted to client the source HTML size is small and thus download time is less and network traffic is also decreased.
In a scenario where the connection between database server and server is slow using session state can decrease access to the database server at the cost of more data load on the server.
Keeping too much data in session state can increase memory consumption exponentially at server end as more client requests are received at the server. Thus unnecessary use of session state can cause inefficient memory utilization and limit the resources of server. Keeping all data lumped in session can give rise to scenario where most of the data is session state is not utilized and thus leads to wastage of memory resources.
Detailed implementation work description
In implementation phase test case are implemented using ACT simulations on the test web application.
7. DB entry and expansion
In the implementation phase for database sample data about items is entered into the database. This data includes user accounts, item names, item descriptions, item genre, item authors, item id, item image etc. Database entries are used by web application to ensure proper working of the application and to create transfer and process load of data on server. Apart form data entry database has been expanded for new modules in web application. New database tables are required for messages and notifications. Data entering process by query manager is shown below:
Figure 7-1 Database data entry
9. View state test case implementation
The view state test case implementation is carried out in the following flow of steps.
Test application
Test case plan
Test case specification
Test case implementation
Result summary
Inferences
Hurdles
Each step is described in detail below.
9.1. Test page
To proceed with test case first and foremost we need a web application with view state implemented in it. The test web application fulfills this requirement. The control property of controls on the page for view state is by default enabled to true. This means that view state will be used to carry data to server end for processing. This is shown in figure below.
Figure 9-1 View state set to true for text box control
9.4. Measuring client HTML size
Measure the client HTML size. The client HTML can be viewed in the browser. It can be exported to a text file to measure its size. In the HTML the view state components can be seen. For every component used there is a view state section even though the component is not using view state. This is unnecessary data bulked in the HTML. It has been depicted in the following figure.
Figure 9-5 View state information bulked in client HTML source code
9.5. Optimizing view state
For controls that do not take part in view state set their view state values to false so that the useless information is not bulked in the HTML. Compare the size of the resulting HTML source code. The optimized code is less in size.
10. Session state test case implementation
The view state test case implementation is carried out in the following flow of steps.
Test application
Test case plan
Test case specification
Test case implementation
Result summary
Inferences
Hurdles
10.1. Test page
To proceed with test case first and foremost we need a web application with session state implemented in it. The test web application fulfills this requirement. In the test application the session state is primarily used to keep track of user authentication at the start of application pages. Session state is usually used to get away from excessive database access as in congested network scenario frequent database access can result in a lot of delay, but this escape does not come for free as session state as its own limitations and direct impact on the memory and the processing resources of the web server. In this test case different configurations of session state and database access are implemented and analysis the corresponding effects in the performance parameters is performed.
It is carried out in test application by filling the messages information for the users in the database to decrease the database access. Similarly all the bookmarks are loaded at the login in session state.
