Sei sulla pagina 1di 8

Table of Contents

1 Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms, and Abbreviations. 1.4 Overview 2 The Overall Description 2.1 Product Perspective 2.1.2 Software Interfaces 2.2 Product Functions 2.3 ser !"aracteristics 2.4 Apportionin# of $e%uirements 2.& Assumptions and Dependencies 3 Specific Requirements 3.1 '(terna) *nterfaces 3.1.1 User Interfaces 3.1.2 Software Interfaces 3.1.3 Hardware Interfaces 3.1.4 Communication Interfaces 3.2 Functiona) $e%uirements 3.3 ,onfunctiona) $e%uirements 3.3.1 Performance Requirements 3.3.2 o!ica" #ata$ase Requirements 3.3.3 #esi!n Constraints 3.3.4 Standards Com%"iance 3.3.5 Re"ia$i"it& 3.3.6 ()ai"a$i"it& 3.3.7 *aintaina$i"it& 3.3.' Porta$i"it& Chan!e "ana!ement #rocess 5 Document %pprovals &.1 .eam One Approva) & Supportin! Information 2 2 2 3 3 3 3 3 3 4 4 4 5 & 5 5 5 6 + 7 7 7 7 ' ' ' ' $ $ / $

Introduction

+,e fo""owin! su$sections of t,e Software Requirements S%ecifications -SRS. document %ro)ide an o)er)iew of t,e entire SRS.

1'1 #urpose
+,e Software Requirements S%ecification -SRS. wi"" %ro)ide a detai"ed descri%tion of t,e requirements for t,e /n ine mo)ie tic0et $oo0in! s&stem. +,is SRS wi"" a""ow for a com%"ete understandin! of w,at is to $e e1%ected of t,e H*S to $e constructed. +,e c"ear understandin! of t,e /n ine mo)ie tic0et $oo0in! s&stem and its2 functiona"it& wi"" a""ow for t,e correct software to $e de)e"o%ed for t,e end user and wi"" $e used for t,e de)e"o%ment of t,e future sta!es of t,e %ro3ect. +,is SRS wi"" %ro)ide t,e foundation for t,e %ro3ect. 4rom t,is SRS5 t,e H*S can $e desi!ned5 constructed5 and fina""& tested. +,is SRS wi"" $e used $& t,e software en!ineers constructin! t,e /n ine mo)ie tic0et $oo0in! s&stem and t,e ,ote" end users. +,e software en!ineers wi"" use t,e SRS to fu""& understand t,e e1%ectations of t,is /n ine mo)ie tic0et $oo0in! s&stem to construct t,e a%%ro%riate software. +,e ,ote" end users wi"" $e a$"e to use t,is SRS as a 6test7 to see if t,e software en!ineers wi"" $e constructin! t,e s&stem to t,eir e1%ectations. If it is not to t,eir e1%ectations t,e end users can s%ecif& ,ow it is not to t,eir "i0in! and t,e software en!ineers wi"" c,an!e t,e SRS to fit t,e end users2 needs.

1'2 Scope
+,e software %roduct to $e %roduced is a /n ine mo)ie tic0et $oo0in! s&stem w,ic, wi"" automate t,e ma3or $oo0in! o%erations. +,e first su$s&stem is a 8oo0in! S&stem to 0ee% trac0 of mo)ie a)ai"a$i"it&. +,e second su$s&stem is t,at c,ar!es t,e tic0et. +,e t,ird su$s&stem is a 9enera" *ana!ement Ser)ices and (utomated +as0s S&stem w,ic, !enerates re%orts to audit a"" tic0et& o%erations and a""ows modification of su$s&stem information. +,ese t,ree su$s&stems2 functiona"it& wi"" $e descri$ed in detai" in section 2: /)era"" #escri%tion. +,ere are two end users for t,e /n ine mo)ie tic0et $oo0in! s&stem. +,e end users are t,e staff -customer ser)ice re%resentati)e. and mana!ers. 8ot, user t&%es can access t,e /n ine mo)ie tic0et $oo0in! s&stem. +,e 9enera" *ana!ement S&stem wi"" $e restricted to mana!ement users. /n ine mo)ie tic0et $oo0in! s&stem o$3ecti)es is to %ro)ide a s&stem to mana!e a s&stem of s,ows. ;it,out automation t,e mana!ement of t,e s,ows ,as $ecome an unwie"d& tas0. +,e end users2 da&:to:da& 3o$s of mana!in! a s,oes wi"" $e sim%"ified $& a considera$"e amount t,rou!, t,e automated s&stem. +,e s&stem wi"" $e a$"e to ,and"e man& ser)ices to ta0e care of a"" customers in a quic0 manner. +,e s&stem s,ou"d $e user a%%ro%riate5 eas& to use5 %ro)ide eas& reco)er& of errors and ,a)e an o)era"" end user ,i!, su$3ecti)e satisfaction.

1'3 Definitions( %cron)ms( and %bbreviations'


SRS < Software Requirements S%ecification Su$3ecti)e satisfaction < +,e o)era"" satisfaction of t,e s&stem =nd users < +,e %eo%"e w,o wi"" $e actua""& usin! t,e s&stem

1'

Overvie*

+,e SRS is or!ani>ed into two main sections. +,e first is +,e /)era"" #escri%tion and t,e second is t,e S%ecific Requirements. +,e /)era"" #escri%tion wi"" descri$e t,e requirements of t,e /n ine mo)ie tic0et $oo0in! s&stem from a !enera" ,i!, "e)e" %ers%ecti)e. +,e S%ecific Requirements section wi"" descri$e in detai" t,e requirements of t,e s&stem.

The Overall Description

#escri$es t,e !enera" factors t,at affect t,e %roduct and its requirements. +,is section does not state s%ecific requirements. Instead it %ro)ides a $ac0!round for t,ose requirements5 w,ic, are defined in section 35 and ma0es t,em easier to understand.

2'1 #roduct #erspective


+,e /n ine mo)ie tic0et $oo0in! s&stem is an inde%endent stand<a"one s&stem. It is tota""& se"f contained. 2'1'1 +ard*are Interfaces +,e /n ine mo)ie tic0et $oo0in! s&stem wi"" $e %"aced on PC2s t,rou!,out t,e mo)ie %a"aces. 2'1'2 Soft*are Interfaces ("" data$ases for t,e /n ine mo)ie tic0et $oo0in! s&stem wi"" $e confi!ured usin! /rac"e 'i. +,ese data$ases inc"ude ,ote" rooms and customers information. +,ese can $e modified $& t,e end users. +,e room data$ase wi"" inc"ude t,e room num$ers and if t,e& are )acant or occu%ied. +,e customers information data$ase wi"" contain a"" t,e information of t,e customer suc, as first name5 "ast name5 assi!ned mo)ie5 %,one num$er5 w,et,er or not t,e mo)ie is !uaranteed5 credit card num$er5 confirmation num$er5 automatic cance""ation date5 e1%ected c,ec0 in date and time5 amount owed $& customer5 and a$$re)iated customer feed$ac0.

2'2 #roduct ,unctions


Reser)ation and 8oo0in! S&stem (""ows for t&%in! in customer information Inc"udes a descri%tion fie"d for t,e c,an!ed rate ;,en a customer c,ec0s in5 t,e mo)ie wi"" $e c,an!ed to occu%ied in t,e data$ase ($i"it& to modif& a reser)ation

;,en no mo)ie is a)ai"a$"e and a customer wou"d "i0e to e1tend t,eir tic0et $oo0in! t,eir information wi"" $e %"aced in a data$ase and w,en t,ere are tic0ets a)ai"a$"e t,e first customer on t,e "ist wi"" ,a)e t,e room ;,en a customer c,ec0s out t,e amount owed is dis%"a&ed If t,e interna" c"oc0 states t,at is a customer2s time to ,a)e c,ec0ed out and customer ,as not c,ec0ed out5 adds an e1tra ni!,t to amount owed and %ro)ides a re%ort Records t,at seats are a)ai"a$"e Records %a&ment (""ows for s%ace to write customer2s feed$ac0 9enera" *ana!ement Ser)ices and (utomated +as0s S&stem =1ce%tion re%orts "istin! e1ce%tions to t,e norma" cost (""ows addition5 de"etion and modification of information on tic0et rates5 Creation of users and assi!nin! %asswords

2'3 -ser Characteristics


=ducationa" "e)e" of H*S com%uter software < ow =1%erience of H*S software < ?one +ec,nica" =1%ertise < itt"e

2'

%pportionin! of Requirements

+,e audio and )isua" a"erts wi"" $e deferred $ecause of "ow im%ortance at t,is time.

2'5 %ssumptions and Dependencies


: +,e s&stem is not required to sa)e !enerated re%orts. : Credit card %a&ments are not inc"uded

Specific Requirements

+,is section contains a"" t,e software requirements at a "e)e" of detai"5 t,at w,en com$ined wit, t,e s&stem conte1t dia!ram5 use cases5 and use case descri%tions5 is sufficient to ena$"e desi!ners to desi!n a s&stem to satisf& t,ose requirements5 and testers to test t,at t,e s&stem satisfies t,ose requirements.

3'1 ./ternal Interfaces


+,e Hote" *ana!ement S&stem wi"" use t,e standard in%ut@out%ut de)ices for a %ersona" com%uter. +,is inc"udes t,e fo""owin!A Be&$oard *ouse *onitor Printer 3'1'1 -ser Interfaces +,e User Interface Screens are descri$ed in ta$"e 1.
Table 10 +otel "ana!ement -ser Interface Screens

Screen 1ame o!in Reser)ation C,ec0:in C,ec0out Hote" Pa&ment Room Ser)ice@Restaurant Customer Record (dminister Rooms (dminister User (dminister *ea"s Re%orts 3'1'2 Soft*are Interfaces

Description o! into t,e s&stem as a CSR or *ana!er Retrie)e $utton5 u%date@sa)e reser)ation5 cance" reser)ation5 modif& reser)ation5 c,an!e reser)ation5 ad3ust room rate5 acce%t %a&ment t&%e@credit card *odif& room sta& -e.!.5 new credit card.5 c,ec0:in customer -wit, or wit,out a reser)ation.5 ad3ust room rate5 s%ecia" requests5 acce%t %a&ment t&%e@credit card C,ec0out customer5 !enerate $i"" (cce%t %a&ment for room and food Create order5 modif& order5 )iew order5 cance" order5 !enerate mea" $i"" (dd or u%date customer records ()ai"a$i"it& and rates Create5 modif&5 and de"ete usersC c,an!e %assword Create5 modif&5 and de"ete mea" items and %rices Se"ect5 )iew5 sa)e5 and de"ete re%orts

+,e s&stem s,a"" interface wit, an /rac"e or (ccess data$ase. 3'1'3 +ard*are Interfaces +,e s&stem s,a"" run on a *icrosoft ;indows $ased s&stem.

3'1'

Communication Interfaces

+,e s&stem s,a"" $e a standa"one %roduct t,at does not require an& communication interfaces.

3'2 ,unctional Requirements


4unctiona" requirements define t,e fundamenta" actions t,at s&stem must %erform. +,e functiona" requirements for t,e s&stem are di)ided into t,ree main cate!ories 1. 8oo0in! 1.1. +,e s&stem s,a"" record reser)ations. 1.2. +,e s&stem s,a"" record t,e customer2s first name. 1.3. +,e s&stem s,a"" record t,e customer2s "ast name. 1.4. +,e s&stem s,a"" record t,e customer2s %,one num$er. 1.5. +,e s&stem s,a"" dis%"a& w,et,er or not t,e mo)ie is !uaranteed. 1.6. +,e s&stem s,a"" !enerate a unique confirmation num$er for eac, tic0et. 1.7. +,e s&stem s,a"" automatica""& cance" non:!uaranteed tic0et $oo0in!. 1.'. +,e s&stem s,a"" record t,e s,ow date and time. 1.D. +,e s&stem s,a"" c,ec0:in customers. 1.1E. +,e s&stem s,a"" a""ow reser)ations to $e modified wit,out ,a)in! to reenter a"" t,e customer inforamtion.

3'3 1onfunctional Requirements


4unctiona" requirements define t,e needs in terms of %erformance5 "o!ica" data$ase requirements5 desi!n constraints5 standards com%"iance5 re"ia$i"it&5 a)ai"a$i"it&5 securit&5 maintaina$i"it&5 and %orta$i"it&. 3'3'1 #erformance Requirements Performance requirements define acce%ta$"e res%onse times for s&stem functiona"it&. +,e "oad time for user interface screens s,a"" ta0e no "on!er t,an two seconds. +,e "o! in information s,a"" $e )erified wit,in fi)e seconds. Fueries s,a"" return resu"ts wit,in fi)e seconds. 3'3'2 2o!ical Database Requirements +,e "o!ica" data$ase requirements inc"ude t,e retention of t,e fo""owin! data e"ements. +,is "ist is not a com%"ete "ist and is desi!ned as a startin! %oint for de)e"o%ment. 3oo4in!5Reservation S)stem Customer first name Customer "ast name Customer address Customer %,one num$er ?um$er of occu%ants (ssi!ned mo)ie Rate descri%tion 9uaranteed mo)ie tic0et -&es@no. Credit card num$er Confirmation num$er (utomatic cance""ation date Customer feed$ac0 Pa&ment recei)ed -&es@no. Pa&ment t&%e 3'3'3 Desi!n Constraints +,e /n ine mo)ie tic0et $oo0in! s&stem s,a"" $e a stand:a"one s&stem runnin! in a ;indows en)ironment. +,e s&stem s,a"" $e de)e"o%ed usin! Ga)a and an (ccess or /rac"e data$ase. 3'3' Standards Compliance

+,ere s,a"" $e consistenc& in )aria$"e names wit,in t,e s&stem. +,e !ra%,ica" user interface s,a"" ,a)e a consistent "oo0 and fee".

3'3'5 Reliabilit) S%ecif& t,e factors required to esta$"is, t,e required re"ia$i"it& of t,e software s&stem at time of de"i)er&. 3'3'& %vailabilit) +,e s&stem s,a"" $e a)ai"a$"e durin! norma" ,ote" o%eratin! ,ours. 3'3'6 "aintainabilit) +,e Hote" *ana!ement S&stem is $ein! de)e"o%ed in Ga)a. Ga)a is an o$3ect oriented %ro!rammin! "an!ua!e and s,a"" $e eas& to maintain. 3'3'$ #ortabilit) +,e Hote" *ana!ement S&stem s,a"" run in an& *icrosoft ;indows en)ironment t,at contains Ga)a Runtime and t,e *icrosoft (ccess data$ase.

Chan!e "ana!ement #rocess


C,an!es to t,is document ma& $e made after a%%ro)a" from t,e %ro3ect mana!er and t,e c"ient a%%ro)a" officer.

Document %pprovals

5'1 Team One %pproval


HHHHHHHHHHHHHHHHHHHHHHHH (ns,u 0umar s,arma HHHHHHHHHHHH #ate

&

Supportin! Information

( s&stem conte1t dia!ram as we"" as use cases and use case descri%tions ,a)e $een de)e"o%ed in se%arate documents.

Potrebbero piacerti anche