13. System Development

System development turns organizational needs into working systems. This chapter introduces requirements, design, and testing as disciplined ways to reduce bad requirements, poor usability, buggy systems, and weak controls.

Video

How Does Application Security Fit Into the SDLC? by IBM Technology

This video is embedded from YouTube for course reference. It remains hosted by YouTube and belongs to its creator or rightsholder.

Learning Objectives

By the end of this chapter, you will be able to:

1. Translate an organizational need into scoped, prioritized, and verifiable requirements.

2. Connect architecture and usability choices to actual user tasks and exceptions.

3. Compare life-cycle, iterative, agile, and low-code/no-code approaches.

4. Distinguish verification, validation, acceptance, conversion, and ongoing maintenance.

Concept Map

System Development

Requirements

• Users
• Problems
• Scope

Design

• Processes
• Interfaces
• Controls

Testing

• Bugs
• Usability
• Acceptance

Glossary

#	Term	Explanation
1	Systems development	The process of analyzing, designing, building, testing, deploying, and maintaining information systems.
2	Organizational change	A shift in work, roles, processes, or structures caused or supported by a system.
3	System analysis	Studying a problem, current process, and requirements before designing a solution.
4	Requirement	A statement of what a system must do or quality it must have.
5	Functional requirement	A required behavior or capability of a system.
6	Nonfunctional requirement	A required quality such as performance, security, usability, reliability, or scalability.
7	Stakeholder	A person or group affected by or able to influence a system.
8	System design	Specifying how a system will meet requirements through data, interface, process, and architecture choices.
9	Prototype	An early version or mockup used to explore requirements or design.
10	Systems development life cycle	A staged approach to planning, building, testing, deploying, and maintaining systems.
11	Agile development	An iterative approach that delivers work in small increments with frequent feedback.
12	DevOps	Practices that connect development and operations to improve delivery and reliability.
13	Low-code development	Building applications with visual tools and limited hand-coded programming.
14	No-code development	Building applications through configuration and visual tools without traditional coding.
15	Testing	Checking whether a system works as intended and meets requirements.
16	User acceptance testing	Testing by users or business representatives to decide whether a system is ready for use.
17	Conversion	Moving from an old system or process to a new one.
18	Maintenance	Ongoing correction, adaptation, and improvement after a system is deployed.
19	Usability	How effectively and comfortably people can use a system to accomplish tasks.
20	Defect	A flaw in requirements, design, code, data, or configuration that can cause failure or poor performance.

Lecture Slides

Chapter 13 Slides

These lecture drafts follow the authored sections and aligned assignments.