PROJECT SYNOPSIS

ON

VCE_INFO

WEBSITE OF VAISH COLLEGE OF ENGINEERING

SUBMITTED TO:1

Mr. DEEPAK GUPTA H.O.D. I.T. DEPARTMENT V.C.E. ROHTAK

SUBMITTED BY:KAMESH GUPTA 630/IT/07 KULVIR GAHLAWAT 633/IT/07 OJAS JUNEJA 648/IT/07

VAISH COLLEGE OF ENGINEERING, ROHTAK.

2

ACKNOWLEDGEMENT
We are very thankful to everyone who all supported us,for we have completed our project SPY EYE effectively and moreover on time.We are equally grateful to our lecturer,Mr. SUNIL MAGGU.He gave us moral support and guided us in different matters regarding the topic.He had been very kind and patient while suggesting us the outlines of this project and correcting our doubts.We thank him for his overall supports. Thanking you, Kamesh (630/IT/07) Kulvir (633/IT/07) Ojas (648/IT/07)

CONTENTS
1. INTRODUCTION 1.1 ABOUT THE PROJECT 2. ABSTRACTION

2.1 ATTRACTIVE POINTS OF PROJECT 3. OBJECTIVES 3.1 WEB SITE OF VAISH COLLEGE OF ENGINEERING 4. FEASIBILITY STUDY & COST/BENEFIT ANALYSIS 4.1 UESR REQUIREMENT 4.2 OPERATIONAL REQUIREMENT 5. SYSTEM REQUIREMENTS 5.1 BACK END 5.2 FRONT END 5.3 DEVELOPMENT ENVIRONMENT 6. DATA FLOW DIAGRAM 7. DESIGN 7.1 VISUAL DESIGN 7.2 CONCEPTUAL DESIGN 7.3 COMPONENT DESIGN 7.4 SYSTEM DESIGN 8. TESTING 9. IMPLEMENTATION 9.1 DATABASE FILES

9.2 WORD FILES/PDF FILES 10. FUTURE SCOPE OF PROJECT 11. REFERENCE

INTRODUCTION
Purpose:
The purpose of this application are as follows :

 Desktop capturing Remote application execution Remote system Lock Monitor and control the remote computer Import and Export RDP files

Admin :
Capture desktop image Remote application execution Import and export files Remote system Lock

ABSTRACTION:
Abstraction contains multiple features of our project in some few attractive ways like:

Easy tracing. Search engine. E-library. Membership facility. Cooperative admission procedure. Notice board alert. Presentable site.

OBJECTIVES:
This section presents a modular overview of the solution, and then provides an introduction to its requirements. Modular Concept:

The website of Vaish college of engineering consists of:

Administration Module: Administrator shall be implemented to control access to functions and process within the sub-sytems as well as by assigning individual account access rights to each user.

User Module: The default access for all the users at all the times will be read only. When a user access a specific data updated by administrator shall be opened for the duration of session only. User can access data using spreadsheets, word files, PDF files and internet tools.

Security Module: The access rights to specific data must be altered in a controlled way by the process that updates the data and resets to read only at the end of process. The reason with the session ID is that with open database connectivity users can access the controlled database.

The following diagram describes the proposed solution architecture at a high level.

Usage Summary Website will address the following use cases. The complete usage scenarios will be completed during the information-gathering process. Use cases will be created and prioritized. Selected use cases will be expanded into usage scenarios and features that are derived from both use cases and the usage scenarios.

FEASIBILITY STUDY &COST/BENIFIT ANALYSIS:

Cost-effectiveness:
Its cost is under the budget and make within given time period. It is desirable to aim for a system with a minimum cost subject to the condition that it must satisfy the entire requirement.

Feasibility Study:
User Requirement:

The site must be user friendly i.e. must contain relevant information about college. It must have the facility of on-line library system that user can easily access any content of
8

their interest. Members (registered users) data must be fully secured. The site must not be heavily loaded so it may pass trade off between time and space. The site must be provided with search engine technique, so that every surfer may access any particular data related to any subject. The process can be represented by the following diagram:

Data Base Server

Application Server

Operational Requirement:

It follows the client server architecture, showing that how data moves from at a time, manyWorkstatio users can access the data nN simultaneously.
Workstatio Workstatio databasen 1user access. It may respondWorkstatio to tonmany users n2 3

SYSTEM REQUIREMENT:
General Requirement for the Project:
Type Work Node Software 1. Windows XP 2. ASP.net 2008 3. SQL Server 2005 1. SQL Server 2005 Hardware 1. P-4 2. RAM -256 MB 1.P-4 2.RAM- 1GB 3.Hard Disk-160GB 4.RAID 1.P-4

Station/

Database Server

Application

1. SQL Server 2005

9

Server

2.RAM- 1GB 3.Hard Disk-40GB

Front End:
1. ASP.Net

ASP is built on the Web Server System to take major advantage of the OS and which comes with a host of different servers which allows for building, deploying, managing and maintaining Web Based solutions. The Web Server System is designed with performance as priority and it provides scalability, reliability. The advantage of ASP.NET includes Rapid Application Development (RAD) Support. Powerful Web-based Applications Simplified Deployment Powerful, Flexible, Simplified Data Access Improved Coding Direct Access to the OS Platform Object-Oriented Constructs COM Interoperability

Back End:
1. SQL 2005:

SQL is RDMS support all application with all features like relational query, different data types, joins, and query. Includes Easy to use and easy to deployment. Integration with Windows OS Scalability Import and Export of data in all major database system. Centralized Management Reliability Automating Tasks

Development Environment:
1. Visual Studio 2008 2. SQL Server 2005

DATA FLOW DIAGRAM:

10

Show the flow of data from central system to various modules.& relation between the different entities.

Context level DFD:

Level 0 DFD:

Level 1 DFD:

DESIGN ANALYSIS:
Visual Design:
We have included images , the gif. files mainly in our site, moreover the flash files and the CSS files to make the site much more attractive. Dynamic effects are presented here as the mouse effects are well presented here, with java scripts introduction. We can present the visual design with the external view concept representation as: External View:

11

The External view of software features visible to users and derived from explicit user requirements. The external view includes screen images, report formats, and responses to user actions as might occur with embedded software. This view might identify features that are shared with other applications and hence potentially reusable. This view also should deal with error-handling for user errors. This view will also discuss the various hardware and software platforms on which the application will operate, and also the various countries and national languages that will be supported. This view is fairly concise and seems to average between 0.5 and 1.0 page per function point.

Conceptual Design:
The conceptual design can be presented by the following ways like: Algorithm View:

The Alogrithm view of the mathematical formulas or algorithms contained in the application. These might be straightforward calculations such as currency conversions or very complex formulas such as those associated with quantum mechanics. In any case, the major algorithms need to be represented and explained prior to encoding them. This view is very concise and averages below 0.25 page per function point. Logistical View:

. The logistical view records certain historical facts about software applications that are often lost or difcult to nd. These logistical topics include the date the application was rst started, the locations and companies involved in construction, and information on the methods, tools, and practices used in construction. Application size in terms of both function points and logical code statements would be included in the logistical view, along with the various languages utilized.. The logistical view would also be useful for multiple regression analysis to demonstrate the effectiveness of methods such as Agile or TSP.

Natural language:

The text can be used for dening the attribute view, the logistics view, and for some of the external views. Special forms of natural language such as executable English may also be used. Mathematical formulas or other forms of scientic notations are needed for the algorithm view.

Component Design:
Component Design can be presented using the following points: Structural View:
12

The structural view of software applications includes components and modules and how they are joined together to form a complete application. This view includes the sequence or concurrency with which these modules will execute. Calls or interfaces to external applications are also part of the structural view. This view might also show modules or features that are reused from external sources or custom-built for a specic application. Classes and inheritance using object-oriented methods would also be shown in the structural view. Security View:

The security view or how the application will defend itself against viruses, worms, search bots, denial of service attacks, and other attempts to either interfere with the operation of the software or steal information used by the software. This view is new circa 2009, but quickly needs to become a standard feature of software application design and especially so for nancial applications, health-care applications, and any application that deals with valuable or classied information. Attribute View:

The attribute view or nonfunctional goals and targets for the appli cation once it is deployed. These attributes can include performance in terms of execution speed, reliability in terms of mean time to failure (MTTF), quality in terms of delivered defects, and a number of other attributes as well. This view is also very concise and usually requires less than three pages no matter how large the application itself is.

System Design:
Expert-System Design:

An expert-system design tool will be needed in order to mine information from similar legacy applications. This tool will include the features of static analysis, complexity analysis, security analysis, architecture and design structural analysis, and also the capability of extracting algorithms and business rules from legacy code. Outputs from the tool will include structural design graphs, control flow information, information on dead code, and also textual and mathematical descriptions of business rules and algorithms embedded in the legacy code.Even sample use cases and user stories could be constructed automatically by an intelligent agent based on examining information available on the Web and from published literature. Data dictionaries of all applications could also be constructed using expert systems with little human involvement.

TESTING:
13

Features of testing: 1. Many kinds of testing can be performed either by developers, by in-house test organizations, by outsource test organizations, or by quality assurance teams based on company test strategies. 2. Some test organizations are part of quality assurance organizations and therefore have several kinds of specialists besides testing. 3. Some quality assurance organizations collect data on test results, but do no testing of their own. 4. Some testing organizations are called quality assurance and perform only testing. These may not perform other QA activities. Testing can be applied in following: Unit Test :

Unit testing is one of the core practices of XP and consists of taking each class of an object oriented software system and testing it in isolation. User are encouraged to select a bottomup testing approach, i.e. testing the classes of the system first and then testing the sum of its classes. On such an approach, integration testing becomes much easier. Teachers also encourage students to putspecial emphasis on unit testing due to the following reasons: Unit testing implicitly involves a sort of documentation that provides user with a better understanding of modules, requirements and APIs. Good unit tests are fundamental when doing regression tests. Box Testing:

It is interesting that there is much debate over black box testing, which lacks information on internals; white box testing, with full visibility of internal code; and gray box testing, with visibility of internals, but testing is at the external level.So far as can be determined, the debate is theoretical, and few experiments have been performed to measure the defect removal efficiency levels of black, white, or gray box testing. When measures of efficiency are taken, white box testing seems to have higher levels of defect removal efficiency than black box testing. Integration Testing:

This approach allows a step-by-step integration, i.e. if we replace factory methods one by one, we are adding the original classes to the integration test one-by-one. In comparison with unit tests, integration tests are more diffcult to implement due to the complexity of setting up the domain in the right state to test a specifc behavior. In integration tests lots of

14

objects are involved while in unit tests only a few mock objects, plus the target object, are involved. Moreover, mock objects state is very easy to set up comparatively. Due to these diffculties, we have found that students need extra support and instruction to make integration testing successfully.

IMPLEMENTATION:
Database:
Database contains all the database of the different parts like Governing Body, Time Table, Faculty, User, which are connected with the main Administrator. Open database connectivity is followed here.

Word files/PDF files:

All the information provided is in the Word/PDF files which can be downloaded as on click on their corresponding links.
15

Following information provided by these are: 1. Syllabus 2. Time-table 3. Books from e-library 4. Certain rules and regulations regarding admission etc.

FUTURE SCOPE OF PROJECT:

This application can be easily implemented under various situations. We can add new features as and when we require. Reusability is possible as and when require in this application. There is flexibility in all the modules.

Website Scope:
1. Extensibility:

This software is extendable in ways that its original developers may not expect. The following principles enhances extensibility like hide data structure, avoid traversing multiple links or methods, avoid case statements on object type and distinguish public and private operations.
2. Reusability:

Reusability is possible as and when require in this application. We can update it next version. Reusable software reduces design, coding and testing cost by amortizing effort over several designs. Reducing the amount of code also simplifies understanding, which increases the likelihood that the code is correct. We follow up both types of reusability: Sharing of newly written code within a project and reuse of previously written code on new projects.
3. Understandability:

A method is understandable if someone other than the creator of the method can understand the code (as well as the creator after a time lapse). We use the method, which small and coherent helps to accomplish this.
4. Cost-effectiveness:

16

Its cost is under the budget and make within given time period. It is desirable to aim for a system with a minimum cost subject to the condition that it must satisfy the entire requirement. Scope of this document is to put down the requirements, clearly identifying the information needed by the user, the source of the information and outputs expected from the system.

REFERENCE:

1.

Software engineering, Roger Pressman 5th edition

2. ASP.Net, Wrox Publication 3. SQL, TMH Publication JAVA Script and CSS, Ivan Bayross

4.

5. Internet Reference

17