Software Design Architecture Comparison

From Foss2Serve
Revision as of 22:16, 4 February 2016 by Nyeates (Talk | contribs)
Jump to: navigation, search
Title Software Design and Architecture Comparison (Eclipse vs Openstack)
Overview Students will research existing software design documents and resources for both projects and then write a report detailing their differences and helpfulness to various levels of developers.
Prerequisite Knowledge Students should have:
  • Taken a CS1 course (Introduction to Programming).
    • Already learned syntax and the basics of a programming language.
    • Already learned simple data structures.
  • Rudimentary software design knowledge
    • Could be delivered along-with this activity
    • Ex: Design Patterns knowledge
Learning Objectives Upon completion, students should:
  • Understand how thoughtful software design is encouraged, or not, in open source communities.
  • Be able to give examples of software design artifacts, and how to go about finding them.
  • Realize what they consider good software design, and be able to back it up with reason.
  • Realize why software design is important, and how it will effect them in their future careers.


Is there background reading material?

What is the rational for this activity?

For students, who are often novice and beginner developers, it is critical to understand the big-picture when jumping into a new software project. A proper view of the system-wide architecture can bring context on how the entire system works, instead of focus on a particular component. When you can have knowledge of other pieces of the puzzle, you tend to implement better code because it is thoughtful of how your current focus interacts with functionality around it and even to functionality seemingly far-removed. Students need to be aware of why this helps them and their career, how to find this kind of documentation, and that it might shape their opinions and focus when choosing projects to interact with.

Are there any similar activities?

See OpenMRS_Design_Reverse_Engineering_Activity_(Android_App) for an activity that has students reverse engineer a design / architecture from an existing open source Android applications codebase.

Background reading:


Part 1: Software design background

Bacon ipsum dolor amet tail swine fatback short loin venison, flank boudin. Boudin kevin landjaeger pork loin drumstick. Fatback biltong swine spare ribs, pig hamburger jowl leberkas pork belly. Beef jerky meatloaf, chuck swine tail pork chop shank jowl cupim strip steak salami.

Chuck swine flank beef, strip steak ham hock short ribs capicola doner salami tongue beef ribs. Filet mignon strip steak ball tip pork loin beef ribs spare ribs pork chop picanha kielbasa meatball boudin landjaeger. Venison tongue rump sausage biltong pork belly kevin t-bone prosciutto corned beef. Jowl frankfurter ground round pastrami pork chop swine tri-tip porchetta landjaeger. Pork belly pig shank ribeye.

Part 2: Comparison


What will the student hand in?


How will the activity be graded?

How will learning will be measured?

Include sample assessment questions/rubrics.

Criteria Level 1 (fail) Level 2 (pass) Level 3 (good) Level 4 (exceptional)
The purpose of the project
Why the project is open source


What should the instructor know before using this activity?

What are some likely difficulties that an instructor may encounter using this activity?

Additional Information:

ACM Knowledge Area/Knowledge Unit What ACM Computing Curricula 2013 knowledge area and units does this activity cover? ACM_Body_of_Knowledge
ACM Topic What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics -
Level of Difficulty Is this activity easy, medium or challenging?
Estimated Time to Completion How long should it take for the student to complete the activity?
Materials/Environment What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?
Author Nick Yeates
Source Is there another activity on which this activity is based? If so, please provide a link to the original resource.
License Creative Commons CC-BY

Suggestions for Open Source Community:

Suggestions for an open source community member who is working in conjunction with the instructor.

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


Note: Can be removed later, or kept as a resource to teaches looking into other communities.

Software design - Potential communities to look into:

Personal tools
Learning Resources
HFOSS Projects