0% found this document useful (0 votes)
18 views

Se Lab Practical

1. The document introduces software engineering processes like feasibility studies, requirements analysis, design, coding, unit testing, integration, and system testing. 2. It describes the waterfall model as a basic software development lifecycle model that divides the process into sequential phases without overlap. 3. Agile methods like Scrum, Crystal, and DSDM are also introduced as alternatives that focus on frequent delivery and response to change.

Uploaded by

zeel 6819
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views

Se Lab Practical

1. The document introduces software engineering processes like feasibility studies, requirements analysis, design, coding, unit testing, integration, and system testing. 2. It describes the waterfall model as a basic software development lifecycle model that divides the process into sequential phases without overlap. 3. Agile methods like Scrum, Crystal, and DSDM are also introduced as alternatives that focus on frequent delivery and response to change.

Uploaded by

zeel 6819
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 22

(4340702)

atroduction to software engineering

4 Testiag lauclity SSUe


5.
Deple yent
Red bacR ho Pheuse you ust
-pequment, gutheotng - Jn bsme55
ezplen,
EURments you shauld
delne the
Cwhte techniclL cmd eo romic Feasi bil ity.
idenhe
RIgn Hhe nequiotment' ahen yoy heve
The Pooject wct cith stackh old eos to define
diugrn
Eruigemets Yo Ccm uSe the usea floas
O he high lael, 1ML Aie ocn to shoco Ahe c
F nes featuoes cmd shou hbw it ill aeply to yUa
estng 5ystem.
3.
Constoachon, liteton i ahern the tem efines
the eu loernents the cacot begims qesfes md
devetees stot ccat2ia on. Heir pzoject cohich amt
to dPloy a cactaing oduc te, Pocduct will undeos

gimple minim fnctonay


AsarxYe
IesHng :- In this Þhese He quality
t
Bem ecmies te Pc ductp m e
(ocs k te bg
phuse he tecm 15e
5 eploynent In tig
Pduct fcg the
E\eushf te Pacuc te lcol
i- AeS
6 Fedbucle fdhucà Jn thiS te. ttm ociVeS, h the
tee rdeL cmd a e
feedlcl? art
10|4e Ceedhus
Introductson to software engincering (4 344)7(0Z)
Ter he oYn
t0 romplet e he grint or cycto

eXtro ne Progqnm fng CxP ) Te


meth od ol ogy ?1 wo when customors
his +yee o or ohon hoy
changíng domqndi or roguir orn onts
aboyt +he systems perf rmane
Kystql methocd
rhere 4Te three concepts of thíc
activi+iec are i nvolred n this phaso
Chqrt ering Muiti 4eam pesfominy Fosibifty
Such ur making 4 development
Anqlyss, developina plqms etc
2. Cyic delivgry ynde this, too more c ycles
there
he eleuse plqn
A. Team updates
to the uiesi
B. Fntegryted prduct deliye
Accordisa to the wer envísonment , this phue
.WTap 4p- deplyment
pes furmí deploymen , past
Devel opment Metho CDs pM) -
Oynanjc
development otytegy for
DSOM is q rupid applicutio dictnbyto
developm ent d giver qn agile Tefoject
thi ser
feqtyrr oF
otructyse The essenttal
must be actively Onnect ed 4nd te ms
the síght to m4lce decisionr. fhe technique yecl in ni

Time Bo ving
2. Mos COw Pyles
8. Protot yping
he DsoM roject contuinr sevn stuye
5. Design un builel iy3n
2 Feuaibility tudy 6. mplemen tutin
8. Businerr stuey . fos Pojer
4, functiun al Mode Heytjon
11
fven Development CFpo):
thà methed Foeue on Defynfyy nd Budig nhres in
Cotqst to the Smuvt metod on detibe c the snl)
stepr 6F *he we thut shoutol be obtuineel tepavtoly

Develop mont
he prineiele
development methudoloyy Folleor euter
methocl indi he
juot in ime Produejon'. rhe lean
educing
devel opment nndseven
Inereqsing pee of soptoave yomje phded
Leqn development eun be s
3. ctimineting veute
Amplifing lenmg
S. Defeo commitment
t . Eyy elivwry
he te m
S
cmpoceg
Building Jnteg oit y
whole
?. Optnile the
when to yse he Hgile Moctel
Feguent chqngur re qujrec
whe
pe' enee tesm
when q highiy qurifiec and
av i luble
when
is e dy to hve mecting
all the time

when eojtt s e is mal}

Advan tager Cos) of Mgile


Freyent Peljveg

Fue
Introduction to sottware engineering (4340702)
9. Crficient design cmd fulEilk the businorr meqnirem9
4. Anytíme chunger re cceptuble
. It educer totul development time

Dis ad v4ntug er Ccons) of Agile Mode| .


Dye to the shortyye o 6 Forma) docymety, t (royter
confujon qcl (Tuefal deisionr tukern thruuyhout
phuser ca) be minjstpreted at qny t frne bt
dirferent teym membens
Due to Hhe luclc 6f puper ocym entfon 0nce the po Dje utt
omplete 4nd the eveloperr 4llo te to motheg project
be come
muiten 4mce of the Finished project
dirficulty.

WATER FAL MobE


clessicul Wyterfyl| model
The clusial oqterful| model jr the buuic software
development Iífe cycle model
. It i very
smple byt ideqistjc
tyrlier thir model wo very populyr byt noodayr if
is not wwed,
soffwaro
Byt it is rery jmpostnt becqw e ull the other
the clusiul
development life cycle modelr 4re buued on
outesful) mudel.
The usicul outerfall model devides the ice ytle into
q setr of phuer
his model consider thut 0ne phwe cun be styrtod
actex 4hir comple Fion o6 4he previbur phse

Thys the develu pmrent proerr cun be consdere y


sequenfi4l How in the wjat erfall Here the phuerdo
not orexlup with ech other
91:
FEnsieraitY STUDY

PEQUIEEMENT A NALYsr

DESIGN

CODNG RND NIT TESTING


LNIEoQATIONANp syeTEM
TCSTING
MAIN TENACE

Feusibitity ctudy
"The main goql of thir phsie i to detY mine whetheY
it uould be fingncially nd techni cully fuible to develog
+he so Ftoae
he Fea cibility stud involave understandiny the
problem qnd then determine the vazítur fousible stat
to ore th e problem
These Jiferent identified solutjonr re qmalyed bese
on theiY bene fitr und dru ub atie4
Requirementr nalyir specificatton- The ain oc
the seyuire ment umalyir and speciFica tion pheie s tu
undesstand 4he eyct Te qurement of the custmer qm
docun ent +hern
difer ent uctivitie
propery.Thir phuse Coniirtr of two
Peguirement guthering md qnalyi- tintty at hc
requirenentr egrrdng
+hecustomer 4md ton the gatheTe
anulg2ed. The goa of the unatyi purtnauirement
is to remve
e
Intrdcthn to soXuare engineenng (4340702)
fequiement Speiticdíon' hee |nly1el ro9iromon
CCqye n the sRI)mto 4 ocument
Constuet between the (ustom es ndl
An future
tho develment +eqm nd c ustomer, he developerr
end t
he (ustom
dieute betuoen
document
Cen be cet led by emininy the
The gocql of 4his phuse ir toenvert the
Desg)
4cquired in the Sns ihto 4 formyt tht
euiYmentT Softoare
Cun be codecd i 4
Pregmmig lungueye
Pocyment use fo ocum ent
Desiym

teting': Jhthe co ding rhwe softar


koding and unit yore code ing qm Suituble
tgnslate into
eign i im of the ynit teting
prog mmis qngu 49e.7he is uorjkíny
e qch module
phuse N to eck whether
Or not

(ntergatío <nd systcm testing -lntegation of diferent


malules aTe 4nder taen sOon ates thoy have been code
ir comil
CLnd unit tested. Integution of vanu module
Out ncrementqlly ver qnmber of steps. p4ing o qch
ad dec
ntegation step pTeViously plamnecl mudules are
partially inteoqte ystem md the reetent
system t esteal,

System toating confsts of hree diferont vineds oR tuty


activijo escbed balow'.
Aleha testing: Aiphy tasl ny is Ahe yoten teutíy pefoml
by the derelopm ent toqm
" Bet1 ostg': Bets toting is the sytem teatiypma
b4 e4fendly et of customevs,
" Acceptamce t astiy Ates the sof}cwe hr bee) delio
he customeY peromecd
pert accepmee t osting to deteYn inc
whethe to q cc ept +he elirered sotwaTe,
Introduction to sofware engineering (4 l40702)
Maintunc Main t nemee'- Maintunon re is the nost
ce
importmt maintunnce i oy of the total efo st pent
Spent on there re basially 4hee
Softwure.
to develop q ful

Maintunen (e thio 4ee of meínt4me is


C6Yective

during +he pyoduct devel opment phse, naintanam ee


Majntunancel- Thist e e oF
PeTFeve c+fonuliHes ef the iytem
+he Fun
c n e out to Qnhamee Tequef.
bqed on the customex' Adapive maintunqe in thoyte
Ad4pËve Mqintangn ce:
+he Softoyre to w0TK
on q now
Tequirecl fo parting
nýison ment ueh w oo<n
oK fn q ne
eith 4 new operuting yste
tomputes pl«t fosn
l Wattqfull Model model FoY
Advantugerr toatefull mocel 's un 'deali'sticcqn be
of clasjca
ít
imple,sodenelopment
‘he clessfea |
fe
iS ery
ent,$4 ptheYsoftcwqre
Sofoqre developm fos
consjdere he basic unclesstund,
ewy to
Cyele models.
very simple nd 's one at q time.
mudel iT procesred
This model qre eleqrly definecl.
phaser in this
the model ir wneevstyno milestoneJ
in well-
E4ch stge rry
eleq Qnd
rey we| docum entecl,
hr
This modelcLC+[on qre projech
m meuit smqlley projcth qnd
procerr oell for nclorstood,
cDosk
This model
nequiyementr 4e
uwel|
cohore WatexFall Moe|
oF clucseul from v biu short
Drqwbycks nodel suftre projects but
clusjcul
wuterfal| 4)e H in re al modelr
cam't (ifecyele
The busically we developmentwutesftl model, Boloc
commjng. soFfoare clssjcal
other
basec on the ofthi mole!
Cwhich qrenujos aluwbuC KJ waterfall model
some he
rlusjul
fo tother pese
Pth: In om one phuye
feedbucic sofBw4re
" NO therefore.
phuse,eor
evylytËon of qn
(osrechjan
developeys,4 ymechunfom for
mitecd by|mcoYPos qte emy
com
t does not

9/
Introduetion to software engineering (4340702)
pifiylt to qccom modute eh4nge roqueas qhír model
essymes that all the (ustomer nequirem ents e y be
of tho
eompletely end correcty aefined at the boginning
projet, but actuay eustumeris euiremonty teeipr on
chunging
ehamge rejuett afr the mequirement! pecifi<atjun phse
iS comglete.
of phwe, rhis model reco mmendr thyt 4
"Noe kugeing
new phuue cun oturt only ftts the
eompletun of 4ho
prerio phuse. yt i n neal rojets, +hir can't be meiin.
cost, physes
ined. To in Yeqse e rfitegey umd reduce
myy overlp.
In crementa] Mode| Inement #n
Commymjcqt(ov)

tuYes
fwue
4l|t1 plunn/ng
N Modeling camulys, designs) Deliey of 4ingemen
ontyuctíoy (codo, test )
Y Depleymentcdeliver, f ced butk
Inqem ent tt 2

pelivey of inmomont

Delivery uf 1 in rement

Projoct eajendgy time


9
wht i 4n neemenf indo

verjuq vnodat,

Jncemetl phuce
Retremea Anntyeí6

ponign
tude

Tosl
dowg (ntu
Rquirements of softoyre 4re irst broken
tonstrurtod
evel modutey thut cun be fnrementally
and aelivered, For the nezt inrm
nude sust
At 4my me, +ho pl4 na is
tongr4erm pbyA,
md mot for 4ny ind o
to vnodi the venfun us perthe need
Therefoye it is eusier
of the (ustomer, tore
e4m Fiwt 4ndorta ker to develup
Developmont
" The
yttm,
feutyres df he
yr fully devetoppe,4hen theie
One 4 he core Feytyre
inYouSe levels o- eapabiliher b adding
qse efino to sy(cerive vemjoni,
new functin ir wing
uuall develope
Euch inrementul versíon irof developnnt
inieoutive w4tex fatl model
vesion or the soFto4re jf onstryct oc
Ar qch cuceeoive feed back. of he cutumer ir tobe
tk
nd delivesel, mow the then incorpertteq intoH
weT e ta tcen ueTe
nd these
9|
ue ]yere)entul Molel ?
when to cloqrly ndetool
systeng qre
Requiement f the
"
when sowrt engineesiny
invalv e
eatyer 4ne goalr tre
when hish- isk lanshtiy dowlupnent cehedule
fivut
" A prje t has n9uireme
pviititel
derelop
yuy cun r e ucl,
NeQtechnoluyie

Nodel
Advantuger of Jnremental el
ecogni
RqUy u be
end debug
- cuey to tut
dujy itr
More Flexible hunlle
mqn4e i k beequye
Simple to
îalion, fntionslity ealy,
yetr
imfovtant
The clent
of fhemental Model
Disqdvqntsges
Need for gool elummy

modyle Îyteruter ane meedet


well de finel emeatatly
etd bui it M
to breqe it down lenion of the
-1 In oYder cleqY
tomplete 4nd
e
it neeclect
whole syoten.

9
IntnxttAH sotuarr engineering (4340 N2}
Inrementl Model ?
Q1- when tu wse. the
oftn. fncemen Modyles u e wed when
w' Mout

Reguive ments qre elearly specifjed, undesst ocd und


" re941rements hove
Known up-Font tertqin

There r q requirement to releaJe the prodyt ea


t to he muMeet eqny,
O set
he eyuire| leil set oY
+eqm lacjer
Engiteei re qngvailable

based compaie devalop their own eroducts


poduet-
techmol ogies ee sed.
New re hvolved.
feutyres
Hish k oulc qra
development scheduley
long
" Prejecte have
Introduetion to sottwarc engneering (4340702)
6. Budger: Include the lotalestimated cost of the projcct and how much you have budgeted (Note that this
shouldn't be a line iten budget.) Use aproject budget terplate for a more detailed breakdown ot
budgeted and actual yojtexpenses.
Get feedback:Seek fexdtback trom key stakeholders, custoners, and anyone inmpacted by the project for
fevdback Ask them to explain the project in their own words to get a sense of how clearly you' ve
communicated the vision.

8 Peer Review:Have smeone else read the projetdescription In addition to spelling and grammatieal
errOrs, ask them to look for missing details that are significant to the project.
9. Revise: Update and revise the document as the project progresses. Treat the project description as a
living document.

H. Practical relatedQuiz.
1. Select and \Write your system (project) definition with brief introduction.
2. Write abstract, scope of thc sclected projcct and nced of your syste.

Aizline eSeNation System .


inntocductom :
Ihe meum pupose of this softwege is to
Smplhty the tedious tula. softuae is to ticeets
this sevice nlime is cL
foien
by Poovidig
dy Enviomet it alsG cumns ct InceAsimg
the efficiency emd oeducimg Ahe doas buclas of
Ecistng remual aieline eservcetion PooceS5,
thas main9 it mooe CoNeniet for the ustsme
to book the Aghts as whem the oequioe
This oject is suPPooted by a coell designed
cohich Alight imkosmation i integoted
togethes. A foiondhy UI
U1 is clbo Poovided so
het the seasches made by the ige give.
CrsRct aesalto by accessimog the infeomc tiom
stoed im the dctube1se .
14|
Introduction tu sofware cngineering (4340702)

Ams ;- Abotouct
Aolime Reeycttom Gytern ContinG the
detu ls cbatt Aiaht schedues cmd itts froe turiff,
te
Passengerg oGeavation cmd 4iclãet oecasds.
Am culkne imVemtoay onteumo ll Aigts
coth thei cNCLikuble Gecte. The. imven toy of
Cn aisline Sevice
Sevice i9 9eneul divided imto
moee Categogy of clcsses Ce.g.iast BusimesS
ooo Enomy dess) nd ech certegooy is oving
Sect up to es boolaigg, alon9 euth Paces
emd bool@im9 Condtions. nventoy dertu 15
isn Doted Gnd moim tuimed theugh. a scheduld
D(sta tiom Gystem avea stum derdized
ton teafces
Cne. of the cooe fmotioms of
Fhe ínventoy memagement of aialime ee
Naiom the imvemtoory contaol .
Conto l steeas hocw momy ects inventory
aae cvcu leble
foa the diffeet bookim classes by opeat
amd closing in diviucl boo kaing cles
fo ale. (m
nd.
n
Com bimatiom cwh the feoes
boo Rimg Conditioms stoEd in the froe
quoBe System the Poice. foa each. sod eat
dedeamimed
15|
intrduetion te sotwre engineering (4240702)

ScoPe

This Sotuae culocS the uses to


Vieau the. CNCulaibilts of Vaius on diffexn
detee detes and ime it gives them he
ticlaet, enfuie abort
Fac1lity to bool
4he total Cost malae onlime Fenpnonts
a Penticuleaeentton
emd modiy
intrsketh o ertare egeering t4 i47};
Practical No.3: Select relevand process model to define activities arnd related tasks set for assigned project
A. Objective: Software Process model gives graphical repreentaticon of systerm to be built
Modeiing contritutes to asucCEssful software orgarnization Modelirng is aproven and wel
accepted engineering technique.

B. Expected Program Outeomes(POs)


1 Basic and Discipline specifie knowledge: Apply knowledye of basic
mathematics, science and engineering fundamentals and engineering
specialization tosolve the engineering problerms

C. Expected skills to be developed based on competency


This practical is expected to develop the following skills for the industry identified
competency: 'Define the project title with bounded scope oftheproject."
1.Software Model Selection skills
2. Apply appropriate Software rmodel for the given probiem

D. Expected CourseOuteomeyCos)
Explaín fundamentals of Software Engineering

E. PracticalOutcome(Pro)
1. Recommend the reievarnit software solution for the given problern.
2. Select the relevant soft ware process model for the given problern statement with
justification.

F. Expected Affective domain Outcome(ADos)


1. Work 2s 2 lezder a team menber
2. Follow ethácal practice.

G. Prerequisíte Theory:
Howto elect the right software process model.
Selecting the right software prOcess model is a process in itself that the organization can implement
internally r consult for. There are sorme steps to get the right selection.
STEP 1: Leatn the about sofrware process model.
STEP 2: Assess the needs of Stakeholders
We must study the busines domain, stakeholders concerris and requirements, business priorities, our
technical capability and ability, and technology constraints to be abie to choose the nght SDLC
agairst their seiection critea
STEP 3: Define the criteria
Some of the selection criteria or arguments that you may use to select sottware process mxoiei are.
Is the software process rmodel suitable for the size of our tearn and their skills
s the sft ware process model suitable for the selected technology we use for implmentin

19
Itrouetion oeos engieerimg 43407921
Practicat relatedQQuiz.
I ldentify software process mode for
yor systemn and justify your selection of
particular process model

Ams OATERFALL oo LiNEAR SEQYENTAL MoDEL


ntestuims a deve lo Ament storte9y uhich has
Phases cmd 4he. duocion of each pheSeS deRCnds
On the
tyee. oC model mdeotlAen to sove
Pagtiau le
is rateofall Pooblenllneo
The model used fo 4hic, Poojet
he SEQUENTIAL model
So Awcãe simplest olkst coidely Sed model for
develo
Shuen ial model. Thepment is
straucSe
pf softeaewith cestuim model coatefell
has d
ot limes
phase SPeciHPooceSS
to the CG
developnent
mum cituy.t cmd ecch phuse i6
SeAuemttal appooach
that bogesses though.toSugstL aea Systemotic Softco,
Analysis
Desigm. developmert
co dimg
TestimTheg
fo coote begins by esta
Some Gubget Systern bilshimq
oequiaere
Goftcirmtensi
orOE. The of theseelemetS cmd
euratnent clloccettn
to the
The
ied equiment
md focused gathestn9 Paore s5
on the softee
21 |
AN ALySG
To undeostnd the matuf of the pooyrn, c5)
to be buált ,the &eve lopo must rndesstrrd the
functioms. 'mteofutes rnd pefosrne oith
the uiemerts given to me l deci ded t
muae Hhe imtoface lilae fon5 to
UGe t Gnteg the messtnt
(m toefates to vieas he md ctrer
domaim is decided as he
detelle, The inforrrto
tbles attrtbuteG of to
DESIaN
Thes poces_ tomslates equrtnerrtsito
EpoGentetiom of the sftoat that Corn be
cCCCSsed fo quea litry tefooe ce srot coding
The imteofaces coe desrmed im visUAL BASic
cnd coe tested for quu (ity emd Auisrnert
CoDINa
The design ís then tozmsluted to
ma chine Eadeb le fesn -The
(oding fo
the dota is to be sav ed in the detci
md hoait is eteieied. The dertougE is
is gerococ ted in ACEs
AcCES.

22
Intnvduction to soffware engineering (4340702)

Arline teser vton gyGtemsCARS) aae systeg thelt


low cAn cistine to sell their inventooy Csects).
It Contcuins infos meLtion on schedules cnd fus
H Con tuins cL dateibuge of eservHons
(ox Pas Senger name Te cosds) nd of tickets
isSUed Cif cpplicable ). ARss lre Putt of pAssehser

ARS evenually evo)ved nte the Computed


TE SEVations SHstem CcrS). A ComPtes es
ervuton system is uSed Aor the reserCHio
Uf u Putticylur wrline cnd inteyfceg wt
u glo bcll distribution system Caos)which
Suppos trvel ugencies cand other d's ti
bution GyeteA ca DS} chunne i mut
Ring eSeYvato ns Pos mogt nuJoY
airlines 1n u single System.

26|
(4 40702)
Introdution to sottware engineerg
requirements- Requirement gatheriny
Practical No.4: Gother appication specific generating a list of requirementa
Objecive: Requirements Gathering is the process of
A, stakeholders (customers, users, vendors,
(tunctional, system, technical, ete) from all the definition of what the project is
lornal
Tstat) that will beused as the basis for the

B.
Expeeted Program Outeomes(POs)
knowledye of basic
Basie and Discipline speeifle knowledge:Apply engineering specialization
mathematics, scienece andengineering fundomentals and
tosolve the enginecring problems.
well-defined enginecring problems using
2. Problem analysis: Identify and analyze
codified standard nnethods

Design solutions for well-defined technical


3. Design/ development of solutions components or processes to neet
problems and assist with the design of systems
specified needs

Experimentation and Testing:Apply modern


4. Engineering Tools, conduct standard tests and
engineering tools and appropriate technique to
1measurements

5. Project Management:Use
engineering management principles individually, as a
projects and effectively communicate about
team member or a leader to manage
well-defined engineering activities.
individual needs and engage in updating in
6. Life-long learning:Ability to analyze
the context of technological changes.
C. Expected skills to be developed based on competency: identified
the following skills for the industry
This practical is expected to develop
competency:
Requirement gathering.
1.Gather application specific requirements-
D.
Expected CourseOutcomes(Cos)
using SRS, DFD and object oriented UML
1. Prepare software analysis and design
diagrams.

E. PracticalOutcome(Pro)
1. Identify software requirement for the given problenm.

F. Expected Affective domain Outcome(ADos)


1. Work as a leader/ a team member
2. Follow ethical practice.

G. Prerequisite Theory:

Requirements are an essential part of any sottware project and the foundation on which all projects
should be buil. The gathering of and comp1ling of requirements for a software project is very much a
Intrteteon n efepte whgiseeting t4 34702 )
thest
Aitine ESeVaiion gyG+Cs(ARS) re 9ystmy
CAllow cAn caintine t0 Gel theix invenioy (seats)
I+ Con+ ciins infox metion on schedules and fud
Umd en Con tins c dtubuse cf rServHons
of ticKets
(0Y PS Senger name ecotds) and

> ARS evenually evolved into the Cornfuse


YeSErVutions s45+em (cRs). A CompeY YEs
ervuicn gystem is used for the reserrHi
Patticuur airline cind interfuces wt
Uf u
u globcl distribu#oy systtm (ao5) ushic
GuPPots t e l ugencies nd other dis t
butioy Gy4em (aos ch unne) in mu
Ring Teservtiong for megt mJoY
airline 1n u single Sysiem.

You might also like