ProjectsGeek

Railway Reservation System Rational Rose UML Diagrams

January 20, 2012 by ProjectsGeek Leave a Comment

Railway Reservation System Rational Rose UML Diagrams

AIM: IMPLEMENTATION OF RAILWAY RESERVATION SYSTEM USING RATIONAL ROSE UML DIAGRAMS

THEORY:

Rational Rose provides support for two essential elements of modern software Engineering: component-based development and controlled iterative development.

While these concepts are conceptually independent, their usage in combination is both natural and beneficial.

Rational Rose’s model-diagram architecture facilitates use of the Unified Modeling Language (UML), Component Object Modeling (COM), Object Modeling Technique (OMT), and Booch‘93 method for visual modeling. Using semantic information ensures correctness by construction and maintaining consistency.

Modeling with Rational Rose

Rational Rose is the visual modeling software solution that lets you create, analyze, design, view, modify, and manipulate components. You can graphically depict an overview of the behavior of your system with a use-case diagram. Rational Rose provides the collaboration diagram as an alternative to a use-case diagram. It shows object interactions organized around objects and their links to one another. The state chart diagram provides additional analysis techniques for class switch significant dynamic behavior. A state chart diagram shows the life history of a given class, the events that cause a transition from one state to another state, and the actions that result from a state change. Activity diagrams provide a way to model a class operation or the workflow of a business process.

Notations

Notation plays an important part in any application development activity—it is the glue that holds the process together. UML provides a very robust notation, which grows from analysis into design.

UML diagrams

• Instead of the Context, Data-Flow and Entity-Relationship Diagrams used in Structured Analysis, UML produces 9 types of diagrams

– Use Case Diagram

Use cases are best discovered by examining what the actor needs and defining what the actor will be able to do with the system; this helps ensure that the system will be what the user expects.

– Sequence Diagram

A sequence diagram is a graphical view of a scenario that shows object interaction in a time-based sequence—what happens first, what happens next. Sequence diagrams establish the roles of objects and help provide essential information to determine class responsibilities and interfaces. Sequence diagrams are normally associated with use cases.

This type of diagram is best used during early analysis phases in design because they are simple and easy to comprehend. A sequence diagram has two dimensions:

Typically, vertical placement represents time and horizontal placement represents different objects.

– Collaboration Diagram

A collaboration diagram is an interaction diagram which shows the sequence of messages that implement an operation or a transaction. These diagrams show objects, their links, and their messages. They can also contain simple class instances and class utility instances. Each collaboration diagram provides a view of the interactions or structural relationships that occur between objects and object-like entities in the current model.

– State chart Diagram

State chart diagrams model the dynamic behavior of individual classes or any other kind of object. They show the sequences of states that an object goes through, the events that cause a transition from one state or activity to another, and the actions that result from a state or activity change.

State chart diagrams are closely related to activity diagrams. The main difference between the two diagrams is state chart diagrams are state centric, while activity diagrams are activity centric. A state chart diagram is typically used to model the discrete stages of an object’s lifetime, whereas an activity diagram is better suited to model the sequence of activities in a process.

– Activity Diagram

An activity represents the performance of “task” or “duty” in a workflow. It may also represent the execution of a statement in a procedure. An activity is similar to a state, but expresses the intent that there is no significant waiting (for events) in an activity.

– Class Diagram

A Class Specification displays and modifies class properties and relationships. Some of the information in the specification can also be displayed inside class icons.

If a field does not apply to a particular class type, the field is unavailable and you cannot add or change information in the field.

– Object Diagram

An Object Flow Specification allows you to display and modify the properties and relationships of an object flow on an activity diagram.

– Component Diagram

A component diagram shows the physical dependency relationships (mapping to a file system) between components—main programs, subprograms, packages, and tasks—and the arrangement of components into component packages.

– Deployment Diagram

A deployment diagram shows processors, devices, and connections. Each model contains a single deployment diagram that shows the connections between processors and devices, and the allocation of its processes to processors.

CONCLUSION:

We implemented the railway reservation sys using UML diagrams described above in rational rose.

Samba as Open Source Project

January 20, 2012 by ProjectsGeek Leave a Comment

To study Samba as an open source project for sharing

Samba

(Server Message Block Protocol )

Aim:

To study Samba as an open source project for sharing

Theory:

Samba on Linux is something completely different. Samba is an implementation of a Server Message Block (SMB) protocol server that can be run on almost every variant of UNIX in existence. Samba is an open source project, just like Linux. The entire code is written in C so it is easily portable to all flavors of UNIX. Samba is a tool for the peaceful coexistence of UNIX and Windows on the same network on the level of File and Print sharing over the NetBIOS protocol. It allows UNIX systems to move into a Windows “Network Neighborhood” without causing a mess. With Samba, UNIX servers are acting as any other Windows server, offering its resources to the SMB clients.

When the Samba package is installed, a default configuration file is installed in: etc/smb.conf

Creating shares

A simple share can be defined in the smb.conf file as follows:

[redbook]

comment = Redbook files

path = /redbook

browseable = yes

printable = no

writable = yes

write list = @users

Share permissions:

Although we can control the share permissions with share parameters, UNIX permissions are applied before share permissions. Make sure the UNIX permissions let the users access the share directory in the UNIX environment. When a user creates a new file on the shared directory, the default create mask used is 0744. For directory creation, the default create mask is 0755.

Creating shares for home directories

For handling home directories smb.conf has a special share section called [homes]. This share definition is used for all home directories, so we don’t need to create separate shares for each user. When a client requests a connection to a share, existing shares are scanned. If a match is found, that share is used. If no match is found, the requested share is treated as the username and validated by security. If the name exists and the

password is correct, a share with that name is created by cloning the [homes]

section. Home share definitions use the same parameters as normal shares. The

following is an example of a [homes] share definition in the smb.conf file:

[homes]

comment = Home Directories

path = %H

valid users = %S

browseable = no

writable = yes

create mode = 0700

directory mode = 0700

Parameter Description

%H This variable represents the home directory of the user.

%S The name of the current service, which is in the case of [home]

shares equal to username.

Creating a printer share

A Samba server uses the same procedure for [printer] shares as for [home] shares. The share definitions and user names are tested against the requested share name. If a match is found in the [printers] share section, a share with that name is cloned with the name of the requested service. The following is an example of a [printers] definition in the smb.conf file:

[printers]

comment = All Printers

path = /var/spool/samba

browseable = no

# Set public = yes to allow user ’guest account’ to print

guest ok = no

writable = no

printable = yes

create mask = 0700

Starting and stopping the Samba server

One can start the Samba server by executing the following

command:

/etc/rc.d/init.d/smb start

You will see:

Starting SMB services:

Starting NMB services:

Two daemons are started: smbd and nmbd. smbd is the Samba server and nmbd is the WINS server. The Samba server can be stopped by executing the command:

/etc/rc.d/init.d/smb stop

Whenever you modify the smb.conf configuration file you must restart the Samba server.

Creating a new share

1. Create the directory that will be used for the share. You can do this by

executing the command:

mkdir /home/public

2. Make sure that UNIX permissions are set correctly in the directory so that only

intended users have access rights to it.

Restarting the Samba server

To restart the Samba server, click the Status icon. Click Restart smbd. On this page you can also restart the WINS server by clicking Restart nmbd.

Conclusion:

Thus we have studied Samba, an implementation of a server message block protocol.

Create a Help file for an Application using Help Workshop

January 20, 2012 by ProjectsGeek Leave a Comment

Create a Help file for an Application using Help Workshop

HELP FILE USING HELP WORKSHOP

Aim: Create a Help file for an Application using Help Workshop

Theory: Help files can be created in HTML Help Workshop or in any other HTML authoring tool (for example, Front Page, Word, or a text editor). Then use the Answer Wizard Builder to create the AW file from the HTML or CHM Help content.

Creating custom Help topics involves these steps:

Ø Choosing a custom Help file format (HTML or CHM files).

Ø Creating the custom HTML topics.

If you want to create, format, and link HTML Help topics, you can use any HTML editor. If you want to create CHM files, install Microsoft HTML Help Workshop and compile your custom Help.

The format you choose for your Help files also depends on where you plan to store the files and how often you need to update the content.

Advantages of using HTML Help

Ø HTML Help files can be stored on either a Web server or a network file share. If they are stored on either of these, the following advantages apply:

Ø You can update Help content in one place and not have to worry about deploying or updating it on individual computers.

Ø No hard-disk space is required on a user’s computer.

Ø HTML Help does not require a hosted Web site to display Help content.

Disadvantages to using HTML Help files include the following:

Ø If you use HTML Help files hosted on a Web site, users must have access to the Web.

Ø A CHM file is a compressed HTML Help Meta file. You can take the equivalent of an entire Web site and compile it into a CHM. It uses a special technology to combine HTML files into one file with a special directory, index, and file structure similar to a compressed drive.

CHM files offer the following advantages over other file types:

Ø CHM files can be compressed, taking up less hard-disk space and providing more portability than an entire Web site.

Ø Users get faster results when the CHM file is stored locally.

Ø A single CHM file can contain an entire Web site of HTML files.

Ø Users do not need access to the Web or the network.

Disadvantages to using CHM files include the following:

Ø You are required to register the CHM before it can be used.

Ø However, once it is registered, it does not need to be registered again.

Ø You are required to recompile the file every time a change is made to the Help system.

Creating custom Help topics

After you choose what format you will use for your custom Help topics, you can begin creating your topics. Where you start the process of creating custom Help depends on what format your Help files are in. If you have CHM files or Help topics in Win Help format, you can import them into HTML Help Workshop.

Start with Win Help sources

Microsoft HTML Help Workshop can automatically convert the source files for these to HTML.

After converting your source files, use HTML Help Workshop to create a CHM file from the new HTML files.

Help files can be created in HTML Help Workshop or in any other HTML authoring tool (for example, Front Page, Word, or a text editor). Then use the Answer Wizard Builder to create the AW file from the HTML or CHM Help content.

Conclusion: Thus we have created a help file using HELP WORKSHOP

To study Berkeley Internet Name Domain (BIND) in LINUX

January 20, 2012 by ProjectsGeek Leave a Comment

To study Berkeley Internet Name Domain (BIND) in LINUX

BIND

AIM:

To study Berkeley Internet Name Domain (BIND) in LINUX

THEORY:

BIND (Berkeley Internet Name Domain, previously: Berkeley Internet Name Daemon) is the most commonly used DNS server on the Internet, especially on UNIX systems, where it is a de facto standard. Supported by Internet Systems Consortium. BIND was originally created by four graduate students with CSRG at the University of California, Berkeley and first released with 4.3BSD. Paul Vixie started maintaining it in 1988 while working for DEC.

A new version of BIND (BIND 9) was written from scratch in part to address the architectural difficulties with auditing the earlier BIND code bases, and also to support DNSSEC (DNS Security Extensions). Other important features of BIND 9 include: TSIG, DNS notify, nsupdate, IPv6, rndc flush, views, multiprocessor support, and improved portability architecture. It is commonly used on Linux systems.

History:

BIND was originally written in the early 1980s under a DARPA grant. In the mid-1980s, DEC employees took over BIND development. One of these employees was Paul Vixie, who continued to work on BIND after leaving DEC. He eventually helped start the ISC, which became the entity responsible for maintaining BIND.

The development of BIND 9 was done with a combination of commercial and military contracts. Most of the features of BIND 9 were funded by UNIX vendors who wanted to ensure that BIND stayed competitive with Microsoft’s DNS offerings; the DNSSEC features were funded by the US military who felt that DNS security was important.

Criticisms:

Like Sendmail, WU-FTPD, and other systems dating back to the earlier laissez-faire days of the Internet, BIND 4 and BIND 8 have had a large number of serious security vulnerabilities over the years. BIND 9, being a rewrite, has a much better security history.

GeoDNS:

GeoDNS is a 40-line patch to BIND to allow split horizon DNS, such that different requesters receive different responses, depending on proximity.

In this way if a website has, for example, a French server, a US server and a South Korean server, they can easily specify that people in Europe go to the French server, people in East Asia go to the Korean server and those in the rest of the world be served by the American server. This can give improved performance and potentially lower costs than a single hosting location or a round robin DNS setup.

As it is DNS based, it is much easier to deploy than BGP any cast. It does not require any support from the ISP and will not break existing connections when the server selected for a particular client changes. However, as it is not intimately tied into the network infrastructure it is likely to be less accurate at sending data to the nearest server.

CONCLUSION:

Thus we have successfully studied the application of BIND in Linux.

Creating SDI, MDI, Dialog Based Application

January 20, 2012 by ProjectsGeek Leave a Comment

Creating SDI, MDI, Dialog Based Application

AIM: Creating SDI, MDI, Dialog Based Application

THEORY:

Dialog Box : A dialog box is a specialized window that is used to provide feedback or collect input from the user. Dialog boxes come in all shapes and sizes, ranging from simple message boxes that display single lines of text to large dialog boxes that contain sophisticated controls. Dialog boxes are also used for one-way communication with a user, such as “splash screens” used to display copyright and startup information as a program is launched. Dialog boxes are sometimes used to notify the user about the progress of a lengthy operation.

SDI: Single Document Interface or SDI is a method of organizing graphical user interface applications into individual windows that the operating system’s window manager handles separately. A window does not have a “background” or “parent” window containing its menu or toolbar; instead, each window contains its own menu or toolbar. Applications which allow the editing of more than one document at a time.

MDI: Multiple Document Interface (MDI) are those whose windows reside under a single parent window as opposed to all windows being separate from each other.

Advantages

• Many child windows do not fill up the OS task management interface, as they are hierarchically organized. Users simply switch applications.

• With MDI a single menu bar and/or toolbar is shared between all child windows, reducing clutter and increasing efficient use of screen space.

• All child windows for an application can be hidden/shown/minimized/maximized as a whole.

Disadvantages

• Cannot be used successfully on desktops using multiple monitors.

• MDI can make it more difficult to work with several applications at once, by restricting the ways in which windows from multiple applications can be arranged together.

• The shared menu changes, which may cause confusion to some users.

Creating SDI Application Using Visual C++:

The AppWizard In Visual C++, provides the facility of creating MDI or SDI applications. To create a simple SDI program, select Single Document on the opening MFC AppWizard screen. AppWizard displays six Wizard pages filled with default information for a typical SDI program. You can tell AppWizard to create the project for you by pressing the button labeled Finish. AppWizard will create several classes and files for you and create a project that you can use to manage the process of compiling the program AppWizard creates these classes for a program named Hello:

• CHelloApp: Derived from CWinApp, the application class for the program

• CHelloDoc: The program’s document class, derived from CDocument

• CHelloView: The program’s view class derived from CView

• CMainFrame: The main frame class for the program

In addition, AppWizard creates several files that are not used for C++ classes. Some of these files are

• hello.aps: A file that contains a precompiled version of the program’s resources

• hello.clw: A file that contains information used by ClassWizard

• hello.rc: A resource file that contains information about dialog boxes, menus, and other resources used by the program

• resource.h: A header file containing declarations needed for the resources used by the program

• hello.dsp and hello.dsw: The project and workspace files used by Developer Studio to build the program

• stdafx.cpp: A file included in all AppWizard programs that includes all the standard include files

• stdafx.h: A standard header file included in all AppWizard programs that is used to include other files that are included in the precompiled headers

Creating MDI Application Using Visual C++:

You can use AppWizard to create an MDI application almost as easily as an SDI.

The basic difference between an SDI application and an MDI application is that an MDI application must manage multiple documents and, usually, multiple views. The SDI application uses only a single document, and normally only a single view. Both SDI and MDI applications use an object called a document template to create a relationship between a view, a document, and a frame class, as well as an identifier used for the program’s menu, icon, and other resources. You use the CSingleDocTemplate class for SDI applications and the CMultiDocTemplate class for MDI applications. These two classes share a common base class, CDocTemplate.

To study KDE desktop Environment.

January 20, 2012 by ProjectsGeek Leave a Comment

To study KDE desktop Environment.

AIM: To study KDE desktop Environment.

THEORY:

KDE was founded in 1996 by Matthias Ettrich. KDE is a network transparent contemporary desktop environment for UNIX workstations. KDE seeks to fill the need for an easy to use desktop for Unix workstations, similar to the desktop environments found under the MacOS or Microsoft Windows.

The traditional X11 desktops had many drawbacks:

No easy dialog based desktop configuration
No common application development framework or application help system
Lack of network transparency on the application level
Authoring of X11 applications extremely difficult and tedious

To the user KDE brings among other things:

A good looking contemporary desktop exhibiting complete network transparency.
An integrated help system allowing for convenient, consistent access to help on the use of the KDE desktop and its applications
Consistent look and feel of all KDE applications
Standardized menu and toolbars, key bindings, color-schemes, etc.
Internationalization: KDE is available in more than 50 languages
Centralized consisted dialog driven desktop configuration
A great number of useful KDE applications

The KDE Project has developed a first rate compound document application framework, implementing the latest advances in framework technology and thus positioning itself in direct competition to popular development frameworks.

Leveraging the KDE application development framework a great number of applications have been built for the K Desktop Environment. A selection of those applications is contained in the KDE base distribution. At this moment KDE is developing an office application suite based on KDE’s KParts technology consisting of a spread-sheet, a presentation application, an organizer, a news client and more.

Major KDE applications are Amarok (audio player),K3b (CD and DVD burning), Kate(text editor), Kmail (email client), Konsole (terminal emulator),Kopete (instant messaging), Kword, Kspread, Kplayer and TaskJuggler (Project management software)

KDE FEATURES

KDE can be viewed either as a user desktop or as a development platform for applications.

The Kdesktop Environment

Konqueror Browser
Konqueror is KDE’s next-generation web browser, file manager and document viewer. The standards-compliant Konqueror combines the features and functionality of Internet Explorer/Netscape Communicator and Windows Explorer. Konqueror supports the full gamut of current Internet technologies.
KIO Network Transparency
In addition, KIO’s network transparency offers seamless support for accessing or browsing files on GNU/Linux, NFS shares, MS Windows SMB shares, HTTP pages, FTP directories and LDAP directories. The modular, plug-in nature of KDE’s file architecture makes it simple to add additional protocols.
aRts Multimedia Architecture
KDE 2.0 introduced a new multimedia architecture based on aRts, the Analog Realtime Synthesizer. ARts enables playing multiple audio or video streams concurrently, whether on the desktop or over a network.

The K Development Environment

KDE offers developers a rich set of major technologies. Chief among these are the Desktop COmmunication Protocol (DCOP), the I/O libraries (KIO), the component object model (KParts), an XML-based GUI class, and a standards-compliant HTML rendering engine (KHTML).
DCOP Messaging: DCOP is a client-to-client communications protocol. The protocol supports both message passing and remote procedure calls.
KIO Network Technology: KIO implements application I/O in a separate process to enable a non-blocking GUI without the use of threads. The class is network transparent. Its modular and extensible design permits developers to “drop in” additional protocols.
KParts Components: KParts, KDE’s component object model, allows an application to embed another within itself. The technology handles all aspects of the embedding.This technology is used extensively by the KOffice suite and Konqueror.
XML GUI Builder: The XML GUI employs XML to create and position menus, toolbars and possibly other aspects of the GUI. This technology offers developers and users the advantage of simplified configurability of these user interface elements.
KHTML Rendering Engine: KHTML is an HTML 4.0 compliant rendering and drawing engine. The class supports a full gamut of internet technologies. The KHTML class can easily be used by an application as either a widget or as a component .

CONCLUSION: Here by we have successfully studied the KDE desktop Environment.

Railway Reservation System Rational Rose UML Diagrams

Samba as Open Source Project

Create a Help file for an Application using Help Workshop

To study Berkeley Internet Name Domain (BIND) in LINUX

Creating SDI, MDI, Dialog Based Application

To study KDE desktop Environment.

The Kdesktop Environment

The K Development Environment

Download Java Project

Download Visual Basic Projects

Download .Net Projects

Download VB Projects

Download C++ Projects

Download NodeJs Projects

Download School Projects

Download School Projects

Ask Questions - Forum

Latest Projects Ideas

Assembly Codes

Datastructure Assignments

Computer Graphics Lab

Operating system Lab

ProjectsGeek

Other Projects to Try:

Other Projects to Try:

Other Projects to Try:

Other Projects to Try:

Other Projects to Try:

The Kdesktop Environment

The K Development Environment

Other Projects to Try:

Footer