Software Development Life Cycles (Activity)

(Difference between revisions)
Jump to: navigation, search
(Created page with "__NOTOC__ === Overview === {{Learning Activity Overview |title= Software Development Life Cycles (Activity) |overview= This POGIL activity explores ways to organize 4 categ...")
 
Line 70: Line 70:
 
[[Category:Communication]]
 
[[Category:Communication]]
 
[[Category:Teamwork]]
 
[[Category:Teamwork]]
[[Category:Ready To Use]]
+
[[Category:Ready to Use]]

Revision as of 13:49, 8 September 2018


Overview

Title

Software Development Life Cycles (Activity)

Overview

This POGIL activity explores ways to organize 4 categories of activities (analysis, design, coding, testing) into a software development process or life cycle (SDLC). This parallels how an animal is born, matures, and dies.

Prerequisites
  • Some experience with software development projects and some knowledge of the 4 categories of software development activities.
Learning
Objectives
After successfully completing this activity, the learner should be able to:
  • Describe common SDLC models (WaterFall, Iterative, Spiral, Agile), and their advantages & disadvantages.
Process Skills
Practiced

Information Processing, Critical Thinking, Communication, Teamwork


Background, Directions, Deliverables

See details in the Student version of the POGIL activity.

Notes for Instructors

See details in the Teacher version of the POGIL activity.

Assessment

  • How will the activity be graded?
  • How will learning will be measured? Ideally, there should be a way to measure each of the objectives described above.
  • How will feedback to the student be determined?

This is a classroom POGIL activity, so all teams should complete it in class with correct answers. Thus, the activity is typically not graded, but there might be related quiz or exam questions later.

Suggestions for Open Source Community

N/A

Additional Information

ACM BoK
Area & Unit(s)
ACM BoK
Topic(s)
Difficulty

easy

Estimated Time
to Complete

1 hour

Environment /
Materials

paper activity (1-2 per team or 1 per student) or Google Doc activity (1 per team)

Author(s)

Clif Kussmaul

Source

http://cspogil.org/Software+Engineering (for sample version)

License

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License

Creativecommons-by-nc-sa-40.png



Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox