Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1


Ratings: (0)|Views: 81|Likes:
Published by Sagar

More info:

Published by: Sagar on Jun 30, 2009
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





1.0 DOCUMENT CONTROLAuthor / OwnerReviewerAuthoriser
Signature NamePurnima MenonShrikant BrahmeRaj DhillonDesignationSEPGHead SEPGManagement Representative
Preparing the Requirements Specification is a key software life cycle event, for all turnkeysoftware projects executed by ZENSAR. The customer may ask ZENSAR to prepare aRequirements Specification or the customer could supply the Requirements Specification.
The objective of this document is to provide a guideline to arrive at a RequirementsSpecification which is unambiguous, complete as far as possible, verifiable, modifiable,traceable and usable during the development of software or maintenance of installed turnkeysoftware or already existing software.
This format applies to all Requirements Specification documents, unless otherwise a separatestandard is explicitly specified by the customer.
 The purpose of the project
User problem or background of the project effort 
In existing system what kind of problems faced by the user and background work done by theclient.
Goals of the project 
It should includes what exactly wants to achieve from this system by keeping that goal inmind implementation should be done.
Technology Used:Software and Hardware Requirements:
iii) User of the product
Hands on users – people who operate the product and number of simultaneous usersPriorities assigned to usersUser participation – an estimate of needed involvement in the projectUser classes may vary as an end-user, super user or administrator with there specificcharacteristics.
iv) Benefit
Here, will describe the details of who is the beneficiary of this system that may be client perspective, administration point of view, end-user point of view, planner point of view or etc.
v) Limitations
Limitations of the system in terms of number of transactions, batch processing, hardwareconfiguration and etc.
vi) Critical success factors
In order to make development successful, enlist the critical factors and taken intoconsideration while going through software development life cycle.
2) Architecture about flow of the system
It would deals with what way data is to be processed and information has to be passed to thedestination through bridges, routers or hub etc.
3) Project constraintsi) Mandated constraint
Solution design constraint  Implementation environment of the current system Partner or collaborative applications to be used by the product Off the shelf software used within the product  Anticipated workplace environment  Project duration budget  Financial budget for the project 
ii) Relevant Facts, Assumptions and Dependencies
Factors that have an effect on the product but are not mandated requirements
iii) Constraints
Assumption the team is making about the project
46.7 System Objectives
The system objectives should cover the business objectives and the quality objectives, as far as possible in full detail and in measurable terms.This process tries to ensure that all aspects necessary to satisfy the customer's need regardingthe deliverable software and associated accessories are defined and/or mentioned. All suchobjectives could be addressed in this section.As a guideline to write these objectives, the following points must be considered
:a)Functional requirements:
 Functionality -
A set of attributes characterising what the softwaredoes to fulfil the user's functional needs. Each functional requirementshould be stated in terms of input and output and the neededtransformation, as seen by the user.ii)
- Ability to interact with specified systems asmentioned in the section System Interfaces later in this standard.iii)
- Adherence to application related standards, conventionsor regulations.
Data requirements
Volumes of data, normalization, etc
5b)Reliability requirements:
i)Fault tolerance - Ability to maintain a specified level of performance incase of software faults or of infringement of its specified interface. Failsafe capability.ii)Recoverability - Capability to re-establish its level of performance andrecover the data directly affected in case of a failure.iii)Load / Stress – Requirements to evaluate a system or component at o beyond the limits of its specified boundaries.
c) Usability
i)Understandability - User's effort for recognising the logical conceptand its applicability.ii)Learnability - User's effort for learning the application.iii)Operability - User's effort for operation of the application andoperational control.
d) Efficiency:
i)Time behaviour - Response and processing time and throughput rates.ii)Resource behaviour - Amount of resources used.
e) Performance
i)Performance in terms of response time, number of simultaneous users,administration efforts etc
Non-Functional RequirementsLook and feel requirements
Look and feel of screens and sub screens
User interfaces
GUI screen layout / Screen Transitions
It should consist all types of screen layouts.
GUI report layout 
It should consist all types of report layouts
 Interface appearance
How it looks like.
Usability and Humanity Requirements

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->