Developing Software Components Based on Brain Lateralization

• US 20080134132A1
• Filed: 11/30/2006
• Published: 06/05/2008
• Est. Priority Date: 11/30/2006
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sadovsky, Vladimir, Stokes, Michael D., Schwarz, Jonathan R., Norlander, Rebecca A.
• Application Number:
  US11/565,495
• Publication Number:
  US 20080134132A1
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 8/20 Software design

Abstract

A software design process includes three elements—an object/component driven element, a situation/scenario driven element, and an arbitrator/communicator element that is logically interposed and serves as an intermediary between the object/component driven and the situation/scenario driven elements. Through an iterative communication process overseen by the arbitrator/communicator, software design can take place and be measured against a metric. The communication process overseen and implemented by the arbitrator/communicator can allow ideas and developments provided by one element to be translated into a format that the other element understands. Once the metric has been achieved, the design process can be terminated.

Claims

1. A method comprising:

identifying an opportunity associated with designing software;

providing an arbitrator/communicator who is to serve as an intermediary between an object/component driven element and a situation/scenario driven element composed of individual who are to use designed software;

assembling the object/component driven element, wherein said object/component driven element includes individuals who design software;

developing a metric associated with development of said software and against which design activities are to be measured;

seeding one of said elements with an idea associated with the metric; and

iteratively translating and communicating results from one element to another until the design process is terminated.

2. The method of claim 1, wherein the opportunity manifests itself in the form of a demand or request from a customer or vendor.

3. The method of claim 1, wherein the opportunity manifests itself in the form of a new customer.

4. The method of claim 1, wherein the situation/scenario driven element comprises one or more of end users, vendors, or customers of said software.

5. The method of claim 1, wherein said act of developing a metric is performed by the arbitrator/communicator.

6. The method of claim 5, wherein said metric is developed, at least in part, by ascertaining one or more problems associated with the situation/scenario driven element.

7. The method of claim 1, wherein the act of seeding is performed by seeding the object/component driven element.

8. The method of claim 1, wherein the design process is terminated responsive to achieving the metric.

9. A system comprising:

an object/component driven element comprising individuals associated with the design of software;

a situation/scenario driven element associated with individuals who use software designed by the object/component driven element; and

an arbitrator/communicator logically interposed between the object/component driven element and the situation/scenario driven element and serving as an unbiased communication intermediary between said two elements,

wherein the arbitrator/communicator iteratively communicates results achieved by said two elements between said two elements until a design metric is achieved.

10. The system of claim 9, wherein the arbitrator/communicator produces said design metric.

11. The system of claim 9, wherein the arbitrator/communicator seeds one of the elements with an idea associated with achieving the design metric.

12. The system of claim 9, wherein the arbitrator/communicator does not inject personal opinions about software design in the iterative communication that takes place between the two elements.

13. The system of claim 9, wherein the arbitrator/communicator translates information from one element into a form that the other element understands.

14. A method comprising:

providing an object/component driven element comprising individuals associated with the design of software;

providing a situation/scenario driven element associated with individuals who use software designed by the object/component driven element;

logically interposing an arbitrator/communicator between the object/component driven element and the situation/scenario driven element; and

using the arbitrator/communicator as an unbiased communication intermediary between said two elements, wherein the arbitrator iteratively communicates software design-related results achieved by said two elements between said two elements.

15. The method of claim 14, further comprising using the arbitrator/communicator to produce a design metric against which design activities are measured.

16. The method of claim 15 further comprising using the arbitrator/communicator to seed one of the elements with an idea associated with achieving the design metric.

17. The method of claim 14, wherein the arbitrator/communicator does not inject personal opinions in the iterative communication that takes place between the two elements.

18. The method of claim 14 further comprising using the arbitrator/communicator to translate information from one element into a form that the other element understands.