Integrating Content Management tool with Software Development Assistance (SDA)

1. Integrating Content Management tool with Software Development Assistance(SDA) Presented by Capstone Team #1

2. Team Members • Instructor • Name: Dr. Alfredo Perez-Davila • Email: perezd@uhcl.edu • Mentor • Name:Abbasi Dhilawala • Dmail: Abbasi.Dhilawala@tietronix.com

3. Team Members • Omkar Wadkar • wadkar05011@uhcl.edu • Team Leader/ Researcher/ Programmer/Developer • Adebiyi Olukayode • adebiyiO2496@uhcl.edu • Researcher/ Programmer/Web designer • Prachi Phatak • Phatakp7215@uhcl.edu • Researcher/ Programmer/Database administrator • Zhen-Yu Fang • Fangz5973@uhcl.edu • Researcher/ Programmer/Web developer

4. Introduction • Tietronix Software, Inc. • Founded in 1999 by Victor W. Tang, Michael E. Izygon, and Stuart S. Engelhardt. • Develops sofware and technology solutions for the world’s most selective customers including NASA and Fortune 1000. • Two mission: • Develop reliable software and technology solutions that solve customers’ problems on time and on budget. • Apply technologies developed for NASA to commercial markets.

5. Introduction of SDA • What is SDA? • an engineering process automation tool that already has built in support fro software development. • web based and is geared towards team development. • built on J2EE technologies like EJBs, Struts, Servlets, JSP and more. • The SDA UI framework is built upon a leading open source portal called Liferay. • How SDA helps? • web based content management systems • helps software development team to automate software processes

6. Requirement • The team should either select an open source content management tool or develop one for the integration. • The tool should store the content in a database. Preferably works with multiple leading database management tools like SQL Server, MySQL, Oracle etc • The tool should allow certain users with the appropriate right to create/modify the content with a rich text editor. • The tool should display the managed content to other users in a read only format.

7. Test & Final Present SDA Core Design SDA Solution Approaches Setup SDA Environment Requirement Specification Doc. Team & Website February March April May 12 8 16 4 Weeks Project Schedule

8. Test & Final Present SDA Core Design SDA Solution Approaches Setup SDA Environment Requirement Specification Doc. Team & Website February March April May 12 8 16 4 Weeks Current Status Project Current Status

9. Current System PROCESS AUTHOR READ PROCESS AUTHOR PUBLISH AFTER PUBLISH TIETRONIX XML FILE PROCESS AUTHOR XML EDIT SEND TO PUBLISH DOC PUBLISH AGAIN

10. Required System AUTHOR PROCESS READ PROCESS AUTHOR PUBLISH AFTER PUBLISH PROCESS PROCESS AUTHOR EDIT PUBLISH

11. Solution Approaches • Two solution Approaches • Research • Search a wiki • Development. • Database approach

12. First approach –research An open source content management tool • Should store the content in a database • Should allow users to create/modify • Should support rich text editing • Should support access control mechanism

13. Research on wikis • Research for wiki management tools:

14. Short listed wikis • Wiki evaluation:

15. Development • Plan of development • Search an open source web based editor • Integrate searched editor into SDA • Provide access control by applying locking mechanism

16. Development (continued…) Open source Editor HTML File Store to Database

17. HTML File storage HTML File File storage Database

18. Thank You!