You are on page 1of 5

Virtual DBA

Title of the Project: Virtual DBA Project Architecture: N-Tire Architecture SDLC Methodologies: Waterfall/Spiral Model
Course: Roll No: Name of the Student: Technology And Language: Internal Guide: E-Mail ID: Mobile No (Student):

MS.Net Framework 3.5 With Visual C#

Abstract of the Project: Introduction:


The project has been planned to be having the view of distributed architecture, with centralized storage of the database. The application for the storage of the data has been planned. Using the constructs of MS-SQL Server and all the user interfaces have been designed using the ASP.Net technologies. The database connectivity is planned using the SQL Connection methodology.

FUNCTIONAL REQUIREMENTS:
Here we need to enhance the logic of sql server Mechanism in our Application In logic coding part we need to access the corresponding database in application using the authentication. Every user having different rights in accessing database. All operations will be performed in sql server and executed the result in our application.

Non-Functional Requirements:
24 X 7 availability Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension

EXISTING STSTEM

Let us consider the existing system is a manual system and it has most number of disadvantages like following. Less Security. Fewer Users - Friendly. The complete hierarchy is doesnt implemented in manually.

PROPOSED SYSTEM:
In our Proposed System, We are going to implement the SSL with Backend Forwarding model (Algorithm) is to overcome the problem of existing system. The Scope of administration of such complex task is still limited to the desktop over a LAN network where the Server is installed on a Single system, which acts as server, and the other systems in the client work under the client environment to interact with the SQL Server.

Module description:
The system after careful analysis has been identified to be presented with the following modules: The modules involved are:

Login:

Login Database, Tables Stored procedure Views Security

In this module user login to the server using their server address, username and password. Database: The user will connect to the server, after connect to the server then user can create databases and table within the database.

Stored procedures:

This module is used to create the stored procedures on the table. Views: In this module we have to create a view for the particular table. Security: The application should run in a browser from where the administrator can connect to any server installed on some other machine by providing the name of the server, its username and password.

User Authentication & Authorization Module: This module contains all the information about the authenticated user. User without his/her username and password cant enter into the login if he/she is only the authenticated user then he/she can enter to his/her login and he/she can see the all the information related to the project which he/she is developing. This module uses Form Based Authentication & Authorization to make security.

Environment:

Operating System: - Microsoft Windows XP/2000 or Higher Data Base: Microsoft SQL Server 2005 Development Tools: Microsoft Visual Studio .Net 2008 Documentation Tools: MS Office 2007 Drawing Tools: IBM Rational Rose Enterprise, MS Office Visio 2007 Code Behind: VC#.NET

REQUIREMENTS:
SOFTWARE REQUIREMENTS: MS .Net Framework 3.5 MS SQL SERVER 2005 Windows XP. IIS

HARDWARE REQUIREMENTS: Hard disk : 40 GB

RAM Processor Monitor

: : :

512mb Pentium IV 17Color Monitor

Milestones:
No. Milestone Name Requirements Specification Milestone Description Remarks

Technology Familiarization

Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of the technology needed to implement the project.

Attempt should be made to add some more relevant functionality other than those that are listed in this document. The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective. It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself. The scenarios should map to the requirement specification

Database Creation

A database of at least 10 entries of users with at least 1 should application admin.

High-level Detailed Design

and

Development of Front End Functionalities.

Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario. Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options

During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.

Integrating the Front-end with the Database

Integration Testing

The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing. The system should be thoroughly tested by running all the test cases written for the system (from milestone 5).

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.

Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.

During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled

The following steps will be helpful to start of the project:


Study and be comfortable with technologies such as: Win Form with C#. Gather some knowledge of product hierarchies and maintenance before starting the design. Create menus for navigation and group the functionalities as sub menus. Create the help-pages of the application in the form of FAQ. This will helps user.