Wrox Press – Beginning Linux Programming – 3rd Edition
Student Database using Rational Rose UML diagrams
To implement student database 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 can be useful at any point in the application development process.
• Initial Design Work (Requirement Analysis and Definition)
– Use Cases
– Class Diagrams
– Sequence Diagram
–
–
– Generality is Good in early design.
•
• Refinement of Early Models (System & Software Design)
• Introduced in Middle of Project
•
– Rational Rose includes tools for reverse engineering as well as forward engineering of classes and component architectures.
–
– You can gain valuable insights to your actual constructed architecture and pinpoint deviations from the original design.
–
– Rose offers a fast way for clients and new employees to become familiar with system internals
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.
AIM: To implement student database 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.
WHEN TO USE RATIONAL ROSE:
• Modeling can be useful at any point in the application development process.
• Initial Design Work (Requirement Analysis and Definition)
– Use Cases
– Class Diagrams
– Sequence Diagram
–
–
– Generality is Good in early design.
•
• Refinement of Early Models (System & Software Design)
• Introduced in Middle of Project
•
– Rational Rose includes tools for reverse engineering as well as forward engineering of classes and component architectures.
–
– You can gain valuable insights to your actual constructed architecture and pinpoint deviations from the original design.
–
– Rose offers a fast way for clients and new employees to become familiar with system internals
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 classes with 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, 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
THE DIFFERENT VIEWS: There are five different views
-Logical view
.analysts/designers structure
-Process view
.System integrators performance, scalability, throughput
-Implementation view
.Programmers software management
-Deployment view
.System engineering system topology delivery, installation communication
-Use case view
.End user functionality
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 have implemented student database by making use of Rational Rose software .
To study about the Zope as a open source web application server.
To study about the Zope as a open source web application server.
ZOPE
Aim – To study about the Zope as a open source web application server.
Theory – Zope is an open source web application server primarily written in the python programming language. It features a transactional object database which can store not only content and custom data but also dynamic HTML templates, scripts, a search engine, and relational database (RDBMS) connections and code. It features a strong through-the-web development model. Built around the concept of “safe delegation of control”, Zope’s security architecture also allows you to turn control over parts of a web site to other organizations or individuals. The transactional model applies not only to Zope’s object database, but to many relational database connectors as well, allowing for strong data integrity. This transaction model happens automatically, ensuring that all data is successfully stored in connected data sources by the time a response is returned to a web browser or other client.
Unlike common file-based Web templating systems such as ASP or PHP, Zope is a highly object-oriented Web development platform that covers much more of the problem domain for Web application developers. It provides clean separation of data, logic and presentation, an extensible set of built-in objects and a powerful integrated security model. The Zope infrastructure relieves the developer of most of the onerous details of Web application development such as data persistence, data integrity and access control, allowing you to focus on the problem at hand.
Who uses Zope?
Zope users include Viacom, Boston.com, SGI, AARP, Bell Atlantic Mobile, Red Hat, NASA, The US navy, Digital Garage and Storm Linux.
Features of Zope:
Zope provides all of the necessary tools to integrate data and content from nearly any source into powerful, coherent and maintainable Web applications:
· Through-the-Web management
· Integrated access control
· Content management
· Enterprise data access
· Built-in search tools
· Powerful data sharing
· Safe delegation
Application of Zope:
1. The Web Application Platform
2. XML Support
3. Data Access
4. Data Sharing
5. Integrated searching
New Versions of Zope:
A new version of Zope, Zope 3, has been in development for some years. Zope 2 has proven itself as a useful framework for web applications development, but its use revealed some shortcomings. To name a few, creating Zope 2 products involves copying a lot of boilerplate code – “magic” code – that just has to be there, and the built-in management interface is difficult to modify or replace. Zope 3 is a rewrite of the software that attempts to address these shortcomings while retaining the advantages of Zope that led to its popularity. Zope 3 is based on a component architecture that makes it easy to mix software components of various origins written in Python. The first production release of the new software, Zope X3 3.0.0, was released on November 6, 2004. The current production release, Zope 3.3.0, was released on September 27, 2006. We can download it from internet.
Conclusion:
So we have studied about the Zope, its features, its application and how it is useful to help us in computer field and how to get it.
Hotel Management Project Rational Rose UML Diagrams
Hotel Management Project Rational Rose UML Diagrams
AIM: IMPLEMENTATION OF HOTEL MANAGEMENT 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 hotel management using UML diagrams described above in rational rose.
Study of Python (programming language)
Study of Python (programming language)
Aim: Study of Python (programming language)
THEORY:
a) Introduction:
Python is an object-oriented high-level programming language, first released by Guido van Rossum in 1991. Python has a fully dynamic type system and uses automatic memory management; it is thus similar to Perl, Ruby, Scheme, Smalltalk, and Tcl.
The philosophy behind Python is noteworthy among high-level programming languages because it emphasizes the importance of programmer effort over computer effort, and because it rejects more arcane language features, prioritizing readability over speed or expressiveness. Python is often characterized as minimalist, although this only applies to the core language’s syntax and semantics; the standard library provides the language with a large number of additional libraries and extensions.
b) Syntax and Semantics:
Python was designed to be a highly readable language. It aims toward an uncluttered visual layout, uses English keywords frequently where other languages use punctuation, and has notably fewer syntactic constructions than many structured languages such as C, Perl, or Pascal. Python uses indentation, rather than curly braces, to delimit statement blocks. An increase in indentation comes after certain statements; a decrease in indentation signifies the end of the current block. Python’s statements include:
* The if statement, which conditionally executes a block of code, along with else and elif (a contraction of else-if).
* The while statement, which runs a block of code until a condition is False.
* The for statement, which iterates over an iterable, capturing each element to a local variable for use by the attached block.
* The class statement, which executes a block of code and attaches its local namespace to a class, for use in object oriented programming.
* The def statement, which defines a function.
Each statement has its own semantics:
for e.g. the def statement does not execute its block immediately, unlike most other statements.
CPython does not support continuations, and according to Guido van Rossum, never will. However, better support for co routine-like functionality is provided in 2.5, by extending Python’s generators. Prior to 2.5, generators were lazy iterators — information was passed monodirectionally out of the generator.
c) Implementation :
The mainstream Python implementation, also known as CPython, is written in C, and is distributed with a large standard library written in a mixture of C and Python. CPython ships for a large number of supported platforms, including most modern Unices and Microsoft Windows; see the full list for more. The code base is written in compliant C89, and is easily portable to most operating systems, especially POSIX-compliant or Unix-like operating systems.
Python was originally developed as a scripting language for the Amoeba distributed operating system which was capable of making system calls; however, that version is no longer maintained. CPython was intended from almost its very conception to be cross-platform; its use and development on esoteric platforms such as Amoeba alongside more conventional ones like Unix or Macintosh has greatly helped in this regard.
Stack less Python is a significant fork of CPython that implements micro threads. It can be expected to run on approximately the same platforms that CPython runs on.
There are two other major implementations: Jython for the Java platform and Iron Python for the .NET platform. PyPy is an experimental self-hosting implementation of Python, in Python, that can output a variety of types of byte code and object code. Several other experimental implementations have been created, but have not yet been widely adopted.
Several programs exist to package Python programs into standalone executables, including py2exe and py2app.
Many Python programs can run on different Python implementations, on such disparate operating systems and execution environments, without change. In the case of the implementations running on top of the Java virtual machine or the Common Language Runtime, the platform-independence of these systems is harnessed by their respective Python implementation.
Many third-party libraries for Python (and even some first-party ones) are only available on Windows, Linux, BSD, and Mac OS X
Conclusion:
Thus we have studied Python (programming language) successfully
