Video RecordingSoftware Requirements Specification (SRS)AbstractThis document fully and formally describes the requirement...
or problems to be solved and the software behavior necessary to      address those problems. Therefore, the SRS should be ...
IntroductionThis project is used to list out all the camera’s connected to the computer.Capturing the video from the multi...
Hardware RequirementsProcessor           :   Pentium IV 2GHz and AboveRAM                 :   2GB RAMMonitor             :...
Upcoming SlideShare
Loading in...5
×

Academic project video recording and broadcasting synopsis

129

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
129
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Academic project video recording and broadcasting synopsis"

  1. 1. Video RecordingSoftware Requirements Specification (SRS)AbstractThis document fully and formally describes the requirements of the proposedsaid project system. It sets out the functional and non-functionalrequirements and includes a description of the user interface anddocumentation and training requirements.An SRS is basically an organizations understanding (in writing) of a customeror potential clients system requirements and dependencies at a particularpoint in time (usually) prior to any actual design or development work. Its atwo-way insurance policy that assures that both the client and theorganization understand the others requirements from that perspective at agiven point in time.The SRS document itself states in precise and explicit language thosefunctions and capabilities a software system must provide, as well as statesany required constraints by which the system must abide. The SRS alsofunctions as a blueprint for completing a project with as little cost growth aspossible. The SRS is often referred to as the "parent" document because allsubsequent project management documents, such as design specifications,statements of work, software architecture specifications, testing andvalidation plans, and documentation plans, are related to it.Its important to note that an SRS contains functional and nonfunctionalrequirements only; it doesnt offer design suggestions, possible solutions totechnology or business issues, or any other information other than what thedevelopment team understands the customers system requirements to be.A well-designed, well-written SRS accomplishes four major goals:  It provides feedback to the customer. An SRS is the customers assurance that the development organization understands the issues
  2. 2. or problems to be solved and the software behavior necessary to address those problems. Therefore, the SRS should be written in natural language, in an unambiguous manner that may also include charts, tables, data flow diagrams, decision tables, and so on.  It decomposes the problem into component parts. The simple act of writing down software requirements in a well-designed format organizes information, places borders around the problem, solidifies ideas, and helps break down the problem into its component parts in an orderly fashion.  It serves as an input to the design specification. As mentioned previously, the SRS serves as the parent document to subsequent documents, such as the software design specification and statement of work. Therefore, the SRS must contain sufficient detail in the functional system requirements so that a design solution can be devised.  It serves as a product validation check. The SRS also serves as the parent document for testing and validation strategies that will be applied to the requirements for verification.SRS are typically developed during the first stages of "RequirementsDevelopment," which is the initial product development phase in whichinformation is gathered about what requirements are needed--and not. Thisinformation-gathering stage can include onsite visits, questionnaires,surveys, interviews, and perhaps a return-on-investment (ROI) analysis orneeds analysis of the customer or clients current business environment. Theactual specification, then, is written after the requirements have beengathered and analyzed.The National Bureau of Standards, IEEE (Standard No: 830-1984), and theU.S Department of Defense have all proposed candidate formats for softwarerequirements specifications. The general structure is implemented with therelated software application
  3. 3. IntroductionThis project is used to list out all the camera’s connected to the computer.Capturing the video from the multiple camera’s, also to take snap for thecamera.PurposeThe purpose of this document is to specify requirements and to giveguidelines for the development of above said project. In particular it givesguidelines on how to prepare the above said project.This document is intended to be a practical guide for people who developingthis software.ScopePresently all camera manufacturers give application software with thecamera. This application software can only capture one camera video. Ourapplication will capture from multiple camera’s.GoalThe main goal of the project is to list out the number of camera’s connectedto the system. And allow user capture the video from multiple camera’s.ReferencesOverviewCamera Drivers for the vendorsCustomer User Manual
  4. 4. Hardware RequirementsProcessor : Pentium IV 2GHz and AboveRAM : 2GB RAMMonitor : 15” Color MonitorKeyboardMouseSoftware RequirementsOperating System. : Windows XPDeveloping Tool : VB2005Database : No Database

×