
	Trending ▼ ICSE CBSE 10th ISC CBSE 12th CTET GATE UGC NET Vestibulares ResFinder

srssdfghhjjkkkk

38 pages, 0 questions, 0 questions with responses, 0 total responses,

	joyara	+Fave Message
	Profile Timeline Uploads

Home > joyara >

Formatting page ...

Foolish Nerds Work to worker services to unorganized sector Team Guide Deepa Gangwani Team Members Rajat Mahadevan Saurajit Bhuyan Shiv Shankar Kumar Singh Sumit Anand Index & Tables 1) Introduction: 1.1) Purpose:------------------------------------------------------ 3 1.2) Scope:--------------------------------------------------------- 3 1.3) Abbreviations:----------------------------------------------- 3 1.4) References:--------------------------------------------------- 5 1.5) Technologies:------------------------------------------------ 5 1.6) Overview:---------------------------------------------------- 5 2) Overall Description: 2.01) Product Perspective:--------------------------------------- 5 2.02) Software Interface:----------------------------------------- 5 2.03) Hardware Interface:---------------------------------------- 5 2.04) Communication Interface:-------------------------------- 5 2.05) User Characteristics:--------------------------------------- 5 2.07) Constraints:-------------------------------------------------- 5 2.08) Use-Case Model Survey:---------------------------------- 6 2.09) Product Perspective:-------------------------------------- 11 3) Specific Requirements: ------------------------------------------ 36 2 1) Introduction: 1.1) Purpose: The purpose of the project is to provide workers of the unorganized sector to actually communicate with the customers in a systematic and organized manner which can be profitable to workers and as well as for the customers. The basic aim of the Software Requirement Specification is specify the requirements of the project as well as the basic functioning and overview of the system. 1.2) Scope: Create different system users and assign different roles with related permissions. Manage all the account details such as user name, password, phone numbers, address websites, email addresses of the entire customers and workers from one central location. Track all the contact details of customers and workers. Maintain the services provided to the customer as well as the workers. Providing an interface through which customers can publish their job requests to the workers. Providing an interface through which workers can apply for their respective jobs. View and edit all user activities, including email, chats, and services calls in a single system. Categorization of different type of workers according to their skills and semi skills. Confirmation of end user identity and validation of user accounts. Maintain history of each worker s job completion listings and their related information. Provide a general forum workspace for the users of the system to communicate and query with each other. Enhancing the means of communication between customer and worker through the means of SMS/chat and messaging. Providing a community workspace for the customers for reference purpose. Easy user interface and multi language for specifically for workers for better interaction with the system and customers. A rating evaluation system for workers to rate them according to their quality of work by the customers. Providing easy interface for job carts for the customers and workers for better work allocation and work searching respectively. 1.3) Abbreviations: HTML: Hypertext Markup Language is a markup language used to design static WebPages. Visitors: Users that are not registered, casual users visiting the website. 3 Customers: Users of the system employing workers to do their specified job. Workers: Users of the system accepting job requests from the customers. Job cart: List containing job offers made by the customers. Admin: User of the system privileged to control all functions in the system. Forums: Place of interaction among users of the system except the visitors. FAQ: Frequently asked questions published on the website. Community: Workspace where customers create communities for reference purpose. Grievance Readdresses: Workspace where users of the system post complaints and queries about the website, customer support. Feedback: The reviews and comments given to the worker by customers according to their quality of work. Work Offer: The requests made by the customer for job offers to the workers. Skill: The type of work that a worker is proficient. SMS: Short Messaging Service. EJB: Enterprise Java Beans. J2EE: Java 2 Enterprise Edition is a programming platform part of the Java Platform for developing and running distributed multitier architecture Java applications, based largely on modular software components running on an application server. DB2: DB2 Database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications. WAS: Web sphere application server is an application server that runs business applications and supports the J2EE and web services standards. WSAD: Web sphere studio application developer is a toolkit which is designed for the creation of more complex projects, providing fully dynamic web application utilizing EJB s. This consist of EJB tools, CMP, data mapping tools & a universal test client that is designed to aid testing of EJB s. HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server. HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer). TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP. 4 1.4) References: IEEE SRS Format Problem Definition (Provided by IBM) 1.5) Technologies: J2EE: Application Architecture DB2: Database WSAD: Development Tool WAS: Web Server Rational: Design Tool 1.6) Overview: SRS will include two sections: Overall Description will describe major components of the system, interconnection and external interfaces. Specific Requirements will describe the functions of actors, their role in the system and constraints. 2) Overall Description: Describe the general factors that affect the product and its requirements. 2.1) Product Perspective: The web pages (XHTML/JSP) are present to provide the user interface on customer client side. Communication between users of the system and server is provided through HTTP/HTTPS protocols. The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used. On the server side web server is for EJB and database server is for storing the information. 2.2) Software Interface: Client on Internet: Web Browser, Operating System (any) Client on Intranet: Client Software, Web Browser, Operating System (any) Web Server: WAS, Operating System (any) Data Base Server: DB2, Operating System (any) Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML), DB2, OS (Windows), Web Server. 5 2.3) Hardware Interface: Tab: 2.1 Hardware Requirements 2.4) Communication Interface: Client on Internet will be using HTTP/HTTPS protocol. 2.5) User Characteristics: Every user should be comfortable of working with computer and net browsing. He must have basic knowledge of English too. 2.6) Constraints: GUI is only in English. Login and password is used for identification of customer and workers. No facility for visitors to participate in active system activities. This system is working for single server. There is no maintainability of back up so availability will get affected. Limited to HTTP/HTTPS. 6 2.7) Use-Case Model Survey Fig: 2.1 Use Case Diagram for Overall System 7 Fig: 2.2 Use Case Diagram for Administrator s Functions Administrator: Responsible for managing system users, viewing logs and managing standard the system. Maintain System: The Administrator will carry system backup and restoring operations, add new skills and maintain the portals (update new web interfaces). Manage Job Cart: The administrator will delete inactive jobs after a specified period of inactivity, prioritize sponsored jobs and delete bad/vulgar job cart additions. Manage Members: The administrator blocks or deletes unwanted users and views user profiles. Manage Forums: The administrator creates or deletes topics. Manage FAQ: The administrator creates deletes or edits FAQs. Search Member: The administrator search for a member to view his/her profile details. Generate Reports: Reports based on different parameters are generated by the administrator. Solve Grievances: The grievance raised by the users need to be addressed by the administrator. 8 Delete Community: The illegal/vulgar/obscene communities need to be deleted by the administrator. Manage accomplished Job List: The list of jobs that have been accepted by both the worker/workers and a customer is to be maintained by the administrator. Update Personal Information Change Security Info View Cart apply for Job delete profile Browse Job Cart Manage Profile M anage Remi nder Search j ob Manage Job schedual Look Up View Cart Search Customer Manage Calender Worker Manage Memo Appl y For Work View FAQ Grivances Readressal Forum Log in Log Out create topi c post repl y fl ag topics delete topics Fig: 2.3 Use Case Diagram for Worker s Function Worker: Is a member who has specific skill and is seeking for work through the system. Manage Profile: The worker creates profile, update profile and could also change the security in formations after proper verifications. Browse Job Cart: The worker can view the job cart listed with the work requirements and could also apply for the work. Manage Calendar: The worker manages calendar for daily work schedules and appointments. Worker may also save reminder which system will remind as per the schedule. The worker keeps account about the jobs applied for. 9 Forums: The worker may create topics; post reply s, deletes topics and may flag required topics. FAQ: The worker view FAQ s. Search Job: The worker search for jobs, specifying the skill or the region of preference. Search Customer: The Worker search for customer, specifying the name or the region. To contact customers or post queries. Apply For Job: A Worker may apply for job on the home page or on the job cart. Grievances: The grievances raised by the Worker are addressed to the concerned. Fig 2.4 Use Case Diagram for Visitor s Functions Visitor: Is an anonymous user who can be a future member. Registration: Visitor can register to become a member providing various information and identity. Browse Forum: Visitor can view the forum post and post a reply. Look for Work or Worker: Visitor can search or browse for offered work or any specific skill in a specific region. 10 View Business Rules: The visitor view or browse the business rules imposed by system administrator to run the system. View FAQ: The visitor views FAQs. View About: The visitor views about the system. Rate Worker Giv e Feedback Manage List <<include>> View Result Browse Skill <<include>> Delete a community Browse Region <<include>> Visit Worker Prof ile Griev arance Readressal <<extend>> Search Make Community Manage Prev ious Worker list Remov e User Look Up Request a Worker Join Community Manage Community Unjoin a Community Reschedual a Work Manage Worker Booking Customer Manage Work Of f er Update Work status Finalize a Worker Manage Prof ile Cancel Work Of f er Forums Reject a Worker Login View FAQ Edit Work Of f er LogOut Manage worker Application List P ost Work Of f er Delete Prof ile Edit Prof ile Reject Request Accept Request Create Topic Delete Topic Flag a Topic Post a Reply Fig: 2.5 Use Case Diagram for Customer s Functions Customer: Manage Worker Booking: Provides editing, rescheduling, deletion etc of the job offering made by the customers. Manage Profile: Enable users to edit and delete their account. Manage worker Application List: Customers can accept and deny worker request for a job through this list. Manage Work Offer: Customers can edit, delete etc their work offers from the job cart. Manage Community: Customers can perfor m functions related to community. 11 Manage Previous Worker list: Customers can review and give feedbacks to the appointed workers. 2.8) Product Perspective HTTP/HTTP HTTP Client (Administrator) WAS DB2 HTTP/HTTP HTTP Client (Members/Users) Fig: 2.6 Product Perspectives The web pages provide the user interface(s) for visitor on client side. Communication between client and server is provided through HTTP/HTTPS protocol. The web pages provide the user interface for administrator on client side. Communication between administrator and server is provided through HTTP/HTTPS protocol. On the server side, web server is for PHP and DB2 database for storing the information. 12 3) Specific Requirements Use-Case Reports (Functional Requirements) Administrator: Responsible for managing system users, viewing logs and managing standard the system. Maintain System: The Administrator will carry system backup and restoring operations, add new skills and maintain the portals (update new web interfaces). Manage Job Cart: The administrator will delete inactive jobs after a specified period of inactivity, prioritize sponsored jobs and delete bad/vulgar job cart additions. Manage Members: The administrator blocks or deletes unwanted users and views user profiles. Manage Forums: The administrator creates or deletes topics. Manage FAQ: The administrator creates deletes or edits FAQs. Search Member: The administrator search for a member to view his/her profile details. Generate Reports: Reports based on different parameters are generated by the administrator. Solve Grievances: The grievance raised by the users need to be addressed by the administrator. Delete Community: The illegal/vulgar/obscene communities need to be deleted by the administrator. Manage accomplished Job List: The list of jobs that have been accepted by both the worker/workers and a customer is to be maintained by the administrator. Maintain System: Fig 3.1: Use case Diagram for Maintaining System 13 Ask wants to Backup or Restore Ask for Location to s ave BackUp Restore Backup Ask for BackUped file Location Invalid File Unsucessful BackUp Sucessful BackUp Display Confirmation Valid File Fig: 3.2 Activity Diagram for Back Up / Recovery of System Name of use case: Back Up / Recovery Description: To create a backup of the system or to recover the system. Preconditions: Administrator is already logged in. Normal flow of events: Select Back Up or Recover Select location to store backup or select file to from where to recover the system Relevant confirmation displayed. Alternate flow of events: None. Post Condition: Back up created or system recovered. 14 Ask Administrator Password Invalid Skill Details Ask for Skill Details Add Skill Delete Skill Confirm Deletion Yes Valid Skill Details Display Confirmation Add New Skill and Display Confirmation No Fig: 3.3Activity Diagram for Managing Skills Name of use case: Manage Skills Description: To create new skills or delete skills. Preconditions: Administrator is already logged in. Normal flow of events: Select weather to new create skills or delete existing skills. Confirm Deletion (if deletion is selected). Display confirmation. Alternate flow of events: None. Post Condition: Skills added or deleted. 15 Manage Job Cart: Fig: 3.4 Use Case Diagram for Managing Job Cart Display Inactive Jobs Confirm Deletion of Selected Job Yes Display Confirmation No Fig: 3.5 Activity Diagram for Deleting Inactive Jobs Name of use case: Delete Inactive Jobs Description: To delete jobs those are inactive for a specific period of time. Preconditions: Administrator is already logged in. Normal flow of events: Select inactive jobs to be deleted. Confirm Deletion. Alternate flow of events: None. Post Condition: Inactive jobs deleted. 16 Manage Members: Fig: 3.6 Use Case Diagram of Managing Members Ask for Member Name/Names Member does not Exist Member Exists Dispaly Matched Member Name/Names Confirm deletion of S elected Members Yes Display Confirmation No Fig: 3.7Activity Diagram for Blocking Members Name of use case: Block Member. Description: To block Member. Preconditions: Administrator is already logged in. Normal flow of events: Select user/users to block. 17 Confirm blocking of selected user/users. Alternate flow of events: None. Post Condition: Selected member/members blocked. Manage FAQ: Fig: 3.8Use Case Diagram for Managing FAQ Ask for the FAQ to Edit Show the FAQ t o Edit Display Confirmation Fig: 3.9 Activity Diagram for Editing FAQ Name of use case: Edit FAQ Description: To edit an FAQ. Preconditions: Administrator is already logged in. Normal flow of events: 18 Select FAQ to edit. Edit FAQ. Alternate flow of events: None. Post Condition: FAQ edited. Manage Forums: Fig: 3.10Use Case Diagram for Managing Forums Ask Topic Details and Content Topic Already Exists New Topic Display Confirmation Fig: 3.11 Activity Diagram for creating a topic in the forums Name of use case: Create topic Description: To create a new topic in the forums. Preconditions: Administrator is already logged in. Normal flow of events: Create a new Topic. 19 Edit FAQ. Alternate flow of events: None. Post Condition: FAQ edited. Worker: Is a member who has specific skill and is seeking for work through the system. Manage Profile: The worker creates profile, update profile and could also change the security in formations after proper verifications. Browse Job Cart: The worker can view the job cart listed with the work requirements and could also apply for the work. Manage Calendar: The worker manages calendar for daily work schedules and appointments. Worker may also save reminder which system will remind as per the schedule. The worker keeps account about the jobs applied for. Forums: The worker may create topics; post reply s, deletes topics and may flag required topics. FAQ: The worker view FAQ s. Search Job: The worker search for jobs, specifying the skill or the region of preference. Search Customer: The Worker search for customer, specifying the name or the region. To contact customers or post queries. Apply For Job: A Worker may apply for job on the home page or on the job cart. Grievances: The grievances raised by the Worker are addressed to the concerned. Worker Update Profile: delete profil e Change Security Info Manage Profil e Update Personal Information Fig: 3.12 Use Case Diagram To Manage Profile: 20 A sk Password Invalid Password Valid Password Display Profile Details Invalid Profile Details Valid Profile Details Display Conformation Fig: 3.13 Activity Diagram of Updating Profile Name of use case: Worker Update Profile Description: To update worker profile Preconditions: Worker is already logged in Normal flow of events: User authentication is asked Profile details are displayed Conformed details are submitted Alternate flow of events: A message displayed for the again entering the password A message displayed to enter valid profile details. Post condition: The worker profile is conformed. 21 Worker Job Cart V iew Cart Browse Job Cart apply for Job Fig: 3.14 Use Case Diagram for Workers Job Cart Display Job Lists Display Work Details View Other Job Details Apply For Work Display Application Conformation Fig: 3.15 Activity Diagram for accepting a job offer Name of use case: Apply for job Description: Worker may apply for job or view details of job. Preconditions: Worker is logged in. Normal flow of events: 22 Job list is displayed. Worker apply for a job Worker view details of other jobs Alternate flow of events: none Post condition: A job application confirmation is displayed. Worker Job Calendar: M anage Remi nder Manage Job schedual Manage Cal ender Manage Memo Fig: 3.16 Use Case Diagram For Worker Job Calendar: Display The Date Schedules View Other Date View Details Display Details Of A schedule Delete Schedules Add Schedules Display the Schedules Fig: 3.17 Activity Diagram for viewing, adding or deleting work schedules. 23 Name of use case: Worker Job Calendar Description: Worker may view the work schedules on date. Workers could add or delete the schedules. Preconditions: Worker is logged in. Normal flow of events: Job schedules are displayed for the date. Workers may view the other dates schedules. Worker adds or deletes schedules. Alternate flow of events: A message displayed if no schedule for the date. Post condition: Display of on the date schedules. Worker Search Job: Search job View Cart Look Up Fig: 3.18 Use Case Diagrams to Search Jobs 24 Ask For Skill Or Region Search Skill Search Region Display Jobs A ccording To Region Display Jobs A ccording To Skills Fig: 3.19 Activity Diagram for searching a job. Name of use case: Worker Search Job Description: Worker may search for jobs according to their skills and region. Preconditions: Worker is logged in. Normal flow of events: Job search options are displayed. Worker search for a job according to skills or region Worker view details of the jobs. Alternate flow of events: A message displayed for a wrong input. Post condition: Lists of jobs are displayed according to the search. 25 Worker Login: L og Out Log i n Fig: 3.20 Use Case Diagram for worker login/logout Ask For Username And Password Invalid Create User Valid Display User Account Fig: 3.21 Activity Diagram for Login/ Logout operations Name of use case: Worker Login Description: User authentication is done for privacy of workers account. Preconditions: Worker is not logged in. Normal flow of events: System asks for worker username and password. System verifies the user and password After verification user visits its account. Alternate flow of events: 26 A message displayed for a wrong input. A message displayed for invalid entries. A message displayed to create a user. Post condition: A user successfully logged in. Manage Worker Bookings Request a Worker Reschedual a Work Manage Worker Booking Finalize a Worker Reject a Worker Fig: 3.22 Use Case Diagram of Managing Booking of Workers 27 Ask Password Invalid Password Valid Password Display Selected Job Invalid Input Valid Input Change Confirmation Fig: 3.23 Activity Diagram of Rescheduling a Job Name of use case: Reschedule a Work Description: Customers can reschedule the work. Preconditions: Customer is logged in. Normal flow of events: Ask for password. Display selected job. Confirm change. Alternate flow of events: none Post condition: The change is confirmed. 28 Look Up Browse Skill Browse Region Look Up S earch Fig: 3.24 Use Case Diagram for Looking for workers Ask for Skill or Region Skill Display Worker according to Skill Region Display Workers according to Regions Fig: 3.24 Activity Diagram for Looking for workers Name of use case: Customer lookup. Description: Customers can search according to specified conditions. Preconditions: Customer is logged in. Normal flow of events: Ask for skill or region. Display workers either according to regions or skill. Alternate flow of events: none Post condition: Display workers. 29 Manage Profile E dit Profile Manage Profile Delete Profile Fig: 3.25 Use Case Diagram for Managing Profile Ask Password Invlid Password Valid Password Display Profile Invalid Profile Detials Valid Profile Details Display Confirmation Fig: 3.26 Activity Diagram for Managing Profile Name of use case: Customer Edit Profile. Description: Customers can edit/delete their profile details. Preconditions: Customer is logged in. Normal flow of events: Ask for password confirmation. Display profile of customer. Display confirmation information. 30 Alternate flow of events: none Post condition: Display Confirmation Ask Password Invlid Password Valid Password Confirm Deletion No Yes Display Confirmation Fig: 3.27 Activity Diagram for Editing Customer Information Name of use case: Customer Delete Profile. Description: Customers can delete their profile details. Preconditions: Customer is logged in. Normal flow of events: Ask for password confirmation. Display profile of customer. Display confirmation information. Alternate flow of events: none Post condition: Display Confirmation. 31 Forum Activities: Flag a Topic Delete T opic Forum s Post a Reply Create T opic Fig: 3.27 Use Case Diagram of Forums Activities Ask For Topic Details Display Confirmation Fig: 3.28 Activity Diagram of Forums Activities Name of use case: Customer Create New Forum. Description: Customers can delete their profile details. Preconditions: Customer is logged in. Normal flow of events: Ask for password confirmation. Display profile of customer. Display confirmation information. Alternate flow of events: none Post condition: Display Confirmation. 32 Visitor: Is an anonymous user who can be a future member. Registration: Visitor can register to become a member providing various information and identity. Browse Forum: Visitor can view the forum post and post a reply. Look for Work or Worker: Visitor can search or browse for offered work or any specific skill in a specific region. View Business Rules: The visitor view or browse the business rules imposed by system administrator to run the system. View FAQ: The visitor views FAQs. View About: The visitor views about the system. Browse Forum: <<include>> View Post <<include>> Browse Forum Reply a Post Fig: 3.29 Use Case Diagram for Browse Forum Select a Topic View Post Reply a Post Ask To W rite Post the Reply Fig: 3.30 Activity Diagram for Browse Forum 33 Name of use case: Browse Forum Description: To view and reply any post in available in forum. Preconditions: Visitor is already be in Forum Section Normal flow of events: Select a Topic. Post the Reply Alternate flow of events: None. Post Condition: Reply Posted. Registration: <<include>> Registeration Register Fig: 3.31 Use Case Diagram for Registration Ask for Registration Info Info entered Check info Validity Invalid Display Plz Provide Valid Info Valid Create User Show Conformation Send Activation to Code to User e-mail id Fig: 3.32 Activity Diagram for Registration 34 Name of use case: Visitor Registration Description: Visitor can register to take services of the system. Preconditions: None Normal flow of events: Ask for registration information Confirm registration. Alternate flow of events: None. Post Condition: User Created. Look For Work or Worker: B rowse Region <<include>> Browse Skill <<include>> <<include>> Look For Work Or Worker View Result Browse Work Offers <<include>> Search Fig: 3.33 Use Case Diagram for Look for Work or Worker 35 Ask To Select Task Search Work offer or Skill Browse Region and Skill Ask To Enter S kill and Region Data Entered Promt to Select Region and Skill selected Searh Database Show Results No Match Found Match Found Display Result Fig: 3.34 Activity Diagram for Look for Work or Worker Name of use case: Look for Work or Worker Description: Visitor can search or browse skill or category. Preconditions: None Normal flow of events: Search database Show results Alternate flow of events: None. Post Condition: display searched result. 36 4) Supplementary Requirements (Non-Functional Requirements) Non-functional requirements govern characteristics of a system. Many non-functional requirements will have direct Implications to the project in the form of cost implications, performance objectives and future growth potential. The followings are the Non-Functional Requirements of the project: Have hours of operation: that are 24 x 7 - Because system can be an automated process, so it can stay open for 24 hours a day. Making the existing Web site more dynamic in nature: An effective system should be largely dynamic taking advantage of technology that automates this process rather than relying on manual processes. Application should serve dynamic user based customized web pages to its clients from server. Provide good performance and the ability to scale the server: The Web Application Server should provide good performance and the ability to manage performance with techniques, such as support for caching, clustering, and load balancing. Providing session management capability: Web application developers should not spend valuable time worrying about how to maintain sessions within the application. The Web Application Server should provide these services. Architecture: Flexible service based architecture will be highly desirable for future extension. Better component design to get better performance at peak time Sufficient network bandwidth: Availability of Sufficient network bandwidth. Configuration analysis: The environment and infrastructure which the web application will reside are identified. 37 User interface and priorities: Professional look and feel. Browser testing and support for IE, NN, Mozilla, and Firefox. Use of Graphical tool like JASPER to show strategic data to admin. Reports exportable in .XLS, .PDF or any other desirable format. Domain name registration: Domain name of the web site should be registered. Server space: Sufficient amount of server space must be purchased to run the web site. Submission of web site to the popular search engine like goggle, yahoo, etc. Important Issues: Any creative ideas to support and promote to urbanize the economy. Web services should be highly customizable and flexible enough to easily deploy. High dependability/low downtime 38

Formatting page ...

joyara chat

Horizontal lines at:
Guest Horizontal lines at:
AutoRM Data:
Box geometries: