Table Of Content

1. Introduction
1.1 Purpose
1.2 Document Conventions
1.3 Contact Information/SRS team members
1.4 Reference

2. Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 User Environment
2.4 Design/Implementation Constraints
2.5 Assumptions & dependencies

3. External Interface Requirement

3.1 User Interface
3.2 H/w Interface
3.3 S/w Interface
3.4 Communication Protocols & Interfaces

4. System Features
4.1 Action/Results
4.2 Architectural Design
4.3 E.R. Diagram
4.4 Data Flow Diagram
4.5 Use Case Model

5. Other Non-Functional Requirements

5.1. Performance Requirements
5.2. Software Quality Attributes

Appendix A: Terminology/Glossary/Definition List

 Online Resume Builder

1. Introduction

Before we begin a new system it is important to study the present system that will be
improved or replaced. We need to analyze how this system uses hardware, software etc. In this
present age of competition our resume need to be prepared and updated according to the
changing requirements of industry. The present system for resume building just provides wizard
through which one can prepare resume only in given format.

1.1 Purpose

Develop an Intranet Application 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.

The Basic Requirement is to have a centralized repository of all the skill-holders

in the organization so that an employee with a particular skill set can be immediately
found in case of urgent requirement.

1.2 Document Conventions

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 References
a) IEEE SRS Format
b) Problem Definition (Provided by IBM)
c) CT Arrington
d) Enterprise Java with UML
e) OMG Press.
2. Overall Description

Describe the general factors that affect the product and its requirements.

a. Product Perspective:
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.

b. Product Function:
1. Track Account Level Data: In this module, receivables from customer
are maintained.
2. User Contact Information: It maintains all the details (Personal, Official, Contact,
and Company) of the customer.
3. Maintaining Logs: Activities of the System Users can be tracked through the logs,
which are maintained by the system.

c. User Environment:

Every user should be comfortable of working with computer and net browsing. He
must have basic knowledge of English too.

d. Design / Implementation 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

e. Assumptions & 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. External Interface Requirement

5.1 User Interface:

1) Name of use case: Sign in

Description: Accessing the user account

Preconditions:

There should be an existing account of the user.

Normal flow of events:

user details are entered

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?

Normal flow of events:

user details are entered

storage of information to the database

Alternate flow of events: None.

Post Condition: None.

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?

Normal flow of events:

user details are entered

storage of information to the database

Alternate flow of events: None.

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?

Normal flow of events:

The information regarding the respective user is retrieved from the

database
Showcasing the entire user 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?

Normal flow of events:

Changes to the existing profile

Displaying the changed profile

Alternate flow of events: None.

Post Condition: None.

6) Name of use case: Update profile

Description: Additions to the existing profile

Preconditions:

There should be an existing profile?

Normal flow of events:

Add on to the existing profile

Displaying the changed profile

Alternate flow of events: None.

Post Condition: None.

7) Name of use case: Change password

Description: Creating a new password

Preconditions:

There should be an existing password?

Normal flow of events:

Entering the existing password

Entering the new password

Alternate flow of events: None.

Post Condition: None.

8) Name of use case: Forgot Password

Description: Request new password

Preconditions:

There should be an existing account of the user.

Normal flow of events:

Enter Email Id / User Name

Verify Details
Enter new password

Alternate flow of events: None.

Post Condition: None.

9) Name of use case: Delete account

Description: Deleting the existing account

Preconditions:

There should be an existing account?

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.

10) Name of use case: Create resume

Description: Addition of all the details

Preconditions:

Accumulating each and every detail of the user at one place

Normal flow of events:

User sign in
Creation of resume as per the users choice

Alternate flow of events: None.

Post Condition: None.

11) Name of use case: Download resume

Description: Download Word file of the resume.

Preconditions:

User should be logged in?

There should be an existing resume

Normal flow of events:

User logging in
Opening the existing resume
Downloading the resume

Alternate flow of events: None.

Post Condition: None.

12) Name of use case: About Us

Description: Giving Company Details

Preconditions: None.

Normal flow of events: None

Alternate flow of events: None.

Post Condition: None.

13) Name of use case: Contact Us

Description: User Feedbacks And Querys

Preconditions:

Existing user account

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

Alternate flow of events: None.

Post Condition: None.

5.2 H/w Interface:

5.3 S/w 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: PHP

PHP is a scripting language designed to fill the gap between SSI (Server
Side Includes) and Perl, intended for the web environment. Its principal
 application is the implementation of web pages having dynamic content. PHP has
gained quite a following in recent times, and it is one of the frontrunners in the
Open Source software movement. Its popularity derives from its C-like syntax,
and its simplicity. PHP is currently divided into two major versions: PHP 4 and
PHP 5, although PHP 4 is deprecated and is no longer developed or supplied with
critical bug fixes. PHP 6 is currently under development.

If you've ever been to a website that prompts you to login, you've probably
encountered a server-side scripting language. Due to its market saturation, this
means you've probably come across PHP. PHP was designed by Rasmus Lerdorf
to display his resume online and to collect data from his visitors.

Basically, PHP allows a static webpage to become dynamic. "PHP" is an

acronym that stands for "PHP: Hypertext Preprocessor". The word "Preprocessor"
means that PHP makes changes before the HTML page is created. This enables
developers to create powerful applications which can publish a blog, remotely
control hardware, or run a powerful website such as Wikipedia or Wiki books. Of
course, to accomplish something such as this, you need a database application
such as MySQL.

Before you embark on the wonderful journey of Server Side Processing, it

is recommended that you have a basic understanding of the HyperText Markup
Language. PHP is also being used to build GUI-driven applications; PHP-GTK is
used to build graphical user interfaces.

5.4 Communication Protocols & Interfaces:

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

2. Client on Intranet will be using TCP/IP protocol.
6. System Features

6.1 Action/Results
1. Login Page..
2. User Home Page
3. Resume Creator Page
4. Edit Profile Page
 6.2 Architectural Design

Architectural design represents the structure of data and program components that are
required to build a computer-based system. It considers the architectural style that the system
will take, the structure and properties of the components that constitute the system, and the
interrelationships that occur among all architectural components of a system.
6.3 E-R Diagram

The object/relationship pair is the cornerstone of the data model. These pairs
are represented graphically using E-R diagrams. A set of primary components are
identified for the ERD: data objects, attributes, relationships and various type
indicators. The primary purpose of ERD is to represent data objects and their
relationships.
6.4 Data Flow Diagram

The data flow diagram enables the software engineer to develop models of the
information domain and functional domain at the same time. As the DFD is refined
into greater level of detail, the analyst performs an implicit functional decomposition
of the system. At the same time, the DFD refinement results in corresponding
refinement of data as it moves through the processes that embody the application.
6.5 Use Case Model

Use Case Model is an approach that is a combination of text and pictures in

order to improve the understanding of requirements. A use case model' is describes
the complete functionality of a system by identifying how everything that is outside
the system interacts with it.

A Use Case Diagram is given below that relates to this application.

Description This project is a web application that manages a system of

building resumes online.
Actors It has 3 actors.
1) Administrator
2) Customer
3) Viewer
Flow of Events
User logins into the system using ID and password.
If user is an authorized user then access is granted otherwise denied.
User selects any tasks to do and task is performed.
Special Requirements
Data will flow from one user to another.
Data generated by one user cant be altered by another user.
One user cant change the status of another user.
Pre Condition
All customers should have their account created on the system.
Post Condition
Details are available to users.
Details and information are intact and valid.
7. Other Non-Functional Requirements

7.1 Performance Requirements

Very secure - Use HTTPS/SSL for transmission during the login process.
Easy to use and customizable interface.
Ability to add & maintain faculty resume.
Users must be able to configure the positioning of various elements.(Which is 1st,
2nd and so on)
Easy to add various elements such as new publications, or research grants.
Ability to have resume in Microsoft Word, PDF & plain text format.
Email functionality for all the above formats.
System should email users if they lost their username/password via email.

7.2 Software Quality Attributes

Free Resume hosting
Wide range of resume formats
Expert guidance at every step of resume building
Search for a particular candidate by skills
 Appendix

1. Terminology:
a) FRRB: Feature-rich resume builder
b) SRS: software requirement specification.
c) WWW: world wide web
d) EJB: Enterprise Java Beans.
e) J2EE: Java 2 Enterprise Edition
f) DB2: DB2 Database
g) WAS: Web sphere application server
h) UML: unified modeling language
i) XML: extended markup language
j) AJAX: asynchronous JavaScript + xml
k) SOA: service oriented architecture

2. Glossary:

3. Definitions:

Resume: Job-seekers create their resume of their chosen styles so that companies can
select and give them an invitation.

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