Business information systems development

8/17/2019 Business information systems development

1/29

Slide 7.1

Bocij, Greasley and Hickie, Business Information Systems PowerPoints on the Web, 5th edition © Pearson Education Limited !15

Part Business information

systems development

"ha#ter 7

An introduction to acquiringand developing BIS


2/29

Slide 7.


Learning objectives

$ %&ter this lecture, you 'ill (e a(le to) * e+aluate the di&&erent alternati+es &or acuirin- BS/

* distin-uish (et'een the ty#ical sta-es in+ol+ed in

(uildin- BS/

* e0#lain the #ur#ose o& each sta-e in (uildin- a

system/

* select the (est alternati+e ty#e o& a##roach or

methodolo-y &or (uildin- a BS.


3/29

Slide 7.


Management issues

2rom a mana-erial #ers#ecti+e, this lectureaddresses the &ollo'in- areas)

$ 3hat are the alternati+es &or systems acuisitionand ho' is the most suita(le a##roach selected4

$ 3hat alternati+e models are there &or the di&&erent

sta-es &or introducin- a BS4 3hich is most

a##ro#riate4

$ 3hich acti+ities need to occur at each sta-e &or

the #roject to (e success&ul4


4/29

Slide 7.


2i-ure 7.1 6ri+ers &or in&ormation systems auisition


5/29

Slide 7.5


“information into a single application wasessential in order to enable meaningfulinterrogation of the data. This not only

proved time consuming but increased the potential risk of error and the time takento act on results.” Today, each care home can now log intothe system and complete the information.The data is then validated by the systemand is immediately available for analysis

and central reporting purposes.

"We have greater dataconsistency and as a resultwe have already seen a

25 drop in complaints.”

!ur carbon foot printing software helps you measure manage and reduce yourorganisation#s carbon footprint.


6/29

Slide 7.


Introducing BIS acquisition

$ BIS acquisition) 8he #rocess o& e+aluatin- andim#lementation &or a BS.

6escri(es the method o& o(tainin- an in&ormation

system &or a (usiness. 8he main choices are)

$ 9&&:the:shel& ;#acka-ed<

$ Bes#oke ;tailor:made< a##lications de+elo#ed (y an

in:house 8 de#artment or a so&t'are house$ Systems de+elo#ed (y end:user ;i.e) S=8

#ro&essionals


7/29

Slide 7.7


2i-ure 7. %n e0am#le o& a ty#ical e+aluation o& alternati+es &or BS acuisition


8/29

Slide 7.>


1. Bespoke development

$ Bespoke development) %n S is de+elo#ed ?&romscratch@ (y an S #ro&essional to suit the (usiness

reuirements o& the a##lication.

$ Bene&its)

* 8ailored to reuirements o& (usiness

* Aay con&er s#eci&ic com#etiti+e ad+anta-e.

$ Pro(lems)

* E0#ense * Aost e0#ensi+e 'ay o& de+elo#in- a ne'

in&ormation system

* 8ime * 6e+elo#ment is o&ten delayed

* uality * So&t'are code may contains (u-s.


9/29

Slide 7.C


. !ff"t#e"s#elf purc#ase

$ !ff"t#e"s#elf purc#ase) %n acuisition method thatin+ol+es direct #urchase o& a #re:'ritten a##lication

used (y more than one com#any.

$ Bene&its)

* 8ime * uick #urchase * "ost * Lo' cost due to economies o& scale

* uality * Should o&&er sta(ility and (e &eature:rich.

$ 6is(ene&its)

* Aay omit some &eatures s#eci&ically reuired (y

indi+idual customer

* Deuires chan-es to #rocess to meet needs o&

so&t'are.


10/29

Slide 7.1!


. !ff"t#e"s#elf purc#ase $%ontinued&

$ % tailored off-the-shelf #urchase is an o&&:the:shel&#urchase that has s#eci&ic #ro-rammin-

de+elo#ment or e0tensi+e con&i-uration tailored to

the needs o& the customer.

$ % component off-the-shelf #urchase is an o&&:the:shel& #urchase that can (e con&i-ured usin-

#re:'ritten modules.


11/29

Slide 7.11


'. (nd"user"developed soft)are

$ (nd"user"developed soft)are) So&t'are 'ritten (ynon:S #ro&essionals, i.e. the (usiness users.

$ Bene&its)

* 8ailored to the needs o& end:users

* 9&ten relati+ely &ast.

$ Pro(lems)

* Aay not achie+e 'ider (usiness o(jecti+es

*uality may (e a #ro(lem 'hen 'ritten (y non:S#ro&essional. Aaintenance may (e di&&icult.

Slid 7 1


12/29

Slide 7.1


!t#er factors affecting selection

$ Sie o& the or-anisation) large, medium or small.

$ Sie o& in:house 8 ca#a(ility) the expertise within the

organisations to make effectie procurement decisions

$ "om#le0ity o& in&ormation system ;are there s#ecial

issues &or the market the com#any o#erates in


13/29

Slide 7.1


Summary * acquisition alternatives

8a(le 7.1 %n e+aluation o& alternati+es &or BS acuisition

Slide 7 1


14/29

Slide 7.1


Systems development lifecycle $S+L%&) %ny

in&ormation systems #roject &ollo's a lo-ical serieso& de+elo#ment #hases. 8hese are kno'n as the

systems de+elo#ment li&ecycle.

S+L% stages)$ Initiation, a start u# #hase in res#onse to a (usiness #ro(lem or o##ortunity/$ -easibility study, to determine the +ia(ility o& the #ro#osed systems

de+elo#ment/$ System analysis) analysis o& (usiness reuirements/$ Systems design, to s#eci&y ho' the system 'ill deli+er the stated reuirements/$ System build, the desi-n is trans&ormed into a #hysical system (y #ro-rammin-,

testin- and creation o& data(ases/$ Implementation and c#angeover, the or-anisation mo+es &rom installin- and

testin- the in&ormation system to o#eratin- in a li+e (usiness en+ironment/$ evie) and maintenance, the success o& the system is measured a-ainst the

ori-inal reuirements and modi&ications are made o+er its li&etime.

Systems development lifecycle $S+L%&

Slide 7 15


15/29

Slide 7.15


Soft)are acquisition and t#e systems

development lifecycle

$ 8he systems de+elo#ment li&ecycle ;S6L"< model 'as

de+elo#ed and launched (y the Fational "om#utin-

"entre in the in 1CC. 8he S6L" a##roach reco-nises

that systems are de+elo#ed in a series o& ste#s or #hases

and that each #hase needs to (e com#leted (e&ore thene0t one commences.

$ Deco-nition is also -i+en to the &act that the #ro-rammin-

acti+ity ;#art o& the (uild #hase< should only commence

once user reuirements ha+e (een determined and thesystem desi-n #roduced. 2i-ure 7. illustrates the normal

ste#s &ound in the systems de+elo#ment li&ecycle.

Slide 7 1


16/29

Slide 7.1


2i-ure 7. 8he systems de+elo#ment li&ecycle ;S6L"<

Slide 7 17


17/29

Slide 7.17


Initiation p#ase

$ Initiation p#ase) * 8he start:u# #hase in an S de+elo#ment #roject.

ts aims are to esta(lish 'hether the #roject is

&easi(le and then #re#are to ensure the #roject is

success&ul.$ Initiation p#ase conte/t)

* n#ut) creati+e thou-ht and=or systematic

e+aluation o& S needs.

* 9ut#ut) idea &or initiation o& a ne' in&ormation

system.

Slide 7 1>


18/29

Slide 7.1>


-easibility assessment

$ -easibility assessment) %n acti+ity at the start o& a#roject to ensure that the #roject is a +ia(le (usiness

#ro#osition. 8he &easi(ility re#ort analyses the need

&or and im#act o& the system and considers di&&erent

alternati+es &or acuirin- so&t'are.

$ -easibility assessment conte/t)

* n#ut) idea &or initiation o& a ne' in&ormation system.

* 9ut#ut) &easi(ility re#ort and recommendation to

#roceed.

Slide 7.1C


19/29

Slide 7.1C


Systems analysis

$ Systems analysis) 8he ca#ture o& the (usiness

reuirements o& a system &rom talkin- to or o(ser+in-

end:users and usin- other in&ormation sources such

as e0istin- system documentation. 6e&ines what the

system 'ill do.

$ Systems analysis conte/t)

* n#ut) terms o& re&erence in &easi(ility re#ort descri(in-

outline reuirements. * 9ut#ut) detailed reuirements s#eci&ication

summarisin- system &unctions. Su##orted (y dia-rams

sho'in- the in&ormation &lo' and #rocesses that are

reuired.

Slide 7.!


20/29

Slide 7.!


Systems design

$ Systems design) 6e&ines how the system 'ill 'ork

in key areas o& user inter&ace, #ro-ram modules,

security and data(ase structure and transactions.

$ Systems design conte/t)

* n#ut) reuirements s#eci&ication.

* 9ut#ut) detailed desi-n s#eci&ication.

Slide 7.1


21/29


System build

$ System build) 6escri(es the creation o& so&t'are (y

#ro-rammers. t in+ol+es 'ritin- the so&t'are code

;#ro-rammin-


22/29


System implementation

$ System implementation) n+ol+es the transition orchan-eo+er &rom the old system to the ne' and the

#re#aration &or this such as makin- sure the hard'are

and net'ork in&rastructure &or a ne' system are in

#lace/ testin- o& the system/ and also human issueso& ho' (est to educate and train sta&& 'ho 'ill (e

usin- or a&&ected (y the ne' system.

$ System implementation conte/t)

* n#ut) 'orkin- system, not tested (y users. * 9ut#ut) si-ned:o&&, o#erational in&ormation system

installed in all locations.

Slide 7.


23/29


evie) and maintenance

$ 9nce an in&ormation system is o#eratin- under li+erunnin- conditions, it 'ill (e ine+ita(le that chan-es

'ill (e reuired o+er time. 8he maintenance #hase

in+ol+es t'o di&&erent ty#es o& maintenance.

$ ?n#roducti+e maintenance@, stems &rom errors oro+ersi-hts in the ori-inal systems de+elo#ment

'hich, 'hile not #re+entin- the system o#eratin- to

an acce#ta(le le+el, are still necessary to correct &or

it to con&orm 'ith the ori-inal s#eciIcation.$ 8he second &orm o& maintenance in+ol+es the

addition o& ne' &eatures and &acilities that e0tend the

sco#e and &unctionality o& the in&ormation system.

Slide 7.


24/29


apid applications development $A+&

$ apid applications development $A+&) % method o&

de+elo#inin&ormation systems 'hich uses #rototy#in- toachie+e user in+ol+ement and &aster de+elo#ment com#ared totraditional methodolo-ies such as SS%6A.

$ 0rototyping) % #rototy#e is a #reliminary +ersion o& #art o& a&rame'ork o& all o& an in&ormation system 'hich can (e re+ie'ed

(y end:users. Prototy#in- is an iterati+e #rocess 'here userssu--est modi&ications (e&ore &urther #rototy#es and the &inalin&ormation system is (uilt.

$ "haracteristics

* Da#id

* Small teams

* ser in+ol+ement

* 2reuent re+ie' and testin-.

Slide 7.5


25/29


2i-ure 7.5 8he role o& #rototy#in- 'ithin the systems de+elo#ment li&ecycle

Slide 7.


26/29


Spiral model

$ Spiral model ) %n iterati+e systems de+elo#ment in'hich the sta-es o& analysis, desi-n, code and re+ie'

re#eat as ne' &eatures &or the system are identi&ied.

$ 8he &our main acti+ities o& this model are as &ollo's)

* Planning * settin- #roject o(jecti+es, de&inin-alternati+es.

* !isk analysis * analysis o& alternati+es and the

identi&ication and solution o& risks.

* "ngineering * eui+alent to the (uild #hase o& theS6L" 'ith codin- and testin-.

* #ustomer ealuation * testin- o& the #roduct (y

customers.

Slide 7.7


27/29


Agile and lean soft)are development

$ 8he lean a##roach to so&t'are de+elo#ment em#hasises 'hat isessentially an incremental a##roach to so&t'are de+elo#ment 'here

so&t'are is de+elo#ed and de#loyed in small and use&ul &eature sets

'hich 'ork incrementally. 8his ?&eed(ack:dri+en@ a##roach to so&t'are

de+elo#ment is in contrast to the traditional 'ater&all model 'here

so&t'are de+elo#ment #roceeds in a series o& discreet ste#s, each o&'hich should (e com#leted (e&ore the ne0t one can #roceed.

$ %-ile So&t'are 6e+elo#ment tends to relate more to the so&t'are

en-ineerin- as#ects o& systems de+elo#ment. 8he term ?%-ile

Aethods@ has (een around since !!1 and today encom#asses a

num(er o& a-ile so&t'are de+elo#ment methods includin- %da#ti+eSo&t'are 6e+elo#ment ;%S6


28/29


+ynamic Systems +evelopment

Met#odology $+S+M&

$ +ynamic Systems +evelopment Met#odology

$+S+M&) % methodolo-y that descri(es ho' D%6 can

(e a##roached.

1. $ctie user inolement is imperatie.

. %S%& teams must be empowered to make

decisions.

. 'he focus is on fre(uent deliery of products .

. )itness for business purpose is the essentialcriterion for acceptance of delierables.

Slide 7.C


29/29

B ij G l d Hi ki B i I f ti S t P P i t th W b 5th diti © P Ed ti Li it d !15

5. Iteratie and incremental deelopment.

. $ll changes during deelopment are reersible.

7. !e(uirements are baselined at a high leel .

>. 'esting is integrated throughout the lifecycle.C. $ collaboratie and co-operatie approach between

all stakeholders is essential .

+ynamic Systems +evelopment

Met#odology $+S+M& $%ontinued&

Documents

Business information systems development