Computer Software and Hacker

Analysis of the Powerscreen Problem In our recent negotiation, my partner Dave and I assumed the roles of Alan Hacker, a computer software developer, and Alan Hacker’s lawyer. Being the lawyer in the negotiation my objective was to avoid litigation with my client’s partner Stanley Star and to aid in the continuation of my client’s co-owned company HackerStar. In addition, I would assist Hacker in coming to an agreement that would be satisfying for him both personally and financially. I felt that Dave and I presented a reasonable argument on Hacker’s behalf and, since I was able to apply some of our class readings during the process, I was overall pleased with the outcome. My partner Dave and I met on 3 separate occasions to discuss the side of Alan Hacker in “The Powerscreen Problem” negotiation. Alan Hacker and his partner Stanley Star own a software company named HackerStar, which was financed solely by Star. Hacker, the key programmer, manages the company. Even though they have had minor success with two other computer software programs, they recently had a major disagreement over the ownership of a new computer program that Hacker created called Powerscreen. After many failed attempts to convince Star to back Powerscreen, Hacker decided to seek out a third party for support. Hacker came to an agreement with third party, Jeremy Gates, to buy Powerscreen and for Hacker to receive a percentage of the royalties which is dependent upon the amount of the software that is sold. Star argued that since Powerscreen was developed using HackerStar office equipment, any royalties should the owned by the company. Hacker disagrees with Star’s right to ownership and they get in a heated argument that quickly turns personal. My task as Hacker’s attorney in the negotiation is to avoid litigation and keep the company afloat. I am to advise Hacker during the course of the meeting as I see fit. Dave and I decided early on that one of our main goals, besides the