Create
Learn
Share

OOP Exam 3 Overview

rename
xazebafe's version from 2017-11-02 13:57

Section 1

Question Answer
Elements of the Development Life CyclePlanning, Analysis, Design, Implementation
System Development MethodologiesStructured Design, Rapid Application Development, Agile Development
System Development methodologies (alternate)Process-Centered, Data-Centered, Object-Oriented
Roles of System AnalystBusiness A, Systems A, Infrastructure A, Change Management A, Project Manager
Skills of System AnalystTechincal, Business, Analytical, Interpersonal, Management, Ethical
Characteristics of Object Oriented System Analysis and DesignUse-case Driven, Architecture-centric, Iterative and Incremental
Benefits of Object Oriented System Analysis and Designlarge problems broken down, easier to grasp and share, reusable parts, new projects don't have to start from scratch
Features of Unified ProcessPHASES: inception, elaboration, construction, transition workflows WORKFLOWS: business modeling, requirements, analysis, design, implementation, test, and deployment
memorize

Section 2

Question Answer
Technical FeasibilityCan we build it? Risk Factors: less familiarity, large projects, compatibility of to-be and as-is systems
Economic FeasibilityShould we build it? Costs: Development, Yearly Benefits: intangible, yearly
Organizational FeasibilityDoes it make sense within the context of our business? Strategic Alignment with business model? Consider management and user roles
memorize

Section 3

Question Answer
What is a Requirement?what a system must have or do; later becomes technical description of system implementation
Types of Requirementsfunctional (data or the process itself) non-functional (performance)
Ways to Determine Requirementsinterviews, questionnaires, observation, joint application development, document analysis
Problems that Arise when Determining Requirementsanalyst may not have access to the right users, requirement specs may not be adequate, missing requirements, verifying/validating requirements can be difficult
Analysis StrategiesProblem A, Root Cause A, Duration A, Activity-based costing, informal benchmarking, outcome a, technology a, activity elimination
Problem Analysisask users to identify problems and how they would solve them
Root Cause Analysisfocus on cause of problem, not the solution
Duration Analysisdetermine time required to complete each step and total time
Activity-Based Costingdetermine cost of each step to total budget
Informal Benchmarkinganalyze similar processes in similar successful organizations
Outcome Analysisdetermine what the customer wants from the system
Technology Analysisidentify benefits of applying new technology to the process
Activity Eliminationeliminate non-essential activities
Requirement Gathering TechniquesInterviews, Joint application development, questionnaire, document analysis, observation, concept map, user stories, system proposal
Types of Interview Questionsclosed-ended (short, concise) open-ended (long and unassisted) probing (elaborate on previous answers)
Joint Application Developmentall levels of the process work together to decide requirements (from user to management)
Questionnaireused with a large population size to determine requirements
Document Analysisanalyze the as-is system to determine requirements
ObservationNick literally wrote "Duh"
Concept Maprepresents meaningful relationships between concepts
User Storiesmodules of the system
System Proposalexecutive summary, system request, work plan, feasibility analysis, requirement definitions, and current model of the system
memorize

Section 4