1/21
Vocabulary flashcards covering key roles, SDLC phases, methodologies, OOSAD, Agile, and Unified Process concepts from Systems Analysis and Design Chapter 1.
Name | Mastery | Learn | Test | Matching | Spaced | Call with Kai | Chat |
|---|
No analytics yet
Send a link to your students to track their progress
Systems Analyst
A key person who analyzes the business, identifies opportunities for improvement, and designs information systems to implement these ideas.
Business Analyst
A project team role focused on analyzing key business aspects, identifying how the system will provide business value, and designing new business processes and policies.
Infrastructure Analyst
A project team role responsible for ensuring the system conforms to infrastructure standards and identifying required infrastructure changes.
Change Management Analyst
A project team role tasked with developing and executing both a change management plan and a user training plan.
Project Manager
A project team role responsible for managing specialists, developing and monitoring the project plan, assigning resources, and serving as the primary point of contact.
Planning Phase
The SDLC phase focused on determining why to build the system, identifying business value, analyzing feasibility, developing work plans, staffing, and controlling the project.
Analysis Phase
The SDLC phase that determines who, what, when, and where the system will be, comprising information gathering, process modeling, and data modeling.
Design Phase
The SDLC phase that specifies how the system will work, including physical, architectural, interface, database/file, and program design.
Implementation Phase
The final SDLC phase involving system delivery through construction and installation.
Waterfall Development
A structured design methodology where project phases move sequentially from planning to implementation, requiring requirements and designs to be specified on paper before programming.
Parallel Development
A structured design methodology that splits a project into subprojects performed in parallel after design to shorten overall development time before integration.

Rapid Application Development (RAD)
A collection of methodologies (Phased development, Prototyping, Throwaway prototyping) utilizing CASE tools, JAD sessions, fourth-generation/visualization programming languages, and code generators.
Prototyping Methodology
A RAD approach where analysis, design, and implementation occur concurrently to generate system prototypes iteratively until the final system is completed.

Throwaway Prototyping
A RAD approach that uses design prototypes during analysis and design strictly to explore design options before building the actual system.

Object-Oriented Systems Analysis and Design (OOSAD)
A balanced, use-case driven, and architecture-centric methodology that develops systems iteratively and incrementally across functional, structural, and behavioral views.


Agile Development Values
A development philosophy prioritizing individuals and interactions over process and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
Extreme Programming (XP)
An Agile technique built around four core values: Communication (rapid feedback), Simplicity (KISS), Feedback (incremental changes), and Courage (quality-first mentality).
Scrum
An Agile development framework where features are stored in a prioritized product backlog managed by a product owner and developed during iterative cycles called sprints.
DevOps
A development approach that includes operations personnel within the development team and focuses on continuous deployment.

Methodology Selection Criteria
A framework for choosing system development methodologies based on requirements clarity, technology familiarity, system complexity, system reliability, time schedule, and schedule visibility.
Unified Process Phases
The four sequential phases of the Unified Process: Inception, Elaboration, Construction, and Transition.
Unified Modeling Language (UML)
A modeling standard defined by the Object Management Group whose Version 2.5 includes fifteen diagramming techniques classified into structure and behavior diagrams.