Software Requirements Specification

For

Professional Interview Coordinator

Sruthi.M101744MCA

Aloysius Institute of Management and Information Technology (AIMIT)St. Aloysius College (Autonomous)

Madoor, Mangalore01-03-2013

Under the guidance of

Mr. Lanwin LoboAssistant Professor, Department of MCA

Aloysius Institute of Management and Information Technology (AIMIT)St. Aloysius College (Autonomous)

Madoor, Mangalore

Submitted to

ALOYSIUS INSTITUTE OF MANAGEMENT AND INFORMATION TECHNOLOGY (AIMIT)

ST ALOYSIUS COLLEGE (AUTONOMOUS)MANGALORE, KARNATAKA

0

Table of Contents

Table of Contents...........................................................................................................................iiRevision History.............................................................................................................................iii

1. Introduction1.1 Purpose............................................................................................................................21.2 Document Conventions.....................................................................................................21.3 Intended Audience and Reading Suggestions.......................................................................21.4 Project Scope…................................................................................................................21.5..........................................................................................................................................References3

2. Overall Description...................................................................................................................32.1 Product Perspective..........................................................................................................32.2 Product Features..............................................................................................................32.3 User Classes and Characteristics.......................................................................................32.4 Operating Environment....................................................................................................42.5 Design and Implementation Constraints............................................................................42.6 User Documentation.........................................................................................................42.7 Assumptions and Dependencies........................................................................................4

3. System Features........................................................................................................................53.1 PIC Admin...................................................................................................................53.2 Admin mailer...............................................................................................................63.3 Interviewer...................................................................................................................6

4. External Interface Requirements............................................................................................64.1 User Interfaces..................................................................................................................64.2 Hardware Interfaces..........................................................................................................64.3 Software Interfaces............................................................................................................74.4 Communications Interfaces................................................................................................7

5. Other Nonfunctional Requirements.......................................................................................75.1 Performance Requirements................................................................................................75.2 Safety Requirements.........................................................................................................75.3 Security Requirements.......................................................................................................75.4 Software Quality Attributes...............................................................................................7

Appendix A: Glossary.....................................................................................................................8

1

I. Introduction1.1 Purpose

Professional interview coordinator is a complete interview management and

applicant tracking solution aimed to get better people. It is a complete web based

software solution designing to reduce human efforts, increase efficiency and for effective

management of profiles. The main purpose of this product is eliminating the

complications of choosing a right person to interview and to reduce the complexity of

interview process.

1.2 Document Conventions

The font style followed is Times New Roman throughout the SRS. The Main

Headings make use of Font size 16 and sub headings make use of Font size 14. The

Headings are kept Bold. The text is in Font size 12 with 1.5 interline spacing.

1.3 Intended Audience and Reading Suggestions

Purpose of this software requirements specification is to verify that all the specifications

are correct and verified. This document also serves to ensure that the software is traceable

throughout its software development life cycle. This SRS would be used by following

people:

• Developers: The developers would use these documents to implement the

functionalities

• Testers: The testers would use these documents to know the interfaces and to test the

software accordingly.

• Project Manager: The project manager will use this document to ensure that all the

requirements given by the customer is dealt.

• User: The users would use these documents to verify if all the requirements are met and

to ensure traceability of the software.

1.4Project Scope

Interview coordinator is designed to find the best personalities easier and more

efficient way and also to provide an easy user interface for the interviewer. It will provide

a chance to contact the interviewee at anytime. This system will help to collect and keep a

2

database of qualified professionals which will help interviewer to search and get better

personalities according to their profession. This may reduce the time and complexities of

interview process. This system will allow the reader to comment about interviewee

statements.

1.5 References

1. Software Engineering by K.K Aggarwal and Yogesh Singh.

2. Software Engineering A Practitioner’s Approach –Roger S Pressman

2. Overall Description

2.1 Product Perspective

Conducting interview at professional level, editing and publishing require lot of

efforts and resources. Interview process will be easy if we avoid manual and providing a

new way by connecting people through internet. Time and distance will not be a

constraint for the proposed system.

2.2 Product Features

The product allows only authorized members to login. Admin can add new profile

and by searching he can assign some question to members related to their profiles. After

assigning questions admin will send question to members by emails .Now members will

answer the questions. Admin will see the question and will do necessary modification.

2.3 User Classes and Characteristics

The different users of this system are as follows:

Administrator: Here admin can act as interviewer by assigning questions to

professionals. And he can also add new profile and search for the appropriate

personalities. And admin can send the link to professionals by mail.

Professionals: professionals can act here as interviewee and he can answer the

question assigned by admin by click the link which is send by admin.

Readers: readers are the users who can read the question and answer and gain

knowledge. He can also comment to the statements.

3

2.4 Operating Environment

Operating System:

Microsoft® Windows XP or above

Memory:

512MB RAM

Minimum 40 GB HDD

Software Specification

Internet Explorer 8 / Mozilla Fire Fox 3.6/Google Chrome

MYSQL 5.5.16 Database Management System

Dreamweaver CS5 or PHP Edit

2.5 Design and Implementation Constraints

This section will indicate the design constraints that apply on the system being developed and

that shall be adhered to during the development phase of the project.

Programming language: The application is mainly developed using PHP. PHP

smarty also using which will separate the presentation logic and business logic.

This will provide reusability of code.

Database: SQL server shall be used as the systems database management system.

Development Tool: Dreamweaver CS5 and PHP Edit is using as IDE.

Standards: The application shall be able to work in any browser. The hardware

specification must meet the minimum requirements of 512Mb RAM, 40GB hard

disk space.

Legal Constraints: Any modification that has to be done to the system can only

be done by the Admin.

2.6 User Documentation

The documentation of the system such as the requirement specification, system

design, database design, tutorials and guidelines will be delivered to the clients along

with the software.

2.7Assumptions and Dependencies

It is assumed that the system is accessible to multiple users without reflecting

the load. The response time from the system is considered to be lowest. The back-end is

4

assumed to resist system crashes to some extent. It is developed by assuming that end

user will have basic knowledge about computer.

3. System Features

3.1 PIC Admin

3.1.1 Description and PriorityThis module has higher priority since it is related to administrator.

It is used by the administrator when he wants to modify details about the

professionals. All details needed for this web site can be provided through this

module. This role will provide the administrator over all control to the web site.

3.1.2 Stimulus/Response SequencesThe PIC Admin module configurations allows to add/update

professional profiles, add/update questions, search appropriate

personalities and assign the questions, resend the request if question is not

answered and verify the answers.

3.1.3 Functional Requirements

3.1.3.1 Add/Update Category: Here admin can create or update category. Here category means Questions category.

3.1.3.2 Add Questions: Here admin will add questions to existing cate-gory.

3.1.3.3 Update Questions: Here we will provide option to edit existing questions.

3.1.3.4 Find and assign: Here admin can search the network members based on some keywords. After searching admin can assign a category questions to members.

3.1.3.5 View Answer: In This tab admin will see the answer of question .Based on the answer he can approve or disapprove the user.

3.1.3.6 Resend: If user not answered the question, Admin can assign the different category question and send the questions again.

3.1.3.7 Approved Members: Under this tab all approved members will be displayed. Admin also can search the members.

3.2 PIC Mailer Admin

5

3.2.1 Description and PriorityThis module implements the functionality to send mails to network

members.

3.2.2 Stimulus/Response SequencesThis module will be used by the admin to send the Interviewer

URL to members.

3.2.3 Functional Requirements

3.2.3.1: Complete details of all the resources must be there in the database.

3.3 Interviewer

3.3.1 Description and PriorityThis module is used by interviewee. Interviewee can get the

questions from this module.

3.3.2 Stimulus/Response SequencesThis module will work like an online test. When user will open the

interviewer URL, Questions assigned by Admin will be displayed. Here members will answer the questions and submit his profile.

3.3.3 Functional Requirements

3.3.3.1: To answer the question admin should send a link to the member.

4. External Interface Requirements

4.1 User Interfaces

The user/reader interface will be web based, and accessible to the user via web

browser. After the user logs in he will be provided with a standard screen layout that is

maintained throughout his session. This includes a standard header, a dynamic menu

that is built according to the objects that he has access to. And will provide an option to

comment readers view.

4.2 Hardware Interfaces

Processor/RAM/HDD : 512MB RAM, 40GB HDD

Web server : Apache

Database Server : MYSQL 5.5.16

6

4.3 Software Interfaces

OS : Windows

DBMS : MYSQL 5.5.16

4.4 Communications Interfaces

Professional coordinator is a web application used through a web browser. Admin

should send email messages to the professionals.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

There was no special request regarding performance from the client. Still, the

system should have a minimum response time. The performance will be better as web

application can support more users at a time. The system should be stable and should not

fail under increased workload.

5.2 Safety Requirements

The web-server must be hosted in a safe, hack-proof environment. The location

must be physically safe and all possible unwanted ports must be closed. Regular backup

of the database must be taken on portable media.

5.3 Security Requirements

The system will have provision for additional confirmation and authorization

features for performing key actions. Since such data might have to bind to many other

data, a user can perform such action only if there is appropriate authorization.

5.4 Software Quality Attributes

Correctness: The test cases results have be checked correctly.

Robustness: The application must be tolerant to various erroneous inputs from

the user

Usability : The application must be easy to use, with a user friendly GUI, and

understandable error reports.

7

Appendix A: Glossary

PIC: Professional interview coordinator

GUI: Graphical User Interface

SQL: Structured Query Language

FTP: File transfer protocols

Appendix B: Analysis Model

7. Entity Relationship Diagrams

Basic Notations

Shape Notation Description

EntityAn entity is an object or concept about

which you want to store information.

Weak Entity

A weak entity is an entity that must

defined by a foreign key relationship

with another entity as it cannot be

uniquely identified by its own

attributes alone.

AttributeRepresents the characteristic properties

belonging to the entity.

Key Attribute

A key attribute is the unique,

distinguishing characteristic of the

entity.

Multi-valued AttributeA multivalued attribute can have more

than one value.

RelationshipRelationships illustrate how two

entities share information.

8

Attribute

admin

approve

maileradmin

add/update

category

search

userinfo

userinfo01

reads

interviewee

add/update

assignquestion

userapproach

add

cname

priority

keywordlevel1

cid

level2

level3

qlevel1

qlevel2

qlevel3

userid

personal

interest

contact

email

educationalexp

experience

user id

name

passwordvalid user

flag

messagecount

interest

address

phone

currently

log count

assign

userid

section

question id

answer

position

status

answereddate

date addedstatus

total_answers

recentanswers

approved_date

date added

email_senddate

mailer

admincomment

email_status

category id

userid

street

city

state

searchreads

1

M

N

N1

1

N

N

M

N

Data Flow Diagrams

9

DFD’s are used to convey how data or information flows through the system and how

data is transformed in the process. They are able to provide both high-level system-

overview with boundaries and connection to other systems as well as detailed

representation of system components. They are easy to understand for both technical,

non-technical audiences.

Basic notations

Shape Notation Description

Source/ Destination

Sources and destinations (sink) define

the system’s boundaries. It is

represented by a square.

Process

A process, or transform, identifies an

activity that changes, moves, or

otherwise transforms data. It is shown

as a round-cornered rectangle/ oval

Data Store

Represents data at rest and implies that

the data are held (for some logical

reason) between processes. It is shown

as an open-ended, horizontal rectangle

Flow of Activity or

Control

A data flow represents data in motion.

It is depicted with an arrow.

10

DATA FLOW DIAGRAM

Context Level

DFD Level-1 for Admin

11

Admin

Mailer Admin IntervieweePIC

Category details

Question D

etails

Question details

Answer

Mailing

12

Category details

1Category

Management

Admin2

Question management

3Profile

Management

Question details

Profile info

Request

Response

CategoryInfo

Request

Response

QuestionInfo

Request

Response

ProfileInfo ProfileInfo

4

AnswersAnswer Details

Approval Info

Approval info

DFD Level-1 for Mailer Admin

DFD- Level 1 for Interviewee

13

Mailer Admin

1 Profile

Management

2

Mailing

Profile Details

Mailing Details

Interviewee

1

Answers

Profile Info

Request

Request

Response

Response

MailerInfo

Answer Details

Answer

Category details

DFD-Level-2 for Mailer Admin

14

Admin

1.1Add Category

1.2Edit category

Category details

Category ID

Category Info

Category details

Category ID

2.1Add

Questions

Question details

2.2Edit

Questions

Question ID

2.2Edit

Questions

3.1Add

Profile

4.1View/

Approve answer

Question Info

Category details

Profile Info

Answer Details

1.1 Search User

Keyword Profile Info

Keyword

User ID

DFD-Level-2 for Interviewee

15

1.1 Search User

User ID

Interviewee

1.1

Add answer

Answers

Answer details

Answer

Response