Modern Systems Analysis and Design Joey F. George Jeffrey A. Hoffer Joseph S. Valacich

Chapter 2Succeeding as a Systems AnalystModern Systems Analysisand DesignThird Edition

2.11Relationship between systems analysts skills and the SDLC cycle

Analytical Skills for Systems AnalysisFour Sets of Analytical SkillsSystems ThinkingOrganizational KnowledgeProblem IdentificationProblem Analyzing and Solving2.3System A system is an interrelated set of components, with an identifiable boundary, working together for a purpose A system has nine characteristics A system exists within an environment A boundary separates a system from its environmentSystems Thinking3Systems ThinkingCharacteristics of a System ComponentsAn irreducible part or aggregation of parts that make up a system, also called a subsystemInterrelated ComponentsDependence of one subsystem on one or more subsystemsA BoundaryThe line that marks the inside and outside of a system and that separates the system from its environmentA PurposeThe overall goal or function of a systemAn EnvironmentEverything outside the systems boundary that interacts with the system2.44Systems ThinkingInterfacesPoint of contact at which the system meets its environment or where subsystems meet each otherInputWhatever a system takes from its environment in order to fulfill its purposeOutputWhatever a system returns to its environment in order to fulfill its purposeConstraintsLimits to what it can do and how it can achieve its purpose within an environment (capacity, speed or capabilities)Systems ThinkingImportant System Concepts Open SystemsInteract freely with their environments, taking in input and returning outputAs environment changes, systems much adapt to changes or suffer consequencesClosed SystemsDoes not interact with environmentsAdaptability are not issues for closed systemsBusiness Information Systems are open SystemsSystems ThinkingImportant System Concepts (Continued)DecompositionThe process of breaking down a system into smaller components which can be further broken downAllows the systems analyst to:Break a system into small, manageable subsystemsFocus on one area at a timeConcentrate on component relating to one group of usersBuild different components at independent times2.77Systems ThinkingImportant System Concepts (Continued)ModularityProcess of dividing a system into modules of a relatively uniform sizeDirect result of decompositionModules simplify system designCouplingThe extent to which the subsystems depend on each otherSubsystems should be as independent as possible elsefailure of one subsystem fails the entire system.CohesionExtent to which a system or a subsystem performs a single function2.88Systems ThinkingImportant System Concepts (Continued)Logical System DescriptionPortrays the purpose and function of the systemDoes not tie the description to a specific physical implementationPhysical System DescriptionFocuses on how the system will be materially constructed2.99Systems ThinkingApplying Systems Thinking to Information SystemsInformation systems are subsystems in larger organizational systemsTaking input from, and returning output to, their organizational environmentsData flow diagrams represent information systems as systems (clearly illustrate)InputsOutputsSystem boundariesEnvironmentSubsystemsInterrelationships2.1010

Organizational KnowledgeUnderstanding of how organizations workKnowledge of specific functions and procedures of organization and departmentHow work officially gets doneHow departments operates, its purpose, its relationships with other departments, its relationships with customers and suppliersInternal policiesCompetitive and Regulatory EnvironmentOrganizational Strategies and Tactics

2.1212Problem IdentificationProblem: Difference between an existing situation and a desired situationProblem solving: the process of finding a way to reduce differencesIdentification is process of defining differencesDifferences are defined by comparing the current situation to the output of a model that predicts what the output should be

2.1313Problem Analyzing and SolvingMust analyze the problem and determine how to solve itFour PhasesIntelligenceAll relevant information is collectedDesignAlternatives are formulatedChoiceBest alternative solution is chosenImplementationSolution is put into practice2.1414Technical Skills for Systems AnalysisConstant re-education is necessary as technology changes rapidlyActivities to keep skills up-to-dateTrade publicationsProfessional societiesAttend classes or teach at a local collegeAttend courses sponsored by organizationConferences and trade showsBrowse WebsitesParticipate in new groups and conferences

2.1515Technical Skills for Systems AnalysisUnderstanding of a wide variety of technologies is required (requires continuous learning)Microcomputers, workstations, minicomputers and mainframe computersProgramming languagesOperating systemsDatabase and file management systemsData communication standardsSystems development tools and environmentsWeb development languages and toolsDecision support system generators

2.1616Management Skills for Systems AnalysisKnow how to manage your work and use organizational resources in the most productive wayFour categoriesResource ManagementProject ManagementRisk ManagementChange Management

2.1717Resource ManagementSystems analyst needs to know how to get the most out of the resources of an organization, including team membersIncludes the following capabilitiesPredicting resource usageTracking resource consumptionEffective use of resourcesEvaluation of resource qualitySecuring resources from abusive useRelinquishing resources when no longer needed2.1818Project ManagementTwo GoalsPrevent projects from coming in latePrevent projects from going over budgetAssists management in keeping track of projects progressConsists of several stepsDecomposing project into independent tasksDetermining relationships between tasksAssigning resources and personnel to tasksIndependent contractorsContractsRelationship managers (liaisons)

2.1919Risk ManagementAbility to anticipate what might go wrong in a projectMinimize risk and/or minimize damage that might resultPlacement of resourcesPrioritization of activities to achieve greatest gain2.20Change ManagementAbility to assist people in making transition to new systemAbility to deal with technical issues related to changeObsolescenceReusability20Interpersonal Skills for Systems AnalysisMastery of interpersonal skills is paramount to success as a Systems AnalystFour types of skills:Communication skillsWorking alone and with a teamFacilitating groupsManaging expectations2.2121Communication SkillsEffective communication helps to establish and maintain good working relationships with clients and colleaguesClearly and Effectively communicate with othersThree types used by Systems AnalystInterviewing and ListeningQuestionnairesWritten and Oral PresentationsSkills improve with experience2.2222Interviewing and ListeningMeans to gather information about a projectListening to answers is just as important as asking questionsEffective listening leads to understanding of problem and generates additional questionsExpensive and time-consuming2.23QuestionnairesAdvantages:Less costly than interviewsResults are less biased due to standardizationDisadvantagesLess effective than interviews due to lack of follow-up23Written and Oral PresentationsUsed to document progress of project and communicate this to othersCommunication takes several forms:Meeting agendaMeeting minutesInterview summariesProject schedules and descriptionsMemoranda requesting informationRequests for proposals from vendors and contractorsOral presentations2.2424Working Alone and with a TeamWorking alone on aspects of project involves managing:TimeCommitmentsDeadlinesTeam work involves establishing standards of cooperation and coordinationKnow when to trust judgment of others and when to question itUnderstand strengths and weakness of team membersTable 2-2 presents characteristics of a high-performance team2.2525Characteristics of High-Performance Team

Must have motivation and a visionFacilitating GroupsInvolves guiding a group without being a part of the groupMust work to keep the effort on trackUseful skill for sessions such as Joint Application Development (JAD)2.27Managing ExpectationsManaging expectations is directly related to successful system implementationSkills for successful expectation managementUnderstanding of technology and workflowsAbility to communicate a realistic picture of new system to usersEffective education of management and users throughout systems development life cycle

27Systems Analysis as a ProfessionStandards have been established for education, training, certification and practiceStandard ways of analyzing, designing, and implementing systemsSociety for Information ManagementAssociation of Information Technology ProfessionalsAssociation for Computing Machinery (ACM)Certified Computing Professional (CCP) examSeveral aspects:Standards of PracticeEthicsCareer Paths2.2828Standards of PracticeEndorsed Development MethodologySpecific procedures and techniques to be used during development processPromote consistency and reliability across all of an organizations development projectsApproved Development PlatformsOrganizations standardize around a specific platform, sometimes tied to development methodologyStandardization of RolesRoles are becoming better defined across organizationsDevelopment of a Common LanguageCommon programming languagesCommon modeling languages, such as Unified Modeling Language (UML)

2.2929EthicsProfessional EthicsACM Code of Ethics See Figure 2-10Business EthicsStockholder approachAny action taken by a business is acceptable as long as it is legal and maximizes stockholder profitStakeholder approachAny action that violates rights of stakeholder must be rejectedSocial Contract approachAny action that is deceptive, can dehumanize employees or that could discriminate is rejected2.3030Career PathsConsultingInformation Systems within a large corporationSoftware vendorsOther opportunities outside of systems analysis2.3131