Você está na página 1de 7

1/28/2008

AssumingtheRoleof theSystemsAnalyst

LearningObjectives
Recallthebasictypesofcomputerbasedsystems thatasystemsanalystneedstoaddress Understandhowusersworkingincontextwithnew technologieschangethedynamicsofasystem Realizewhatthemanyrolesofthesystemsanalyst are KnowthestepsoftheSDLCastheyrelatetoHCIand howtoapplythemtoarealsystem UnderstandwhatCASEtoolsareandhowtheyhelpa systemsanalyst Exploreothermethodologiessuchasobjectoriented systemsdesignandprototyping
Kendall&Kendall 12

SystemsAnalysisandDesign,7e Kendall&Kendall
2008Pearson PrenticeHall

InformationAKeyResource
Fuelsbusinessandcanbethecritical factorindeterminingthesuccessor failureofabusiness Needstobemanagedcorrectly Managingcomputergenerated informationdiffersfromhandling manuallyproduceddata
Kendall&Kendall 13

MajorTopics
Fundamentalsofdifferentkindsof informationsystems Rolesofsystemsanalysts Phasesinthesystemsdevelopmentlife cycleastheyrelatetoHuman ComputerInteraction(HCI)factors ComputerAidedSoftwareEngineering (CASE)tools
Kendall&Kendall 14

SystemsAnalystsRecommend,Design,and MaintainManyTypesofSystemsforUsers
TransactionProcessingSystems(TPS) OfficeAutomationSystems(OAS) KnowledgeWorkSystems(KWS) ManagementInformationSystems(MIS) DecisionSupportSystems(DSS) ExpertSystems(ES) ExecutiveSupportSystems(ESS) GroupDecisionSupportSystems(GDSS) ComputerSupportedCollaborativeWorkSystems (CSCWS)
Kendall&Kendall 15

Strategic Level

Asystemsanalyst maybeinvolvedwith anyorallofthese systemsateach organizationlevel

Higher Level

Knowledge Level Operational Level

Kendall&Kendall

16

1/28/2008

OperationalLevel
TransactionProcessingSystem(TPS)
Processlargeamountsofdataforroutinebusiness transactions Boundaryspanning Supportthedaytodayoperationsofthecompany Examples:PayrollProcessing,Inventory Management

KnowledgeLevel
OfficeAutomationSystem(OAS)
Supportsdataworkerswhoshareinformation,butdonot usuallycreatenewknowledge Examples:Wordprocessing,Spreadsheets,Desktop publishing,Electronicscheduling,Communicationthrough voicemail,Email,Videoconferencing

KnowledgeWorkSystem(KWS)
Supportsprofessionalworkerssuchasscientists,engineers, anddoctors Examples:computeraideddesignsystems,virtualreality systems,investmentworkstations

Kendall&Kendall

17

Kendall&Kendall

18

HigherLevel
ManagementInformationSystem(MIS)
Supportabroadspectrumoforganizationaltasksincluding decisionanalysisanddecisionmaking Examples:profitmarginbysalesregion,expensesvs. budgets

StrategicLevel
ExecutiveSupportSystem(ESS)
Helpsexecutivestomakeunstructuredstrategicdecisionsin aninformedway Examples:drilldownanalysis,statusaccess

DecisionSupportSystem(DSS)
Aidsdecisionmakersinthemakingofdecisions Examples:financialplanningwithwhatifanalysis,budgeting withmodeling

GroupDecisionSupportSystem(GDSS)
Permitgroupmemberstointeractwithelectronicsupport Examples:email,LotusNotes

ExpertSystem(ES)
Capturesandusestheknowledgeofanexpertforsolvinga particularproblemwhichleadstoaconclusionor recommendation Examples:MYCIN,XCON
Kendall&Kendall 19

ComputerSupportedCollaborativeWorkSystem (CSCWS)
CDCWSisamoregeneraltermofGDSS Mayincludesoftwaresupportcalledgroupwareforteam collaborationvianetworkcomputers Example:videoconferencing,Websurveysystem
Kendall&Kendall 110

IntegratingNewTechnologies intoTraditionalSystems
EcommerceandWebSystems EnterpriseResourcePlanningSystems WirelessSystems OpenSourceSoftware NeedforSystemsAnalysisandDesign

Figure1.2Systemsanalystsneedtobeaware thatintegratingtechnologiesaffectsalltypesof systems

Kendall&Kendall

111

Kendall&Kendall

112

1/28/2008

EcommerceandWebSystems
Benefits
Increasinguserawarenessoftheavailabilityofa service,product,industry,person,orgroup Thepossibilityof24houraccessforusers Improvingtheusefulnessandusabilityofinterface design Creatingasystemthatcanextendgloballyrather thanremainlocal,thusreachingpeopleinremote locationswithoutworryofthetimezoneinwhich theyarelocated
Kendall&Kendall 113

EnterpriseResourcePlanning Systems(ERP)
Performsintegrationofmany informationsystemsexistingon differentmanagementlevelsandwithin differentfunctions Example:SAP,Oracle

Kendall&Kendall

114

WirelessSystems
Systemanalystmaybeaskedtodesign standardorwirelesscommunicationnetworks thatintegratevoice,videoandemailinto organizationalintranetsorindustryextranets Systemanalystmayalsobeaskedtodevelop intelligentagents Example:Microsoft'snewsoftwarebasedon Bayesianstatistics Wirelesscommunicationisreferredasm commerce(mobilecommerce)
Kendall&Kendall 115

OpenSourceSoftware
Analternativeoftraditionalsoftware developmentwhereproprietarycodeis hiddenfromtheusers Opensourcesoftwareisfreetodistribute, shareandmodify Characterizedasaphilosophyratherthan simplytheprocessofcreatingnewsoftware Example:LinuxOperatingSystem,Apache WebServer,MozillaFirefoxWebbrowser
Kendall&Kendall 116

NeedforSystemsAnalysisand Design
Installingasystemwithoutproperplanning leadstogreatuserdissatisfactionand frequentlycausesthesystemtofallinto disuse Lendsstructuretotheanalysisanddesignof informationsystems Aseriesofprocessessystematically undertakentoimproveabusinessthrough theuseofcomputerizedinformationsystems
Kendall&Kendall 117

RolesoftheSystemsAnalyst
Theanalystmustbeabletoworkwith peopleofalldescriptionsandbe experiencedinworkingwithcomputers Threeprimaryroles:
Consultant SupportingExpert Agentofchange

Kendall&Kendall

118

1/28/2008

QualitiesoftheSystemsAnalyst
Problemsolver Communicator Strongpersonalandprofessionalethics Selfdisciplinedandselfmotivated

SystemsDevelopmentLifeCycle (SDLC)
Thesystemsdevelopmentlifecycleisa phasedapproachtosolvingbusiness problems Developedthroughtheuseofaspecific cycleofanalystanduseractivities Eachphasehasuniqueuseractivities

Kendall&Kendall

119

Kendall&Kendall

120

Figure1.3Thesevenphasesofthe systemsdevelopmentlifecycle

IncorporatingHumanComputer Interaction(HCI)Considerations
Thedemandforanalystswhoare capableofincorporatingHCIintothe systemsdevelopmentprocesskeeps increasing,ascompaniesbeginto realizethatthequalityofsystemsand thequalityofworklifecanbeimproved bytakingahumancenteredapproach attheoutsetofaproject

Kendall&Kendall

121

Kendall&Kendall

122

IdentifyingProblems, Opportunities,andObjectives
Activity: Interviewingusermanagement Summarizingtheknowledgeobtained Estimatingthescopeoftheproject Documentingtheresults Output: Feasibilityreportcontainingproblemdefinitionand objectivesummariesfromwhichmanagementcan makeadecisiononwhethertoproceedwiththe proposedproject

DeterminingHumanInformation Requirements
Activity: Interviewing Samplingandinvestingharddata Questionnaires Observethedecisionmakersbehaviorandenvironment Prototyping Learnthewho,what,where,when,how,andwhyofthe currentsystem Output: Analystunderstandshowusersaccomplishtheirworkwhen interactingwithacomputerandbegintoknowhowto makethenewsystemmoreusefulandusable.Theanalyst shouldalsoknowthebusinessfunctionsandhavecomplete informationonthepeople,goals,dataandprocedure involved
Kendall&Kendall 124

Kendall&Kendall

123

1/28/2008

AnalyzingSystemNeeds
Activity: Createdataflowdiagrams Completethedatadictionary Analyzethestructureddecisionsmade Prepareandpresentthesystemproposal Output: Recommendationonwhat,ifanything, shouldbedone
Kendall&Kendall 125

DesigningtheRecommended System
Activity:
Designproceduresfordataentry Designthehumancomputerinterface Designsystemcontrols Designfilesand/ordatabase Designbackupprocedures

Output
Modeloftheactualsystem
Kendall&Kendall 126

DevelopingandDocumenting Software
Activity:
Systemanalystworkswithprogrammerstodevelopany originalsoftware Workswithuserstodevelopeffectivedocumentation Programmersdesign,code,andremovesyntacticalerrors fromcomputerprograms Documentsoftwarewithhelpfiles,proceduremanuals, andWebsiteswithFrequentlyAskedQuestions

TestingandMaintainingthe System
Activity:
Testtheinformationsystem Systemmaintenance Maintenancedocumentation

Output:
Problems,ifany Updatedprograms Documentation
Kendall&Kendall 128

Output:
Computerprograms Systemdocumentation

Kendall&Kendall

127

ImplementingandEvaluatingthe System
Activity:
Trainusers Analystplanssmoothconversionfromold systemtonewsystem Reviewandevaluatesystem

Figure1.4Someresearchersestimatethattheamountof timespentonsystemsmaintenancemaybeasmuchas60 percentofthetotaltimespentonsystemsprojects

Output:
Trainedpersonnel Installedsystem
Kendall&Kendall 129 Kendall&Kendall 130

1/28/2008

TheImpactofMaintenance
Maintenanceisperformedfortwo reasons
Removingsoftwareerrors,and Enhancingexistingsoftware

Figure1.5Resourceconsumption overthesystemlife

Overtimethecostofcontinued maintenancewillbegreaterthanthatof creatinganentirelynewsystem.Atthat pointitbecomesmorefeasibleto performanewsystemsstudy


Kendall&Kendall 131 Kendall&Kendall 132

ApproachestoStructuredAnalysisandDesign andtotheSystemsDevelopmentLifeCycle

CaseTools
CASEtoolsareproductivitytoolsfor systemsanalyststhathavebeencreated explicitlytoimprovetheirroutinework throughtheuseofautomatedsupport ReasonsforusingCASEtools
IncreasingAnalystProductivity ImprovingAnalystUserCommunication IntegratingLifeCycleActivities AccuratelyAssessingMaintenanceChanges
Kendall&Kendall 134

Traditionalsystemsdevelopment lifecycle CASEsystemsdevelopmentlife cycle ObjectOrientedSystemsAnalysis andDesign


Kendall&Kendall 133

CaseToolClassifications
UpperCASEtoolsperformanalysis anddesign LowerCASEtoolsgenerate programsfromCASEdesign IntegratedCASEtoolsperformboth upperandlowerCASEfunctions

UpperCASETools
Createandmodifythesystem design Helpinmodelingorganizational requirementsanddefiningsystem boundaries Canalsosupportprototypingof screenandreportdesigns
Kendall&Kendall 136

Kendall&Kendall

135

1/28/2008

LowerCASETools
LowerCASEtoolsgenerate computersourcecodefromthe CASEdesign Sourcecodeisusuallygeneratedin severallanguages

Figure1.7TraditionalversusCASE systemsdevelopmentlifecycle

Kendall&Kendall

137

Kendall&Kendall

138

ObjectOrientedSystemsAnalysis andDesign
Alternateapproachtothestructuredapproachof theSDLCthatisintendedtofacilitatethe developmentofsystemsthatmustchange rapidlyinresponsetodynamicbusiness environments Analysisisperformedonasmallpartofthe systemfollowedbydesignandimplementation. Thecyclerepeatswithanalysis,designand implementationofthenextpartandthisrepeats untiltheprojectiscomplete

AlternateApproachestoStructuredAnalysis andDesignandtotheSystemsDevelopment LifeCycle

Agileapproach Prototyping ETHICS Projectchampion SoftSystemsMethodology Multiview


Kendall&Kendall 140

Kendall&Kendall

139

Summary
Informationisakeyresource Systemsanalystsdealwithmanytypesof informationsystems Integrationoftraditionalsystemswithnew technologies Rolesandqualitiesofthesystemsanalyst ThesystemsDevelopmentLifeCycle CASEtools Alternativestostructuredanalysisanddesign andtotheSDLC

Kendall&Kendall

141

Você também pode gostar