1 / 23

RIA to visualize the health of a project

RIA to visualize the health of a project. Team #4 Final presentation April 17,2008. Team # 4. Team Information. Team Members Karthik Nittala Email: karthik.nittala@gmail.com Srinivas Veesam Email: srinivasveesam@gmail.com Satya Veni Achanta Email: achanta.sv@gmail.com

luann
Download Presentation

RIA to visualize the health of a project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RIA to visualize the health of a project Team #4 Final presentation April 17,2008 Team # 4

  2. Team Information Team Members Karthik Nittala Email: karthik.nittala@gmail.com Srinivas Veesam Email: srinivasveesam@gmail.com Satya Veni Achanta Email: achanta.sv@gmail.com Rachana Mandava Email:rachana.mandava@gmail.com Mentor Mr. Abbasi Dhilawala Email: abbasi.dhilawala@tietronix.com Instructor Dr. Kwok-Bun Yue Email: yue@uhcl.edu Team # 4

  3. Client Information Tietronix Software Inc., 1331 Gemini Ave, Suite #300, Houston, TX-77058. Website: www.Tietronix.com • Tietronix develops software and technology for the worlds most selective customers including NASA and Fortune 1000 companies. • Tietronix is a full service provider of custom software applications and advanced technology solutions. Team # 4 Health of a Software Project.

  4. Team Roles Team # 4 Health of a Software Project.

  5. Contents • Introduction • Project Abstract • System Architecture • Previous work • Requirements • Use Case Diagram • Technologies Used Team # 4 Health of a Software Project.

  6. Contents Contd.. • Rules • Screen Shots • Project Demo • Time Line • References Health of a Software Project.

  7. Introduction • A UI to monitor and visualize the health of a project • Calculate the health of the project using JBoss Rules • UI built using an RIA(Rich Internet Application) development environment, FLEX. Team # 4 Health of a Software Project.

  8. Project Abstract Team # 4 • Animation of the process flow. • The system uses the existing database to collect data for the rules. • Calculating the health of a project. • System alerts may be generated. Health of a Software Project. 8

  9. System Architecture Health of a Software Project.

  10. Previous work • UI built using Scalable Vector Graphics(SVG). • Displays status of process based on simple metrics. • Doesn’t compute health of project. Team # 4 Health of a Software Project.

  11. Team # 4 Health of a Software Project.

  12. Requirements • Animation of a software process flow diagram. • Identify the set of rules that calculates the Health of the project. • Alerts. Team # 4 Health of a Software Project.

  13. Process flow diagram Team # 4 Health of a Software Project.

  14. Use Case Diagram Team # 4 Health of a Software Project. 14

  15. Technologies Used • FLEX :- Framework to build Rich Internet Application. • Papervision3d.:- An open source realtime 3d engine. • JBoss Rules :- A rule based inference engine. • MS SQL Server :- A relational Database Management System. • Tomcat Web Server:- A Web Container. • XML:- Flexible text format to carry data • Java Server Pages:-To trigger rules and generate XML. Team # 4 Health of a Software Project.

  16. Rule Based Inference Engine What is a rule based inference engine? Why use a rule based inference engine? Declarative: what you want it to do, not how Logic and data separation Scalability and Flexibility Understandable Rules Team # 4 Health of a Software Project. 16

  17. What is production Rule system? Matches facts and data, against Production Rules to infer conclusions which result in actions. Team # 4 process of matching the new or existing facts against Production Rules Manages execution order of rules Conflict Resolution strategy Health of a Software Project. 17

  18. Steps to develop Rules Team # 4 List the attributes Build rules in English, based on those attributes Define classes to represent facts Write rules in drl files to work with those facts Health of a Software Project. 18

  19. Example: if-then-else equivalent Team # 4 If process status = active then    Status = 1.0   Time elapsed so far in hours = (today – planned start)    % complete so far = (value from the database)    Planned % complete so far = (Time elapsed so far in hours / Adjusted total hours to work)   If planned % complete so far > 10 then           Status = (%complete / planned %complete so far)    End if End if Health of a Software Project. 19

  20. Example: JBoss Rules equivalent Team # 4 rule "calculate status when activity active" salience 11 when             act : Activity( activityState == "active" , plannedPercentComplete > 10.0 ) then modify (act) { act.activityStatusValue = act.percentComplete / act.plannedPercentComplete } modify (act) { act.plannedPercentComplete = -1.0 }             act.runQuery("update Capstone_workflow..ActivityData_1202484213721 set activityStatusValue = " + act.activityStatusValue +                                    " where packageName ='" + act.packageName +                                      "' and processName = " + act.processName + " and version = " + act.version + " and processInstanceName = " + act.processInstance + " and activityName = "+ act.activityName )              System.out.println (" :: Status Value = " + act.activityStatusValue); end Health of a Software Project. 20

  21. Time Line Health of a Software Project.

  22. References:- • http://downloads.jboss.com/drools/docs/4.0.4.17825.GA/html_single/index.html • http://www.flex.org/ • http://www.adobe.com/products/air/ • http://en.wikipedia.org/wiki/Rich_Internet_application Health of a Software Project.

  23. Thank You..!!! Health of a Software Project.

More Related