Layered software development and implementation using files

• US 20070240096A1
• Filed: 03/28/2006
• Published: 10/11/2007
• Est. Priority Date: 03/28/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Lev, Boaz, Schaub, David, Pontoppidan, Michael
• Granted Patent: US 7,752,597 B2
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A technology for layered software development using files is disclosed. In one method a runtime environment for a class of a layered software application is developed. A layer file folder is opened. The layer file folder is located in a computer file system and is for storing classes belonging to a layer of the layered software application. A class file is opened in the layer file folder. The class file comprises a text file representing the class of the layered software application that is being developed into a runtime environment. The class file further comprises data describing a method performed as part of the class. It is then determined if the method of the class file has been previously loaded into the runtime environment.

Claims

1. Instructions on a computer-usable medium wherein the instructions when executed cause a computer system to perform a method for storing a class of a software development layer, said method comprising:

opening a layer folder in a computer file system;

opening a class file in said layer folder, wherein said class file comprises an editable text file for storing information related to any methods implemented within said class; and

writing a method of said class into said class file, wherein said method comprises a unit of software instructions to be performed as part of said class.

2. The instructions of claim 1, wherein said opening a layer folder in a computer file system comprises:

creating said layer folder if said layer folder does not exist.

3. The instructions of claim 2, further comprising:

including layer sequence information in said layer folder.

4. The instructions of claim 1, wherein said opening a class file in said layer folder comprises:

creating said class file if said class file does not exist in said layer folder.

5. The instructions of claim 1, wherein said opening a class file in said layer folder comprises:

writing a class header in said class file, said class header comprising identifier information for said class.

6. The instructions of claim 1, wherein said writing a method of said class into said class file comprises:

determining if said method differs from all said lower layer methods of said class by comparing method identifier information from said method with method identifier information of all said lower layer methods.

7. The instructions of claim 6, further comprising:

writing said method into said class file if no matching method identifier information exists in any of said lower layer methods.

8. The instructions of claim 6, further comprising:

comparing content of said method with all said lower layer methods of said class determined to have matching method identifier information to said method; and

writing said method into said class file if, as a result of said comparing content, said method is determined to comprise different content than all said lower layer methods determined to have matching method identifier information to said method.

9. A computer implemented method for generating a runtime environment for a class of a layered software application, said method comprising:

opening a layer file folder, wherein said layer file folder is located in a computer file system, and wherein said layer file folder is for storing classes belonging to a layer of said layered software application;

opening a class file in said layer file folder, wherein said class file comprises a text file representing said class of said layered software application, and wherein said class file comprises data describing a method performed as part of said class; and

determining if said method of said class file has been previously loaded into said runtime environment.

10. The method of claim 9, further comprising:

sequencing a group of layer file folders into an ascending hierarchical order from a lowest precedence layer file folder to a highest precedence layer file folder.

11. The method of claim 9, wherein said opening a layer file folder comprises:

opening said layer file folder in an ascending sequence from a group of layer file folders comprising a hierarchical order.

12. The method of claim 9, wherein said determining if said method of said class file has been previously loaded into said runtime environment further comprises:

reading data within said class file to ascertain contents of said class file.

13. The method of claim 9, wherein said determining if said method of said class file has been previously loaded into said runtime environment comprises:

loading said method into said runtime environment if said method has not been previously loaded into said runtime environment.

14. The method of claim 9, wherein said determining if said method of said class file has been previously loaded into said runtime environment comprises:

loading said method into said runtime environment to override a previously loaded version of said method, wherein said previously loaded version of said method is from a lower precedence layer of said layered software application.

15. A system for folder and file based management of layers and classes of a layered software application, said system comprising:

a folder manager coupled to a storage area, said folder manager for receiving inputs to said system and for opening a file folder within said storage area, said file folder for storing information related to a layer of said layered software application;

a file manager coupled to said storage area, said file manager for opening a file within said file folder, said file for storing a software application class implemented in said layer; and

a write manager coupled to said storage area, said write manager for writing textual information into said file, said textual information defining a method implemented within said software application class.

16. The system of claim 15, further comprising:

a load manager coupled to said storage area and to a runtime environment, said load manager for reading said textual information from said file and selectively providing an output from said system to said runtime environment, said output comprised of a portion of said textual information.

17. The system of claim 15, wherein said folder manager further comprises:

a sequence information generator configured to automatically associate layer sequence information with each said file folder, said layer sequence information representing a hierarchical layer of said layered software application that said file folder is associated with.

18. The system of claim 15, wherein said folder manager further comprises:

a sequencer for arranging a plurality of said file folders into hierarchical order by means of layer sequence information associated with each said file folder.

19. The system of claim 15, wherein said file manager is configured to automatically create a file name for said file by a reading a portion of said textual information.

20. The system of claim 15, wherein said write manager is configured to write a class header into said file, said class header comprising information for defining a formalized structure of operation for any methods implemented within said software application class.