Step by Step Monitoring for Product Purchasing System

Step by Step Monitoring for Product Purchasing System

Abstract:
Business processes are increasingly distributed and open, making them prone to failure. Monitoring is, therefore, an important concern not only for the processes themselves but also for the services that comprise these processes. We present a framework for multilevel monitoring of these service systems. It formalizes interaction protocols, policies, and commitments that account for standard and extended effects following the language-action perspective, and allows specification of goals and monitors at varied abstraction levels. We demonstrate how the framework can be implemented and evaluate it with multiple scenarios that include specifying and monitoring open-service policy commitments.

EXISTING SYSTEM:

While the existing system was most of our large software systems are now constructed as group of interoperating systems made to interoperate through various forms of interfaces.
Instead, the open and distributed process includes tasks that are performed by services that are not centrally controlled, and hence, can be unpredictable. As a result, service outcomes themselves tend to be uncertain.

Disadvantage:
 Although, we can conceive these large service systems, we have trouble building them.
 Anecdotal accounts of systems integration efforts points to failures and underscore the need to address the underlying cause:
• Rapidly Changing Environmental forces.

PROPOSED SYSTEM:

The goal of this research is to develop a framework for monitoring such service systems. To establishes its feasibility, and evaluates it with scenarios and comparisons against existing proposals.
It monitoring the software systems is closely tied to the monitoring of requirements and how they are realized in software.
If observes and analyzes the behavior of another (target) system, that determining qualities of interest, such as satisfaction of the target system’s requirements.

ADVANTAGE:

 Where well-specified business processes with service to perform tasks are advanced changes such as stability, feasibility, predictability.
 We develop the contribution as an extension to prior work in monitoring, establish its feasibility and demonstrate it with multiple scenarios.
 Service systems build upon the basic idea of software as a service that allows legacy and new applications to declare their capabilities in a machine-readable format.

Main Modules:-

Module Description:

MODULES:

 Customer Details
 Merchant Details
 Loan Approved
 Shipping Process
 Payment Gateway

Customer Details:

In this module the details about various customers are maintained and each has a unique id. And includes about various merchants are maintained and each has a unique id. The customer select best merchant and then send quote to that merchant mail account. And send his purchasing order details with some conditions. After that receive amount quote, customer check the conditions and then he take decision. If he satisfies means approach the merchant.

Merchant Details:

As same as, in this module the details about various merchants are maintained and each has a unique id. The merchants receives item id, & consults the policy order and sends the quote to customer, and receives either accept-quote or reject-quote. When merchant satisfies the condition from the customer then only he able to transact the materials to customer with help of shipper. He send the quotation to customer. After that the customer transact money to merchant account. Merchant check the account details then he giving order to shipper. Otherwise, he rejected the customer order.

Loan Transaction:

In this module the authentication of the customer’s to be checked their quotation and items are monitored. Then, loan approver confirms his account and quotation to be authorized/unauthorized. If, the customer to be authorized person the loan to be sanction to that specific customer. When unauthorized customer loan to be rejected.

Shipping Process:

The shipper who transports the physical items to the customer from merchant within the given date. He receive the details about the product order and customer. Finally he check the account to be credit of not. And they know the conditions and commitments of both customer and merchants. If account to be credit means he gets the orders from merchants and send to that particular customer. Otherwise, reject the order.

Payment Gateway:

Merchants who authorize the customer payments for his purchase order. The customer who pays the money to his account. After payer sends payment information, eventually payer receives receipt. After payer commits to order, payer pays for order.
SYSTEM REQUIREMENTS:

HARDWARE REQUIRED:

 SYSTEM : PENTIUM IV 2.4 GHZ
 HARD DISK : 40 GB
 FLOPPY DRIVE : 1.44 MB
 MONITOR : 15 VGA COLOR
 MOUSE : LOGITECH.
 KEYBOARD : 110 KEYS ENHANCED
 RAM : 256 MB

SOFTWARE REQUIRED:

 O/S : WINDOWS XP.
 LANGUAGE : ASP.NET, C#.
 DATA BASE : SQL SERVER 2005.

Algorithm:

LINEAR TEMPORAL LOGIC (LTL) ALGORITHM:-

It can be used to prove properties when the set of states reachable from an initial state in a system module is finite.
We can distinguish two levels of specification:
• A system specification level, provided by the rewrite theory specified by that system module which defines the behavior of the system, and
• A property specification level, given by some property (or properties) φ that we want to state and prove about our module.
An interaction protocol is defined as the “Rules of Engagement” among interacting participants. Therefore, include:
1) Specificity
2) Semantic
3) Composability

In Specificity represent interactions among services. That is domain independent.
(e.g. for shipment , may be domain-dependent.)
In Semantic concern is semantic content. i.e., the nature of the interactions. (Request – Reply mechanism).
(e.g., destination, payment info) to capture content. The message itself may capture the semantics to distinguish actions, such as direct, inform, cancel, and others.

Finally, composability is concerned with how a designer might specify the process by combining protocols.

Comments are closed.