1 / 21

RIA to visualize the health of a project

RIA to visualize the health of a project. Team #4 Midterm presentation February 28,2008. Team # 4. Team Information. Team Members Karthik Nittala Email: karthik.nittala@gmail.com Srinivas Veesam Email: srinivasveesam@gmail.com Satyaveni Achanta Email: achanta.sv@gmail.com

rebekah-mullins
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 Midterm presentation February 28,2008 Team # 4

  2. Team Information Team Members Karthik Nittala Email: karthik.nittala@gmail.com Srinivas Veesam Email: srinivasveesam@gmail.com Satyaveni 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 project.

  4. Contents • Introduction • Previous work • Project Abstract • Requirements • Process Flow Diagram • Technologies Used • Use Case Diagram • Flex • JBoss • References Team # 4 Health of a project.

  5. 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 project.

  6. 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 project.

  7. Team # 4 Health of a project.

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

  9. Requirements • Animation of a software process flow diagram. • Identify the set of rules that calculates the Health of the project. • Alerts. • Dynamic Reports. Team # 4 Health of a project.

  10. Process flow diagram Team # 4 Health of a project.

  11. 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. Team # 4 Health of a project.

  12. Use Case Diagram Team # 4 Health of a project.

  13. Rich Internet Application • Richer • More responsive • Client/server balance • Asynchronous communication • Network efficiency Team # 4 Health of a project.

  14. Why Flex? • Integrated Development Environment • Built on top of the Eclipse Platform or we can use Flex builder • MXML(Macromedia XML) • User Interface Components • Features:- • Integrated compiler • Code hints • Debugger & Design View • Integrated Version Control (CVS, SVN, etc.) Team # 4 Health of a project.

  15. UI using FLEX Team # 4 Health of a project.

  16. Why Jboss for our project • Declarative Programming • Project is just too fiddle for traditional code. • Logic and Data Separation • The logic changes often we can update rules in systems that are in production • Speed and Scalability • Tool Integration • Centralization of Knowledge Team # 4 Health of a project.

  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 project.

  18. Why a Production Rule System is different • Methods of execution : • Forward Chaining: Data driven • Backward Chaining: Goal driven • Hybrid Production Rule Systems. Algorithms used for Pattern Matching : ReteOO Team # 4 Health of a project.

  19. Forward chaining Team # 4 Health of a project.

  20. Backward chaining Team # 4 Health of a project.

  21. 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 project.

More Related