Sangu Record

8/6/2019 Sangu Record

1/59

1COURIER PARCEL MANAGEMENT

1. AbstractThe courier parcel industry is the fastest growing industry on the roads and is looking

for expanding and improving their services across all sectors.

In pursuit of the above goals, courier companies need computerized process support.

All basic support system are already computerized by most such companies. But,

one feature that most software packages miss out is management of parcel information and

tracking of the same by clients.

BITM, BELLARY DEPARTMENT OF MCA 2010-2011


2/59


2. Introduction

2.1 Project Description

The project entitled as COURIER MANAGEMENT SYSTEM is developed to transfer

the some important and personal messages from one place to another. So this is used for

global connections. Immediate processing will be done. The important notification of this

project is to maintain a high level of tradings .

Today people like to send the letter and other things with the help of this courier. Because it

is maintaining the timings and the minimum expenditures. The international and cargo

trading can be done in this courier. This project is provided for making this work as

computerized one. So the manual workings can be reduced by this valuable processing.

A courier is a person or a company who delivers messages, packages, and mail.

Couriers are distinguished from ordinary mail services by features such as speed, security,

tracking, signature, specialization and individualization of services, and committed delivery

times, which are optional for most everyday mail services. As a premium service, couriers

are usually more expensive than usual mail services, and their use is typically restricted to

packages where one or more of these features are considered important enough to warrant

the cost.

Different courier services operate on all scales, from within specific towns or cities,

to regional, national and global services. The world's largest courier companies are DHL,

FedEx, TNT N.V., UPS, andAramex.[citation needed] These offer services worldwide,

typically via a hub and spoke model .



3/59


The core of the system is used to categorize to various modules:

Parcel Management

Customer Management

Bills Management

Branch Management

2.1.1 Parcel Management

The purpose of the courier Parcel details is to maintain the data about the

transformation of the couriers from one place to another. So the courier return and courier

lost courier dispatch details can be viewed easily and the processing of this automation can

be obtained successfully.

2.1.2 Customer Management

The purpose of account holder is to maintain the account of the regular

customer and other details of the customer. So the staff working in the courier office can

view the details without any interruption.



4/59


2.1.3 Bills Management

This detail is provided for the allowance of the workingmembers, travelling charges, Vehicle Allowances are maintained in this form. According to

the changes of data it can be updated.

2.1.4 Branch Management

The branch details are used to have the records about the branches provided in

different places and in various locations. So the urgent information can be transferred very

quickly by viewing the address of the courier branch.

EXISTING SYSTEM

The system study phase studies the problem, identifies alternate

Solutions evaluate those solutions and finally recommends the best solution.

The system study gives the structure & function of the system.The system

Study can be performed only on an existing system.

The system study gives an idea of then user requirements. A detailed

system study is an essential for developing an efficient system.The techniques used are:



5/59


Limitations of existing system:

At present, the requirements of the system are done manually and hence

there are number of limitations .

The various activities are carried out by different section depending on their

activity.

The various status information is maintained in books and files, which is

very difficult.

Reports are produced by manual processing, that will be an unformatted

manual and unreliable.

Data security is less.

Calculations are done manually.

PROPOSED SYSTEM:

The proposed s system tries to avoid the problems arised in the existing

system. It automates the entire process of embroiding managementSystem. It should have a

provision to maintain master entries, provision to Prepare inward, invoice etc. It should also

provide often needed reports toSatisfy the need of the concern.

MERITS OF PROPOSED SYSTEM:

As the proposed system is system oriented it is faster than the manual process

It also minimizes the errors in the data entry.

It improves customer satisfaction due to the improvement in the stitches.

It reduces the burden of staff.



6/59




7/59


2.2 Object Oriented Methodology

There are many ways to look at a problem to be solved using a software-based solution.

One widely used approach to problem solving takes an object-oriented viewpoint. The

problem domain is characterized as a set of objects that have specific attributes and

behaviors. The objects are manipulated with a collection of functions (called methods,

operations, or services) and communicate with one another through a messaging protocol.

Objects are categorized into classes and subclasses.

An object encapsulates both data and the processing that is applied to the data. This

important characteristic enables classes of objects to be built and inherently leads to

libraries of reusable classes and objects. Because reuse is a critically important attribute of

modern software engineering, the object-oriented paradigm is attractive to many software

development organizations. In addition, the software components derived using the object-

oriented paradigm exhibit design characteristics (e.g., functional independence, information

hiding) that are associated with high-quality software.

Object-oriented software engineering follows the same steps as conventional

approaches. Analysis identifies objects and classes that are relevant to the problem domain;

design provides the architecture, interface, and component-level detail; implementation

(using an object-oriented language) transforms design into code; and testing exercises the

object-oriented architecture, interfaces and components.

A set of object oriented models is produced. These models describe the

requirements, design, code, and test process for a system or product.



8/59


2.3 Introduction to OMT

The object-modeling technique (OMT) is an object modeling language for software

modeling and designing. It was developed circa 1991 by Rumbaugh, Blaha, Premerlani,

Eddy and Lorensen as a method to develop object-oriented systems, and to support object-

oriented programming.

We will be using this methodology to develop this project.

OMT was developed as an approach to software development. The purposes of

modeling according to Raumbaugh (1991) are:

Testing physical entities before building them (simulation),

Communication with customers,

Visualization (alternative presentation of information), and

Reduction of complexity.

OMT has proposed three main types of models:

Object model: The object model represents the static and most stable phenomena in

the modeled domain. Main concepts are classes and associations, with attributes and

operations. Aggregation and generalization (with multiple inheritance) are

predefined relationships.

Dynamic model: The dynamic model represents a state/transition view on the model.

Main concepts are states, transitions between states, and events to trigger transitions.

Actions can be modeled as occurring within states. Generalization and aggregation

(concurrency) are predefined relationships.



9/59


Functional model: The functional model handles the process perspective of the

model, corresponding roughly to data flow diagrams. Main concepts are process,

data store, data flow, and actors.

OMT is a predecessor of the Unified Modeling Language (UML). Many OMT modeling

elements are common to UML.

Main phases of OMT

The Object Modeling Technique (OMT) software engineering methodology is another

well known example of a software engineering methodology. The OMT software

engineering methodology deals with object-oriented development in the analysis and design

phases.

The analysis phase starts with a problem statement which includes a list of goals and a

definitive enumeration of key concepts within a domain. This problem statement is then

expanded into three views, or models: an object model, a dynamic model, and a functional

model. The object model represents the artifacts of the system. The dynamic model

represents the interaction between these artifacts represented as events, states, and

transitions. The functional model represents the methods of the system from the perspective

of data flow. The analysis phase generates object-model diagrams, state diagrams, event-

flow diagrams, and data-flow diagrams. The analysis phase is now complete.

The system design phase follows the analysis phase. Here the overall architecture is

established. First the system is organized into subsystems which are then allocated to

processes and tasks, taking into account concurrency and collaboration. Then persistent data



10/59


storage is established along with a strategy to manage shared-global information. Next,

boundary situations are examined to help guide trade-off priorities.

The object design phase follows the system design phase. Here the implementation plan

is established. Object classes are established along with their algorithms with special

attention to the optimization of the path to persistent data. Issues of inheritance,

associations, aggregation, and default values are examined.

The OMT software engineering methodology is sequential in the sense that first comes

analysis, followed by design. In each phase, a cyclical approach is taken among the smaller

steps. The OMT is very much like the Booch methodology where emphasis is placed on the

analysis and design phases for initial product delivery. Both the OMT and Booch do not

emphasize implementation, testing, or other life cycle stages.

OMT object diagram is illustrated below:



11/59


OMT state diagram is illustrated below:

3. Literature Survey

3.1 The .NET Technology



12/59


The .NET Framework is a rather radical and brute-force approach to making our lives

easier. It is a completely new model for building systems on the Windows family of

operating systems, and additional (nonMicrosoft) operating systems now and in the future.

Here is a quick rundown of some core features provided courtesy of .NET:

Full interoperability with existing Win32 code. This is (of course) a good thing.

Existing COM binaries can commingle (i.e., interop) with newer .NET binaries and

vice versa. Also, PInvoke (Platform Invocation) allows you to invoke invoke raw C-

based functions (such as the Win32 API) from managed code.

Complete and total language integration. Unlike classic COM, .NET supports cross-

language inheritance, cross-language exception handling, and crosslanguage

debugging.

A common runtime engine shared by all .NET-aware languages. One aspect of this

engine is a well defined set of types that each .NET-aware language "understands."

A base class library that provides shelter from the complexities of raw API calls, and

offers a consistent object model used by all .NET-aware languages.

No more COM plumbing! IClassFactory, IUnknown, IDispatch, IDL code, and the

evil VARIANTcompliant data types (BSTR, SAFEARRAY, and so forth) have no

place in a native .NET binary.

A truly simplified deployment model. Under .NET, there is no need to register a

binary unit into the system registry. Furthermore, the .NET runtime allows multiple

versions of the same *.dll to exist in harmony on a single machine (using an

approach termed "side-by-side execution").



13/59


Figure 1 - Building Blocks of the .NET Platform

.NET applications are constructed by piecing together any number of assemblies.

Simply put, an assembly is nothing more than a versioned, self-describing binary (*.dll or

*.exe) containing some collection of types (classes, interfaces, structures, etc.) and optional

resources (images, string tables, etc).

A .NET binary consists of five major elements:

A standard Windows file header

A CLR header that marks the file as a managed module

CIL code

Type metadata

The assembly manifest

Given that .NET is such a radical departure from the current thoughts of the day,

Microsoft has developed a new programming language (C#) specifically for this new

platform. C# is a programming language that looks very similar (but not identical) to the

syntax of Java. For example, like Java, a C# class definition is contained within a single-

source code file (*.cs) rather than the C++-centric view of splitting a class definition into

discrete header (*.h) and implementation (*.cpp) files. However, to call C# a Java rip-off is

inaccurate. Both C# and Java are based on the syntactical constructs of C++. Just as Java is

in many ways a cleaned-up version of C++, C# can be viewed as a cleaned-up version of

Javaafter all, they are all in the same family of languages.



14/59


The truth of the matter is that many of C#'s syntactic constructs are modeled after

various aspects of Visual Basic and C++ itself. For example, like Visual Basic, C# supports

the notion of formal class properties as well the declaration of methods that take a varying

number of arguments (via parameter arrays). Like C++, C# allows you to overload

operators on your custom types, as well as create structures (value types) and enumerations

(as you may know, Java lacks all of these features).

Given that C# is a hybrid of numerous languages, the result is a product that is as

syntactically clean (if not cleaner) than Java, just about as simple as Visual Basic 6.0, and

provides just about as much power and flexibility as C++ (without the associated ugly bits).

In a nutshell, the C# languages offers the following features (many of which are shared by

other .NET-aware programming languages):

No pointers required! C# programs typically have no need for direct pointer

manipulation (although you are free to drop down to that level if you desire).

Automatic memory management. Given this, C# does not support a "delete"

keyword.

Formal syntactic constructs for enumerations, structures, and class properties.

The C++-like ability to overload operators for a custom type, without the complexity(i.e., making sure to "return *this to allow chaining" is not your problem).

Full support for interface-based programming techniques. However, unlike classic

COM, the interface is not the only way to manipulate types between binaries. .NET

supports true object references that can be passed between boundaries (by reference

or by value).

Full support for aspect-based programming techniques via attributes. This brand of development allows you to assign characteristics to types and their members (much

like COM IDL) to further qualify the behavior of a given entity.

Perhaps the most important point to understand about the C# language shipped with

the .NET platform is that it can only produce code that can execute within the .NET runtime

(you could never use C# to build a classic COM server or a traditional Win32 API

application). Officially speaking, the term used to describe the code targeting the .NET

runtime is managed code. The binary unit that contains the managed code is termed an

assembly.BITM, BELLARY DEPARTMENT OF MCA 2010-

2011


15/59


3.2 Visual C#

Visual C# Express Edition contains a complete C# compiler and world-class

development tools. You have everything that you need in order to create state-of-the-art

applications and utilities.

Microsoft Visual C# Express Edition is a subset of Visual C# 2008, and provides many

powerful features:

Fully ANSI-compliant C# compiler, incorporating C# version 3.0 language

enhancements. C# is a powerful object-orientated, type-safe programming language.

Integrated developer environment (IDE) with IntelliSense makes creating and

building your application easy.

Powerful debugger for finding and fixing errors.

Full support for Windows Forms and controls that make it easy to create rich user

interfaces for your applications.

Support for creating Windows Presentation Foundation (WPF) applications.

Database support for local data applications.

Language-Integrated Query (LINQ) support to enable data query capabilities,

Ability to consume Windows Communication Foundation (WCF) Services.

ClickOnce Deployment to simplify sharing your finished work.

Visual C# Express Edition can be used to create applications such as the following

examples:



16/59


Windows applications that use Windows Forms and controls to create a rich user

interface.

WPF applications.

Command-line utilities.

Class libraries.

Database applications that use SQL Server Compact 3.5 (local databases only).

Games based on DirectX for managed code. (Separate DirectX SDK installation

required.)

And more

The C# programming language was designed to be powerful, safe, and easy to use. As

part of the .NET initiative, C# was designed to work seamlessly with the .NET Framework,creating a new way of writing reliable software for the fastest servers, the smallest mobile

devices, and everything in between.

Unlike traditional C and C++ code, C# code is not compiled directly into machine

language. The C# compiler converts C# source code into Microsoft intermediate language

(MSIL) files, called assemblies. MSIL files are created by all languages that build on the

common language runtime (CLR), including Visual C++, which can also create native

machine code, Visual J#, and Visual Basic. In fact, the MSIL produced is in most cases

virtually identical from language to language, making it straightforward to combine

different program components written in different languages.

The following diagram shows how the C# code you write is converted into an

executable application:



17/59


Figure 2 - The Building Process

The MSIL files appear as standard .exe or .dll files, but rather than running directly on

the Windows platform, they are executed by the CLR. The CLR compiles the MSIL

program into machine code when required; a process called Just-In-Time (JIT) compilation.

This machine code is then executed directly. By generating intermediate, hardware-neutral

code that is not converted into machine code until the last moment, safety, security, and

portability are all increased. This process is largely hidden from the programmer: C#

programs are compiled, executed, and distributed in the same way as any other program. As

long as the .NET Framework is installed on a computer, the C# program will run like any

other application.



18/59


It is also worth noting that in some cases it is desirable to permanently convert a C#

assembly into machine language, and you can do this with the Native Image Generator

(ngen.exe) tool that ships with Visual Studio.

Because it was designed in conjunction with the .NET Framework, C# is exceptionally

well suited for .NET development. The .NET Framework class library is an extensive

collection of classes that provide your applications with almost everything you could need

to develop applications, such as text and graphics display functionality, collections for

storing data, tools for manipulating XML files and databases, methods for accessing Web

sites, and much more.

The .NET Framework organizes its features by namespaces, each of which typically

contains several classes. For example, the System.IO namespace includes many classes for

reading and writing files, and the System.Text namespace contains many classes that handle

string data. Browse the .NET Framework class library reference documentation to get an

idea of the various namespaces and what they contain.

What follows is a collection of illustrations that try to showcase the various capabilities /

features of Visual C#:



19/59


Figure 3 - Visual C# Project Types

Figure 4 - The Visual C# IDE Design View



20/59


Figure 5 - The Visual C# IDE - Code View

3.3 Visual Web Developer

You can use Visual Web Developer Express Edition to create and work with ASP.NET

Web sites and Web Application projects in the following configurations:

Local IIS Web sites: Local Internet Information Services (IIS) Web sites and Web

Application projects are applications on a local computer that run by using a local

copy of IIS.

File system Web sites: In a file-system Web site or Web Application project, files

can be in any folder. This includes on your computer or in a folder on another

computer that you access by using a network share. Instead of using IIS to test the

site, you use the ASP.NET Development Server.

FTP-deployed Web sites: You can work with Web sites that you access by using

FTP. You can connect from Visual Web Developer Express Edition to any FTP

server on which you have read and write permissions. You can then create and edit



21/59


Web pages on that server. Web Application projects do not support FTP deployment

directly, although you can publish your Web Application project to an FTP site.

As in Visual Studio, the Start Page and the File menu of Visual Web Developer Express

Edition enable you to open or create a Web site project or a Web Application project.

Visual Web Developer Express Edition helps you create both ASP.NET Web pages

and HTML pages. ASP.NET Web pages are dynamic pages. They include ASP.NET Web

server controls and code that is processed by ASP.NET on the server. During processing on

the server, the controls and the code produce output that is sent as HTML (or other markup)

to the browser.

Visual Web Developer Express Edition includes a Web page designer. In Design

view, it provides a WYSIWYG design surface where you can type text and add controls.

When you want to edit the page markup directly, you can switch to Source view. In Source

view, the editor provides tools to help you create well-formed markup, such as statement

completion and IntelliSense. The editor also checks that the markup complies with a

validation schema that you have selected, such as Internet Explorer 6 or XHTML 1.0. Split

view enables you to see both the design view and the markup at the same time.

To simplify Web page development, you can use ASP.NET Web server controls.

Web server controls provide familiar types of functionality for pages, such as displaying

text boxes, buttons, check boxes, menus, and so on.

ASP.NET Web server controls differ from HTML elements in that you can program

the ASP.NET controls in server code. This enables you to create Web pages that present a

sophisticated interface to users while enabling you to create Web page content dynamically,

based on information that you can access on the server.

ASP.NET includes Web server controls for a great variety of tasks you might

perform in Web pages, which includes these:



22/59


Standard controls: Enable you to add both basic functionality and complex

functionality to ASP.NET Web pages. Standard controls include buttons, images,

text boxes, check boxes, hyperlinks, list boxes, and so on. Other standard controls

include a calendar, a file upload control, and a control to display XML on a Web

page.

Data controls: Enable you to connect a Web page to various sources of data, which

includes databases and XML files. Data controls also let you display data on the

page in tables or in other formats, and enable users to edit data.

Navigation controls: Enable you to add various types of menus to Web pages.

These include static and fly-out menus, a tree view, and a navigation path (which is

also known as an eyebrow or breadcrumb).

Validation controls: Provide a way to check user input. You can check for

required fields, ranges of values, minimum and maximum values, and specific

patterns.

Login controls: Enable you to easily create logon forms and authenticate users.

You can also use login controls that enable users to register on the Web site and

recover or replace their passwords.

Web Parts controls: Enable users to customize an ASP.NET Web page in the

browser. Web Parts controls can customized content such as news headlines or

weather data. Users can select which Web Parts control they want to see, and they

can customize the layout and appearance of the Web Parts controls. Web Parts

controls are personalized, so that the user's preferences are retained between browser

sessions.



23/59


AJAX extension controls: Enable you to enhance a Web site by using AJAX

capabilities, include asynchronous postbacks.

Visual Web Developer Express Edition supports ASP.NET data source controls, which

perform all the tasks that are required to connect to and communicate with various types of

data sources. For example, the SqlDataSource control contains a data connection object that

can connect to a SQL Server database. It also contains data command objects for SQL

Select, Update, and Delete statements. Other data-source controls enable you to connect to

OLE-DB data sources, XML data sources, and other data sources. The advantage of data

source controls is that they provide a consistent interface for data binding for all ASP.NET

controls.

Visual Web Developer Express Edition supports Language-Integrated Query (LINQ).

LINQ is a query syntax that lets you define query operations directly in C# and Visual

Basic. LINQ lets you query databases or in-memory data sources. To support database

queries, Visual Web Developer Express Edition includes a object-relational mapping

designer that enables you to quickly create and edit data classes that map to objects in a

database.

Visual Web Developer Express Edition also supports a variety of data controls that you

can add to ASP.NET Web pages to display data. These include the GridView, DetailsView,

FormView, ListView, DataList, and Repeater controls. Each of these controls enables you

to present data in different ways. Each control also supports additional features, which

includes sorting, paging, editing data records, inserting new data records, and so on. You

can also populate controls such as the ListBox and DropDownList controls with data from

data source controls.



24/59


Visual Web Developer Express Edition lets you drag data tables onto a page. When you

do, Visual Web Developer Express Edition automatically creates preconfigured controls on

the page.

You can store data in a local database by using SQL Server Express Edition.

By using ASP.NET features such as membership, roles, and login server controls, you

can add authentication (login) and authorization to a Web site by using little or no code.

You can enable users to register on the site, and you can create a login page that

automatically checks users' credentials. You can help protect pages so that only logged-in

users can view them. On a single page, you can present different information to users who

are logged in and to anonymous users. What follows is a collection of illustrations that

showcase the various capabilities / features of Visual Web Developer:

Figure 6 - Visual Web Developer Project Types



25/59


Figure 7 - The VWD IDE - Design View

Figure 8 - The VWD IDE - Code View



26/59


4. Hardware Requirements

4.1 System Requirements

To be used efficiently, all computer software needs certain hardware components or

other software resources to be present on a computer. These pre-requisites are known as

(computer) system requirements and are often used as a guideline as opposed to an absolute

rule. Most software defines two sets of system requirements: minimum and recommended.

With increasing demand for higher processing power and resources in newer versions of

software, system requirements tend to increase over time. Industry analysts suggest that this

trend plays a bigger part in driving upgrades to existing computer systems than

technological advancements.

4.2 Hardware Requirements

The most common set of requirements defined by any operating system or software

application is the physical computer resources, also known as hardware, A hardware

requirements list is often accompanied by a hardware compatibility list (HCL), especially in

case of operating systems. An HCL lists tested, compatible, and sometimes incompatible

hardware devices for a particular operating system or application.

Software Requirements deal with defining software resource requirements and pre-

requisites that need to be installed on a computer to provide optimal functioning of an

application. These requirements or pre-requisites are generally not included in the software

installation package and need to be installed separately before the software is installed.



27/59


Hardware Used:

1.6 GHz or faster processor

1024 MB RAM (1.5 GB if running on a virtual machine)

3 GB of available hard-disk space

5400 RPM hard-disk drive

DirectX 9-capable video card running at 1024 x 768 or higher display

resolution

DVD-ROM drive

Software Used:

Visual Web Developer 2010 Express

SQL Server 2008 R2

Windows 7 Ultimate

Windows Installer 4.5 or later

Internet Explorer 6 or later

.NET framework 4.0



28/59


5. Software Requirement Specification

A Software Requirements Specification (SRS) a requirements specification for a

software system is a complete description of the behavior of a system to be developed. It

includes a set of use cases that describe all the interactions the users will have with the

software. In addition to use cases, the SRS also contains non-functional (or supplementary)

requirements. Non-functional requirements are requirements which impose constraints on

the design or implementation (such as performance engineering requirements, quality

standards, or design constraints).

Benefits of SRS are:

Establish the basis for agreement between the customers and the suppliers on what

the software product is to do. The complete description of the functions to be performed by

the software specified in the SRS will assist the potential users to determine if the software

specified meets their needs or how the software must be modified to meet their needs.

Reduce the development effort. The preparation of the SRS forces the various

concerned groups in the customers organization to consider rigorously all of the

requirements before design begins and reduces later redesign, recoding, and retesting.

Careful review of the requirements in the SRS can reveal omissions, misunderstandings,

and inconsistencies early in the development cycle when these problems are easier to

correct.

Provide a basis for estimating costs and schedules. The description of the product to

be developed as given in the SRS is a realistic basis for estimating project costs and can be

used to obtain approval for bids or price estimates.

Provide a baseline for validation and verification. Organizations can develop their

validation and Verification plans much more productively from a good SRS. As a part of



29/59


the development contract, the SRS provides a baseline against which compliance can be

measured.

Facilitate transfer. The SRS makes it easier to transfer the software product to new

users or new machines. Customers thus find it easier to transfer the software to other parts

of their organization, and suppliers find it easier to transfer it to new customers.

Serve as a basis for enhancement. Because the SRS discusses the product but not the

project that developed it, the SRS serves as a basis for later enhancement of the finished

product. The SRS may need to be altered, but it does provide a foundation for continued

production evaluation.

The Use Case Diagram follows:

Figure 9: Use Case Diagram



30/59


31/59


Physical design, in this context, does not refer to the tangible physical design of an

information system. To use an analogy, a personal computer's physical design involves

input via a keyboard, processing within the CPU, and output via a monitor, printer, etc. It

would not concern the actual layout of the tangible hardware, which for a PC would be a

monitor, CPU, motherboard, hard drive, modems, video/graphics cards, USB slots, etc.

Rapid application development (RAD) is a methodology in which a systems

designer produces prototypes for an end-user. The end-user reviews the prototype, and

offers feedback on its suitability. This process is repeated until the end-user is satisfied with

the final system.



32/59


UML diagrams follow:

ER Diagram

Figure: ER Diagram



33/59


Figure 10: Object Diagram

Figure 11: DFD Diagram

Figure 12: send Parcel DFD



34/59


Figure 13: Customer DFD

Figure 14: Search DFD



35/59


7. Implementation

7.1 The Object Modeling TechniqueThe object-modeling technique (OMT) is an object modeling language for software

modeling and designing. It was developed circa 1991 by Rumbaugh, Blaha, Premerlani,

Eddy and Lorensen as a method to develop object-oriented systems, and to support object-

oriented programming.

We will be using this methodology to develop this project.

OMT was developed as an approach to software development. The purposes of

modeling according to Raumbaugh (1991) are: Testing physical entities before building them (simulation),

Communication with customers,

Visualization (alternative presentation of information), and

Reduction of complexity.

OMT has proposed three main types of models:

Object model: The object model represents the static and most stable phenomena in

the modeled domain. Main concepts are classes and associations, with attributes andoperations. Aggregation and generalization (with multiple inheritance) are predefined

relationships.

Dynamic model: The dynamic model represents a state/transition view on the model.

Main concepts are states, transitions between states, and events to trigger transitions.

Actions can be modeled as occurring within states. Generalization and aggregation

(concurrency) are predefined relationships.

Functional model: The functional model handles the process perspective of the

model, corresponding roughly to data flow diagrams. Main concepts are process, data store,

data flow, and actors.

OMT is a predecessor of the Unified Modeling Language (UML). Many OMT modeling

elements are common to UML.



36/59


Main phases of OMT

The Object Modeling Technique (OMT) software engineering methodology is another well known example of a software engineering methodology. The OMT software

engineering methodology deals with object-oriented development in the analysis and design

phases.

The analysis phase starts with a problem statement which includes a list of goals and a

definitive enumeration of key concepts within a domain. This problem statement is then

expanded into three views, or models: an object model, a dynamic model, and a functional

model. The object model represents the artifacts of the system. The dynamic modelrepresents the interaction between these artifacts represented as events, states, and

transitions. The functional model represents the methods of the system from the perspective

of data flow. The analysis phase generates object-model diagrams, state diagrams, event-

flow diagrams, and data-flow diagrams. The analysis phase is now complete.

The system design phase follows the analysis phase. Here the overall architecture is

established. First the system is organized into subsystems which are then allocated to

processes and tasks, taking into account concurrency and collaboration. Then persistent data

storage is established along with a strategy to manage shared-global information. Next,

boundary situations are examined to help guide trade-off priorities.

The object design phase follows the system design phase. Here the implementation plan

is established. Object classes are established along with their algorithms with special

attention to the optimization of the path to persistent data. Issues of inheritance,

associations, aggregation, and default values are examined.

The OMT software engineering methodology is sequential in the sense that first comes

analysis, followed by design. In each phase, a cyclical approach is taken among the smaller

steps. The OMT is very much like the Booch methodology where emphasis is placed on the

analysis and design phases for initial product delivery. Both the OMT and Booch do not

emphasize implementation, testing, or other life cycle stages.

OMT object diagram is illustrated below:



37/59


Figure 15: OMT Object Diagram

OMT state diagram is illustrated below:

Figure 16: OMT State Diagram



38/59


7.2 Database Schema

Table 1: Parcel

Table 2: Customer



39/59


Table 3: B ill

Table 4: B ranch



40/59


Table 5:Feedback

Table 6:Complaint



41/59


8. Testing & Result

8.1 Unit Testing

Unit testing is a software verification and validation method in which a programmer

tests if individual units of source code are fit for use. A unit is the smallest testable part of

an application. In procedural programming a unit may be an individual function or

procedure.

Ideally, each test case is independent from the others: substitutes like method stubs,

mock objects, fakes and test harnesses can be used to assist testing a module in isolation.

Unit tests are typically written and run by software developers to ensure that code meets its

design and behaves as intended. Its implementation can vary from being very manual

(pencil and paper) to being formalized as part of build automation.

The goal of unit testing is to isolate each part of the program and show that the

individual parts are correct. A unit test provides a strict, written contract that the piece of

code must satisfy. As a result, it affords several benefits. Unit tests find problems early in

the development cycle.

8.2 Usability & Integration Testing

Integration testing is the phase in software testing in which individual software

modules are combined and tested as a group. It occurs after unit testing and before systemtesting. Integration testing takes as its input modules that have been unit tested, groups them

in larger aggregates, applies tests defined in an integration test plan to those aggregates, and

delivers as its output the integrated system ready for system testing.

The purpose of integration testing is to verify functional, performance, and

reliability requirements placed on major design items. These "design items", i.e.

assemblages (or groups of units), are exercised through their interfaces using Black box



42/59


testing, success and error cases being simulated via appropriate parameter and data inputs.

Simulated usage of shared data areas and inter-process communication is tested and

individual subsystems are exercised through their input interface. Test cases are constructed

to test that all components within assemblages interact correctly, for example across

procedure calls or process activations, and this is done after testing individual modules, i.e.

unit testing. The overall idea is a "building block" approach, in which verified assemblages

are added to a verified base which is then used to support the integration testing of further

assemblages.

Some different types of integration testing are big bang, top-down, and bottom-up.

8.3 Acceptance or Validation Testing

Validation testing is a black-box testing performed on a system (e.g. software, lots

of manufactured mechanical parts, or batches of chemical products) prior to its delivery.

This testing generally involves running a suite of tests on the completed system. Each

individual test, known as a case, exercises a particular operating condition of the user's

environment or feature of the system, and will result in a pass or fail boolean outcome.

There is generally no degree of success or failure. The test environment is usually designed

to be identical, or as close as possible, to the anticipated user's environment, including

extremes of such. These test cases must each be accompanied by test case input data or a

formal description of the operational activities (or both) to be performedintended to

thoroughly exercise the specific caseand a formal description of the expected results.



43/59


44/59


Figure 18: New Parcel



45/59


Figure 19: Modify Parcel



46/59


Figure 20: Brows Parcel



47/59


Figure 21: New Customer



48/59


Figure 22:New Bill



49/59




50/59


Figure 23:Brows all Bill



51/59


Figure 24:New Branch



52/59


Figure 25:Brows all Bill



53/59


Figure 26:Search Parcel id



54/59


Figure 27:Complaint



55/59


9. Conclusion

The main conclusions that we can make after finishing the implementation of this project

are: The user requirements as identified in the system analysis stage have all been

implemented & fulfilled.

This project can be easily deployed so that both individuals & business users can

easily start their courier parcel management system in no time.

Being developed using agile methods, new features can be easily incorporated whenever

necessary.



56/59


10. Future Enhancements

In Future using this project we can easily accessible in internet.

More users friendly.

Improve the performance.



57/59


11. Bibliography

Books / Publications

Software engineering: a practitioner's approach - Roger S. Pressman

Software engineering - Ian Sommerville

Software testing techniques: finding the defects that matter - Scott Loveland,

Geoffrey Miller, Michael Shannon, Richard Prew

Software testing: a craftsman's approach - Paul Jorgensen

Verification, validation and testing in software engineering - Aristides Dasso, Ana

Funes

OMT insights - James Rumbaugh

MS Press - Microsoft Visual Web Developer 2008 Express Edition - Eric Griffin

C# And The .NET Platform 2nd Edition - Andrew Troelsen

Apress - Accelerated C# 2008 - Trey Nash

MS Press - Programming Microsoft Windows With C# - Charles Petzold

Apress - Beginning ASP.NET 3.5 in CS 2008 - From Novice to Professional 2E -

Matthew MacDonald

ASP.NET 3.5 For Dummies Ken Cox

Ultra Fast ASP.NET Richard Kiessig

Websites

http://msdn.microsoft.com

http://en.wikipedia.org/wiki/Object-modeling_technique

http://infolab.stanford.edu/~burback/watersluice/node56.html

http://en.wikipedia.org/wiki/Pseudocode

http://en.wikipedia.org/wiki/Unit_testingBITM, BELLARY DEPARTMENT OF MCA 2010-

2011


58/59


http://en.wikipedia.org/wiki/Acceptance_testing

http://en.wikipedia.org/wiki/Integration_testing

http://en.wikipedia.org/wiki/System_requirements



59/59


12. User Manual

Running the Project

Step 1: Open the project in Visual Web Developer:

Figure 28: Opening a Project

Step 2: Next Right-Click on the project name in the Solution Explorer & select View in

Browser command.

Step 3: Theres no step 3! The project is built on the go, & the output is displayed in a

browser window.

Note: You can now enter, modify, browse or search for information by clicking on the

relevant hyper links displayed on the home / sub web pages.

Documents

Sangu Record