Académique Documents
Professionnel Documents
Culture Documents
Irfan khan
2. Objectives
Unconstrained Demand
Shipment dimensions cannot be given accurately at the time the booking
request is made. Often the actual dimensions received at tender do not
anyway become part of any permanent record. Since flights will reach
their volume limitations before they hit weight limits on some sectors,
some heuristic calculation, such as a density code, is needed to forecast
likely volumes. The first step is to use historic data to gauge the total
market demand regardless of the airline’s available capacity. This
unconstrained demand is set for each product type by origin and
destination (O&D), day of week, time of day.
Most cargo customers, unlike passengers, are more concerned with
speed and reliability than with routings. That gives the cargo carrier an
opportunity to route shipments away from congested bottlenecks and
give a better spread of revenues across the network.
For example, a booking request comes through the reservation
center to ship between a hub airport and major destination. The route is
consistently oversold, so the bid rate is high. The router will evaluate
alternative feasible routes which meet both the shipper’s requirements
and the carrier’s business rules.
Removing The Politics
Effectively, the cargo revenue optimization system will allow decisions
to be taken that make optimal use of another, then the choice will not be
made. There will be times when the users override the system’s
decisions, but overall it provides the basis for objective network-wide
decision-making, taking away the guesswork and the politics.
Tools
Front End Visual Studio 2010
Back End Ms Access 2007
4.SYSTEM ANALYSIS
Preliminary Investigation:
A request to take assistance from information system can be made
for many reasons, but in each case some one in the organization
initiate the request. When the request is made, the first system activity
the preliminary investigation begins. This activity has three parts:
Request clarification
Feasible Study
Request approval
Many requests from employees and users in the organization are
not clearly defined. Therefore, it becomes necessary that project
request must be examined and clarified properly before considering
systems investigation.
The feasibility study is carried out by a small group of people who are
familiar with information system techniques, understand the parts of the
business or organization that will be involved or affected by the project,
and are skilled in the system analysis and design process.
Economic feasibility:
1. Development costs
2. Operating costs
Legal feasibility
Operational feasibility
This approach may work well for small systems but is very
unsatisfactory for larger systems. As the code size increases, the
understandability and maintainability of the system decreases.
The simplest, oldest and most widely used process model for
software designing is the waterfall model. It was proposed by
Royce in 1970.
The essence of this software paradigm is that the process of
software designing consists of linear set of distinct phases.
1. Technical feasibility
2. Economic Feasibility
3. Motivational Feasibility
4. Schedule Feasibility
5. Operational Feasibility
Advantages
Disadvantages
Disadvantages
VB
VS.NET
Microsoft Access 2007
DESIGNING TOOL: Visual Studio Tools
7.2 Minimum Hardware requirements are:
The strategy for the design of the object that manage concurrent task are
as follows:
Metadata
All CIL is self-describing through .NET metadata. The CLR checks the
metadata to ensure that the correct method is called. Metadata is usually
generated by language compilers but developers can create their own
metadata through custom attributes. Metadata contains information
about the assembly, and is also used to implement the reflective
programming capabilities of .NET Framework.
Security
.NET has its own security mechanism with two general features: Code
Access Security (CAS), and validation and verification.
When an assembly is loaded the CLR performs various tests. Two such
tests are validation and verification. During validation the CLR checks
that the assembly contains valid metadata and CIL, and whether the
internal tables are correct. Verification is not so exact. The verification
mechanism checks to see if the code does anything that is 'unsafe'. ..NET
Framework uses AppDomains as a mechanism for isolating code
running in a process. AppDomains can be created and code loaded into
or unloaded from them independent of other AppDomains. This helps
increase the fault tolerance of the application, as faults or crashes in one
AppDomains do not affect rest of the application
Class library
Namespaces in the BCL
System.Data.OleDB
System. CodeDom
System. Collections
System. Diagnostics
System. Globalization
System. IO
System. Resources
System. Text
System. Text.RegularExpressions
See also: Base Class Library and Framework Class Library
The .NET Framework includes a set of standard class libraries. The class
library is organized in a hierarchy of namespaces. Most of the built in
APIs are part of either System.* or Microsoft.* namespaces. These class
libraries implement a large number of common functions, such as file
reading and writing, graphic rendering, database interaction, and XML
document manipulation, among others. The .NET class libraries are
available to all .NET languages. The .NET Framework class library is
divided into two parts: the Base Class Library and the Framework Class
Library.
The Base Class Library (BCL) includes a small subset of the entire
class library and is the core set of classes that serve as the basic API of
the Common Language Runtime.[9] The classes in mscorlib.dll and some
of the classes in System.dll and System.core.dll are considered to be a
part of the BCL. The BCL classes are available in both .NET
Framework as well as its alternative implementations including .NET
Compact Framework, Microsoft Silverlight and Mono.
Imports System.Data
Imports System.Data.OleDb
Public Class Form5
Dim mycn As New OleDbConnection
Dim mycm As New OleDbCommand
Dim myad As New OleDbDataAdapter
Imports System.Data
Imports System.Data.OleDb
Public Class Form2
Dim mycn As New OleDbConnection
Dim mycm As New OleDbCommand
Dim myad As New OleDbDataAdapter
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Me.Close()
End Sub
mycn.Close()
End If
End Sub
End Class
Imports System.Data
Imports System.Data.OleDb
End Sub
End Sub
End Class
End If
End Sub
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
'Dim stri As String
'stri = InputBox("Enter the file name:")
RichTextBox1.SaveFile(TextBox3.Text)
End Sub
' End If
End Sub
' End If
' End If
' End Sub
mycn.Close()
End If
End Sub
End Class
Imports System.Data
Imports System.Data.OleDb
End Sub
End Class
End If
End Sub
' End If
End Sub
' End If
' End If
' End Sub
End Sub
End Sub
End Sub
End Sub
a = Val(TextBox1.Text)
b = Val(TextBox2.Text)
If op = 1 Then
TextBox2.Text = a * b
ElseIf op = 2 Then
TextBox2.Text = a + b
ElseIf op = 3 Then
TextBox2.Text = b - a
End If
TextBox1.Text = ""
TextBox1.Focus()
If TextBox2.Text = "" Then
op = 0
End If
Return 0
End Function
End Sub
End Class
Imports System.Data
Imports System.Data.OleDb
Public Class Form5
Dim mycn As New OleDbConnection
Dim mycm As New OleDbCommand
Dim myad As New OleDbDataAdapter
End Class
11. Code Optimization
Although the word "optimization" shares the same root as "optimal," it is rare for
the process of optimization to produce a truly optimal system. The optimized
system will typically only be optimal in one application or for one audience. One
might reduce the amount of time that a program takes to perform some task at the
price of making it consume more memory. In an application where memory space
is at a premium, one might deliberately choose a slower algorithm in order to use
less memory. Often there is no “one size fits all” design which works well in all
cases, so engineers make trade-offs to optimize the attributes of greatest interest.
Additionally, the effort required to make a piece of software completely optimal—
incapable of any further improvement— is almost always more than is reasonable
for the benefits that would be accrued; so the process of optimization may be
halted before a completely optimal solution has been reached. Fortunately, it is
often the case that the greatest improvements come early in the process.
12. Implementation and Maintenance
12.1 Implementation
The implementation of product software, as the final link in the deployment chain
of software production, is in a financial perspective of a major issue.
In general, differences are identified on a scale of size (bigger, smaller, more, less).
An example of the “smaller” product software is the implementation of an office
package. However there could be a lot of end users in an organization, the impact
on the tasks and responsibilities of the end users will not be too intense, as the
daily workflow of the end user is not changing significantly. An example of
“larger” product software is the implementation of an Enterprise Resource
Planning system. The implementation requires in-depth insights on the architecture
of the organization as well as of the product itself, before it can be aligned.
12.2 Maintenance
TESTING OBJECTIVES
Our objective is to design tests that systematically uncover different classes
of error and to do so with minimum amount of time and effort. Data collected, as
testing is conducted provides a good indication of software reliability and quality
as a whole. A successful test is one that uncovers an as yet undiscovered error. A
good test case is one that has a high probability of finding an as yet undiscovered
error.
TESTING APPROACHES
The two strategies we used to test our software are
1. Unit Testing
2. Integration Testing
UNIT TESTING :
Unit testing focuses on verification of the efforts on the smallest unit of
software design-the module. The unit test is always White Box oriented, and the
steps can be conducted in parallel for multiple, modules. In our modules, different
testing at module level is shown above in Test Reports
14.VALIDATION CHECK
INTEGRATION TESTING :
Integration testing addresses the issues associated with the dual problems of
verification and program construction. Black Box test case design techniques are
the most prevalent during integration, although a limited amount of White Box
Testing may be used to ensure coverage of Major control paths.
15. PERT CHART & GANTT CHART
Program Evaluation and Review Technique (PERT) and Critical Path Method
(CPM) are the project scheduling techniques that can be applied to software
development. Both technique are driven by information already gathered in earlier
project planning activities:
Estimation of effort
A decomposition of the product function
The solution of the appropriate model and task set
Decomposition of tasks
Both PERT and CPM provide quantitative tools that allow the software planning to
determine critical path – the claim of task that determined the duration of the
project establish “most likely” times estimates for individual tasks by applying
statically models: and Calculation “boundary times” that define a time “window”
for a particular task.
Both PERT and CPM have been implemented in a wide verity of automated tools
that are available for the personal computer. Such tools are easy to use and make
the scheduling methods described previously available to every software project
manager.
15.2 GANTT CHART :
When creating a software project schedule, the planner begins with a set of tasks
(the work break down structure). If automated tools are used, the work break down
is input as a task network or task outline. Efforts, duration, and start date are then
input for each task. In addition, task may be assigned to specific individuals.
As a sequence of this input, a timeline chart, also called a Gantt chart, is generated.
A Gantt chart can be developed for the entire project. Alternatively, separated it
depicts a part of a software project schedule that emphasizes the concept scooping
task for a new word processing software project. All project tasks (for concept
scooping) are listed in the left hand column. The horizontal bars occur at the same
time on the calendar, task concurrency is implied. The diamonds indicate
milestones.
Once the information necessary for the generation of the Gantt chart has been
input, the major of software project scheduling tools produce project tables a
tabular listing of all project tasks, their planned and actual start and end dates, and
a verity of related information. Used in conjunction with the Gantt Chart project
tables enable the project manager to track progress.
Task name/weak-> 1 2 3 4 5 6 7 8
|
1.Initial planning
2.Concept generation
3.Project outline
4.Module design
phase1
5.Module design
phase2
6.Module design
phase3
7.Module
development
8.Module integration
9.Testing
10.Documentation
11.Product delivery
CONCLUSION & FUTURE SCOPE
CONCLUSION
The project was aimed at understanding the programming methodology
of VB.NET and it’s versatile programming environment. The report is
aimed to provide a clearer understanding of the .NET Technology,
encompassing and elaborating the various elements of the programming
language. This literature also describes the usage and implementation of
the technology with the application software, supporting distributed
systems and information transfer over the internet securely.
FUTURE SCOPE
GC Garbage Collection