Systems Analysis and Design in a Changing World, Thursday, Feb 1

Embed Size (px)

DESCRIPTION

Systems Analysis and Design in a Changing World, Thursday, Feb 1. Today’s Schedule. System Requirements Test #1, Thursday, February 8 Finish Reading Chapter 4, page 120 Assignment #4 Due Monday, Feb 5th. Learning Objectives. - PowerPoint PPT Presentation

Text of Systems Analysis and Design in a Changing World, Thursday, Feb 1

  • Systems Analysis and Design in a Changing World, Thursday, Feb 1

  • Todays ScheduleSystem RequirementsTest #1, Thursday, February 8Finish Reading Chapter 4, page 120 Assignment #4 Due Monday, Feb 5th

    Chart1

    58

    58

    66

    71

    71

    77

    77

    81

    90

    90

    91

    93

    94

    97

    100

    100

    100

    105

    Quiz #1

    Sec 1 Noon

    ITFN1112-01

    Fnds. of Systems Analysis

    12 - 1:15pm, T & Th

    Criswell, Kevin

    Joyner, Brad

    Leaphart, Mia

    Lemmons, Evan

    Martin, Taylor

    Mbi, Marilyn

    Moore, Kenneth

    Sai, Obed

    Stokes, Trey

    Thompson, Antavius

    Todd, Matt

    Wiggins, Marcus

    Williams, Serome

    Charts

    Quiz #1

    58

    58

    66

    71

    71

    77

    77

    81

    90

    90

    91

    93

    94

    97

    100

    100

    100

    105

    Charts

    Quiz #1

    Sec 2 Eveng

    ITFN1112-02

    Fnds. of Systems Analysis

    T & Th, 6-7:15 pm

    Dennis, Brandon

    Irizarry, Javier

    Jarjou, Lamin

    Johnson, Debbie

    Pruitt, Ryan

    Smalls, Jeneen

    Stevenson, Mars

    Sheet3

    100%21%39%20%20%

    AvgProjectTestsFinalHW & Q

    5850509050

    7070709050

    7470709070

    Sec 2 Eveng - Ex Daily

    ITFN1112-02

    Fnds. of Systems Analysis

    T & Th, 6-7:15 pm

    1/9/071/11/071/23/07

    Dennis, Brandon110

    Irizarry, Javier111

    Jarjou, Lamin110

    Johnson, Debbie112

    Pruitt, Ryan110

    Smalls, Jeneen111

    Stevenson, Mars113

    Sec 1 Noon -Ex Daily

    ITFN1112-01

    Fnds. of Systems Analysis

    12 - 1:15pm, T & Th

    Criswell, Kevin

    Joyner, Brad

    Leaphart, Mia

    Lemmons, Evan

    Martin, Taylor

    Mbi, Marilyn

    Moore, Kenneth

    Sai, Obed

    Stokes, Trey

    Thompson, Antavius

    Todd, Matt

    Wiggins, Marcus

    Williams, Serome

    Sec 1 Noon -Grades

    ITFN1112-01

    Fnds. of Systems Analysis

    12 - 1:15pm, T & ThA #1A#2Q #1A#3

    1/15/0722-Jan25-Jan1/29/07

    Criswell, Kevin97

    Joyner, Brad71

    Leaphart, Mia91

    Lemmons, Evan77

    Martin, Taylor

    Mbi, Marilyn94

    Moore, Kenneth58

    Sai, Obed105

    Stokes, Trey100

    Thompson, Antavius71

    Todd, Matt

    Wiggins, Marcus58

    Williams, Serome66

    Sec 2 Eveng - Grades

    ITFN1112-02

    Fnds. of Systems Analysis

    T & Th, 6-7:15 pmA #1A#2Q #1A#3

    1/15/0722-Jan25-Jan1/29/07

    Dennis, Brandon7010077

    Irizarry, Javier98100100

    Jarjou, Lamin9510093

    Johnson, Debbie959581

    Pruitt, Ryan9895100

    Smalls, Jeneen7910090

    Stevenson, Mars10010090

  • Learning ObjectivesIdentify and understand the different types of users who will be involved in investigating system requirements Describe the kind of information that is required to develop system requirements

  • Learning Objectives (continued)Determine system requirements through review of documentation, interviews, observation, prototypes, questionnaires, vendor research, and joint application design sessionsDiscuss the need for validation of system requirements to ensure accuracy and completeness and the use of a structured walkthrough

  • StakeholdersThe Source of System RequirementsPeople with interest in successful system implementation- identified by analystThree primary groups of stakeholdersUsers (use system)Clients (pay for and own system)Technical staff (ensure system operation)

  • Stakeholders Interested in New System Development

  • More On Users as StakeholdersHorizontal user roles information flow across departmentsVertical user roles information needs of clerical staff, middle management, and senior executivesBusiness users perform day-to-day operationsInformation users need current informationManagement users need summary informationExecutive users need strategic informationExternal users may have access to system

  • Techniques for Information GatheringAnalysis phase done to understand business functions and develop system requirementsOriginal structured approach Create model of existing system Derive requirements from existing system modelCurrent approach Identify logical requirements for new system Balance the review of current business functions with new system requirements

  • Relationship Between Information Gathering and Model Building

  • Themes for Information-Gathering Questions (Figure 4-7)

  • Fact-Finding MethodsReview existing reports, forms, and procedure descriptionsInterview and discuss processes with usersObserve and document business processesBuild prototypesDistribute and collect questionnairesConduct joint application design (JAD) sessionsResearch vendor solutions

  • Review Existing Reports, Forms, and Procedure DescriptionsSource: External industry-wide professional organizations and trade publicationsSource: Existing business documents and procedure descriptions within organization Identify business rules, discrepancies, and redundancies Be cautious of outdated materialObtain preliminary understanding of processesUse as guidelines/visual cues to guide interviews

  • Conduct Interviews and Discussions with UsersEffective way to understand business functions and rulesTime consuming and resource expensiveMay require multiple sessions to Meet all usersUnderstand all processing requirementsCan meet with individuals or groups of usersList of detailed questions prepared

  • Sample Checklist to Prepare for User Interviews (Figure 4-9)

  • A Sample Open-Items List

  • Observe and Document Business Processes Varies from office walkthroughs to performing actual tasksNot necessary to observe all processes at same level of detail May make users nervous, so use common sense

  • Build PrototypesPreliminary working model of a larger, more complex system componentDiscovery, design, evolving prototypesPrototype should beOperative Working model to provide look and feelFocused to accomplish single objectiveQuickBuilt and modified rapidly with CASE tools

  • Distribute and Collect QuestionnairesLimited and specific information from a large number of stakeholdersPreliminary insight into businessClosed-ended questions direct person answering questionOpen-ended questions encourage discussion and elaboration

  • Conduct Joint Application Design SessionsExpedites investigation of system requirementsSeeks to compress fact-finding, modeling, policy formation, and verification activities into shorter time frameCritical factor is to have all important stakeholders present

  • Joint Application Design ParticipantsSession leader trained in group dynamics and JAD group facilitationKnowledgeable business and system users and policy makers Technical staff representatives to handleComputer and network configurationsOperating environmentsSecurity issuesProject team members

  • Joint Application Design FacilitiesConducted in special room Limit interruptions May be off-siteResources Overhead projector, white board, flip charts, work materialElectronic support (laptops)CASE toolsGroup support systems (GSS)

  • A JAD Facility (Figure 4-16)

  • Research Vendor SolutionsMany problems have been solved by other companiesPositive contributions of vendor solutionsFrequently provide new ideasMay be state of the artCheaper and less riskyDangerMay purchase solution before understanding problem

  • Validating the RequirementsMake sure gathered information is correctStructured walkthroughEffective means of implementing quality control early in projectVerify and validate system requirementsReview of findings from investigation and of models based on findingsProject manager responsible for system quality Systems analyst, project manager are partners

  • For Tuessday, February 6Install Visual Paradigm, Community EditionTest #1, Thursday, February 8Finish Reading Chapter 4, (Skip Activity Diagrams) Assignment #4 Due Monday, Feb 5th