Chapter 10 Study Notes: Software Programming & System Development


These study notes are structured for active recall and self-testing in Knowt. They cover the fundamental concepts of software programming, software customization, information system components, and the step-by-step System Development Life Cycle (SDLC). Use the embedded self-test prompt boxes after reading each section to verify your memory before checking the answers.

1. The Importance of Programming & Software Customization

Programming is the process of translating a task into a series of commands that a computer CPU can execute. While many students assume coding is only relevant for full-time software developers, understanding programming fundamentals provides immense value to general users and business professionals by enabling software customization and task automation.

Why Create or Customize Software?

Most everyday computer tasks are adequately handled by pre-packaged software products. However, existing software cannot solve every specialized real-world problem. In situations where an existing application does not meet a specific operational requirement, custom software must be developed.

Off-the-Shelf Software: Commercial applications built for general public use (such as word processors, spreadsheets, or standard web browsers). They offer broad functionality but cannot be easily tailored to unique, highly specific workflows.

Custom Software Solutions: Purpose-built programs created from scratch or modified to address specialized tasks. For example, a farmer requiring a drone to fly a specific geographic flight pattern, inspect crops, take automated sensor readings, and compile a weekly report needs a custom software program because no pre-made commercial tool provides that exact combination of hardware control and reporting.

Automating Repetitive Tasks with Macros

For users who rely primarily on off-the-shelf software, basic programming concepts allow for powerful task automation without writing entire applications from scratch.

Macro Definition: A macro is a custom-built mini-program that executes a complex sequence of commands using a single action or shortcut.

Macros allow users to automate repetitive, multi-step procedures within off-the-shelf productivity suites like Microsoft Word and Microsoft Excel. By recording or writing a macro to handle recurring formatting, data entry, or calculation routines, users save significant time and eliminate manual errors.

Key Comparison: Off-the-Shelf vs. Custom Software

To choose the right software approach, developers and organizations evaluate the trade-offs between pre-built tools and custom development:

Feature

Off-the-Shelf Software

Custom Software Solutions

Primary Audience

General public or broad business markets

Specialized users or specific organizational needs

Development Cost

Lower upfront cost per user

Higher initial investment in programming and design

Customization

Limited to built-in settings and macros

Unlimited flexibility tailored to exact operational goals

Deployment Time

Immediate installation and availability

Requires full development life cycle before release

Example Scenario

Using Microsoft Excel for general budgeting

Programming an agricultural drone for automated crop inspection

Active Recall Self-Test: Section 1

What is the primary difference between off-the-shelf software and a custom program?

How is a macro defined, and what is its main function in tools like Word or Excel?

Why would a non-programmer benefit from understanding basic coding concepts?

2. Information System Foundations & The System Development Life Cycle (SDLC)

Complex software applications do not exist in isolation; they operate within larger organizational frameworks known as information systems. Developing reliable information systems requires a structured, orderly process to ensure the final product meets user requirements and functions without critical errors.

The 5 Components of an Information System

An information system is a complete collection of elements working together to accomplish a common goal, gather data, process information, and support decision-making. Every information system consists of five essential components:

Data: Raw, unprocessed facts, numbers, and inputs entered into the system.

People: End users, system administrators, and developers who interact with or maintain the system.

Procedures: The rules, policies, and instructions that govern how data is collected, processed, and managed.

Hardware: Physical computer equipment, processors, storage devices, and networking infrastructure.

Software: Operating systems and application programs that process inputs into meaningful outputs.

The 6 Stages of the SDLC (Waterfall Model)

To build information systems systematically, development teams follow the System Development Life Cycle (SDLC). The traditional SDLC model is known as the Waterfall model because each stage must be completed sequentially before the project flows down into the next step.

Problem and Opportunity Identification: Corporations and development committees evaluate incoming project proposals to decide which problems or market opportunities are worth pursuing based on available funding and personnel.

Analysis: Systems analysts examine the chosen problem in depth to define user requirements and produce a formal Program Specification document outlining project goals and feasibility.

Design: System architects create detailed blueprints for programmers. This stage relies on Flowcharts (visual diagrams of logical decision points) and Data-Flow Diagrams (DFDs), which visually trace how data enters the system, travels through processing steps, and reaches storage or output.

Development: Programmers write, document, and revise the actual source code based on the design specifications.

Testing and Installation: Technical staff rigorously test the software to detect and repair bugs, ensuring it operates correctly before installing it for official end-user operation.

Maintenance and Evaluation: Analysts monitor ongoing system performance, fix unpredicted errors, and evaluate new feature requests from users over time.

SDLC Challenges & Alternative Methodologies

While the traditional Waterfall model provides a clear, structured sequence, its rigid nature presents significant project risks.

Scope Creep: An uncontrolled phenomenon where clients continuously request new features and changes while waiting for system delivery, leading to severe schedule delays and budget overruns.

Because Waterfall delays working prototypes until late in the development cycle, modern software teams often adopt alternative SDLC methodologies:

Agile Methodology: An iterative, feature-driven development process where small, functional pieces of software are built and tested frequently, allowing teams to adapt quickly to changing user demands.

Rapid Application Development (RAD): A strategy centered on constructing working prototypes in parallel. By gathering early user feedback on interactive prototypes, RAD reduces development time and minimizes scope creep.

Methodology

Structural Approach

Key Advantage

Best Fit

Waterfall Model

Rigid, linear 6-stage sequence

Clear milestones and thorough upfront documentation

Predictable projects with fixed requirements

Agile Methodology

Iterative cycles with frequent testing

High adaptability to changing customer needs

Dynamic projects requiring regular feature updates

Rapid Application Development (RAD)

Parallel prototype creation

Fast user feedback and reduced development timeline

Projects prioritizing rapid deployment and user testing

Active Recall Self-Test: Section 2

What are the 5 components that comprise an Information System?

What are the 6 stages of the SDLC Waterfall model in chronological order?

What is the difference between a Flowchart and a Data-Flow Diagram (DFD)?

What is scope creep, and how do Agile and RAD methodologies attempt to solve it?

3. High-Yield Review & Active Recall Master Checklist

Before completing your study session in Knowt, test your recall against these fundamental terms and core concepts from Chapter 10:

Macro: Custom mini-program executing multiple commands via a single shortcut action.

Custom Software: Tailored applications built when off-the-shelf software cannot meet specialized needs.

Information System: Integrated collection of Data, People, Procedures, Hardware, and Software.

Waterfall SDLC: Sequential 6-step life cycle (Identification, Analysis, Design, Development, Testing/Installation, Maintenance/Evaluation).

Program Specification: Formal document generated during Analysis defining project objectives and requirements.

Data-Flow Diagram (DFD): Visual design diagram tracing data movement from input to processing, storage, and output.

Scope Creep: Project expansion and delay caused by ongoing user feature requests during development.

Agile Methodology: Iterative, feature-driven approach relying on continuous testing and fast adaptation.

Rapid Application Development (RAD): Prototype-centered approach running parallel build cycles for quick user feedback.