Scribd
Upload
43 views

Management Information Systems

The document outlines ten important activities involved in the implementation phase of the systems development life cycle: 1) application development, 2) documentation review, 3) program design, 4) coding, 5) testing the system, 6) documentation, 7) management approval, 8) training, 9) data conversion, and 10) system change over methods including direct cut over, parallel change over, pilot change over, and phased change over.

Uploaded by

Aibak Irshad
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
43 views

Management Information Systems

The document outlines ten important activities involved in the implementation phase of the systems development life cycle: 1) application development, 2) documentation review, 3) program design, 4) coding, 5) testing the system, 6) documentation, 7) management approval, 8) training, 9) data conversion, and 10) system change over methods including direct cut over, parallel change over, pilot change over, and phased change over.

Uploaded by

Aibak Irshad
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

Management Information Systems BBD 2053

Activities involved in the Implementation phase of the Systems Development Life Cycle

AIBA I!S"AD S"A" #$5%3

&hen implementing a ne' information system( there are ten important activities to )e considered( these are as follo's*

Application Development Application development is the process of constr+cting the code mod+les and programs 'hich 'ill go on to form the fo+ndations of the ne' information system* Documentation Review It is vital that in the early stages of SDLC that as m+ch information as possi)le is gathered and doc+mented )efore trying to design the ne' system* Information s+ch as data on the old system( client and +ser inp+t on 'hat they e,pect from the ne' system( screen layo+ts( prior coding mod+les etc* Program Design D+ring the program design activity( Analysts and programmers 'ill vie' the system as a series of specific tas-s. f+nctions called mod+les* A mod+le consists of related program code 'hich is organi/ed into small( easy to +nderstand and maintain +nits* Coding Coding is 'here program logic is t+rned into specific instr+ctions that the comp+ter system can e,ec+te* 0his happens 'hen the programmer +ses a special type of programming lang+age to ma-e code statements from program logic* Testing the System &hen all the coding is complete( the programmer 'ill test every program individ+ally to ma-e s+re it operates as it is s+ppose to* Later on in the implementation process( the programs 'ill )e tested in gro+ps and then finally the entire system is tested*

Documentation In order for a system to achieve s+ccessf+l system operation and maintenance( doc+mentation is essential* Acc+rate doc+mentation 'ill ma-e f+t+re program changes easier( faster( and less e,pensive* 0ypes of information that are doc+mented are program doc+mentation( systems doc+mentation( operations doc+mentation( and +ser doc+mentation* Management Approval &hen the programming team has completed all the testing they 'ill present their res+lts to the management* 0hese res+lts 'ill incl+de descri)ing the test res+lts( +pdated doc+mentation( and a s+mmary of inp+t from +sers involved in the system testing* If the system tests res+lts prod+ced no operational( technical( or economical iss+es( then the system is ready to )e implemented* Training &itho+t prior training no system can )e s+ccessf+l* &hether its hard'are or soft'are1 a s+ccessf+l information system re2+ires training for I0 staff( +sers( and managers* 0he entire systems development effort can depend on 'hether or not people +nderstand the system and -no' ho' to +se it effectively* Data Conversion Data conversion plays a -ey part of the system installation process* D+ring this activity data is loaded into the ne' system1 and depending on the system( data conversion can )e done )efore( d+ring( or after the operational environment is complete*

System Change Over 0here are fo+r 'ays 'hich install a ne' system are34 56 Direct Cut over is 'here the old systems stops at the same point the ne' system starts* 0his is not a recommended 'ay to implement a system )eca+se if the ne' system enco+nters a pro)lem( it is impossi)le to go )ac- to the old system*

26 Parallel change over is 'here the ne' system starts )+t the old system 'ill contin+e to )e +sed +ntil a certain point in the f+t+re is reached and it 'ill terminate* 0his is a good 'ay to implement a ne' system )eca+se( +nli-e a direct c+t over( if a pro)lem is enco+ntered )y the ne' system it is still o-ay to operate on the old system*

36 A Pilot change over is +sed 'hen a n+m)er of different )ranches of the same company operate on the same system* "o'ever( 'hen changing to a ne' information system the company 'ill only change one )ranch over at first* 0he other )ranches 'ill monitor any pro)lems enco+ntered )y the )ranch operating the ne' system* &hen all pro)lems are fi,ed( all the other )ranches 'ill change over to the ne' system at the same time*

#6 Phased change over is 'hen one company has many departments* 0he ne' system 'ill )e implemented one department at a time* 0he old system 'ill contin+e to r+n +ntil all departments have changed over*

You might also like