Citizen developer (Textbook, Ch. 10): A non‑IT employee who builds applications using approved low‑code/no‑code tools. Example: A manager creating a workflow app with Power Apps.
Low‑code / no‑code (LCNC) environment (Textbook, Ch. 10): Visual development platforms that reduce or eliminate traditional programming. Example: Building apps with drag‑and‑drop tools.
Programming language (Textbook, Ch. 10): A formal language used to write instructions a computer can execute. Example: Python or Java.
Product owner (Textbook, Ch. 10): The role responsible for defining requirements and prioritizing features. Example: Choosing bug fixes over new features.
Feature creep (scope creep) (Textbook, Ch. 10): Uncontrolled addition of requirements during development. Example: Adding new features without extending deadlines.
Compliance (Textbook, Ch. 10): Meeting legal, regulatory, and ethical requirements. Example: Ensuring HIPAA compliance.
Agile methodology (Textbook, Ch. 10): An iterative approach emphasizing flexibility and frequent feedback. Example: Releasing updates every two weeks.
Waterfall methodology (Textbook, Ch. 10): A linear development approach where each phase must be completed before the next. Example: Completing design before coding begins.
Prototype (Textbook, Ch. 10): A mock‑up used to gather feedback before full development. Example: Clickable wireframes.
Total cost of ownership (TCO) (Textbook, Ch. 10): All costs over a system’s lifetime, not just development. Example: Training and support costs.
Triple constraint (Textbook, Ch. 10): The balance between time, cost, and scope in project management. Example: Adding features increases time or cost.
Software development lifecycle (SDLC) (Textbook, Ch. 10): The process of moving from idea to deployed system. Example: Requirements → Design → Testing.
Software development methodologies (Textbook, Ch. 10): Frameworks for managing the SDLC, such as Agile and Waterfall. Example: Choosing Agile for flexibility.
Brooks’ Law (Textbook, Ch. 10): Adding people to a late project makes it later. Example: New hires slowing progress.
Technical debt (Textbook, Ch. 10): Future costs caused by development shortcuts. Example: Messy code delaying future updates.
Requirements (Textbook, Ch. 10): Clear descriptions of what a system must do. Example: “Transfers must complete in under 3 seconds.”
A non‑IT employee builds an app using a visual tool. This is:
Adding features mid‑project without extending time or budget is called:
Insecure handling of healthcare data illustrates:
Frequent releases with ongoing feedback describe:
Why is the product owner critical?