ResumeReport1

RESUME BUILDER

SOFTWARE REQUIRMENT SPECIFICATION[0]

1. Introduction

1.1 Purpose:

Rich Resume Builder is to 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.

1.2 Scope:

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

New users can register and then upload their resumes and choose the appropriate

resume formats and get the printed copy of that resume.

Manage all the users details such as user name, phone numbers, address, websites,

email addresses etc. of all the users from one central location.

Users can update their resume details.

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

receive support.

Maintain history of each job seeker and their related information.

1.3 Abbreviations:

SRS: Software Requirements Specifications, The document lists the requirements of

the client & serves as a guideline for designers, developers, testers.

ASP.NET: ASP stands for Active Server Pages. ASP.NET is the programming

platform-part of Microsoft’s .Net framework –for developing large web based

applications.

HTML: Hyper Text Markup Language is a markup language used to create static

web pages.

HTTP: Hyper Text Transfer Protocol is a transaction oriented client/server protocol

between web browser & a Web server.

IIS: Internet Information Services is the Web server provided by Microsoft for the

Windows environment to host ASP.NET & XML based web applications.

XML: Extended Markup Language.

1

GEETANJALI INSTITUTE OF TECHNICAL STUDIES

Administrator: A login Id representing a user with user administration privileges to

the System.

SQL: Structured Query Language; used to retrieve information from a Database.

1.4 Technologies:

ASP.NET: Programming platform

C#: Backend Programming Language.

MS SQL Server: Database

IIS: Web Server.

Ms Visual Studio: Integrated Development Environment.

Edraw UML diagram 5.4: Design Tool

1.5 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 users, their role in the system

and constraints.

2. Overall Description:

Describe the general factors that affect our project and its requirements:-

2.1Product Perspective:

The web pages (HTML/Aspx) are present to provide the user interface on user client

side. Communication between customer 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 database server is for storing the information.

2

RESUME BUILDER

Fig: 2.1 Product Perspective

2.2 Software Interface:

Client on Internet: Web Browser, Operating System (any)

Client on Intranet: Client Software, Web Browser, Operating System (any)

Web Server: IIS, Operating System (any)

Data Base Server: SQL, Operating System (any)

Development End: HTML, ASPX, SQL, OS (Windows), Web Server.

3


2.3 Hardware Interface:

Table No 2.1

2.4 Communication Interface:

Client on Internet will be using HTTP/HTTPS protocol.

Client on Intranet will be using TCP/IP protocol.

2.5 Functional Requirements:

Track Account Level Data:

In this module, receivables from job seekers are maintained.

Functional Interfaces:

It provides interfaces for System administrator for performing following tasks (make

standard formats, editing, create users)

It provides interfaces for End Users for performing following tasks (login, searching a

employees on various attributes, set the formats of resume to get printed)

It provides interfaces for job seekers for performing following tasks (create a account,

filling up information like Skill sets, Training and updates it)

Database Design:

The Login to the system is database driven i.e. a user will be allowed to access the

system if and only if he is the valid user of the system.

4

RESUME BUILDER

2.6 User Characteristics:

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

basic knowledge of English too.

2.7 Use-Case Model:

Fig 2.2: Use Case Model

5

Manage user

ProvideAuthentication

Generate resume template.

Generate reports

Create user

View all details

View all resume

Adminstrator

Login

Register

Generate reports

Set resume format

Search employee

View/edit own details

Updation

Tracker

Job Seeker

Build resume in desired format

Company

Register

Login

Post Jobs


2.8 Constraints:

GUI is only in English.

Login and password is used for identification of user and there is no facility for guest..

Limited to HTTP/HTTPS.

2.9 Assumptions and Dependencies:

The details related to the resume are created by the users manually.

Administrator is created in the system already.

Roles and tasks are predefined.

3.1 Use-Case Reports:

Administrator: Responsible for managing system users and managing the generation of

reports.

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

Generate resume template: The administrator will provide different resume

template which will be visible to the users.

View All Details: View the job seekers details and employer’s details.

Provide authentication: Provides authentication to valid users only.

Manage System Users:

Fig 3.1.1: Use Case Report- Manage System Users

6

Manage User

Create User

View User

Update Details

RESUME BUILDER

Name of use case: Create Users

Description: To create system users (Giving them a login name, password and assign roles,

tasks and permissions to them).

Preconditions:

Administrator is already logged in.

Normal flow of events:

New Login name, password, details, roles, tasks and permissions will be entered.

Save the details.

Alternate flow of events:

A message appears for duplicate login name.

The administrator has to fill the details again.

Post condition: A login id is generated with its details.

Activity Diagram:

Fig 3.1.2: Use Case Report-Create Users

7

Enter login Name, Password, Details, role name,

task & Permission

User Successfully Created

Duplicate User Name


Name of use case: View User Details

Description: View the list of users in a role and view the details of roles, tasks and

permissions assigned to a user.

Preconditions:


Users have already been created and assigned some roles, tasks and permissions.


The system user or a role will be selected.

Query will be submitted.

Relevant output will be displayed (If user is selected then roles, tasks and

Permissions assigned to one will be displayed and if role is selected then list of

Users assigned to that role will be displayed).

Alternate flow of events: None.

Post condition: None.

Activity Diagram:

Fig 3.1.3: Use Case Report- View User Details

Name of use case: Update details of Users

8

Ask for Selecting roles or Particular system user

Details of role task & Permission of selected user

List of System User Which Are Assigned to selected role

Role

User

RESUME BUILDER

Description: To update the details of system users (assigning or revoking roles, tasks and

Permissions).

Preconditions:


System Users have already been created.


Select the user name.

Assign or Revoke the roles, tasks and permissions.

Post Condition: None

Activity Diagram:

Fig 3.1.4: Use Case Report- Update details of Users

Name of use case: Enter resume details.

9

Ask for Select the User

Update Roll Tasks & Permission


Description: To enter the details of job seekers (personal, educational and other related

information).

Preconditions:


Normal flow of events

Entry of all the details.

Show all resume details.


Activity Diagram:

Fig 3.1.5: Use Case Report- Enter resume details.

Name of use case: Delete Customer

10

Enter all Resume Details

Select Desired Resume Pattern

Get Resume In Desired Pattern

RESUME BUILDER

Description: To delete the details of job seekers (personal, educational and other related

information).

Preconditions:



Show all resume details.

Delete the selected Customer.


Activity Diagram:

Fig 3.1.6: Use Case Report-Delete Customer

Name of use case: Authentication

Description: To authenticate the Customer by checking for correct User name and password

11

Select Customer from

db

Delete Customer


and then only providing access to their account.

Preconditions:



Input User name and password.

Check if it is in database or not.

Provide access to their account.

Alternate flow of events:

A message appears if user name or password is incorrect.

There is a message appears for incorrect user name or password.


Activity Diagram:

Fig 3.1.7: Use Case Report- Authentication

Name of use case: Generate Template

Description: The administrator can generate design for templates.

12

Input User Name and Pwd from

Customer

Provide Access

Check from db

Reject Access

RESUME BUILDER

Preconditions:



Can generate design of template.

Upload in database to provide that template to user.


Activity Diagram:

Fig 3.1.8: Use Case Report- Generate Template

Name of use case: View details

Description: The administrator can see all the details of Customer.

13

Form new format of templates

Upload in db


Preconditions:



Select Customer of whose details he want.

Show all details of customer.


Activity Diagram:

Fig 3.1.9: Use Case Report- View All Details

Name of use case: Companies Norms

Description: To search candidates who can full fill their norms

14

Select User

view all details

RESUME BUILDER

Preconditions:



Resumes are already submitted.


Trackers: Enter query for selecting required person.

Administrator generates report.


Activity Diagram:

Fig 3.1.10: Use Case Report-Companies Norms

Name of use case: Generate resume format.

Description: Employ trackers generate their own resume format.

15

Enter a Query to Select Desired Skilled Person

Search for those Candidate

Generate Report


Preconditions:




Generate different format.

Upload the database.


Activity Diagram:

Fig 3.1.11: Use Case Report - Generate resume format

Name of use case: Update Resume Details.

Description: Job seekers can Add/Edit/Delete their resume details.

16

Trackers CanGenerate Resume Format

Upload In Database

RESUME BUILDER

Preconditions:

Job Seekers are already logged in.


Update their resume details.

Check for validations.

Submit form for update in database


Activity Diagram:

Fig 3.1.12: Use Case Report-Update Resume Details

3.2 Non Functional Requirements:

Have hours of operation that are 24 x 7 - Because system can be an automated

17

User can edit or add details

Check for validation

Successfully Updated

No

yes


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.

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.

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.

DESIGN

4.1 Entity Relationship Diagram[1]

18

RESUME BUILDER

4.2 Decision Tree

19

Company

Submit Resume

NameAddress

Email

Company Id

Tracker

Administrator

Submit Reports

Name

Email

Mobile

Submit info

Resume Formats

Experienced

FresherWork Histor

y

Personal Details

Skill & Achivemt.

Job Seeker

Education DetailHobbie

s

Fig 4.1: Entity Relationship Diagram of Resume Builder

HOME

LOGIN

ADMIN

TRACKER

EMPLOYER

JOB SEEKER

ACCOUNT

EDUCATION

PERSONAL DETAILS

SKILLS

POST JOB

REFERENCES

RESUMESAMPLE

RESUME FORMAT

OTHERS

ACCOUNT

SAMPLE RESUME FORMAT

Registration


Fig 4.2: Decision Tree

4.3 UML Design[2]

4.3.1 Sequence Diagrams

20

RESUME BUILDER

Fig 4.3.2 Sequence Diagram For Login

21

RegistrationForm

RegistrationForm

RegistrationController


UserProfileUserProfile

SubmitInformation()

validateInfomation(user,password)

user clearence

SubmitInformation()

SubmitInfomation()

CreateProfile()

Fig 4.3.1Sequence Diagram For User Registration

conform registration

FillForm

LoginFormLoginForm LoginControllerLoginController LoginProfileLoginProfile

submitInformation

validateinformation(user,password)

user clearence

loginclearence

Sequence Diagrame For Login


22

SearchProductForm

SearchResume SearchProductController

SearchResumeController

ProductListResumeList

search critiria

submitInfomation()

getInformaton()

Infomation

Desired Resume

Fig 4.3.3: Sequence Diagram for Search Resume

SearchProductForm

ResumeDetailsForm

SearchProductController

ResumeDetailsController

ProductListUserProfile

Fill Forms

submitInfomation()

CheckValidations()

CorrectFormat

SubmitSuccessfully

Fig 4.3.4: Sequence Diagram for Resume Details

RESUME BUILDER

4.3 Class Diagram:

23

RegistrationForm

SubmitInformation()


SubmitInformation()Getinformation()

ValidateInformation()

User Profile

UserNamePassword

EmailViewProfile()CreatProfile()

Fig 4.3.5:Class Diagram for User Registration

LoginForm

SubmitInformation()

LoginController

GetInformation()SubmitInformation()ValidateInformation()

User Profile

UserNamePassword

ViewProfile()

Fig 4.3.6 Class Diagram for Login


24

UpdateForm

SubmitInformation()

UpdateController

SubmitInformation()

Fig 4.3.7: esumeerrmationClass Diagram for Update User Information

UserInformation

UserName

PasswordEmail

ViewDesiredDetails()

...

UpdateDetails()

MaintainUserLoginForm

SubmitInformation()

MaintainUserLoginControls

SubmitInformation()GetInformation()

ValidateInformation()updateInfomation()

User Profile

CustomerIdPassword

EmailResumeDetails

ViewProfile()CreatProfile()

Fig 4.3.8: Class Diagram for Maintain User Profile

RESUME BUILDER

25

ReportForm

SubmitCriteriaForReport()...

SubmitCriteria()

Reportcontroller

SubmitInformation()

SubmitCriteria()

CustomerInformation

CustomerIdCustomerNameResumeDetails

SelectRecordaccordingtoCriteria()

Fig 4.3.9: Class Diagram For View Reports


SCREENSHOTS

26

RESUME BUILDER

27


28

RESUME BUILDER

29


TESTING AND FUTURE SCOPE

1. Testing

Software Testing is an investigation conducted to provide stakeholders with information about quality of the product or service under test.Software testing can also be stated as the process of validating and verifying that a software program/application/product:

Meets the business and the technical requirements that guided its design and development;

Can be implemented with the same characteristics. Two strategies are followed for the testing process

1.1 White box TestingA detailed testing is to be done when the tester has the access to the internal data structures and the algorithms including the code that implement these. All the statements written in the code are tested to assure that they are working fine.

1.2 Black Box TestingIn this only over view is tested .The software is assumed as the black box, without the knowledge of the internal implementation. In this we check only the fact that whether the input is producing desired output.In the PMS both the testing methods have been applied so as to ensure error free product from the development end.

2. Future Scope

This project/software can also be implemented at an advanced level. When implemented at a higher level, user can build resume from experts at

affordable charges. When implemented as a web application over internet, user can search for

vacancies and immediately apply for jobs.

30

RESUME BUILDER

BIBLIOGRAPHY

1. Software engineering by Pressman Published by McGraw-Hill publications sixth edition.

2. Data Base System by W.C Korth seventh edition Published by McGraw- Hill publications.

3. http://social.msdn.com4. Microsoft Visual Studio 2005 Documentation5. www.google.com 6. www.shine.com

31

http://www.shine.com/

http://www.google.com/

http://social.msdn.com/


REFERENCES

[0] IBM SRS Format

[1] DataBase System Concepts Henry F. Korth second edition, McGraw- Hill International Editions.

[2] The Unified Modeling Language User Guide, Grady Booch, James Rumbaugh, IvarJacobson, ISBN 81-7808-169-5, 2002.

32

ResumeReport1

Documents

Transcript of ResumeReport1