SoItware Requirements SpeciIication

!AvA Lul1C8

1.0. Introduction
1.1. Purposed system
1he purpose of Lhls documenL ls Lo presenL a deLalled descrlpLlon of Lhe
[ava edlLor lL wlll explaln Lhe purpose and feaLures of Lhe edlLor Lhe lnLerfaces of
Lhe edlLor whaL Lhe edlLor wlll do Lhe consLralnLs under whlch lL musL operaLe
and how Lhe edlLor wlll reacL wlLh operaLors 1hls documenL ls lnLended for boLh
Lhe user and Lhe developers of Lhe sysLem and wlll be proposed Lo Lhe 8eglonal
PlsLorlcal SocleLy for lLs approval
1.2. Scope of Project
1hls sofLware sysLem wlll be a [ava edlLor for a local edlLor of a
reglonal hlsLorlcal socleLy 1hls edlLor wlll be deslgned Lo maxlmlze Lhe
edlLor's producLlvlLy by provldlng Lools Lo asslsL ln enhance Lhe arLlcle
revlew and worklng process whlch would oLherwlse have Lo be
performed manually 8y maxlmlzlng Lhe edlLor's work efflclency and
producLlon Lhe edlLor wlll meeL Lhe edlLor's needs whlle remalnlng easy
Lo undersLand and use
More speclflcally Lhls edlLor ls deslgned Lo allow an edlLor Lo
manage and communlcaLe wlLh a group of revlewers and deslgners
who work for [ava sofLware
1.3. References
lLLL l 5tJ 8J01998 l kecommeoJeJ ltoctlce fot 5oftwote
kepoltemeots 5peclflcotloos lLLL CompuLer SocleLy 1998

14 MCDULLS
Module1 AppllcaLlon uevelopmenL
Module2 leaLure LxLracLlon (Analyzlng connecLlon servlces uslng log
reporL)
Module3 CeneraLlon of [ava code
Module4 error deLecLlon
Module3 ouLpuL generaLlon
PA8uWA8L SLClllCA1lCn
rocessor lnLel rocessor lv onwards
8AM 312 M8
Pard dlsk 180 C8
Cu drlve x
lloppy drlve 144 M8
MonlLor 14' SmarLen color
keyboard 101 mercury keyboard
Mouse LoglLech mouse

SCI1WAkL SLCIIICA1ICN

CperaLlng SysLem Wlndows x/vlsLa/7/8
Language used !2sdk160

lLASl8lLl1? S1uu?
easibility study is the high level capsule version oI the entire
requirement analysis process. The objective oI Ieasibility study is to
determine whether the propose oI the system can be developed with
available resources.
There are three steps to be Iollowed in determining the Ieasibility oI the
proposed system.
Technical easibility
perational easibility
conomic easibility

Technical Feasibility:
1he proposed sysLem needs Lhe daLa ln an efflclenL manner
le lL needs proLecLlon of daLa and auLhorlzed access Lo daLa 1hls ls
done when we use Lhe sofLware whlch supporLs console orlenLed
meLhodology and daLabase meLhodology 1herefore
Lechnlcal feaslblllLy deLermlnes wheLher Lhe organlzaLlon has Lhe
Lechnology and skllls necessary Lo carry ouL Lhe pro[ecL and how Lhls ls
obLalned 1he sysLem ls Lechnlcally feaslble on Lhe followlng grounds
O All necessary Lechnology ls avallable Lhose are requlred Lo develop
Lhe sysLem
O 1he exlsLlng resource ls capable and can hold all Lhe necessary daLa
ln an efflclenL way
O 1he sysLem ls Loo flexlble and can be expanded furLher
O 1he sysLem can glve guaranLees of accuracy ease of use rellablllLy
and daLa securlLy
O 1he sysLem can glve lnsLanL responses
1he followlng are Lhe acLlvlLles LhaL are under Laken durlng Lhls sLudy
Deve|opment k|sks
ueLermlnlng wheLher Lhe sysLem can be deslgned so LhaL Lhe
necessary funcLlon and performance are achleved wlLhln Lhe
consLralnLs uncovered durlng Lhe analysls
kesource ava||ab|||ty
lL speclfles wheLher Lhe hardware and sofLware resources
necessary Lo develop Lhe sysLem are avallable !ava ls very sulLable Lo
accompllsh Lhe Lask as [ava ls a fronL end Lool 1he organlzaLlon has
boughL Lhe requlred hardware and sofLware Lhese efforLs from Lhe
organlzaLlon made Lhe proposed sysLem Lechnlcally feaslble

1echno|ogy
WeaLher Lhe relevanL Lechnology progressed Lo such a sLaLe LhaL
lL could supporL Lhe sysLem
So we can conclude LhaL Lhe pro[ecL ls Lechnlcally feaslble

Economic Feasibility:

Lconomlc feaslblllLy ls an evaluaLlon of developmenL cosL
welghed agalnsL Lhe ulLlmaLe lncome or beneflL from Lhe developed
sysLem or producL 1hls lncludes Lhe evaluaLlon of all lncremenLal cosLs
and beneflLs expecLed lf proposed sysLem ls lmplemenLed CosLs
beneflL analysls whlch ls Lo be performed durlng economlc feaslblllLy
dellneaLes cosLs for pro[ecL developmenL and welghs Lhem agalnsL
beneflLs of Lhe sysLem lf beneflLs ouLwelgh cosLs Lhen Lhe declslon ls
made Lo deslgn and lmplemenL Lhe sysLem CLherwlse furLher
[usLlflcaLlons or alLeraLlons ln Lhe proposed sysLem wlll have Lo be
made lf lL ls Lo have a chance of belng acceded Lo 1hls ls an ongolng
efforL LhaL lmproves ln accuracy aL each phase of Lhe sysLem llfe cycle

Cperat|ona| Ieas|b|||ty
perational Ieasibility determines whether the proposed
system satisIies the user objectives and can be Iitted in to current
operations oI the organization.

kCILC1 LANNING

lL was declded Lo use good SofLware englneerlng prlnclpals ln Lhe
developmenL of Lhe sysLem almlng Lo expand Lhelr operaLlons ln Lhe
near fuLure So Lhe followlng ro[ecL lan was drawn up

1 1he Ana|ysts w||| |nteract w|th the current manua| system users to
get the kequ|rements As a part of th|s the kequ|rements Spec|f|cat|on
Document w||| be created
. The requirements SpeciIications document will contain the Analysis
& Design oI the system.
3 1he Ana|ys|s Des|gn Imp|ementat|on test|ng of the System w|||
be fo||owed to produce an |ncrementa| cyc|e wh|ch w||| de||ver
m||estones ||ke the kequ|rements Spec|f|cat|on Document etc at the
end of each of the |terat|ons hases or cyc|es
4 1he Arch|tecture 1echno|og|es w||| be dec|ded as a part of the
Ana|ys|s of the requ|rements
3 Cnce the Des|gn |s ready the Imp|ementat|on 1est|ng strategy of
the system w||| commence Lach w||| be |ndependent of the other 1he
|mp|ementat|on of the system |tse|f w||| be broken down |nto sub
systems fo||ow|ng the Software Lng|neer|ng pr|nc|p|es for the
deve|opment of robust software
6 Cnce the |mp|ementat|on |s ready the System test|ng w||| take
p|ace If the system |s [udged to be stab|e then Acceptance test|ng by
the Users w||| take p|ace once the Users are sat|sf|ed the System
w||| be ro||ed out to the Users they w||| be tra|ned on how to use |t
for an |n|t|a| per|od
The Iollowing chapters contain an account oI how the Technology &
architecture Ior the system were chosen.
kCILC1 SCnLDULING
1o develop Lhls pro[ecL l have follows Lhe followlng schedule
Lo fulflll pro[ecL requlremenL lncludlng documenLaLlon wlLh sLrong
LesLlng
Analysls 10 days
ueslgn 23 days
Codlng 30 uays
1esLlng 10 days
uocumenLaLlon 13 days
1herefore l have Laken 3 monLhs Lo develop my successful pro[ecL

6IUNC1ICNAL kLUIkLMLN1S
1he funcLlonal requlremenL of Lhe sysLem deflnes a funcLlon of
sofLware sysLem or lLs componenLs A funcLlon ls descrlbed as seL of
lnpuLs behavlor of a sysLem and ouLpuL
O 1lmellne should noL be dlsLurbed
O lasL and efflclenL
O CompuLaLlonally slmple

63NCN IUNC1ICNAL kLUIkLMLN1S
A nonfuncLlonal requlremenL ln sofLware englneerlng presenLs
sysLemaLlc and pragmaLlc approach Lo 'bulldlng quallLy lnLo sofLware
sysLems' SysLem musL exhlblL sofLware quallLy aLLrlbuLes such as
accuracy performance securlLy and modlflablllLy
O 8esponse Llme 1hls can generaLe deslred ouLpuL
O 1he PluS sysLem provldes user frlendly Cul (Craphlcal user
lnLerface)
O Memory usage lL ls LoLal amounL of memory used by Lhe
sysLem