https://sourceforge.net/p/critical/wiki/Home/Recent changes to HomeenTue, 28 Feb 2012 17:52:32 -0000https://sourceforge.net/p/critical/wiki/Home/<pre>--- v9 +++ v10 @@ -1,24 +1,23 @@ -Welcome to the Wiki page of the **CriticAL** (A **Critic** for **A**PIs and **L**ibraries) project. The objective of this project is to provide a program analysis framework for critiquing API client code in three ways: - +Welcome to the home page of the **CriticAL** (A **Critic** for **A**PIs and **L**ibraries) project. The objective of this project is to provide a program analysis framework for critiquing API client code in three ways: + 1. Provide *explanation* for complex interactions of API elements, + Provide *recommendation* for future use of the API, + Provide *criticism* for improper use of the API. To support an API with **CriticAL**, we need to build a knowledge base of API use rules for the API. The analysis framework associates API use rules to the relevant documentation. More specifically, our analysis is path-and-state-sensitive. The API client code is symbolically executed and the program states are checked against these specified API rules. Users will be presented with the documentation whenever the conditions in the rules are satisfied. We hypothesize that over time, this process will iteratively guide programmers to evolve a better solution from API. Our initial formative study with a dozen students using the first prototype in a GUI design course indicates that the approach is useful and promising. A short paper that summarizes our initial progress can be found [here][3]. **Team**: 1. [Daqing Hou][1]. Chief Scientist, Assistant Professor, Clarkson University * [Chandan Raj Rupakheti][2], Chief Architect, PhD Candidate, Clarkson University * Russell Seidel, Quality Assurance/Technical Writer, Honor Student, Clarkson University [1]: http://www.clarkson.edu/~dhou [2]: http://www.clarkson.edu/~rupakhcr [3]: http://serl.clarkson.edu/site/wp-content/uploads/2011/08/APIcritic.pdf - - +[[project_screenshots]] </pre>Chandan RupakhetiTue, 28 Feb 2012 17:52:32 -0000https://sourceforge.netf363c039f2b13e9db1d36db4dad75ff87aff9d66https://sourceforge.net/p/critical/wiki/Home/<pre>--- v8 +++ v9 @@ -8,15 +8,17 @@ We hypothesize that over time, this process will iteratively guide programmers to evolve a better solution from API. Our initial formative study with a dozen students using the first prototype in a GUI design course indicates that the approach is useful and promising. - -#####**Team**: - +A short paper that summarizes our initial progress can be found [here][3]. + +**Team**: + 1. [Daqing Hou][1]. Chief Scientist, Assistant Professor, Clarkson University * [Chandan Raj Rupakheti][2], Chief Architect, PhD Candidate, Clarkson University * Russell Seidel, Quality Assurance/Technical Writer, Honor Student, Clarkson University [1]: http://www.clarkson.edu/~dhou [2]: http://www.clarkson.edu/~rupakhcr +[3]: http://serl.clarkson.edu/site/wp-content/uploads/2011/08/APIcritic.pdf   </pre>Daqing HouWed, 18 Jan 2012 01:05:41 -0000https://sourceforge.net98f0be9a7f4f7d47b6a040ee38e9b9af2c3fbd30https://sourceforge.net/p/critical/wiki/Home/<pre>--- v7 +++ v8 @@ -1,4 +1,4 @@ -Welcome to the home page of the **CriticAL** (A **Critic** for **A**PIs and **L**ibraries) project. The objective of this project is to provide a program analysis framework for critiquing API client code in three ways: +Welcome to the Wiki page of the **CriticAL** (A **Critic** for **A**PIs and **L**ibraries) project. The objective of this project is to provide a program analysis framework for critiquing API client code in three ways: 1. Provide *explanation* for complex interactions of API elements, + Provide *recommendation* for future use of the API, </pre>Daqing HouThu, 05 Jan 2012 18:08:39 -0000https://sourceforge.net1d4ecedace7af12ed35c22791fefb9b152d8e141https://sourceforge.net/p/critical/wiki/Home/<pre>--- v6 +++ v7 @@ -1,15 +1,15 @@ -Welcome to the Wiki page of the **CriticAL** (A **Critic** for **A**PIs and **L**ibraries) project. The objective of this project is to provide a program analysis framework for critiquing API client code in three ways: - +Welcome to the home page of the **CriticAL** (A **Critic** for **A**PIs and **L**ibraries) project. The objective of this project is to provide a program analysis framework for critiquing API client code in three ways: + 1. Provide *explanation* for complex interactions of API elements, + Provide *recommendation* for future use of the API, + Provide *criticism* for improper use of the API. To support an API with **CriticAL**, we need to build a knowledge base of API use rules for the API. The analysis framework associates API use rules to the relevant documentation. More specifically, our analysis is path-and-state-sensitive. The API client code is symbolically executed and the program states are checked against these specified API rules. Users will be presented with the documentation whenever the conditions in the rules are satisfied. We hypothesize that over time, this process will iteratively guide programmers to evolve a better solution from API. Our initial formative study with a dozen students using the first prototype in a GUI design course indicates that the approach is useful and promising. -**Team**: +#####**Team**: 1. [Daqing Hou][1]. Chief Scientist, Assistant Professor, Clarkson University * [Chandan Raj Rupakheti][2], Chief Architect, PhD Candidate, Clarkson University </pre>Daqing HouThu, 05 Jan 2012 01:43:20 -0000https://sourceforge.netb4feaea2cb7698f288b925a7fb8f147d980afb5ehttps://sourceforge.net/p/critical/wiki/Home/<pre>--- v5 +++ v6 @@ -1,7 +1,22 @@ -Welcome to the Wiki page of the **CriticAL** (A **Critic** for **A**PIs and **L**ibraries) project. This project intends to provide a framework for critiquing API-client code in three ways: - -1. Provide *explanation* for complex interactions of APIs -+ Provide *recommendation* for future use of APIs -+ Provide *criticism* for improper use of APIs - -We plan to achieve this by building a knowledge-base for the supported APIs. This knowledge-base will associate API-use rules to the relevant documentation. The API-client code will be symbolically executed and their state will be checked against these specified rules. Users will be presented with the documentation whenever the conditions in the rules are satisfied. This process will iteratively guide programmers to evolve a better solution from APIs over time. +Welcome to the Wiki page of the **CriticAL** (A **Critic** for **A**PIs and **L**ibraries) project. The objective of this project is to provide a program analysis framework for critiquing API client code in three ways: + +1. Provide *explanation* for complex interactions of API elements, ++ Provide *recommendation* for future use of the API, ++ Provide *criticism* for improper use of the API. + +To support an API with **CriticAL**, we need to build a knowledge base of API use rules for the API. The analysis framework associates API use rules to the relevant documentation. More specifically, our analysis is path-and-state-sensitive. The API client code is symbolically executed and the program states are checked against these specified API rules. Users will be presented with the documentation whenever the conditions in the rules are satisfied. + +We hypothesize that over time, this process will iteratively guide programmers to evolve a better solution from API. Our initial formative study with a dozen students using the first prototype in a GUI design course indicates that the approach is useful and promising. + + +**Team**: + +1. [Daqing Hou][1]. Chief Scientist, Assistant Professor, Clarkson University +* [Chandan Raj Rupakheti][2], Chief Architect, PhD Candidate, Clarkson University +* Russell Seidel, Quality Assurance/Technical Writer, Honor Student, Clarkson University + +[1]: http://www.clarkson.edu/~dhou +[2]: http://www.clarkson.edu/~rupakhcr + + + </pre>Daqing HouWed, 04 Jan 2012 19:01:04 -0000https://sourceforge.net488a4574ee5f46d9ecb2ae820258f11f68680148https://sourceforge.net/p/critical/wiki/Home/<pre>--- v4 +++ v5 @@ -1,6 +1,7 @@ Welcome to the Wiki page of the **CriticAL** (A **Critic** for **A**PIs and **L**ibraries) project. This project intends to provide a framework for critiquing API-client code in three ways: - 1. Provide *explanation* for complex interactions of APIs - 2. Provide *recommendation* for future use of APIs - 3. Provide *criticism* for improper use of APIs + +1. Provide *explanation* for complex interactions of APIs ++ Provide *recommendation* for future use of APIs ++ Provide *criticism* for improper use of APIs We plan to achieve this by building a knowledge-base for the supported APIs. This knowledge-base will associate API-use rules to the relevant documentation. The API-client code will be symbolically executed and their state will be checked against these specified rules. Users will be presented with the documentation whenever the conditions in the rules are satisfied. This process will iteratively guide programmers to evolve a better solution from APIs over time. </pre>Chandan RupakhetiWed, 29 Jun 2011 23:32:57 -0000https://sourceforge.net9ed7989a9de0bcbb803160056a6fb107e1dd57f9https://sourceforge.net/p/critical/wiki/Home/<pre>--- v3 +++ v4 @@ -1,4 +1,4 @@ -Welcome to the Wiki page of the **CriticAL** (A Critic for APIs and Libraries) project. This project intends to provide a framework for critiquing API-client code in three ways: +Welcome to the Wiki page of the **CriticAL** (A **Critic** for **A**PIs and **L**ibraries) project. This project intends to provide a framework for critiquing API-client code in three ways: 1. Provide *explanation* for complex interactions of APIs 2. Provide *recommendation* for future use of APIs 3. Provide *criticism* for improper use of APIs </pre>Chandan RupakhetiWed, 29 Jun 2011 23:26:11 -0000https://sourceforge.netcb60d2a5f704445ab604b560711df7811da99dc2https://sourceforge.net/p/critical/wiki/Home/<pre>--- v2 +++ v3 @@ -1,4 +1,4 @@ -Welcome to the Wiki page of the CriticAL project. This project intends to provide a framework for critiquing API-client code in three ways: +Welcome to the Wiki page of the **CriticAL** (A Critic for APIs and Libraries) project. This project intends to provide a framework for critiquing API-client code in three ways: 1. Provide *explanation* for complex interactions of APIs 2. Provide *recommendation* for future use of APIs 3. Provide *criticism* for improper use of APIs </pre>Chandan RupakhetiWed, 29 Jun 2011 23:25:17 -0000https://sourceforge.net5f4a643118bdd152f6a33772b1978494e15fedebhttps://sourceforge.net/p/critical/wiki/Home/<pre>--- v1 +++ v2 @@ -1,5 +1,6 @@ -Welcome to your wiki! - -This is the default page, edit it as you see fit. To add a page simply reference it within brackets, e.g.: [SamplePage]. - -The wiki uses [Markdown](/p/critical/wiki/markdown_syntax/) syntax. +Welcome to the Wiki page of the CriticAL project. This project intends to provide a framework for critiquing API-client code in three ways: + 1. Provide *explanation* for complex interactions of APIs + 2. Provide *recommendation* for future use of APIs + 3. Provide *criticism* for improper use of APIs + +We plan to achieve this by building a knowledge-base for the supported APIs. This knowledge-base will associate API-use rules to the relevant documentation. The API-client code will be symbolically executed and their state will be checked against these specified rules. Users will be presented with the documentation whenever the conditions in the rules are satisfied. This process will iteratively guide programmers to evolve a better solution from APIs over time. </pre>Chandan RupakhetiWed, 29 Jun 2011 23:24:06 -0000https://sourceforge.net3384dd6d6542b3185fe9d3a6b095f9d14e4afc35https://sourceforge.net/p/critical/wiki/Home/Welcome to your wiki! This is the default page, edit it as you see fit. To add a page simply reference it within brackets, e.g.: [SamplePage]. The wiki uses [Markdown](/p/critical/wiki/markdown_syntax/) syntax. Chandan RupakhetiWed, 29 Jun 2011 19:16:41 -0000https://sourceforge.nete8e947a8cb849db67f2eabe9bfb0906e9f759ee1