srs on feature rich resume builder

1

Amity university noida Uttar pradesh

Feature-rich resume builder

Software requirement specification TEAM Iceangels Team members Megha Sahni Laxmi Rawat Kriti Sharma Kanika Choudhary Project guide Mrs Shilpi Sharma

2

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) User 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

3

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 scope-

a. Create different system users and assign different roles with related permissions.

b. Manage all the account details such as user name, phone numbers, address

,websites, email addresses of all the user from one central location.

c. Track all the users and their contact details.

d. Confirmation of end user identity and will verify which users are authorized to

receive support.

e. Maintain history of each user and their related information .

f. User can select the format of their resume from the given templates.

g. User can update or edit their resume.

h. Users 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 accounts .

m. Giving alerts to the user if he requests for one.

n. User can utilize various applications such as chatting, search engine, weather

reports, latest news etc.

o. User authentication.

1.3) Abbreviations:

1. FRRB: Feature-rich resume builder

4

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 username, company, phone number, address, website, e-mail address etc. Contact details: Details of contact 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 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.

5

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:

6

1. The web pages (XHTML/JSP) are present to provide the user interface on customer client side. Communication between customer and server is provided through HTTP/HTTPS

protocols.

2. The Client Software is to provide the user interface on system user client side and for this TCP/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:

7

2.04) Communication Interface:

1. Client on Internet will be using HTTP/HTTPS protocol.

2. Client on Intranet will be using TCP/IP protocol. 2.05) Product Function: Track Account Level Data: In this module, receivables from customer are maintained. User Contact Information: It maintains all the details (Personal, Official, Contact, and Company) of the customer. Maintaining Logs: Activities of the System Users can be tracked through the logs, which is maintained by the system. 2.06) User Characteristics: Every user 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. Login and password 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

8

2.08) Use-Case Model Survey:

profile

photograph

view resume

create resume

application

customer tips

weather report

chatting

registered

update resume

non-registered

sign up

create account

display information

inform to administrator

set alert

show alertdelete alert

manage the system

view details

administrator

alerts

search

company

sign in

games

<,include

change photo

remove photo

edit profile

update profile

change password

delete account

styles of resume

news

themes

change themeset theme

give alert to user

help

frequently asked questions site map

job articles

9

1. Administrator: Responsible for managing system users, viewing logs and managing standard groups of the system. Manage System Users: The Administrator will create different roles. The system users 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 users. View Logs: Responsible for checking the logs of different system user for auditing and maintaining the integrity of the system. Manage Standard Groups: Standard groups will be created and updated by the administrator, which will be visible to all the system users. View All Details: View the customer details, resume details. Give alerts: The administrator gives alert to the user about the invitations received from the companies. 2.User: A user can be registered user or non registered user Registered user: A registered user is one who has created an account and is ready to create the resumeamong the different format available. Non-registered user: A non-registerd user is one who has not created an account yet but has visited the site as a guest. Create resume: A user can select the format of resume from different styles given and can create and update them. Use applications: A user 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 administrator and the administrator can send alert to the user.

10

2.09) Database design:

System_role

Role_id

Role_name

System_log

User_id

Password

System_registered

User_ID Login_name Password_value First_Name Last_Name E-mail Modified Created

Applications

Themes

News

Customer_tips

Chatting

Games

Weather_ report

Resume

Styles of resume

View_resume

Create_resume

Update_resume

Profile

First_name

Last_name

About_me

Date_of_birth

Qualifications

e-mail

Photograph

Remove_photograph

Change_photograph

ISA

user company

makes

has

11

System_view Company name Skills

System_log Login_id password

Alerts Give alert to the administrator

has

user

System_registered

System_log applications

profile photograph resume

company

System_view System_log

alerts

12

2.10) Assumptions and Dependencies: 1. The details related to the product, customer, payment and service transaction provided manually. 2. Administrator 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 user account Preconditions: ? There should be an existing account of the user ? Administrator is already logged in. Normal flow of events:

• user details are entered • authentication is provided by the administrator • corresponding output if the entries made by the user are correct

Alternate flow of events: None. Post Condition: None.

2) Name of use case: Sign up Description: Creating a user account Preconditions: ? Knowledge about the website ? Existing database ready to accept the details of the user ? Administrator is already logged in. Normal flow of events:

• user details are entered • storage of information to the database


3) Name of use case: Create account Description: Creating a user account Preconditions: ? Knowledge about the website ? Existing database ready to accept the details of the user ? Administrator is already logged in. Normal flow of events:

• user details are entered • storage of information to the database

Alternate flow of events: None.

13

Post Condition: None.

4) Name of use case: Profile Description: Showing user information Preconditions: ? Accumulating each and every detail of the user ? Retrieving user details from the database ? Administrator is already logged in. Normal flow of events:

• The information regarding the respective user is retrieved from the database • Showcasing the entire user information


5) Name of use case: Edit profile Description: Making changes to the current profile Preconditions: ? There should be an existing profile ? Administrator 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 ? Administrator is already logged in. Normal flow of events:

• Add on to the existing profile • Displaying the changed profile


6) Name of use case: Change password Description: Creating a new password Preconditions: ? There should be an existing password ? Administrator is already logged in. Normal flow of events:

• Entering the existing password • Entering the new password


7) Name of use case: Delete account Description: Deleting the existing account

14

Preconditions: ? There should be an existing account ? Administrator is already logged in. Normal flow of events:

• Accessing the details from the database • Removal of all the details from the database


8) Name of use case: Photograph Description: Attachment of the user’s photograph to the profile Preconditions: ? Administrator is already logged in. Normal flow of events:

• Providing the path of the photograph • Attachment of the photograph


9) Name of use case: Change photo Description: Altering the existing photo Preconditions: ? Administrator is already logged in. ? There should be an existing photo Normal flow of events:

• Removing the existing photo • Attaching the new photo


10) Name of use case: Remove photo Description: Deleting the existing photo Preconditions: ? There should be an existing photo in the database ? Administrator is already logged in. Normal flow of events:

• Accessing the existing photo • Removing the existing photo


11) Name of use case: View resume Description: Actual view of the resume Preconditions: ? Administrator is already logged in. ? Already existing resumes of the users Normal flow of events:

• Select the user name

15

• Permission from the administrator for viewing Alternate flow of events: None. Post Condition: None.

12) Name of use case: Create resume Description: Addition of all the details Preconditions: ? Administrator is already logged in ? Accumulating each and every detail of the user at one place Normal flow of events:

• User sign in • Creation of resume as per the user’s choice


13) Name of use case: Application Description: Provide the user with functionalities Preconditions: ? There should be an existing profile for the user Normal flow of events:

• User logging in • Accessing all the pre existing functionalities


14) Name of use case: Games Description: Provides the functionality of gaming Preconditions: ? User should be logged in Normal flow of events:

• User logging in • Selection of a particular game from the given list


15) Name of use case: Chatting Description: Helps the user interact with other users Preconditions: ? User should be signed in Normal flow of events:

• User logging in • Conversation with other users


16) Name of use case: Weather report Description: Describes the current weather Preconditions:

16

? User should be logged in Normal flow of events:

• User logging in • Information received about the current weather


17) Name of use case: Customer tips Description: Provide user friendly tips Preconditions: ? User must be signed in ? Administrator must be logged in Normal flow of events:

• User logging in • Popping user friendly tips


18) Name of use case: News Description: Provide the user with the news upgrades Preconditions: ? User should be logged in Normal flow of events:

• User logging in • Getting upgrades regarding the current topic


19) Name of use case: Themes Description: Getting the different ideas or giving the choices for selecting the different themes Preconditions: ? User should be logged in ? Administrator should be logged in Normal flow of events:

• User logging in • Selecting the appropriate theme


20) Name of use case: Change themes Description: Replacing the current theme by selected one Preconditions: ? User should be logged in Normal flow of events:

• User logging in • Selecting a specific theme from the given choices • Replacing the current theme by the selected one

Alternate flow of events: None.

17

Post Condition: None.

21) Name of use case: Set theme Description: sets the current theme Preconditions: ? User should be logged in Normal flow of events:

• User logging in • Setting up the selected theme


22) Name of use case: Alerts Description: Giving alerts or the latest updates to the user Preconditions: ? User should be logged in Normal flow of events:

• User logging in • Getting the alerts


23) Name of use case: Set alert Description: Sets the required condition to get the alerts Preconditions: ? User should be logged in ? Administrator should be logged in Normal flow of events:

• User logging in • Getting the required updates


24) Name of use case: Show alert Description: Shows the updates on the required page Preconditions: ? User should be logged in Normal flow of events:

• User logging in • Getting the updates


25) Name of use case: Delete alert Description: Deletes the updates displayed on the page Preconditions: ? User should be logged in Normal flow of events:

18

• User logging in • Removal of the unwanted updates by the user


26) Name of use case: Update resume Description: Addition of new information Preconditions: ? Administrator should be logged in ? User should be logged in ? There should be an existing resume Normal flow of events:

• User logging in • Opening the existing resume • Addition of information


27) Name of use case: Create resume Description: Making a resume Preconditions: ? Administrator should be logged in ? User should be logged in Normal flow of events:

• User logging in • Creation of the resume


28) Name of use case: Style of resume Description: Type of resume that has to be built Preconditions: ? User should be logged in Normal flow of events:

• User logging in • Selection of style


29) Name of use case: Help Description: Encouragement to user enquiries Preconditions: ? Existence of a user account ? Administrator must be logged in Normal flow of events:

• User logging in • Entering the queries • Responses given by the administrator

19


30) Name of use case: FAQ Description: Already stored frequently asked questions by the user Preconditions: ? Existing user account ? Existing keywords which could match the user queries Normal flow of events:

• User signing in • Entering the query • Matching of the keywords with the already existing ones in the database • Response given by the administrator if the keyword matches


31) Name of use case: Job articles Description: Showcases the information about the existing vacancies Preconditions: ? Existing user account Normal flow of events:

• User logging in • Pop ups regarding the new jobs


32) Name of use case: Site map Description: Provides the overview of the entire website Preconditions: None Normal flow of events:

• User logging in • Exact view of the site provided by the administrator


33) Name of use case: Search Description: Shortcut to access any feature of the site Preconditions: None Normal flow of events:

• User logging in • Entering search keywords • The matching location is displayed


34) Name of use case: Display info Description: Authentication provided by the administrator, whether the user exists or not Preconditions:

20

? Administrator must be logged in Normal flow of events:

• User logging in • Authentication provided by the administrator


35) Name of use case: Give alert to user Description: Informing the user about the suitable jobs Preconditions: ? Administrator must be logged in ? User must be logged in Normal flow of events:

• User logging in • Pop ups giving the alerts


36) Name of use case: Manage system Description: Performing all user related jobs Preconditions: ? Existing user account ? Administrator must be logged in Normal flow of events:

• User logging in • Administrator revokes all the features


37) Name of use case: View details Description: Displaying all user related details Preconditions: ? Existing user account ? Administrator must be logged in Normal flow of events:

• User logging in • Administrator, displaying all the details


21

include

check

change

view

job search engine

company site

sign in

registered

view resume

create resume

enter details

update resume

submit resume

view the message displayed by the company

online newspaper/article

non-registered

create account

sign in

check skills requirements

search

validation

valid invalid

display message

inform to administrator



sign in

give alert to user

information display to the user

22

3.2) class diagram:

sign in

create password()forget password()

application

chattingweather reportcareer newsarticles

helpfaqsite mapjob articles

photo

edit photo()delete photo()

registerednameaddresscitymobile noqualificationphone nosexage

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

non registerednameaddresscityphone nomobile noagedobsexqualification

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

companiesnameemail_idphone_noaddress

sign in()search()inform()

administrator

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

resumeresume styleresume templatesresume sample

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

alert

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

sign up

create password()enter details()create account()

profile

edit profile()rpdate profile()delete account()change password()

search

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

23

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 support must be on server site for at least 8 hours in case of power failure. System will remain inaccessible to users 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 user 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 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.

24

25

srs on feature rich resume builder

Documents

user authentication

user characteristics

software interface

featurerich resume builder3

various companies

hardware interface

communication interface

different system users