Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/seba-1511/colloquium_310

Files created for the colloquium
https://github.com/seba-1511/colloquium_310

Last synced: 11 days ago
JSON representation

Files created for the colloquium

Awesome Lists containing this project

README

        

# Colloquium 310

This repository will contain all summaries produced for the second part of lecture _Software Engineering_, CSCI 310.

## List of Lectures

The list of covered by those summaries, as well as who worked on them.

Lecture Title | Lecture n° | Authors | Link
----------------------------|------------|-------------------------------------|------
Software Process Models | 12 | Jenny (S) | [link](http://www.github.com/seba-1511/colloquium_310/blob/master/summaries/)
Agile Development | 13 | Matthew (W) | [link](http://www.github.com/colloquium_310/blob/master/summaries/)
Cleanroom Dev Process | 14 | ? | [link](http://www.github.com/seba-1511/colloquium_310/blob/master/summaries/)
Black-box Testing | 15 | Kelsey (T) | [link](http://www.github.com/seba-1511/colloquium_310/blob/master/summaries/BBTesting.md)
White-box Testing | 16 | Anthony (Th) | [link](http://www.github.com/seba-1511/colloquium_310/blob/master/summaries/)
Regression Testing | 17 | Pavel(F) | [link](http://www.github.com/seba-1511/colloquium_310/blob/master/summaries/)
Fault Localization | 18 | Justine (Th) | [link](http://www.github.com/seba-1511/colloquium_310/blob/master/summaries/)
Architectural Styles | 19 | Seb (S) | [link](http://www.github.com/seba-1511/colloquium_310/blob/master/summaries/)
Design Patterns | 20 | Seb (T) | [link](http://www.github.com/seba-1511/colloquium_310/blob/master/summaries/DesignPatterns.md)
Secure Software Engineering | 21 | Daler (F) | [link](http://www.github.com/seba-1511/colloquium_310/blob/master/summaries/)

## Presentation Guidelines

In the span of one hour, we should be able to be able to summarize 2 weeks of lectures. This means about 30 minutes per lecture and thus we should focus on important or advanced concepts as student will be familiar with the basic ones. The idea is that people presenting are experts in their respective lecture and share their knowledge. To have a good idea of what the presentation should be about, check the last slide of every lecture.

### Suggested structure:

* Important Concept 1:
* What it is about ?
* How it fits in the
* Why it is important.
* How does it differ from other concepts we’ve seen ?

* Repeat for every concept

The way I worked through the Design Pattern lecture was to first decide if a slide was important or not, and if it was then imagine what were the possible questions about it.

## Other Resources

A summary built by other team members of the class: [Available here](https://docs.google.com/a/usc.edu/document/d/1Sq-aJOKIpdxkiEUAWjD4DB6DqkHIuCB2MMWoevIOm-Q/edit?usp=sharing_eid)