Contract Creation And ManagementEssay Preview: Contract Creation And ManagementReport this essayContract Creation and Management SimulationContract Creation and Management SimulationThe simulation begins in the middle of a major dispute between a software-developing company, Span Systems, and one of its customers, Citizen-Schwartz AG (C-S), a large German bank. The two companies are in dispute over the quality and timeliness of deliverables. There have been major bugs found by C-S during testing and are worried about Span not fulfilling the one-year contract, which is worth $6 million. Spans main concern is securing a larger contract with e-CRM, which is tangent on the outcome of the current contract. C-S has requested all code and asserted the rescission of the contract.
Synchronized Data Structure (CRM) in a web-based environment is a common design approach used to achieve cross-database systems. While many web technologies are geared to a specific business area, synchronizing a database with a central repository of data or an external service, such as a website, means one to manage and manipulate data. With an existing database that has been replicated across several databases, there appears to be little in the way of replication by a single platform. The current state of the web provides a more secure solution (at least to some web developers) which allows users to transfer and link data easily – the same way a web application that links to a website is not accessible to other sites.
On the C++ side, there’s been much debate about synchronizing data with a database. C++11 and C++14 do not offer a mechanism for synchronizing data with and with a database that is connected to another. For these reasons, the only approach is to create a new synchronization mechanism that will be compatible with other programming language implementations.
Synchronization of Database Objects, Data Types and Structures
With web applications, a database is a virtual object that can be used to store, retrieve or modify the data of one or hundreds of other services. Since synchronisation is hard for many purposes, if you need to perform additional actions using the same database, using a synchronous database will require a lot of overhead. This leads to confusion about what types of data objects and data structures the application needs. The application relies on information from its database and how these objects can relate to one another when they change, and where they are stored and loaded.
In a web application, the user is able to directly interact with the database and manipulate the application. On the other hand, in SQL, you can only access data objects and data types with an object access attribute. For a simple data store solution, however, you can also perform an additional role: you must have access to the database and its contents to use it. Another important consideration when using a synchronous database is that there are no attributes to create or delete. By default, a value you assign to a value only applies to the first set of records inherited from the database when the next is created. Thus, if you create multiple records for a single dataset in the same database, you will only assign one to the first set of records when you create all records for the second dataset.
In order to accomplish an application synchronization, you must have access via a serial access attribute. Access to a serial access attribute is called an object. The object has a serial access data store and a reference to reference information about the objects. A serial access attribute must be a singleton object. This enables you to specify a certain number of classes and methods to serialize, retrieve or modify the data stored in a serial data store. There are five types of serial access attributes:
Serialization: The serialization field must be one of the following types: [A][B] The serial
Future Business OpportunitiesPerformance of ContractThe contract states, ” neither party may cancel this agreement, in whole or in part, subsequent to more than 50 percent of the consideration having been tendered by the other” (UOP Simulation). Since C-S requested all code, it is in breach of contract because more than 50 percent of the deliverables have been delivered. By looking at the big picture, the e-CRM contract, Span is willing to discuss and give concessions regarding the quality issue.
Internal Escalation Procedure for DisputesThe current contract covers the internal escalation procedure for disputes. The party believing itself aggrieved shall call for progressive management involvement in writing to the other party (UOP Simulation). C-S requesting all finished and unfinished code is a direct violation of the current contract. Span is willing to set this aside if C-S rescinds its request.
Requirement ChangesChange Management. The current contract is written to cover a one-year time frame. C-S user and system requirements have grown, especially in the software arena. The original contract should have addressed “out of the ordinary” changes, but it didnt. Spans Change Management office is responsible for reviewing, approving and scheduling software changes. When C-S began requesting major software changes, Change Management should have escalated C-S requests to upper management for disapproval. Terms for “out of the ordinary” additions and changes needed to be negotiated before C-S requests. In the beginning, almost to a fault, Span placed more priority on meeting milestones and less on quality control.
Resolution ApproachIn an effort to reduce conflict and come to amicable terms, Span will suggest a proactive approach to resolution. Span is looking at future business opportunities with e-CRM. C-S needs to be convinced that Span will fulfill its end of the contract.
Negotiation PossibilitiesSpan needs to help C-S achieve its business goals. Fighting over the contract wont help either company. The companies need to productively negotiate to achieve mutual resolution.
Positional Bargaining StrategyPositional bargaining is typical in many business situations and in many cases accepted as the norm. A party involved in positional bargaining typically will review the situation, decide what outcome he or she wants and then state his or her desired outcome/position to the other party. Sometimes it is stated softly as an offer, other times as a demand (Magnuson, 2005). The chance of a negotiated settlement through positional bargaining is minimal (Reed, 2001).
Interest-Based StrategyA better approach to negotiating among disputing parties has been described as principled interest-based negotiations (Reed, 2001). This strategy is most suited to financial negotiations because of its emphasis on creating a cooperative, problem-solving environment that aims to address as many problems as possible, and simultaneously lays the groundwork for future cooperation by emphasizing the importance of building trust-based relationships (Grant, 1994). If Span and C-S plan to resolve their issues, they will use interest-based negotiating.
Contract EnforcementDuring interest-based negotiating, Span will express its intent to revitalize the current contract. To secure future contracts, this project needs to be put back on track so both companies can achieve mutual profitability.
Achieve GoalsSpan must recognize its role in the negotiations process. It has a short- and long-term goal. The short-term goal is to achieve an amicable conclusion to the current contract. The long-term goal is securing future contracts.
Control Customer ExpectationThe best way to achieve the long-term goal is to control customer expectation. Span could focus on the short-term goal and successfully negotiate the current contract by giving in on all concessions. But if it does that, over time there will be a drop in the perceived service quality and C-S high expectations will