Software Requirements

Published on March 2017 | Categories: Documents | Downloads: 42 | Comments: 0 | Views: 304
of 11
Download PDF   Embed   Report

Comments

Content

Software Engineering Software Requirements Specification (SRS) Document
Ryan Evans Barry Chapman Sam Williams Devin Coger SoftEng06 www.radford.edu/ softeng06 !0/"0/"00#

Revisions
Version Final Draft Primary Author(s) Team Description of Version All sections being Filled Date Completed 10/20/09

Review & Approval
Requirements Document Approval History Approvin Party Barry Chapman Dr. T. L. Lewis Version Approved !i nature Date

Requirements Document Review History Reviewer Ryan Evans Sam Williams Devin Coger Version Reviewed !i nature Date

Shock Force Software Team

2

Contents
.........................................................................................................................................................1

Shock Force Software Team

3

1. Introdu tion
1.1 Introdu tion The !r ose of this doc!ment is to define and describe the re"!irements of the ro#ect and to s ell o!t the s$stem%s f!nctionalit$ and its constraints. 1.! S ope o" this Do ument The c!stomer and the !ser for the s$stem are the em lo$ees of the &DA'()* incl!ding +rs. Sheila (oo * and the de,elo ers of the s$stem is the Shock Force Software Team. -!r constraints for this section incl!des o!r deadline for the doc!ment which is d!e 10/29/09 1.# $verview The rod!ct is an Access Database with im ort/e. ort ca abilities from /.cel that will hold information on a!ctions* bid items and their bidders* incl!ding a!ction income* a!ction e. enses* bid amo!nt* bid increment* bid &D* item donor* item%s original ,al!e* a$ment t$ e* bidder name* and bidder email. 1.% Business Conte&t As it a lies to this ro#ect* The &ntellect!al Disabilities Agenc$ of the 'ew (i,er )alle$ is a non0 rofit organi1ation that s! orts eo le str!ggling with intellect!al disabilities thro!gh holding f!ndraisers and silent a!ctions to raise aid as well as awareness

!. 'eneral Des ription
!.1 (rodu t )un tions The rod!ct sho!ld make in !t of data and the entire checko!t rocess easier and streamlined for the !sers 2em lo$ees3 and time efficient for the bidder. !.! Similar System In"ormation The rod!ct is being de,elo ed with Access* so there are a large n!mber of similar databases or s$stems and the$ are !sed for a wide arra$ of different !r oses. The ossible strength o!r s$stem has o,er the ma#orit$ is the /.cel im ort/e. ort feat!re of the rogram. !.# *ser Chara teristi s The !sers incl!de the em lo$ees of the &DA as the$ in !t data on bids and their bidders. For this s$stem* the !ser is re"!ired to know the basic !sabilit$ of /.cel as well as a ,er$ base le,el !nderstanding of access* which ho ef!ll$ will be facilitated b$ the software team thro!gh training. !.% *ser (ro+lem Statement The !sers s$stem* c!rrentl$* is slow and inefficient as it relates to the checko!t rocess. 4idders m!st wait ho!rs to check o!t the item the$ ha,e won. Too man$ man ho!rs ha,e been needed to enter the wealth of information collected. !., *ser $+-e tives The !ser wants a database that will store information on a silent a!ction. The rogram m!st faciliatate the s eed and ease of in !t. &t also m!st store the items the &DA'() needs to store. Shock Force Software Team 5

!.. 'eneral Constraints 6onstraints incl!de an eas$ to !se interface for the rogram thro!gh forms* a 7indows latform or* at bare minim!m* a +ac with Access and /.cel for +ac installed. Also* it m!st be constr!cted in Access* /.cel* or another related rogram that is easil$ learnable.

#. )un tional Re/uirements
1. Items provided to the ID01R2 shall +e stored in the 0 ess Data+ase. 1. &tems shall be stored on the la to machine and ha,e com lete fields. 2. )er$ high criticalit$ 3. 8imited network / wi0fi a,ailabilit$ co!ld resent a technical challenge 5. The abo,e stated factor is a risk we ha,e enco!ntered. /liminate it b$ red!cing the de endenc$ of o!r rogram on these things. 9. This re"!irement is the basis of the ro#ect: all other as ects de end on it.

!. The items shall +e a essi+le via /ueries and reports. 1. ;sers of the database sho!ld be able to r!n re orts on the data that has been !t into the database. The$ sho!ld also be able to r!n "!eries. 2. )er$ high criticalit$ 3. 7e do not foresee an$ technical iss!es re,enting the im lementation of this. 5. <i,en the ca abilities of Access* this re"!irement is able to be satisfied. 9. This re"!irement de ends on re"!irement n!mber one. #. The data stored should +e a+le to +e manipulated through "orms. 1. &tems and other data sho!ld be able to be added and ! dated thro!gh the !se of forms. 2. )er$ high criticalit$ 3. 7e do not foresee an$ technical risks in,ol,ed in this re"!irement. 5. The onl$ factor we can enco!nter here is the !ser of the s$stem not being able to !se it correctl$. 7e will o,ercome this b$ training those who will be !sing it. 9. This re"!irement is de endent on re"!irement one.

Shock Force Software Team

9

%. Inter"a e Re/uirements
"#$ %ser &nterfaces


• • •

%.1.1 '*I The !ser interface for this rogram is the interface ro,ided b$ +icrosoft Access 200=. Access incl!des forms and re orts for the !sers to "!er$ and organi1e data to s!it their needs. Forms and re orts both ha,e b!ilders that let the !ser s ecif$ which fields the$ want to !se and which constraints the$ want to define. %.1.! CLI There is no command line interface %.1.# 0(I There is no A>& for the rod!ct %.1.% Diagnosti s or R$3 There is a tro!bleshooting and hel section ro,ided b$ +icrosoft

"#' Hardware &nterfaces
The rogram 2Access3 !ses the hard disk. Access to the hard dri,e and other hardware is managed b$ the o erating s$stem and Access.

"#( Communications &nterfaces
&f we decide to im lement an Ad ?oc network for a shared database* the o erating s$stem will handle those connections.

"#" !oftware &nterfaces
The Access s$stem ma$ be !sed to im ort and e. ort data with +icrosoft /.cel. This f!nctionalit$ is b!ilt in to the !ser interface.

,. (er"orman e Re/uirements
The database is designed to be o erated thro!gh +icrosoft Access 200=* th!s no additional s$stem re"!irements e.ist be$ond those re"!ired to r!n +icrosoft -ffice 200=* e.ce t for a negligible amo!nt of hard dri,e s ace to store the database. +icrosoft lists the re"!irements for Access 200= as follows@ 900 +?1 rocessor or higher 29A+4 (A+ or higher 1.9<4 A,ailable ?ard Dri,e S ace 7indows B> S>2 or later o erating s$stem. 7indows -ffice >rofessional 200= 27indows Access3 There is also Access A,ailable for +ac -S B* the clients ha,e not stated a need th!s far. Shock Force Software Team A

.. $ther non4"un tional attri+utes
.

)#$ !ecurity
The s$stem shall be designed with a le,el of sec!rit$ a ro riate for the sensiti,it$ of information enclosed in the database. +ore interaction is needed with client abo!t the ,olatilit$ of the information. Since there is no ob,io!s information that is of a high sec!rit$ le,el s!ch as credit card information* the onl$ re"!irements that co!ld be im lemented are encr$ ting the database and/or making the database assword0 rotected* b$ !ser%s re"!est.

)#' *inary Compati+ility
This s$stem will be com atible with an$ com !ter that has +icrosoft -ffice >rofessional 200= or later installed 2whether >6 or +ac3* and will be designed with more than one com !ter in mind.

)#( Relia+ility
(eliabilit$ is one of the ke$ attrib!tes of the s$stem. 4ack0! s will be made reg!larl$ so that restoration with minimal data loss is ossible in the e,ent of !nforeseen e,ents. The s$stem will also be thoro!ghl$ tested b$ all team members to ens!re reliabilit$.

)#" ,aintaina+ility
The s$stem shall be maintained b$ Sheila (oo * of the &DA* or delegated to another em lo$ee.

)#- Porta+ility
The s$stem shall be designed in a wa$ that shall allow it to be r!n on m!lti le com !ters with +icrosoft -ffice >rofessional 200= or later installed.

)#) ./tensi+ility
The s$stem shall be designed and doc!mented in s!ch a wa$ that an$bod$ with an !nderstanding of +icrosoft Access shall be able to e.tend the s$stem to fit their needs with the team%s basic instr!ctions.

)#0 Reusa+ility
The s$stem sho!ld be designed in a wa$ that allows the database to be re0!sed reg!larl$ for the ,ario!s silent a!ctions that the organi1ation shall hold. Shock Force Software Team =

)#1 Application Affinity2Compati+ility
This s$stem re"!ires the +icrosoft -ffice >rofessional 200= s!ite or later* as it o erates rimaril$ thro!gh +icrosoft Access* in con#!nction with +icrosoft /.cel.

)#3 Resource %tili4ation
The reso!rces !sed in the creation of this s$stem incl!de@ Dr. 8ewis* the client 2Sheila (oo 3* the com !ters in Da,is ?all* and the internet.

)#$5 !ervicea+ility
The maintenance of the s$stem sho!ld be able to be s!fficientl$ erformed b$ an$ erson with a basic !nderstanding of +icrosoft Access.

5. $perational S enarios
S enario 06 Initial Item De"initions
The !ser shall enter the information abo!t the items into the database for its initial constr!ction and e,ol!tion. The fields will be com leted ,ia a form that will mani !late the data.

S enario B6 Customer Che 74out
The !ser shall be able to enter information abo!t the c!stomer !rchasing a artic!lar item* and record their bid and other information. The$ will also enter the winning bid

S enario C6 Data+ase 3aintenan e
The !ser ma$ want to alter/delete information after the a!ction is o,er* &n this case the$ will need to be able to remo,e the data that has been entered.

Shock Force Software Team

C

8. (reliminary *se Case 3odels and Se/uen e Diagrams
This section resents a list of the f!ndamental se"!ence diagrams and !se cases that satisf$ the s$stem%s re"!irements. The !r ose is to ro,ide an alternati,e* Dstr!ct!ralD ,iew of the re"!irements stated abo,e and how the$ might be satisfied in the s$stem.

1#$ %se Case ,odel

Shock Force Software Team

9

1#' !equence Dia rams

Shock Force Software Team

10

9. *pdated S hedule
The ! dated >/(T/<A'TT chart is attached at the end of the doc!ment

1:. *pdated Budget
An ! dated b!dget is attached at the end of this doc!ment

11. 0ppendi es
$$#$ Definitions6 Acronyms6 A++reviations
&DA'()0 &ntellect!al Disabilities Agenc$ of the 'ew (i,er )alle$

Shock Force Software Team

11

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close