0% found this document useful (0 votes)
8 views18 pages

Shree. SE 1

The document discusses software development, defining software as a set of instructions that enable users to perform specific tasks. It outlines the principles of software engineering, including design, development, testing, and maintenance, emphasizing the importance of usability, functionality, and validation. Additionally, it covers the software development lifecycle and the need for proper requirements specification and management throughout the process.

Uploaded by

gibok28819
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)
8 views18 pages

Shree. SE 1

The document discusses software development, defining software as a set of instructions that enable users to perform specific tasks. It outlines the principles of software engineering, including design, development, testing, and maintenance, emphasizing the importance of usability, functionality, and validation. Additionally, it covers the software development lifecycle and the need for proper requirements specification and management throughout the process.

Uploaded by

gibok28819
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/ 18

slscute

Pofessional Softave development


What IS SoftuJove 3
hat isSafture enqineeyin S
INhat ave athibuctes of Softare c
lhat ae
fundamentalativites of Softuwore
Specitication,development Valilation , eVolution
Softave
6oftuare is Set of propram CSequence of inshuchion) that allaus
the usexs to perfum cell-defined functioni or Some
Specified task.
Software is Yesponsible foY divectin all Compuctex relatd device
and insuc ting them yeqertding whct ond hoo task is to
be perfomed.

Sofre fogineeving
Softusareienqineevin is the bvach of. CamputeScience
that deals coith the desiqn,devela pment testin and maintain
anceof opplication .

Saftwareengineevin s aply engineeing principles ancd


knocaledge of proramnming languageurta build.seftdare
Solutian for each end users.
2.
3
desighed.a
shichitis
sfox
-Tt impeved
-A coY
Perfovmancei
Can Goodu6aqesheuld
navigation. SofharetheNequtYements.
Usability
Gioad SoftJare
FunctionalityGod designed vepaivedthaintabiAthibudes
Gioed,
liSoftierei
ty of
The The CasyTtSoftwoe Sofhat
handle intexface Includes maintainble.
Satisfiesall
SetuaveYun
large ta is
is .accomodlate
is
amounts.
intuitive..Should user- useful funcional Softusare maintain
tiendly if the
pravide able
eHiciently
and usex heed trtre
of it hos
if
data Can of
cleaxUIusey perfarns t good.
anelis it
users Changes Con
oxtrotfic easily
inshucthions documenttion
be
and
quickioynd intexface) inteYact easily
the
allthe easily
and cilent's funchie modRed
it and cuith
3Softwore
Validationi 2Softuere
Development:.
-Testing
System
intented implemented.to opesatians and must produced -
Component Softubare Avchitecture
Com The beSystem
A The equivedSoftave Specifioation
Sofhoere
Wheve Fundamental
Softare Softoe
ponents desiqn implementution dethining
meets to Specification CustomeYs
processes Validation and fov and.Constraints
Shocs vequivment
System yequrment
testing design.design desiqn deve cohat Acivities
expectaction pro
thect cess ond
, lopmerrt.functional
ond
System ave System oY ahstact Ds isinta of enqineersdefines
mare, descviption mansgament of
i design, activities Saftware identifying is on
of execurtable
Confivms
testingCustomeY and defined ts
Softuare
Vexitication
Specification, the apeahion.
AlgorithmaYeic development of
, Constraints
nen-tunctional isCondition
Acceptance. to systam
buying aYchitectuve process
its. and the
Specificatian design.
interfacedlesign.
theValicdation thraugh is ta
testing Softtsave
System. pracess on the of Jhich
of vequivments
design System's
understonding
(v) Softbare System that
and of
thct is
Converting
of is
Systea. ta
ae be
3. 2

Competence.
property
ayeeandafTntellectual
property
Your SuchRqhtsi
as initially,
agement
Nou ou
We Competencei oYYou fidenConFolloLainqbehaViouYavehat way we Eyolution
Yela SofhuareSoftare
Rngineig
Softe Main Softuare
Should Shauld ShauldShauld clientshauld bilityandflexibility
+here shauld
objec+of then
aJae not iYYespective ioekey enqineering
Caveful net has naxrmally ore usex evoltionaY
KnauJinq avea Yepeatly
Copprights.
cilent ispotertand of
mis been Skilland
ensure vepresernt Signed vepect slsevalutioo
Jocal psit where ta
accept of poc
maistain kthics updating
that cwork of maintenance
cted las whethex the la. byab1lity
Standardof ess
System
your odevelaping
the qovexing to h.
thot level Sliethicsieni oYe ctox
llectual nato
yaueof behave istermn
acceptable ensurinsVaniaus
the isoutside of
foymal vene
use Com emplayee in
dishe Sefh used
of petence. the
propej in
in your
2
.Ditfent an

stotement Roles: on, different


As IFallacaing softoave
pyocess A veleased -lo Computer You
vity Such
boducts-a Softo Computex
as lhichave cell Softare Softoave
products Softuave emplayeés
Bocess exemly
machine) Shauld
alhich
praject asactivities
prodlucts
process
andavaila fox
praject
that these misuse use
eflect e
thSeviaus Misuse
processlactiities.L
outcomeof o design, technical
aYe activty accptance. vanges
ohichmanagex, involve Set
te yesponsibi issue
Softuae merqed of
pe.and cwere
bility fam Skill
before in in Yelative
Configuratian. lrty lalve ike
Softuenre velatively to
Validation, to Security
n.accovdling ot pracess misuge
and te activity
people diffevent
people
aftx process., preject.
managerintalve descniptian System rival
othe
Softugre
a that
process
oFCompuctex.
CHR),in.the Softoore leadof County Cgame.
playing pesple dascHate
depend Cwakfox
e
progammerpracess Volulatian.
to upon. Speciticati oY
the Virues
uniachieves_of
detintion
t epre SoThe Requvivement
Definition
Watefal
ThisModel::diffet ModellSaftsare
laterfall
testing sent qeneric
State
System them madel
modelare Degign
Slo
tundamentol
teqyatianSpecification System
as Fis A
are
Safhoare
Sepaate
pocess
phase
evalvedtoy hat Tmplememtactio
and testingunit
activiy
Valiatian descriphan
mentaton
System lfecele
Sofhsave
of
testing
SyGtem
integrection
evalutian
Specification of
tesing Develsprnerck
SaftJae
gequnnLike develapment
and Maintaince Date
Opeection
Validuin pretess (SLC
pracess
.Operation 3.
fe
invalve The tested os
individual
pragYam
The Implementation System
Softwae The
oY development
Requrivementactivies. oY
Tntegration Unit
pragram Duing System
pecificaticen.
Syskm(fnd by I+ The This
le Sucessfuly.
meet Softare ConsuItatian Softuave
System SyStem,
Yeguived principle
cting testing the model
t. this ahsorpion and
oY ahbutes
developed and public designSystemdesiqn
Softoae
and involves
program phase System illustte
phaseslifecyele
ond Specificackion
wHh
s
erarsMaintaince
Systemto System and must
pvocess
the unit achitecte.
and unit. design Gevvices,
fo
System of
cThich Verifyin identihy
there development. CFig.
testingi
pragram
Lunit o testinq'
Softwave Constrains) atefall
e install : ensure allacate ond A)
cere use.
Canshains
g to that
yelatianship. and
de this
nat pt Saftware the
They finationi
each design descniption theme madel molelknsujn
there inta
ta vequriment are and
s pra Integated unt directy
isCaver vealised Constria
aintainces
chical
use. yeiments fundamental them qoals
meets
ns Yeflect as
as as to defined ave
es Cmenged)and H ideal and LJatertau
eodie
Stoge of Specificctiss. a established
hre set Sene io tundamental
Softiave hardae
m been of detail
as
Description
outline

Tocrementol
Modelia

ConCument
Activities
Fig:2
Fig: Developmert
Validation Specification

intevmediteVexsion
Version
FinalVexsian Thtial

Poce Dete
xKeuse.
Softuave
Orientcd
i i) Lncvement
) Yelatively
dhat kach
tiesThremental
e isMore Cost changed Inoemerrtal
Model Requivement
t Version
that System
Design
Reuse
Jth Spen
easier is
Tapid of
dequied
nes early is ax
accumulated have
to need
incvement SoftJore
elivery tunctionality Stage
qet thyee
ifthe ta
deve Componets
and customex changes benetits develapiment Customnex Development Analysis
of
lopmenti
pment Cumet the
teedback
Can
System
Can
be to Fig2.
inczement
added evaluated
See
is on jncopevocte
if |Requivement
Modification
ofraredevelapment System
Validctio
to the
hasbeen
incremerrt System
delivers
to af dassate
stamers cark. tunctionali
at
*Relse
Softbove
Oviented
2Requiment
aVailable
informationabout
design Design Modificction i Component as
is addedaYe Disodvaotages
System 3.
discovexed. Component Analysisi1.phasesTheAqeneval hSyetem The
thisStageequiments
During DuringarE Given
an
OY shausn process
is
thComponents. Yequivement
to
They implement process
Fi z ShuctuYe
existinqphase 1s
Inoemental
nat
aYe
the Components model tends
Speciication. isible.
tame them thot euse
framwork to
wark madified that Specification based deqode Mode
a
Seach L
is of havebeen
to develsprment nes
System
yeuse. analysiss
Yeflect is incYemets
made Date
JSte
lceate
Date
Poge

4. Develop ment and Tnteqvationi.


Systemdevelap futhey nes ompenets aded and
indicated for nex+ process ocivity

5. Validation.

Availabe Components sith madification Can be tested inpust


and output ealuetion.

Process Aetvities
Sofhware Specification

Feasibility Requivement Requiement


Study Elecittion j Specification
Analysis
Requiremat
Validation

Feasibility System USer Sy stem


Report Models Yequiremert|

Requnimert
Documents
Aychitecture Trfaration
Systen Acitecte Platten
Design Tmplemertian
Desinand

Database
Specificatian
Database
Desiqn Thterface
Design Requivement
Speeification

Thterfce
Spen

'Components
Design Desciption Data
panents
Com
Spen
Design
IIP
Designolp Actiriies
Design
Date
Page

study relatively quic k actions ore made coth


When teasibility
detailed anaksis.
prposedSystem cillbe
The Shudy Consider Jhether the
tom the business point of VieD arnd t Can be develaped
on

profit and loss isSues.

Requiemert Elicitation. ond Araysis


This is the prrcessof deiving System equiremertt though
obseNation of existing System.
Discussion like poterrial usex, talk analysis, differert object
idesficaction, System modelsand prrto-type a

Requiment Spacificationi - a a a g
Transcating
Requiment Specification is the activity the infromation
gathered during the analysisactivity into a docurment that
deines Set of user ond System Yequiement.

Useryequivementsiave abstact Gtocemert of Syskem


Teguirements foy the Customexand end useriof the System.

Requiremat Validtioni
This achvity checks the yequmement tox xeality, Consistancy
Compledeness., diffexent testing achivity
Ewovs in the gequirement documentation is inevatably
discovexed and then modky to Corect vequixemets.
Dete
Poge

Junier Manager

Praject Monger team leader


Web tech

Recorder/
Documentation Desinger Testing Engy
Fi 2. is an abshoct madeliot Slw development
process.
A qeneyal model desiqn pocess i as Shounun Fig
This madel is depend on the equiYement documentation
of Slw Specification.
Fiq ShoLDS tou acthiviteso

1. Axchitecture Designi
OVexall Shuchure of Sy stemcJk mocules,elation Ship
OY
principle.Components.
2Toterface Design'
Jlhen yos define intetace betn ystem Compohents

3.Component Designi
Eoch System Companents anddesign hos t is apevated.
AData base Designi- i
Desin System data stucture and hous these aeto b
mequiventd in database
Sofhare Validationi

Compsnentl System Acceptance


Development Tsting Tesing
Testng

Fig Shos three step testing processes in cJhich sjstkm Componerct


ave tested the inteqvted system

Al Systems are tested with Customey dacta.


The Stoges in the testing processes.
LCompanent testing l Developmarck testiaq:
Each Componerct is testd independetly oithat by the peoplein
develapment Systm.
Components may be simple entities, ohjects Iike classes,
unctons aY any untime entity
2. SystemTesting i

System omponents are inteavcted to Cvte


The System testing shich Concevn to functoral and
non -functional equrement.
Dete

3. Acceptance Testing'
Acceptance testingdepend onon useY, CustomeY needs
the System pertomance ar the bath

It is divided ioto ,P,I testinq chere Custame


organizatiònal are ConSidevedtoy operahonal user of
System.
Softare kvalution Tncremetol Model
Pro pose Systm
Define System Acess
exiting SyStem
Medif
Requivement Changes, System

Existing
System
Nes
Sstem

Change adds to the Cost of sls developrment because


Usualls means thc derkthet has been Campleted be
Yeaden again his Called evalction..

Fallaaing ore the isues to YeduceCastof

1- Change
Where the Slo pracess include octivties that Can anticipa
poasilik changebefore Sigaificant e-ldark is Yeguvied.
2.Change Tolexance
Where the process s desingedsa that Change Can be
accumudated at relative ly los Cos+
The tlexibility of Sla System is one of main Yeasan far Sls is
being inCavpevated in lage and.complex System.

X Rational Unified Bocess ' (RUP)


RUP is an eXample of mochen process model.

Tt identify four discvete phase in the. SaftJare Bocess.

RUP moYe Closely Ye lated to buginess idea


YatheY than technical issue.
4 Tncephion phase:
The qoals inception phase estabilish busniess for the System
Jhexe one Shauld ldentify all external entities that cwe
Ibtexact cwth system defination these inhractan Use this
intonmation acesses the Coti bustion System made busness
2. klabaYationi
The qoal of ela boraction ave to develop understand ing
problemdomain, estabilish and axchitectural fameJork
System,
xÍsk.
deelap the praject plan idenif the key prject

3. Conshuction:
The Conshuchion phase invalve Software proqamminA
Softsare testing part of System develop in paralleland
inteayated develap phase.
Dote

4.ransitionis
The final phase RUR isCon(emtre csith
the System develapment Commuoity to the user
Community and making it cwork in veal envinment.
Copig coith Change

You might also like