PowerPoint PresentationChapter Five Systems AnalysisChapter MapSystems Analysis vs. Systems DesignInformation Systems AnalysisContext of Systems AnalysisRepositoryModel-Driven Analysis MethodsModel-Driven MethodsA Simple Process ModelA Simple Data ModelA Simple Object ModelAccelerated Systems AnalysisDiscovery PrototypingRapid Architected AnalysisRequirements Discovery MethodsRequirements Discovery Methods (con’t)Business Process Redesign MethodsSystems Analysis Methods and Agile MethodsFAST Systems Analysis PhasesContext of Scope Definition Phase ContextTasks for the Scope Definition Phase of Systems AnalysisSample Request for System ServicesSystems Analysis PhasesSample Problem StatementsSlide 26Slide 27Scope Definition PhaseSlide 295C H A P T E RSYSTEMS ANALYSISChapter Five Systems AnalysisDefine systems analysis as it relates to scope definition problem analysis requirements analysis logical design decision analysis Describe systems analysis approaches Describe the the system analysis phases as they relate toKnowledgeProcessCommunicationsDescribe the the system analysis phases in terms of purpose participants Inputsoutputs Techniquessteps.Identify those chapters and modules in this textbook that can help you learn specific systems analysis tools and techniques.Chapter MapParticipantsOwnersUsersOutcomesStatement of workProblem StatementPIECESImprovement ObjectivesPIECESBusiness RequirementsSystem ProposalApplication ArchitectureSystems Analysis vs. Systems DesignSystems analysis is a problem-solving technique that decomposes a system into its component pieces for the purpose of studying how well those component parts work and interact to accomplish their purpose.Systems design (also called systems synthesis) is a complementary problem-solving technique (to systems analysis) that reassembles a system’s component pieces back into a complete system—hopefully, an improved system. This may involves adding, deleting, and changing pieces relative to the original system.Information Systems AnalysisInformation systems analysis is defined as those development phases in a project that primarily focus on the business problem, independent of any technology that can or will be used to implement a solution to that problem.Context of Systems AnalysisRepositoryRepository – a location (or set of locations) where systems analysts, systems designers, and system builders keep all of the documentation associated with one or more systems or projects.A network directory of computer-generated files that contain project correspondence, reports, and dataA CASE tool dictionary or encyclopedia (Chapter 3)Printed documentation (binders and system libraries)An intranet website interface to the above componentsModel-Driven Analysis MethodsModel-driven analysis emphasizes the drawing of pictorial system models•document and validate both existing and/or proposed systems.Ultimately, the system model becomes the blueprint for designing and constructing an improved system.Model – a representation of either reality or vision. Since “a picture is worth a thousand words,” most models use pictures to represent the reality or vision.Model-Driven MethodsStructured analysis is a model-driven, process-centered technique used to either analyze an existing system, define business requirements for a new system, or both. The models are pictures that illustrate the system’s component pieces: processes and their associated inputs, outputs, and files.Information engineering (IE) is a model-driven and data-centered, but process-sensitive technique to plan, analyze, and design information systems. IE models are pictures that illustrate and synchronize the system’s data and processes. Object-oriented analysis (OOA) is a model-driven technique that integrates data and process concerns into constructs called objects. OOA models are pictures that illustrate the system’s objects from various perspectives such as structure and behaviorObject – the encapsulation of the data (called properties) that describes a discrete person, object, place, event, or thing, with all the processes (called methods) that are allowed to use or update the data and properties. The only way to access or update the object’s data is to use the object’s predefined processes.A Simple Process ModelA Simple Data ModelA Simple Object ModelAccelerated Systems AnalysisAccelerated systems analysis approaches emphasize the construction of prototypes to more rapidly identify business and user requirements for a new system.prototype – a small-scale, incomplete, but working sample of a desired system. Don’t worry about “look and feel” Users think completed system can be built fast Prototype tools ie. Access, VB, etc, used to build systemAccelerated systems analysis approachesDiscovery PrototypingRapid Architected AnalysisDiscovery PrototypingDiscovery prototyping – a technique used to identify the users’ business requirements by having them react to a quick-and-dirty implementation of those requirements.AdvantagesPrototypes cater to the “I’ll know what I want when I see it” way of thinking that is characteristic of many users and managers.DisadvantagesCan become preoccupied with final “look and feel” prematurelyCan encourage a premature focus on, and commitment to, designUsers can be misled to believe that the completed system can be built rapidly using prototyping toolsRapid Architected AnalysisRapid architected analysis – an approach that attempts to derive system models from existing systems or discovery prototypes. Reverse engineering – the use of technology that reads the program code for an existing database, application program, and/or user interface and automatically generates the equivalent system model.Requirements Discovery MethodsRequirements discovery – the process, used by systems analysts of identifying or extracting system problems and solution requirements from the user community. Approaches include:Fact-finding – the process of collecting information about system problems, opportunities, solution requirements, and priorities. Sampling of existing documentation, reports, forms, databases, etcResearch of relevant literatureObservation of the current systemQuestionnaires and surveysInterviewsRequirements Discovery Methods (con’t)Joint requirements planning (JRP) the use of facilitated workshops to bring together all of the
View Full Document