SECURE BUG TRACKING SYSTEM A Project Presented to the faculty of the Department of Computer Science California State University, Sacramento Submitted in partial satisfaction of the requirements for the degree of MASTER OF SCIENCE in Computer Science by Nikhita Kamble SPRING 2018 © 2018 Nikhita Kamble ALL RIGHTS RESERVED ii SECURE BUG TRACKING SYSTEM A Project by Nikhita Kamble Approved by: ______________________, Committee Chair Dr. Xiaoyan Sun ______________________, Second Reader Dr. Ahmed Salem _______________________ Date iii Student: Nikhita Kamble I certify that this student has met the requirements for format contained in the University format manual, and that this project is suitable for shelving in the Library and credit is to be awarded for the project. __________________________, Graduate Coordinator ___________________ Dr. Jinsong Ouyang Date Department of Computer Science iv Abstract of SECURE BUG TRACKING SYSTEM by Nikhita Kamble Bug tracking is defined as a procedure of tracking reported software bugs of any product of an organization. While developing any product or software, there are chances of bug occurrences. Keeping track of these bugs/issues manually is not feasible. At the same time, it is also important to keep a detailed record of the bug fixing information, such as the person who fixed the bug, the time of bug fixing, etc. Such information will help developers to resolve similar issues if they occur in future. Therefore, developing a tool for bug tracking is essential. Using a web based bug tracking system would not only satisfy the company needs of bug tracking, but would also facilitate the discussion and problem solving among teams at different locations. Tools such as JIRA, Redmine, and so on are used by many organizations for bug tracking. However, issues such as high cost, unrequired features, non-user friendly interface might create hassle for small start-up companies. The free tools available usually contain advertisements and require installation of unnecessary software. v This results in waste of memory space and creates potential security problems. Attackers could possibly leverage such free tools to conduct attacks towards the host machine. The purpose of this project is to develop a tool which is user-friendly, inexpensive, advertisement free, and secure for start-up organizations. The proposed bug tracking system is user friendly, easy to install, and light-weight. It has low system requirement. Cryptography technique has been used for encrypting some fields of issues to protect the information credentiality. In addition, customized version can be developed given specific features required by organizations. ______________________, Committee Chair Dr. Xiaoyan Sun ______________________ Date vi ACKNOWLEDGEMENTS I thank my guide, Dr. Xiaoyan Sun, for all the guidance and support that she provided me throughout the project. I thank her for having confidence in me and keeping me inspired throughout the duration of my project. I thank my second reader, Dr. Ahmed Salem for reviewing my report and giving valuable feedback for improvising it. I would also like to express gratitude to my graduate coordinator, Dr. Jinsong Ouyang for providing his valuable feedback. Moreover, I thank Computer Science Department at California State University, Sacramento for giving me an opportunity to implement this concept of bug tracking system. Lastly, I would like to thank my parents and siblings for having faith in me and urging me to seek a graduate degree in the U.S. vii TABLE OF CONTENTS Page Acknowledgements .................................................................................................... vii List of Figures ............................................................................................................. ix Chapter 1. INTRODUCTION ................................................................................................ 1 1.1 Problem Statement and Proposed Solution................................................ 1 1.2 Related Work ............................................................................................. 2 2. SYSTEM DESIGN .................................................................................................. 5 2.1 Three-Tier Architecture ............................................................................. 5 2.2 Advantages of Three-Tier Architecture...................................................... 8 3. IMPLEMENTATION....................................................................................... 10 3.1 Technologies, Tools and IDEs ................................................................ 10 3.2 Methodology........................................................................................... 13 4. RESULTS AND TESTING ............................................................................... 19 4.1 Results....................................................................................................... 19 4.2 Testing........................................................................................................ 38 5. CONCLUSION AND FUTURE WORK.............................................................. 42 5.1 Conclusion ............................................................................................... 42 5.2 Future Enhancements.............................................................................. 43 Bibliography ................................................................................................................. 44 viii LIST OF FIGURES Figures Page 1. Related work.....................................................................................................................3 2. Three-tier architecture .........................................................................................5 3. Admin creates user .......................................................................................................14 4. Activity diagram of super admin approving admin’s request...............................16 5. Activity diagram of admin creating project .......................................................17 6. Activity diagram of user creating issue .............................................................18 7. Super admin registration form ...........................................................................19 8. Super admin login form .....................................................................................20 9. Super admin types of issue form .......................................................................21 10. Number of active admins form ........................................................................22 11. Number of non-active admins form.................................................................23 12. Admin registration form .................................................................................23 13. Admin registration confirmation message .......................................................24 14. Super admin gets admins request ....................................................................24 15. Super admin approves admins request ............................................................25 16. Admin login page ............................................................................................26 17. Admin profile setup .........................................................................................26 18. Information about projects ...............................................................................27 19. Information about issue ...................................................................................27 ix 20. Explanation of an issue ....................................................................................28 21. Explanation about keys of a project .................................................................28 22. Explanation of an assignee ..............................................................................29 23. Explanation of status in project .......................................................................29 24. Explanation of issue workflow ........................................................................30 25. Tour completion page ......................................................................................30 26. Project name and key creation .........................................................................31 27. Creating a project .............................................................................................31 28. Inactive users in project ...................................................................................32 29. Active users in project .....................................................................................33 30. User login page ................................................................................................33 31. User profile page .............................................................................................34 32. Create issue page .............................................................................................35 33. User becomes active, seen by admin ...............................................................35 34. Filtering an issue ..............................................................................................36 35. Welcome page .................................................................................................37 36. Contact us page ................................................................................................37