Sei sulla pagina 1di 10

Software Requirements

Specification
for

Portfolio Management System


Version 1.0

Prepared by

Group Name: D
Adnan Ahmed
Ali Zia
Abdul Rahman
Saifullah

327
310
344
308

Instructor:
Course:
Teaching Assistant:
Date:

Mahradnan@ovi.com
Alizia650@yahoo.com
Rahman34487@yahoo.com
Saifi2010@live.com

Maam Sadaf
Software Engineering
Maam Sadaf
18-11-2012

Contents
REVISIONS................................................................................................................................................................III

SoftwareRequirementsSpecificationforPortfolioManagementSystem
1

Pageii

INTRODUCTION................................................................................................................................................1
1.1
1.2
1.3
1.4
1.5
1.6

DOCUMENT PURPOSE.................................................................................................................................1
PRODUCT SCOPE........................................................................................................................................1
INTENDED AUDIENCE AND DOCUMENT OVERVIEW ...............................................................................1
DEFINITIONS, ACRONYMS AND ABBREVIATIONS....................................................................................2
DOCUMENT CONVENTIONS.................................................................................................................. 2
REFERENCES AND ACKNOWLEDGMENTS.............................................................................................. 2

OVERALL DESCRIPTION...............................................................................................................................3
2.1
2.2
2.3
2.4
2.5
2.6
2.7

PRODUCT PERSPECTIVE...................................................................................................................... 3
PRODUCT FUNCTIONALITY................................................................................................................... 3
USERS AND CHARACTERISTICS............................................................................................................ 3
OPERATING ENVIRONMENT.................................................................................................................. 3
DESIGN AND IMPLEMENTATION CONSTRAINTS......................................................................................4
USER DOCUMENTATION....................................................................................................................... 4
ASSUMPTIONS AND DEPENDENCIES..................................................................................................... 5

SPECIFIC REQUIREMENTS...........................................................................................................................6
3.1
3.1.1
3.1.2
3.1.3
3.1.4

EXTERNAL INTERFACE REQUIREMENTS................................................................................................ 6


USER INTERFACE................................................................................................................................. 6
HARDWARE INTERFACE........................................................................................................................ 7
SOFTWARE INTERFACE........................................................................................................................ 7
COMMUNICATION INTERFACE............................................................................................................... 7

OTHER NON-FUNCTIONAL REQUIREMENTS..........................................................................................8


4.1
4.2
4.3

PERFORMANCE REQUIREMENTS.......................................................................................................... 8
SAFETY AND SECURITY REQUIREMENTS.............................................................................................. 8
SOFTWARE QUALITY ATTRIBUTES....................................................................................................... 8

Revisions
Version

Primary Author(s)

Description of Version

1.0

Adnan Ahmed

This is a first version of Portfolio Management


System. Its still in development, its advance
versions of it will released soon.

Date Completed
Still in progress

SoftwareRequirementsSpecificationforPortfolioManagementSystem

Page1

1 Introduction
This document is used for the release: 1.0 for the web based software: Portfolio Management
System. It specifies the services offered by the software and constraints under which it will
operate. The document contains all the information that is needed to develop the project i.e. all
kinds of user requirements that are required to make this project successful.

1.1 Document Purpose


The document contains the information regarding the Portfolio Management System. The SRS
covers all of the requirements that are needed to complete the project. It will be the first release of
the system.
The purpose is to create a computerized system that will transform the whole rigorous job of
creating and managing the portfolios to a trouble-free job that will be gripped in a compact and
efficient manner. The system that is to be developed in this release will cover all of the
requirements needed to complete this project. The software will be providing registration system
for professionals, profile creation, and search system to search for the professionals based on
their skills, education, name etc.

1.2 Product Scope


A web based system for portfolio & CV management is being proposed. It will enable the
professionals from all over the world to create an online portfolio including their educational
details, contact details and projects that they have worked on. The system would enable the
contractors to search the professionals from our website using either the category wise
distribution system, by a specific project name that they have worked on, by name, by the
keywords/tags that professionals have included etc. After finding a specific professional of his
need, a contractor can contact a professional either through our website or the contact details
that he has provided.
Currently there does not exist any website providing such functionality and we hope that the
website will do a good business. It will benefit the professionals in a way that, they dont have to
develop a whole website for their portfolio; they can easily maintain an online portfolio on our
website. On the other hand, it will also help the contractors as well i.e. in finding the employees
easily.

1.3 Intended Audience and Document Overview


The document is intended to be read by project managers, developers, testers, and
documentation writers. The purpose of this document is to serve as a guide to designers,
developers and testers who are responsible for the engineering of this project. It should give the
engineers all of the information necessary to design, develop and test the software. Proceeding

SoftwareRequirementsSpecificationforPortfolioManagementSystem

Page2

with the Section-1 which describes the purpose and scope of the project; and Section-2 gives
an overall description of the software product.

1.4 Definitions, Acronyms and Abbreviations


Terms
Actor
GUI
Info
Log in
Log Out
PMS
RegInfo
User

Description
A person or system that will interact with the system.
Graphical User Interface
Information
Providing username and password to the system using a form to use
the software
A process after which the user can no more access the software. For
further use logging in is required.
Portfolio Management System
Registration Information
Whoever will use the system, professional, contractor, administrator

1.5 Document Conventions


This document uses the font-family of Arial font size 11 for paragraphs, 14 for headings and 18
for the titles throughout the document. Italics are used for the terms that can be seen in the
glossary. The line-height used is 1.15px.
IEEE naming conventions are used all over the document i.e. for the users, system etc.

1.6 References and Acknowledgments


Not applicable.

SoftwareRequirementsSpecificationforPortfolioManagementSystem

Page3

2 Overall Description
2.1 Product Perspective
The PMS has maintains the information about the registered professionals like their education
level, contact information, his picture, projects etc. Portfolio Management System helps the
contractors to find professionals that hold their requirements. The contractor can search for the
professionals by area, skills or projects (that he has worked on). In this way the Portfolio
Management System to be developed benefits greatly, the experts and the contractors.
The complete overview of the system is shown in the use case model below:

The
users of
the system will be:
Administrator; who will be constantly checking the users accounts for any illegal activity.
Professionals; who are the registered members/users of website
Contractors; who can search for the professionals and contact them.

SoftwareRequirementsSpecificationforPortfolioManagementSystem

Page4

2.2 Product Functionality


The Portfolio Management System will be maintaining the information about the registers
members of website. Following are the key functionalities that will be provided by the system:

The professionals/members & Administrator must have to login to use the system.
The administrator can add delete or block different members.
Anyone, whether he has registered or not, can search for the professionals.
To maintain an online portfolio, the user must have to register on our website by
providing the valid information.
Professionals after registering can add the details like, their educational
background, the projects that they have worked on, the family background, and
images for the projects etc.
The maximum number of images that can be added by a single account will be 20.
The administrator can block any member in case of illegal use.
Anyone can visit the system and can use it without logging in i.e. they can search
for the professionals, provide feedback etc.
Anyone can contact a professional by opening his profile.

2.3 Users and Characteristics


The users of the system are professionals, contractors and an administrator. The PMS has a very
simple interface and it will provide guidelines to the users. The contractor is assumed to have a
basic knowledge of surfing web. The administrator of the system have more knowledge about the
internals of the system and resolve the small problems that may arise due to disk crashes, power
failure, taking backup and other glitches to maintain the system.

2.4 Operating Environment


The website will be compatible with all the major browsers like Mozilla Firefox, Google Chrome,
Opera etc. and platform (Windows XP, Windows Vista and Windows 7, Linux, Macintosh etc.).
This website will also be surfed on mini browsers.

2.5 Design and Implementation Constraints

The tools/technologies that shall be used to develop the system will be HTML, PHP 5.0,
CSS and JavaScript.
Dreamweaver IDE will be used.

SoftwareRequirementsSpecificationforPortfolioManagementSystem

Page5

2.6 User Documentation


The User Manual describes the use of the system to Manager and Employees. The user manual
should be available as a hard copy. An installation document will be provided that includes the
installation instructions and configuration guidelines, which is important to a full solution offering.

2.7 Assumptions and Dependencies

The users have sufficient knowledge of computers.


The users know the English language, as the user interface will be provided in English.

3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces

SoftwareRequirementsSpecificationforPortfolioManagementSystem

Req.ID

UI1

UI2

UI2

UI3
UI4
UI5
UI6
UI7
UI8
UI9
UI10
UI11
UI12
UI13
UI14

Page6

Requirement
Whenthewebsiteisopened,thefollowingoptionsareshownonthe
screen:
a)UserLogin
b) SearchProfessionalsbyfollowingcategories(By
name,By
skill,ByProject,ByArea)
c)Signup
d)Amenuwithfollowingoptions(Home,Professionals,
Benefits,AboutUs,ContactUs)
Inthetoprightcornerthereisasigninsectionwheretheuseris
requiredtoenterthefollowingthings:
a)UserName(Tobeenteredthroughatextbox)
b)Password(Tobeenteredthroughatextbox)
After the successful login of the user, following options will be
displayedonthescreen:
a) Amenuintheleftcorner
b) Welcometagintheleftcornerwithfollowingoptions
(Dashboard,EditProfile&Logout)
c) Userimage
d) Facebook&Twitterlinksbeneaththeuserimage
e) Basicinformationoftheuser
f) Followingoptionsontherightside(Mailbox,Personal
Information,Educations,ProjectInformation)
Usercanselectoneoptionatatimebyclickingtherespectivelink.
Iftheuserselectsthelogoutlinkthenhewillbeloggedoutfromthe
system.
Ifheselectstheeditprofilethenhecanedithispersonalinformation,
educationalinformation,projects.
Ifuserselectsthemailboxthenhecancheckhismailsthatweresend
tohim.
Ifauservisitsourwebsiteandheisregisteredmemberthenhecan
onlysearchfortheregisteredmembersandcontactthem.
TheHomelinkinthemenuwillredirecttheusertothemainpageof
thewebsite.Wheretheusercansearchforothermembers.
TheProfessionallinkinthemenuwillredirecttothepagewherethe
usercanseethelistofallotherregisteredusers.
The benefits linkin themenu will redirect the user where hecan
checkthebenefitsaboutusingthesystem.
TheAboutUslinkwillredirecttheusertothepagewherethedetail
abouttheprogrammersisgivenwhodevelopedthesystem.
TheContactUspagewillcontaintheinformationaboutcontacting
thedevelopersincaseofanyproblem.
Whentheuserisloggedoutfromthesystemthentheuserisagain
redirectedtomainpage(indexpage).
IftheLogOutoptionisselected,theadministratorwillbeloggedout
andtheloginscreenwillbeshownagain.

3.1.2 Hardware Interfaces

SoftwareRequirementsSpecificationforPortfolioManagementSystem

Req.ID
HI1

Page7

Requirement
Acompletesystem(withmouse,Keyboard,Monitoretc.)isrequiredinordertosurf
thewebsite.

3.1.3 Software Interfaces


Req.ID
SI1
SI2

Requirement
Latestversionofthebrowserisrequiredtosurfthewebsite.
ThebrowsermustsupportCSS3.0,PHP5.0,HTML5.0.

3.1.4 Communications Interfaces


Req.ID
CI1

Requirement
Internetisrequiredbytheuserinordertosurfthewebsite.

4 Other Non-functional Requirements


4.1 Performance Requirements
Req.ID

Requirement

P1

Thebackupofthesystemwillbetakenafterevery24hours.
Ifanytechnicalproblemoccursthenthesystemadministratorwillbenotified
immediately.

P2

4.2 Safety and Security Requirements


Req.ID

Requirement

SoftwareRequirementsSpecificationforPortfolioManagementSystem

S1
S2
S3
S4

Page8

On the main page there is a signup section, login section and search section and
no option other than exit will be shown on the main page of the system.
Toupdatehisinformationonthesystemtheusermusthavetologininorderto
dothat.
Onlyoneinstanceofasystemcanberunningatatime.
Thenonregisteredmembercanonlysearchfortheotherregisteredusersand
contactthem.

4.3 Software Quality Attributes


This SRS is gratifying all the requirements of the programmer and user of the system. The
programmer has no need to access exterior resources to fulfill the chucks.

Potrebbero piacerti anche