25-10-2016, 04:19 PM
1461150773-FCopy.doc (Size: 3.28 MB / Downloads: 6)
ABSTRACT
i
RECONFIGURABLE GUI BASED CONFIGURABLE DATABASE CONSOLES is about a GUI application that is directly connected to a dynamic database. In this we access the application that does not need to be altered separately in the code; instead for any configuration we can directly change the database. Any changes made in the database will automatically effects the change in the application. The application we develop is a windows form c# application and QT application.
Windows forms c# based are used to develop any GUI application. The console is made out of a MS Access incorporated, and GUI (graphical client interface) and applications written in VB (visual fundamental) connected to the database utilizing ODBC (open database network). Everything is included in this tool, which makes it easy to create any application. For connection to database we will be using Microsoft SQL server management studio. For the reconfigurable database console, we will see further in the project. The concept is proposed before but never implemented, hence coming up with a new concept.
INTRODUCTION
When you work with database applications, it generally needs to interface your application with a database like MSSQL or ORACLE or any others. Be that as it may, for fledglings, it's difficult to make database association with the application. When I confronted this issue. So for tenderfoots, now I am demonstrating how to associate your application with MSSQL express release utilizing ADO.NET.
We display another innovation which empowers sorted out database administration frameworks to be produced quickly. Here, we are outlining a Reconfigurable DBMS, to have the framework reconfigure itself to store and recover the information as indicated by this design. Reconfigurable administration is an administration with outside noticeable configurable parameters that can be balanced by invokers.
We trust that the reconfigurable programming innovation proposed here exemplifies a critical development in customizing DBMSs to particular application. The application we created in this is online GUI application. The web application we create is database driven application.
From the viewpoint of GUI, several methods have been studied to elucidate software development and productivity. The operational data of accelerators, including operational log, records of trouble and maintenance, accelerator and device data tables, and accelerating tube temperatures are given by MS-Access applications in VB using ODBC for compatibility with the Windows system. To date, we have focused on developing an environment in which the console can be operated via Windows, since it was felt that safety problems existed in accelerator operations in context with OS databases, except for Windows. However, after providing a viable environment for Java and JDBC, we started to develop software for multi-platform operations. Minimal necessary functions have been completed for displays of conventional factors using the Web browser.
RELATED WORK:
“In quickening agent control frameworks, littler quickening agents have started to utilize the most exceptional PC frameworks accessible. In the meantime, in the area of quickening agent control, a product outlook change has happened. This change is not ascribed just to the accessibility of quicker, all the more effective equipment, or a more powerful OS, additionally to the advancement of new programming and system innovations. These headways in both equipment and programming were foreseen, so alongside the expansion in vitality from 2.5 GeV to 8 GeV of the KEK electron/positron LINAC, we have moved up to another PC based quickening agent control framework. This paper proposes "COACK" (Component-product Oriented Accelerator Control Kernel), and examines COACK stage 2”.
Generally, quickening agent control frameworks have been assembled utilizing object arranged programming or organized programming, actualizing a procedural dialect. This is the situation of the old Linac control framework. The new framework is being made not using a procedural dialect, but rather by utilizing part product and devices. Prior to this thought showed up, the advancement of quickening agent control programming experienced issues, which are examined beneath. Development was on an extensive scale, bringing about high creation costs. Quickening agent control programming devices are promptly accessible available, or if not accessible can be made through a joint venture between organizations.
2.SYSTEM ANALYSIS
EXISTING SYSTEM:
The creation and maintenance of a database requires a great deal of labor, far more than we initially expected, and not many have succeeded in developing a satisfactory database. However, the use of advanced PCs simplifies the building of a flexible, practical accelerator database system. Moreover, particularly in the case of the display function, by making applications windows based, their operation becomes more generalized
PROPOSED SYSTEM:
The Linac has both static and dynamic databases, which store accelerator data, a troubleshooting log and operator’s notes. The console is composed of an MS Access integrated, and GUI (graphical user interface) and applications written in VB (visual basic) linked to the database using ODBC (open database connectivity). Recently, the need for web-based applications linked to a database has grown, and JDBC (Java database connectivity) has enabled this. This treatise compares ODBC and JDBC, both of which are used in the Linac PC system, and reports the issue of their application
2.1 INPUT DESIGN
The input design is the link between the information system and the user. It comprises the developing specification and procedures for data preparation and those steps are necessary to put transaction data in to a usable form for processing can be achieved by inspecting the computer to read data from a written or printed document or it can occur by having people keying the data directly into the system. The design of input focuses on controlling the amount of input required, controlling the errors, avoiding delay, avoiding extra steps and keeping the process simple. The input is designed in such a way so that it provides security and ease of use with retaining the privacy. Input Design considered the following things:
What data should be given as input?
How the data should be arranged or coded?
The dialog to guide the operating personnel in providing input.
Methods for preparing input validations and steps to follow when error occur.
OBJECTIVES
1. Input Design is the process of converting a user-oriented description of the input into a computer-based system. This design is important to avoid errors in the data input process and show the correct direction to the management for getting correct information from the computerized system.
2. It is achieved by creating user-friendly screens for the data entry to handle large volume of data. The goal of designing input is to make data entry easier and to be free from errors. The data entry screen is designed in such a way that all the data manipulates can be performed. It also provides record viewing facilities.
3. When the data is entered it will check for its validity. Data can be entered with the help of screens. Appropriate messages are provided as when needed so that the user will not be in maize of instant. Thus the objective of input design is to create an input layout that is easy to follow
2.2 OUTPUT DESIGN
A quality output is one, which meets the requirements of the end user and presents the information clearly. In any system results of processing are communicated to the users and to other system through outputs. In output design it is determined how the information is to be displaced for immediate need and also the hard copy output. It is the most important and direct source information to the user. Efficient and intelligent output design improves the system’s relationship to help user decision-making.
1. Designing computer output should proceed in an organized, well thought out manner; the right output must be developed while ensuring that each output element is designed so that people will find the system can use easily and effectively. When analysis design computer output, they should Identify the specific output that is needed to meet the requirements.
2. Select methods for presenting information.
3. Create document, report, or other formats that contain information produced by the system.
The output form of an information system should accomplish one or more of the following objectives.
Convey information about past activities, current status or projections of the
Future.
Signal important events, opportunities, problems, or warnings.
Trigger an action.
Confirm an action.
4.SYSTEM STUDY
FEASIBILITY STUDY
The feasibility of the project is analysed in this phase and business proposal is put forth with a very general plan for the project and some cost estimates. During system analysis the feasibility study of the proposed system is to be carried out. This is to ensure that the proposed system is not a burden to the company. For feasibility analysis, some understanding of the major requirements for the system is essential.
Three key considerations involved in the feasibility analysis are
• ECONOMICAL FEASIBILITY
• TECHNICAL FEASIBILITY
• SOCIAL FEASIBILITY
4.1 ECONOMICAL FEASIBILITY
This study is completed to check the financial effect that the framework will have on the association. The measure of asset that the organization can fill the innovative work of the framework is constrained. The consumptions must be legitimized. Hence the created framework too inside the monetary allowance and this was accomplished on the grounds that the vast majority of the innovations utilized are uninhibitedly accessible. Just the modified items must be bought.
TECHNICAL FEASIBILITY
This study is completed to check the specialized possibility, that is, the specialized prerequisites of the framework. Any framework created must not have a popularity on the accessible specialized assets. This will prompt levels of popularity on the accessible specialized assets. This will prompt levels of popularity being put on the customer. The created framework must have an unassuming necessity; as just negligible or invalid changes are required for actualizing this framework.
4.3 SOCIAL FEASIBILITY
The aspect of study is to check the level of acceptance of the system by the user. This includes the process of training the user to use the system efficiently. The user must not feel threatened by the system, instead must accept it as a necessity. The level of acceptance by the users solely depends on the methods that are employed to educate the user about the system and to make him familiar with it. His level of confidence must be raised so that he is also able to make some constructive criticism, which is welcomed, as he is the final user of the system.
SDLC METHDOLOGIES
This document plays a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.
As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
The steps for Spiral Model can be generalized as follows:
• The new system requirements are defined in as much details as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.
• A preliminary design is created for the new system.
• A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.
• A second prototype is evolved by a fourfold procedure:
• Evaluating the first prototype in terms of its strengths and risks.
• Defining the requirements of the second prototype.
• Planning a designing the second prototype.
• Constructing and testing the second prototype.
• At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.
• The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.
• The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.
• The final system is constructed, based on the refined prototype.
• The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.
ADVANTAGES
• Estimates(i.e. budget, schedule etc .) become more relistic as work progresses, because important issues discoved earlier.
• It is more able to cope with the changes that are software development generally entails.
• Software engineers can get their hands in and start woring on the core of a project earlier.
• We are providing interactive data visualizing techniques to observe the Patterns and to adjust the graph parameters dynamically. So we can say that this system is reliable.
INTERFACE
• The user interface is based on the web desktop. The application is developed using c#
• The Interface design is aimed at a flexible front-end communication to provide the user with clear information in navigating a user-friendly interface is planned.
5.SYSTEM REQUIREMENTS:
Hardware Requirements:
• System : Pentium IV 3.5 GHz.
• Hard Disk : 40 GB.
• Floppy Drive : 1.44 Mb.
• Monitor : 14’ Colour Monitor.
• Mouse : Optical Mouse.
• Ram : 1 GB.
Software Requirements:
• Operating system : Windows XP or Windows 7, Windows 8.
• Coding Language : dot net
• Data Base : /MS Access.
• Documentation : MS Office
• IDE : visual studio
• Development : c#
6.1DATA FLOW DIAGRAM
1. The DFD is also called as bubble chart. It is a simple graphical formalism that can be used to represent a system in terms of input data to the system, various processing carried out on this data, and the output data is generated by this system.
2. The data flow diagram (DFD) is one of the most important modeling tools. It is used to model the system components. These components are the system process, the data used by the process, an external entity that interacts with the system and the information flows in the system.
3. DFD shows how the information moves through the system and how it is modified by a series of transformations. It is a graphical technique that depicts information flow and the transformations that are applied as data moves from input to output.
4. DFD is also known as bubble chart. A DFD may be used to represent a system at any level of abstraction. DFD may be partitioned into levels that represent increasing information flow and functional detail.
DATA FLOW DIAGRAM / USE CASE DIAGRAM / FLOW DIAGRAM
The DFD is also called as bubble chart. It is a simple graphical formalism that can be used to represent a system in terms of the input data to the system, various processing carried out on these data, and the output data is generated by the system.
6.2UML DIAGRAMS
UML remains for Unified Modeling Language. UML is an institutionalized universally useful displaying dialect in the field of item arranged programming building. The standard is overseen, and was made by, the Object Management Group.
The objective is for UML to end up a typical dialect for making models of article arranged PC programming. In its present structure UML is contained two noteworthy segments: a Meta-model and a documentation. Later on, some type of technique or procedure may likewise be added to; or connected with, UML.
The Unified Modeling Language is a standard dialect for determining, Visualization, Constructing and archiving the relics of programming framework, and also for business demonstrating and other non-programming frameworks. The UML speaks to a gathering of best building rehearses that have demonstrated effective in the displaying of substantial and complex frameworks. The UML is an imperative piece of creating items arranged programming and the product advancement process. The UML utilizes for the most part graphical documentations to express the configuration of programming tasks.
OBJECTIVES:
The Primary objectives in the outline of the UML are as per the following:
1. Provide clients a prepared to-use, expressive visual demonstrating Language with the goal that they can create and trade important models.
2. Provide extendibility and specialization components to amplify the center ideas.
3. Be autonomous of specific programming dialects and advancement process.
4. Provide a formal premise for comprehension the demonstrating dialect.
5. Encourage the development of OO apparatuses market.
6. Support larger amount advancement ideas, for example, joint efforts, structures, examples and segments.
7. Integrate best practices.
6.3 USE CASE DIAGRAM
An utilization case outline in the Unified Modeling Language (UML) is a sort of behavioral graph characterized by and made from a Use-case examination. Its motivation is to display a graphical review of the usefulness gave by a framework as far as performing artists, their objectives (spoke to as use cases), and any conditions between those utilization cases. The principle reason for an utilization case chart is to show what framework capacities are performed for which on-screen character. Parts of the performing artists in the framework can be delineated.
8.SOFTWARE ENVIRONMENT
An Introduction to .NET Framework
The .NET Framework is a Microsoft's improvement stage.
• It offers to create programming applications.
• It was discharged by Microsoft Corporation in 2002. Later on, a few changes happen in .NET Framework, which makes it as much solid, progressed and more effective stage for building various types of programming applications.
• Why it is called as "stage" is, it goes about as stage for various dialects, apparatuses and libraries.
• It offers outwardly dazzling client encounters, which is generally required today's focused programming world.
• It offers highly propelled security highlights at no other time.
• Supports many dialects like C#, VB.NET, VC++.NET, COBOL, Pascal, Python and so on.
Features of .NET Framework
Next Generation User Experiences:
.NET offers a Framework for building applications and high-loyalty encounters in Windows that mix together application UI, reports, and media content, while misusing the full force of the PC. WPF (Windows Presentation Foundation) offers engineers support for 2D and 3D design, equipment quickened impacts, versatility to various structure elements, intuitive information perception, and predominant substance coherence.
Seamless and Secured Environment:
Application security is a major ordeal nowadays; maybe the most nearly inspected highlight of any new application. .NET offers its best secured environment at run time. With the goal that it is exceptionally difficult to get to the .NET application and its related information by the un-approved clients/programmers.
The get together (the arranged code of .NET structure) contains the security data like which classifications of clients or who can get to the class or technique. With the goal that we can say that .NET Framework applications are highly secured.
The security can be enhanced in the ASP.NET Web Sites by Security models like Integrated Windows Authentication, Microsoft Passport Authentication, Forms Authentication, and Client Certificate confirmation.
Multi Language Support:
.NET gives a multi-dialect advancement stage, so you can work in the programming dialect you lean toward. The Common Language Runtime (A some portion of .NET Framework) gives backing to 3 Microsoft created dialects and a few different dialects from different merchants.
APPLICATIONS OF .NET
Utilizing .NET Framework, we offered to build up the accompanying sorts of utilizations.
1. Console Applications
• These applications contain comparative client interface to the working frameworks like MS-DOS and UNIX.
• Known as C.U.I (Character User Interface) applications.
• These are like C/C++ applications.
• These are littler in size.
• Doesn't contain any graphical elements like mouse pointer, hues, text styles, catches and so on.
Windows Applications
• These applications are outlined like the "Windows" working framework.
• Known as G.U.I (Graphical User Interface) applications.
• Offers graphical elements like mouse pointer, hues, textual styles, catches, content boxes and so forth.
Windows Services
• A Windows administration is a long-running executable application.
• These can run just on windows stages.
• These perform particular capacities as foundation procedure.
• Doesn't contain client interface or doesn't require any client association.
• Windows administrations can be designed to begin when the working framework is booted and keep running out of sight the length of Windows is running, or they can be begun physically when required.
• Examples:
o Windows Time.
o Windows Audio.
o Anti-Virus Security.
o Database administrations like Sql Server, My Sql and Oracle and so on.
o IIS State Services.
o Battery Power Supply Status on Laptops and so forth.
• To see the all the introduced windows administrations on the framework, click on "Begin" – "Control Panel" – "Authoritative Tools" – "Administrations".
Introducing Visual Studio
About Visual Studio:
• Visual Studio is only the Visual IDE (Integrated Development Environment), which is expected to advancement applications with .NET Framework.
• In basic, we can say like ".NET Framework is something that is required to run the .NET applications" and "Visual Studio is something that is required to build up the .NET applications".
Visual Studio Versions:
• There are a few renditions in Visual Studio like Visual Studio 2002, Visual Studio 2003, Visual Studio 2005 and Visual Studio 2008 (as appeared in the past table).
System Requirements of Visual Studio 2008
Processor:
• Minimum: P-IV
• Recommended: Higher than P-IV
RAM:
• Minimum: 512 MB
• Recommended: 1 GB (or above)
OS:
• MS Windows
(XP / 2003 / Vista / 2008 / Windows 7)
Hard disk free space:
• 4.2 GB (on system drive (C)
CD/DVD Drive
(For Installation)
Internet Connection (optional)
(To get latest news and updates from Microsoft’s web site)