Coding · 1st Year · Software Development and Collaboration · 4.º Período

The Software Development Life Cycle

Explore the stages of software development, from initial design and prototyping to testing and evaluation.

TL;DR:The Software Development Life Cycle (SDLC) is the process used by professional programmers to build high-quality software. It involves several stages: planning, designing, coding, testing, and evaluating. This topic teaches students that coding is only one part of a much larger project.

• NCCA Curriculum Specifications
• NCCA Coding Strand 3: 3.5
• NCCA Coding Strand 3: 3.6

About This Topic

The Software Development Life Cycle (SDLC) is the process used by professional programmers to build high-quality software. It involves several stages: planning, designing, coding, testing, and evaluating. This topic teaches students that coding is only one part of a much larger project.

In the NCCA framework, this aligns with Strand 3, focusing on the design and development process. Students learn to think about user needs and plan their solutions before they start typing. This topic is best explored through active learning, as it allows students to experience the different roles and stages of a project. Students develop a deeper understanding of the process through collaborative problem-solving and peer review.

Key Questions

1. What are the phases of software development?
2. Why is planning crucial before coding?
3. How do user needs shape software design?

Watch Out for These Misconceptions

Common Misconception

Coding is the most important and longest part of making software.

What to Teach Instead

In reality, planning and testing often take much more time. Using a 'time-tracking' activity during a project helps students see that 'thinking' and 'fixing' are just as vital as 'typing'.

Common Misconception

You only test the software once it is completely finished.

What to Teach Instead

Testing should happen at every stage. A 'bug-hunt' activity on early prototypes helps students realize that finding errors early saves a lot of work later on.

Active Learning Ideas

Simulation Game

The App Factory

Divide the class into 'departments' (Design, Coding, Testing). A 'client' (the teacher) gives a simple request. The project must pass through each department, with students experiencing how a lack of planning in 'Design' makes 'Coding' impossible.

60 min·Whole Class

Inquiry Circle

User Persona Design

Groups are given a 'user' (e.g., a grandmother who wants to video call her grandkids). They must design the interface of a simple app for her, focusing on her specific needs before they even think about the code.

40 min·Small Groups

Gallery Walk

Prototype Parade

Students create paper prototypes of a simple game or app. They display them, and 'users' (other students) try to 'click' the paper buttons. The 'developers' take notes on where the users get confused.

45 min·Small Groups

Frequently Asked Questions

What are the stages of the SDLC for 1st Years?

Keep it simple: 1. Plan (What are we making?), 2. Design (What will it look like?), 3. Code (Build it!), 4. Test (Does it work?), and 5. Evaluate (How can we make it better?). This five-step process is easy to remember and apply to their own projects.

Why is planning so important in coding?

Planning helps you avoid 'spaghetti code' and logic errors. It is like having a blueprint before you build a house. If you just start building without a plan, you might forget the stairs or put the front door on the second floor!

How can active learning help students understand the SDLC?

The SDLC can feel like a dry list of steps. Active learning, like the 'App Factory' simulation, turns it into a lived experience. When students see how a bad design makes the 'coders' frustrated, or how 'testers' find bugs they never expected, they internalize the value of each stage in a way that a lecture simply cannot achieve.

What is a 'prototype'?

A prototype is a simple, early version of a product used to test an idea. In coding, this can even be a 'paper prototype' where you draw the screens of an app on paper to see if the layout makes sense to a user.