1/99
Looks like no tags are added yet.
System Development Life Cycle (SDLC)
The process of determining how an information system can support business needs, designing and building the system, and delivering it to users.
Planning Phase
The SDLC phase where the project is planned and organized.
Analysis Phase
The SDLC phase where the team's goal is to understand the problem and determine what the system needs to do.
Design Phase
The SDLC phase where the team describes how the system will work and how it will solve the problem.
Implementation Phase
The SDLC phase where the system is built and delivered.
Project Initiation
The process of identifying a business need, finding a project sponsor, completing a system request, and submitting it for approval.
Project Sponsor
The person who supports a project and completes the system request for the business need.
System Request
A document submitted for project approval. It includes the project sponsor, business need, business requirements, business value, and special issues.
Project Methodology
The approach used to guide how a project is planned and completed.
Waterfall Development
A development approach where the project team completes each phase before moving on to the next phase.
Rapid Application Development (RAD)
An approach that uses tools to speed up analysis, design, and implementation so users can evaluate the system and provide feedback quickly.
Computer-Aided Software Engineering (CASE) Tools
Software tools that help automate parts of the SDLC and make development tasks faster
Scope Creep
When project requirements continue to expand beyond the original plan.
Agile Development
An approach that focuses on simple, iterative development, short development cycles, and communication with users.
Extreme Programming (XP)
An Agile method where programmers build and test small, simple modules to meet user needs.
Project Management Trade-offs
The decisions involved in balancing the size and features of a system, the time needed to complete it, and the project's cost.
Project Work Plan
A plan that outlines project activities and is updated by the project manager to monitor progress.
Gantt Chart
A horizontal bar chart that visually displays a project's work plan and tasks.
PERT Chart (Program Evaluation and Review Technique)
A flowchart that displays project tasks and the dependencies between them.
Critical Path Method (CPM)
The longest path of dependent tasks from the beginning to the completion of a project. It identifies tasks that must stay on schedule for the entire project to finish on time.
Upper CASE
CASE tools used during the analysis phase to create system diagrams and store information about system components.
Lower CASE
CASE tools used during the design phase to create diagrams and generate code for database tables and system functionality.Requirement
Requirement
A statement describing what a system must do or what characteristics it needs to have.
Business Requirements
Requirements that describe what the business needs.
User Requirements
Requirements that describe what users need to do with the system.
Functional Requirements
Requirements that describe what the software should do.
System Requirements
Requirements that describe how the system should be built.
Requirement Determination (Elicitation)
The process of gathering information to understand and identify the system's requirements.
Interviews
A requirement-gathering technique where analysts ask people questions to understand how a business process works and what the system needs.
Closed-Ended Questions
Questions that have a limited set of possible answers.
Open-Ended Questions
Questions that allow people to explain their thoughts and provide detailed answers.
Probing Questions
Follow-up questions used to get more information or clarify an answer.
Joint Application Development (JAD)
A structured information-gathering technique where the project team, users, and management work together to identify requirements.
Electronic JAD (e-JAD)
JAD sessions that use groupware and electronic tools to help participants work together.
Problem Analysis
A technique that examines problems in the current system and considers how a new system could solve them.
Root Cause Analysis
A technique used to identify the underlying causes of important problems.
Duration Analysis
A technique that measures how much time each process takes in the current system.
Activity-Based Costing
A method used to understand the costs associated with individual business activities.
Informal Benchmarking
Comparing how other organizations perform similar business processes.
Outcome Analysis
A technique that identifies the main outcomes that provide value to customers.
Technology Analysis
Examining how different technologies could be used to improve a business process.
Activity Elimination
Examining whether an activity can be removed from a business process.
Use Case
A set of activities performed by a user to produce an output. It describes how an event triggers actions involving the user and the system.
Use Case Analysis
The process of using use cases to understand a system's functional requirements, exceptions, special cases, and error-handling needs.
Actor
A person, software system, or hardware device that interacts with the system in a use case.
Trigger
An event that causes a use case to begin.
External Trigger
An event caused by something outside the system, such as a customer placing an order.
Temporal Trigger
An event that occurs at a particular time or when a time-based condition is met, such as an e-book becoming overdue.
Preconditions
Conditions or tasks that must be completed before a use case can begin.
Normal Course
The steps followed when everything works as expected during a use case. Also known as the happy path.
Postconditions
The final results or conditions that exist after a use case is completed.
Exceptions
Errors or unexpected conditions that may occur while a use case is being performed.
Happy Path
The normal sequence of steps in a use case when no problems occur.
Use Case Name
A short, descriptive name that explains the goal of the use case.
Use Case Description
A brief explanation of what the use case does and what result it produces.
Use Case Preconditions
Conditions that must be true before the use case starts.
Use Case Postconditions
Conditions that should be true after the use case finishes.
System
A group of related components that work together to achieve a purpose.
Computer Application
A software program that runs on a computing device to perform a specific function or set of related functions.
Information System (IS)
A set of related computer components that collects, processes, stores, and provides information needed to complete business tasks.
Systems Analysis and Design (SA&D)
The tools and techniques used to understand a business need, define a solution, communicate it, build it, and confirm that it meets the need.
Systems Analysis
Activities used to understand and specify what a new system should accomplish. It focuses on what the system must do.
Systems Design
Activities used to describe in detail how a system will work to solve a problem or meet a need.
Project
A planned undertaking with a beginning and an end that produces a specific result.
Systems Development Life Cycle (SDLC)
The entire process of building, launching, and maintaining an information system.
Initiation Phase
The phase where the problem or need is identified and approval to proceed is obtained.
Deployment Phase
The phase where system testing is completed and the solution is released for use.
Information Systems Development Process
The actual approach used to develop a particular information system.
Predictive Approach
A development approach that plans the project phases in advance and generally follows a defined sequence.
Waterfall Model
A traditional development approach that assumes project phases are completed sequentially, with little or no overlap.
Waterfall Model with Overlap
A variation of Waterfall that allows phases to overlap, providing more flexibility and efficiency
V-Model
A Waterfall variation that gives more attention to testing by defining tests during the analysis and design phases.
Adaptive/Iterative Model
A development approach that repeats development activities through multiple cycles until the system is complete.
Spiral Model
An adaptive SDLC approach that repeatedly cycles through development activities until the system is completed.
Unified Process (UP)
An iterative development process in which each cycle generally ends with a release of the system.
Inception
The Unified Process phase where the project's purpose and scope are established.
Elaboration
The Unified Process phase where the project requirements and system architecture are developed in more detail.
Construction
The Unified Process phase where the system is built through development and testing.
Transition
The Unified Process phase where the completed system is delivered to customers or users.
System Prototyping
Creating an early version of a system so users can evaluate it and provide feedback.
Agile Development
A philosophy and set of guidelines for developing systems in environments where requirements may be unknown or change quickly.
Manifesto for Agile Software Development
A set of values that prioritizes responding to change, individuals and interactions, working software, and customer collaboration.
Scrum
An Agile development method identified in the course as one of the popular Agile methods.
Project Initiation
The process of identifying a problem or opportunity and defining the need for a new system.
System Vision Document
A document that helps define the scope of a new system by describing the problem, business benefits, and system capabilities.
Business Benefits
The benefits a project provides to an organization, usually measured in dollars.
System Capabilities
The functions or abilities that the proposed system must provide.
Cost/Benefit Analysis
Comparing estimated project costs with anticipated benefits to determine whether an investment is worthwhile.
Net Present Value (NPV)
The present value of the dollar benefits and dollar costs of an investment.
Break-Even Point
The point in time when the dollar benefits of a project equal its dollar costs.
Payback Period
The amount of time it takes for the benefits of a project to offset its costs.
Tangible Cost/Benefit
A cost or benefit that can be measured or estimated in dollars.
Intangible Cost/Benefit
A cost or benefit that affects an organization but cannot be accurately measured in dollars.
Project Feasibility
An assessment of whether a project can realistically be completed, considering organizational, technological, resource, and schedule factors.
Project Scope Statement
A statement that describes the boundaries and work included in a project.
Work Breakdown Structure (WBS)
A list or hierarchy of a project's activities and tasks, used to estimate the work and create a detailed schedule.
Critical Path
The tasks that must stay on schedule for the overall project to finish on time.
System Development Methodology
A set of comprehensive SDLC guidelines that includes specific models, tools, and techniques.
Model
A representation of an important aspect of the real world. It can represent inputs, outputs, processes, data, objects, and other system components.
Abstraction
Representing important information while leaving out unnecessary details.