Synopsis of project of MTech - III Sem in AKTU
- 1. ONLINE TECHNICAL DISCUSSION FORUM (TechDec) A synopsis Submitted In Partial Fulfillment of the Requirements for the Degree of MASTER OF TECHNOLOGY (COMPUTER SCIENCE) By EHTESHAMUDDIN Enroll. No.- 220384010032283 Under the Supervision of Dr. B. D. MAZUMDAR (Prof. in UNITED COLLEGE) SARASWATI HIGHER EDUCATION AND TECHNICAL COLLEGE OF ENGINEERING, VARANASI (College Code-384) AFFILIATED TO Dr. A.P.J. ABDUL KALAM TECHCHNICAL UNIVERSITY LUCKNOW, UTTAR PRADESH 2022-2024
- 3. Declaration I hereby declare that this SYNOPSIS report entitled, βONLINE TECHNICAL DISCUSSION FORUM (TechDec)β, being submitted by me to the DR. A P J ABDUL KALAM TECHNICAL UNIVERSITY, LUCKNOW for the award of the degree of Masters of Technology (CS) is a record of bonafide work carried by me (Roll No.- 2203840105002). I worked under the guidance and supervision of DR. B. D. MAZUMDAR, (Prof., UNITED COLLEGE) Prayagraj. The matter embodied in this report has not been submitted to any other university or institute earlier for the award of any degree or diploma. EHTESHAMUDDIN M. TECH. IIIRD SEM (2023-24) ROLL NO.- 2203840105002
- 4. Acknowledgements I have taken efforts in this project. However, it would not have been possible without the kind support and help of many individuals and organizations. We would like to extend my sincere thanks to all of them. I would like to take the opportunity to express my humble gratitude to Dr. B. D. MAZUMDAR (prof. UNITED COLLEGE) under whom I executed this project and most thankful his constant guidance and willingness to share his vast knowledge made me understand this project and its manifestation in great depth and helped me to complete the assigned task. We would like to thank all faculty members and staff of the department of SARASWATI HIGHER EDUCATION AND TECHNICAL COLLEGE OF ENGINEERING, VARANASI for their generous help in various ways for the completion of this synopsis. PLACE: VARANASI EHTESHAMUDDIN DATE: M. TECH. CS III RD SEM ROLL NO.- 2203840105002
- 5. CONTENT PAGE NO. 1. INTRODUCTIONβ¦ ................................................................................................6 2. OBJECTIVEβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦..7 3. ROLES AND REPONSIBILITYβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦..8 4. REQUIREMENTS ANALYSISβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦...9 5. SOFTWARE SPECIFICATIONβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦.β¦10 6. SYSTEM DESIGN ................................................................................................ 11 7. USE CASE DIAGRAMβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦..12 8. SECQUENCE DIAGRAMβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦.13 9. DFDβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦14-16 (a) 0-Level DFDβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦...17 (b) 1-Level DFDβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦..17 10. ER-DIAGRAMβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦..18 11. TABLE DESIGNβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦..19-22 12. MODULESβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦....23 13. BIBLIOGRAPHYβ¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦β¦.....24
- 6. TechDec- 6 Introduction TechDec is a Online Technical Discussion Forum who provides the Technical solution of your problems. This βTechDecβ is aimed at developing online form for the group discussion. This is a web-based application to manage group discussion forum. Whenever a question is asked by the end-user to get information ,it is received by the administrator. Any user can post the doubts topics and can reply for the other user doubts. There is a centralized database in which all the information is managed. The user can invites others for Discussion and submit query. The administrator has the rights to update the database. This is useful for a small office, school or a department or for that matter any group who is interested to organize it effectively. There are also connected user who acts as an intermediate user who can also answer the questions of the end-user if they know it. Facility to share the resource and post articles that can be viewed by registered user. Whenever the new information is arrived it is updated by the end-user. This TechDec Website involves with three types of users / Modules are: - β’ Administrator β’ Guest User β’ TechDec User
- 7. TechDec- 7 Objectives β’ To automate the multiple answers of the problem that helps people to find out relevant solution. β’ To automate the online discussion forum that helps users to easily find the answers & get your relevant solution. β’ To help users to provide skilled candidates with the help of Scale Point System. β’ To help the users to update their Profiles & do the Query. β’ It reduces cost to buy many books to find the relevant Solution for any query. β’ It reduces time to find the solutions & get may answers of their queries. β’ TechDec always get updated queries for your solution of the probems via notifications.
- 8. TechDec- 8 Roles and Responsibilities β’ Analysis users and Guest users module for TechDec β’ Designed mock up UI for users and guest users module β’ Implement view, model & controller for users and guest users module β’ Designed tables w.r.t users and guest users module β’ Fix issues while review by Project manager
- 9. TechDec- 9 Requirements Analysis The requirement analysis is done in order to understand the problem the software system is to be solved. The emphasis in requirement analysis is on identifying what is need for the system not how will achieve its goal. The goal of requirement activities is to document requirement in a software requirement specification. There are two major phase in this phase 1. Problem understood or analysis. 2. Requirement specification. In problem analysis the aim is to understand the problem and its context, the requirement of the system to be develop. Once problem analysis done and requirements understood. Requirements must be specified in requirement specification document. The requirement document must be specifying all function and performance of requirement. Format of input and output and design constraints due to political economical and environmental and security reasons. In other word besides functional specification all the factor the affect and design and proper functionality of the system must be specify in requirement document. Overall in requirement analysis we identify the requirement and constraints of proposal system. We can define requirement as βA condition of capability by a user to solve a problem or achieve an objectiveβ βA condition or a capability that must be met or possessed by a systemβ¦.. to satisfy a contract, standard, specification, or other formally imposed document.β
- 10. TechDec- 10 Software Specifications OS Windows 7 & Linux IDE& Other tools Eclipse, Navicat, Beyond, Compare, Pencil Versioning System Tortoise SVN Database MySQL Web Server Tomcat 7.0 Server side Languages& other tools Java 7, JDBC, JSP 2.2, Servlet 3.0.1 Client Side Languages & Other tools HTML, XML, CSS, JavaScript, JQuery, Bootstrap, JSON, AJAX
- 11. TechDec- 11 System Design System design is the process or art of defining the architecture, component, module, interface the data for a system to specified requirement. Object-oriented analysis and design (OOAD) methods are becoming the most widely used method for computer system design. The UML has become the standard language used in Object-oriented analysis and design. It is widely used for modeling Software System and is increasing used for high designing non-software system and organization.
- 12. TechDec- 12 Use Case Diagram A use case diagram at its simplest is a representation of a user's interaction with the system that shows the relationship between the user and the different use case in which the user is involved. A use case diagram can identify the different types of users of a system and the different use cases and will often be accompanied by other types of diagrams as well. TechDec View querie s Active/Un User Active/U n Post Delete query/ comment Guest User Registration / Login Post comment s Post query View Comme nts Post commen ts LogOut Update profile TechDec User Admin Add/del topic/sub topic LogOut Registration / Login View topics Contact
- 13. TechDec- 13 Sequence Diagram A Sequence diagram is an interaction diagram that shows how processes operate with one another and in what order. It is a construct of a Message Sequence Charts. A sequence diagram shows object interactions arranged in time sequence.
- 14. TechDec- 14 Data Flow Diagram DFD (data flow diagrams) known as a bubble chart has the purpose of clarifying system requirement and identifying major transformation that will e come programs in system design. So it is starting point of the design phase that functional decompose the requirement speciation down to lowest level of details. A DFD consist of bubbles joined by the lines. The bubbles represent the data transformation and the lines represent data flow in the system. DFD describes what data flow rather than how they are processed. The key question that we are trying to answer is: what major transformation must occur for input to be correctly transformed into output. Data Flow Diagram Symbols External Entity An external entity is a source or destination of a data flow. Only those entities which originate or receive data are represented on a business process diagram. The symbol used is a square containing a meaningful and unique identifier. Process External entity Proces s
- 15. TechDec- 15 A process shows a transformation or manipulation of data flows within the system. A circle represents a process that transfer incoming data flow into outgoing data flow. Dataflow A data flow shows the flow of information from its source to its Destination. A data flow is represented by a line, with arrowheads Showing the direction of flow. Information always flows to or from a process and may be written, verbal or electronic. Each data flow may be referenced by the processes or data stores at its head and tail, or by a description of its contents. Data store Data store A data store is a holding place for information within the system: It is represented by an open ended narrow rectangle. Steps to Construct Data Flow Diagrams Four steps are commonly used to construct a DFD β’ Process should be named and numbered for easy reference. Each name should be representative of the process.
- 16. TechDec- 16 β’ The direction of flow is from top to bottom and from left to right. β’ When a process is exploded into lower level details they are numbered. β’ The names of data stores, sources and destinations are written in capital letters. Rules for constructing a Data Flow Diagram β’ Arrows should not cross each other. β’ Squares , Circles and files must bear names. β’ Decomposed data flow squares and circles can have same names. Choose meaningful names for dataflow. β’ Draw all data flows around the outside of the Diagram.
- 17. TechDec- 17 Level 0 DFD request response request response Level 1 DFD role Request role Request User User User Response Query Request Response Contact User Guest User Administrator response response Guest user TechDec TechDec User Login TechDec user Login Admin
- 19. TechDec- 19 Database Design 1. User Field Data type (size) Constrains Description Id Int(11) Primary key Store Id fName Varchar(255) Not null Store fname lName Varchar(255) Not null Store lname Password Varchar(255) Not null Store password Gender Int(1) Not null Store gender DoB Date Not null Store dob Address Varchar(255) Null Store address State Varchar(10) Null Store statee Contry Varchar(50) Null Store country Contact Varchar(11) Not null Store contact Active Int(1) Not null Store active roleId Int(1) Not null Store role Email Varchar(100) Not null Store email
- 20. TechDec- 20 2. Role - Field Data type (size) Constrains Description Id Int(11) Primary key Store Id Name Varchar(50) Not null Store name 3. Topic- Field Data type (size) Constrains Description Id Int(11) Primary key Store Id Name Varchar(255) Not null Store name 4. Sub-Topic Field Data type (size) Constrains Description Id Int(11) Primary key Store Id pId int(11) Not null Store pid Name Varchar(50) Not null Store name
- 21. TechDec- 21 5. Question - Field Data type (size) Constrains Description Id Int(11) Primary key Store Id active int(11) Not null Store active Topicid Int(11) Not null Store topic subtopicId Int(11) Not null Store subtopic Description Varchar(500) Not null Store description Postdate Datetime(0) Not null Store date Postedby Int(11) Not null Store postedby
- 22. TechDec- 22 6. Answer - Field Data type (size) Constrains Description Id Int(11) Primary key Store Id qid int(11) Not null Store qid Answer Varchar(4000) Not null Store ans Postedat Datetime Not null Store date Postedby Int(11) Not null Store postby 7. Contact - Field Data type (size) Constrains Description Id Int(11) Primary key Store Id userId int(11) Not null Store user Suggestiondate Date Not null Store date Subject Varchar(100) Not null Store subject Suggestion Varchar(500) Not null Store suggestion
- 23. TechDec- 23 Modules The system has various modules:- β’ Administrator: The authorized person who controls the entire network. β’ User: Those who are post queries / comments for the solution. β’ Guest User: Those who are posting queries & comments for the general category only. Functional Specification Administrator a) Manage Job Seeker and Employer Profiles ,Payment of both . b) Add new Service related to Employer or jobseeker and send massage for subscriber etc. c) Provide Role and authentication to user. d) Ability to change the look and feel of your site by changes templates . e) Most recent job to be displayed on home page. f) Search job on category base.
- 24. TechDec- 24 BIBLIOGRAPHY A bibliography, the product of the practice of bibliography, is a systematic list of books and other works such as journal articles. Bibliographies range from "works cited" lists at the end of books and articles to complete, independent publications. As separate works, they may be in bound volumes or computerized bibliographic databases. A library catalog, while not referred to as a "bibliography," is bibliographic in nature. The complete reference java 2, fourth edition - Herbert Schildt An Integrated Approach to Software Engineering - Press man Java 2 Black Book - Steven Holzner et al,