Srs On Feature Rich Resume Builder 3h6j6y

Amity university noida Uttar pradesh

Feature-rich resume builder Software requirement specification

TEAM Iceangels Team Megha Sahni Laxmi Rawat Kriti Sharma Kanika Choudhary Project guide Mrs Shilpi Sharma

1

Index & Tables 1) Introduction: ..............................................................................................................................3 1.1) Purpose: ...............................................................................................................................3 1.2) Scope: ..................................................................................................................................3 1.3) Abbreviations:.....................................................................................................................3 1.4) References: ...........................................................................................................................5 1.5) Technologies: .......................................................................................................................5 2) Overall Description:.................................................................................................................5 2.01) Product Perspective: ..........................................................................................................5 2.02) Software Interface:.............................................................................................................6 2.03) Hardware Interface: ...........................................................................................................6 2.04) Communication Interface:.................................................................................................7 2.05) Product Function:...............................................................................................................7 2.06) Characteristics:..........................................................................................................7 2.07) Constraints: ........................................................................................................................7 2.08) Use-Case Model Survey:...................................................................................................8 2.09) Database design: ..............................................................................................................10 2.10) Assumptions and Dependencies: ....................................................................................12 3) Specific Requirements: ...........................................................................................................12 3.1) Use-Case Reports:..............................................................................................................12 3.2) class diagram: .................................................................................................................22 3.3)supplementary requirements:…………………………………………………………………...23

2

1) Introduction: 1.1)

Purpose: Feature-rich resume builder is used for automating the process of Resume Writing. This would be facilitating the employees to make and print their resumes in a proper format. In addition, it will be facilitating the higher management to search the employees depending upon their skills sets and other attributes.

1.2)

Scope: we describe what features are in the scope of the software and what are not in the scope of the software to be developed. In scopea. Create different system s and assign different roles with related permissions. b. Manage all the details such as name, phone numbers, address ,websites, email addresses of all the from one central location. c. Track all the s and their details. d. Confirmation of end identity and will which s are authorized to receive . e. Maintain history of each and their related information . f. can select the format of their resume from the given templates. g. can update or edit their resume. h. s can take print of their resume. i. Interface for filling up the information like Skill sets, Training and Visa Details. j. Having collaboration with various companies. k. Companies can search the employees on the basis of skills sets. l. Companies can send invitation on their s . m. Giving alerts to the if he requests for one. n. can utilize various applications such as chatting, search engine, weather reports, latest news etc. o. authentication.

1.3)

Abbreviations: 1. FRRB: Feature-rich resume builder 3

2. SRS: software requirement specification. 3. WWW: world wide web 4. EJB: Enterprise Java Beans. 5. J2EE: Java 2 Enterprise Edition 6. DB2: DB2 Database 7. WAS: Web sphere application server 8. UML: unified modeling language 9. XML: extended markup language 10. AJAX: asynchronous javasript+xml 11. SOA: service oriented architecture DEFINITIONS: Resume: Job-seekers create their resume of their chosen styles so that companies can select and give them an invitation. Company: various companies are having collaboration with the site and they can choose the resumes of job seekers. Personal details: Details of customer such as name, company, phone number, address, website, e-mail address etc. details: Details of persons associated with the company (customer). HTML: Hypertext Markup Language is a markup language used to design static web pages. 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 costeffective database platform to build robust on demand business applications. WAS: Web sphere application server is an application server that runs business applications and s 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. 4

1.4)

References:

1. IEEE SRS Format 2. Problem Definition (Provided by IBM) 3. CT Arrington. Enterprise Java with UML. OMG Press. 1.5) Technologies: 1. J2EE: Application Architecture 2. DB2: Database 3. WSAD: Development Tool 4. WAS: Web Server 5. Rational: Design Tool 6. UML: design tool 7. XML 8. e-Forms 9. AJAX 10. Web 2.0 11. Web-services 12. SOA 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.01) Product Perspective:

5

1. The web pages (XHTML/JSP) are present to provide the interface on customer client side. Communication between customer and server is provided through HTTP/HTTPS protocols. 2. The Client Software is to provide the interface on system client side and for this T/IP protocols are used. 3. On the server side web server is for EJB and database server is for storing the information.

2.02) 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.

2.03) Hardware Interface:

6

2.04) Communication Interface: 1.

Client on Internet will be using HTTP/HTTPS protocol.

2.

Client on Intranet will be using T/IP protocol.

2.05) Product Function: Track Level Data: In this module, receivables from customer are maintained. Information: It maintains all the details (Personal, Official, , and

Company) of the customer. Maintaining Logs: Activities of the System s can be tracked through the logs, which is maintained by the system.

2.06) Characteristics: Every should be comfortable of working with computer and net browsing. He must have basic knowledge of English too.

2.07) Constraints: 1. GUI is only in English. 2. and is used for identification of customer and there is no facility for guest. 3. This system is working for single server. 4. There is no maintainability of back up so availability will get effected. 5. Limited to HTTP/HTTPS

7

2.08) Use-Case Model Survey:

<,include update resume

photograph

sign in

ed

remove photo view resume profile

styles of resume

create

change photo delete

edit profile

sign up

create resume

update profile change

application games

company themes

chatting

non-ed news

weather report customer tips

change theme set theme

help

search

job articles

manage the system

view details

display information

frequently asked questions

site map

alerts inform to set alert show alert

delete alert give alert to

8

1. : Responsible for managing system s, viewing logs and managing standard groups of the system. Manage System s: The will create different roles. The system s will be created and will be assigned with the different roles. More than one task and permissions can be granted or revoked from the system s. View Logs: Responsible for checking the logs of different system for auditing and maintaining the integrity of the system. Manage Standard Groups: Standard groups will be created and updated by the , which will be visible to all the system s. View All Details: View the customer details, resume details. Give alerts: The gives alert to the about the invitations received from the companies. 2.: A can be ed or non ed ed : A ed is one who has created an and is ready to create the resumeamong the different format available. Non-ed : A non-d is one who has not created an yet but has visited the site as a guest. Create resume: A can select the format of resume from different styles given and can create and update them. Use applications: A can use the various applications provided such as games,chatting,weather report,news,themes,etc. 3.company:A company can select the resumes by searching for a particular skill attribute they want. Send alerts: a company can send alert to the and the can send alert to the .

9

2.09) Database design:

ISA

System_role Role_id Role_name

company

System_ed

System_log

has

_ID _name _value First_Name Last_Name E-mail Modified Created

_id

Applications Themes News Customer_tips makes

Chatting

Resume

Games

Styles of resume

Weather_ report

Update_resume

First_name Last_name

View_resume Create_resume

Profile

Photograph

About_me

Remove_photograph

Date_of_birth

Change_photograph

Qualifications e-mail

10

System_view Company name Skills

has

System_log _id

Alerts Give alert to the

company



System_re gistered

System_view System_log

applications

System_log

alerts profile

photograph

resume

11

2.10) Assumptions and Dependencies: 1. The details related to the product, customer, payment and service transaction provided manually. 2. is created in the system already. 3. Roles and tasks are predefined.

3)Specific Requirements: 3.1) Use-Case Reports: 1) Name of use case: Sign in Description: Accessing the Preconditions: ? There should be an existing of the ? is already logged in. Normal flow of events: • details are entered • authentication is provided by the • corresponding output if the entries made by the are correct Alternate flow of events: None. Post Condition: None. 2) Name of use case: Sign up Description: Creating a Preconditions: ? Knowledge about the website ? Existing database ready to accept the details of the ? is already logged in. Normal flow of events: • details are entered • storage of information to the database Alternate flow of events: None. Post Condition: None. 3) Name of use case: Create Description: Creating a Preconditions: ? Knowledge about the website ? Existing database ready to accept the details of the ? is already logged in. Normal flow of events: • details are entered • storage of information to the database Alternate flow of events: None. 12

Post Condition: None. 4) Name of use case: Profile Description: Showing information Preconditions: ? Accumulating each and every detail of the ? Retrieving details from the database ? is already logged in. Normal flow of events: • The information regarding the respective is retrieved from the database • Showcasing the entire information Alternate flow of events: None. Post Condition: None. 5) Name of use case: Edit profile Description: Making changes to the current profile Preconditions: ? There should be an existing profile ? is already logged in. Normal flow of events: • Changes to the existing profile • Displaying the changed profile Alternate flow of events: None. Post Condition: None. Name of use case: Update profile Description: Additions to the existing profile Preconditions: ? There should be an existing profile ? is already logged in. Normal flow of events: • Add on to the existing profile • Displaying the changed profile Alternate flow of events: None. Post Condition: None. 6) Name of use case: Change Description: Creating a new Preconditions: ? There should be an existing ? is already logged in. Normal flow of events: • Entering the existing • Entering the new Alternate flow of events: None. Post Condition: None. 7) Name of use case: Delete Description: Deleting the existing 13

Preconditions: ? There should be an existing ? is already logged in. Normal flow of events: • Accessing the details from the database • Removal of all the details from the database Alternate flow of events: None. Post Condition: None. 8) Name of use case: Photograph Description: Attachment of the ’s photograph to the profile Preconditions: ? is already logged in. Normal flow of events: • Providing the path of the photograph • Attachment of the photograph Alternate flow of events: None. Post Condition: None. 9) Name of use case: Change photo Description: Altering the existing photo Preconditions: ? is already logged in. ? There should be an existing photo Normal flow of events: • Removing the existing photo • Attaching the new photo Alternate flow of events: None. Post Condition: None. 10) Name of use case: Remove photo Description: Deleting the existing photo Preconditions: ? There should be an existing photo in the database ? is already logged in. Normal flow of events: • Accessing the existing photo • Removing the existing photo Alternate flow of events: None. Post Condition: None. 11) Name of use case: View resume Description: Actual view of the resume Preconditions: ? is already logged in. ? Already existing resumes of the s Normal flow of events: • Select the name 14

• Permission from the for viewing Alternate flow of events: None. Post Condition: None. 12) Name of use case: Create resume Description: Addition of all the details Preconditions: ? is already logged in ? Accumulating each and every detail of the at one place Normal flow of events: • sign in • Creation of resume as per the ’s choice Alternate flow of events: None. Post Condition: None. 13) Name of use case: Application Description: Provide the with functionalities Preconditions: ? There should be an existing profile for the Normal flow of events: • logging in • Accessing all the pre existing functionalities Alternate flow of events: None. Post Condition: None. 14) Name of use case: Games Description: Provides the functionality of gaming Preconditions: ? should be logged in Normal flow of events: • logging in • Selection of a particular game from the given list Alternate flow of events: None. Post Condition: None. 15) Name of use case: Chatting Description: Helps the interact with other s Preconditions: ? should be signed in Normal flow of events: • logging in • Conversation with other s Alternate flow of events: None. Post Condition: None. 16) Name of use case: Weather report Description: Describes the current weather Preconditions: 15

? should be logged in Normal flow of events: • logging in • Information received about the current weather Alternate flow of events: None. Post Condition: None. 17) Name of use case: Customer tips Description: Provide friendly tips Preconditions: ? must be signed in ? must be logged in Normal flow of events: • logging in • Popping friendly tips Alternate flow of events: None. Post Condition: None. 18) Name of use case: News Description: Provide the with the news upgrades Preconditions: ? should be logged in Normal flow of events: • logging in • Getting upgrades regarding the current topic Alternate flow of events: None. Post Condition: None. 19) Name of use case: Themes Description: Getting the different ideas or giving the choices for selecting the different themes Preconditions: ? should be logged in ? should be logged in Normal flow of events: • logging in • Selecting the appropriate theme Alternate flow of events: None. Post Condition: None. 20) Name of use case: Change themes Description: Replacing the current theme by selected one Preconditions: ? should be logged in Normal flow of events: • logging in • Selecting a specific theme from the given choices • Replacing the current theme by the selected one Alternate flow of events: None. 16

Post Condition: None. 21) Name of use case: Set theme Description: sets the current theme Preconditions: ? should be logged in Normal flow of events: • logging in • Setting up the selected theme Alternate flow of events: None. Post Condition: None. 22) Name of use case: Alerts Description: Giving alerts or the latest updates to the Preconditions: ? should be logged in Normal flow of events: • logging in • Getting the alerts Alternate flow of events: None. Post Condition: None. 23) Name of use case: Set alert Description: Sets the required condition to get the alerts Preconditions: ? should be logged in ? should be logged in Normal flow of events: • logging in • Getting the required updates Alternate flow of events: None. Post Condition: None. 24) Name of use case: Show alert Description: Shows the updates on the required page Preconditions: ? should be logged in Normal flow of events: • logging in • Getting the updates Alternate flow of events: None. Post Condition: None. 25) Name of use case: Delete alert Description: Deletes the updates displayed on the page Preconditions: ? should be logged in Normal flow of events: 17

• logging in • Removal of the unwanted updates by the Alternate flow of events: None. Post Condition: None. 26) Name of use case: Update resume Description: Addition of new information Preconditions: ? should be logged in ? should be logged in ? There should be an existing resume Normal flow of events: • logging in • Opening the existing resume • Addition of information Alternate flow of events: None. Post Condition: None. 27) Name of use case: Create resume Description: Making a resume Preconditions: ? should be logged in ? should be logged in Normal flow of events: • logging in • Creation of the resume Alternate flow of events: None. Post Condition: None. 28) Name of use case: Style of resume Description: Type of resume that has to be built Preconditions: ? should be logged in Normal flow of events: • logging in • Selection of style Alternate flow of events: None. Post Condition: None. 29) Name of use case: Help Description: Encouragement to enquiries Preconditions: ? Existence of a ? must be logged in Normal flow of events: • logging in • Entering the queries • Responses given by the 18

Alternate flow of events: None. Post Condition: None. 30) Name of use case: FAQ Description: Already stored frequently asked questions by the Preconditions: ? Existing ? Existing keywords which could match the queries Normal flow of events: • g in • Entering the query • Matching of the keywords with the already existing ones in the database • Response given by the if the keyword matches Alternate flow of events: None. Post Condition: None. 31) Name of use case: Job articles Description: Showcases the information about the existing vacancies Preconditions: ? Existing Normal flow of events: • logging in • Pop ups regarding the new jobs Alternate flow of events: None. Post Condition: None. 32) Name of use case: Site map Description: Provides the overview of the entire website Preconditions: None Normal flow of events: • logging in • Exact view of the site provided by the Alternate flow of events: None. Post Condition: None. 33) Name of use case: Search Description: Shortcut to access any feature of the site Preconditions: None Normal flow of events: • logging in • Entering search keywords • The matching location is displayed Alternate flow of events: None. Post Condition: None. 34) Name of use case: Display info Description: Authentication provided by the , whether the exists or not Preconditions: 19

? must be logged in Normal flow of events: • logging in • Authentication provided by the Alternate flow of events: None. Post Condition: None. 35) Name of use case: Give alert to Description: Informing the about the suitable jobs Preconditions: ? must be logged in ? must be logged in Normal flow of events: • logging in • Pop ups giving the alerts Alternate flow of events: None. Post Condition: None. 36) Name of use case: Manage system Description: Performing all related jobs Preconditions: ? Existing ? must be logged in Normal flow of events: • logging in • revokes all the features Alternate flow of events: None. Post Condition: None. 37) Name of use case: View details Description: Displaying all related details Preconditions: ? Existing ? must be logged in Normal flow of events: • logging in • , displaying all the details Alternate flow of events: None. Post Condition: None.

20

view the message displayed by the company

view the message displayed by the company

view the message displayed by the company sign in

sign in

view

check skills requirements

give alert to

job search engine search information display to the include validation online newspaper/article

company site

valid

invalid

sign in

check

non-ed

display message

ed

create

inform to

view resume

create resume

enter details

change

update resume

submit resume

21

3.2) class diagram:

sign in create () forget ()

ed name address city mobile no qualification phone no sex age

application chatting weather report career news articles

profile

faq site map job articles

edit photo() delete photo()

resume resume style resume templates resume sample

view resume() create resume() sign in() update resume()

non ed name address city phone no mobile no age dob sex qualification

photo

edit profile() rpdate profile() delete () change ()

help

view resume() update resume() delete resume()

sign up

companies name email_id phone_no address sign in() search() inform()

create () enter details() create ()

view resume() create resume() sign up() update resume() alert

alert() manage system() manage information() vier details()

set alert() delete alert() show alert()

search search qualification() search details() send alert to istraror()

22

3.3) Supplementary Requirements: ? 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. If the base is now the entire world, staying open 24 hours a day becomes critical. System is required to be available 24X7 so UPS must be on server site for at least 8 hours in case of power failure. System will remain inaccessible to s at 2:00 to 4:00 am for backup and maintenance purpose. ? Reduce the cost of a sales transaction - To the extent that one can automate the sales process through this system, one can start to reduce the cost of that sales transaction. This is particularly true of mundane sales transactions where the customer knows what they want. ? Make the existing Web site more dynamic in nature - Many early Web implementations consisted of static HTML pages. This becomes very difficult to manage if the number of pages gets too large. 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 based customized web pages to its clients from server. ? Tie the existing Web site into existing enterprise systems – Any existing Web site that relies on the manual duplication of data from another system is one that can be improved. Most of the business data in the world today exists in enterprise servers that can be connected to the Web servers to make this process far more effective. ? 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 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.

23

24

25