Skip to content
Snippets Groups Projects
Commit 9f22af8a authored by Christopher Bohn's avatar Christopher Bohn :thinking:
Browse files

added syllabus for Fall 2019

parent d102177a
Branches CSCE361-1198
No related tags found
No related merge requests found
Show whitespace changes
Inline Side-by-side
TA.tex 0 → 100644
+ 26
− 0
View file @ 9f22af8a
gitlab username: @bohn
\section*{TAs}
\begin{tabular}{|l|c|l|l|l|}
\hline
Name & G/U & Office Hours & email & gitlab username \\ \hline
Jianghao Wang & GTA & T 10:00-11:00; R 9:00-10:00 & jianghaow@cse.unl.edu & @jh \\ \hline
Joey Ballentine & UTA & W 7:00-9:00pm & jballentine@cse.unl.edu & @joeyballentine \\ \hline
Christian Berck & UTA & W 10:30-12:30 & cberck@cse.unl.edu & @christian \\ \hline
Utkarsh Hardia & UTA &
\begin{tabular}{l}
T 3:30-5:30; W 3:30-5:00; \\ R 9:45-11:15
\end{tabular}
& uhardia@cse.unl.edu & @utkarshhardia23 \\ \hline
Ryan Le & UTA & M 10:30-12:30 & rle@cse.unl.edu & @ryanle \\ \hline
\end{tabular}
\\
TA office hours are in the Student Resource Center (SRC) in Avery 012 or in the Computer Lab in Avery 015.
% \section*{TA}
% \begin{tabular}{lp{1cm}l}
% Rubi Qui\~nones && \\
% Avery 122 && \\
% rquinones@cse.unl.edu && \\
% Office Hours: MTW 9:00-10:00, RF 2:00-3:00
% \end{tabular}
grading.tex 0 → 100644
+ 27
− 0
View file @ 9f22af8a
\section*{Grading}
Your grade will be calculated based on your performance in the following areas: \\ \textbf{Note: Final grading may deviate from these percentages; however, no student's grade will be lower than what it would be with these percentages.}
\begin{itemize}
\item \textit{Lesson Preparation Assessments (LPAs)} (5\%) We cannot cover all of the lecture material unless you have read the assigned reading material before class. To encourage you to do so, we will assign simple open-book assessments through Canvas for you to demonstrate knowledge-level understanding of the assigned readings. Each LPA will be due before the start of class.
\item \textit{Setup and In-Class Activities} (5\%) There will be a couple of assignments to set up tools we'll use in class, and there will be a few in-class activities. Setting up the tools and participating in the in-class activities should be easy points for tasks that you'll do anyway.
\item \textit{Individual Assignments} (20\%) There will be individual homework assignments to help cement the concepts from the lecture and the textbook. Because group study is an effective learning technique, I encourage you to work with your peers to discuss the homework at a conceptual level, but \textbf{you must arrive at your own solutions and indicate whom you worked with}.
\item \textit{Pair Assignments} (20\%) There will be assignments in which you work with one other student to help cement the concepts from the lecture and the textbook and to help you gain experience developing software in cooperation with others. You will have a different partner for each pair assignment.
\item \textit{Exams} (20\%) We will have two exams during the semester. These exams will be conducted at the DLC scheduled for \textbf{October 8-10} and \textbf{November 19-21}. \textit{Unless I explicitly specify otherwise, the exams will be closed book/closed note/closed neighbor; and laptops, tablets, and smartphones will be disallowed.} Electronic translators and bilingual dictionaries may be used.
\item \textit{Capstone Assignment} (20\%) At the end of the course will be a group project in which you will have the opportunity to practice most of what you learned by preparing the artifacts for a small software system that you and your team of 3-4 students will develop. In addition to code, you will demonstrate your ability to work on a team and your ability to communicate in both written and oral forms.
\item \textit{Team Contribution} (10\%) A significant portion of your grade will be based on how well you contribute to team efforts in the pair assignments and in the capstone assignment. Assessment will be based off of peer evaluations, git history, and observation by the instructional team. Obviously a student who chooses not to make an equitable contribution to an assignment will score poorly; however, students who choose to ``do it all themselves'' and prevent others from contributing are also failing to demonstrate their ability to work on a team.
\textbf{Note:} Performance in the individual and pair assignments will inform placement on capstone teams. I will attempt to construct balanced teams of A-level, B-level, and C-level contributing performers. However, I reserve the right to form a capstone team of habitual non-contributors.
\item Final grades will be assigned based on the traditional cutoff percentages.
\begin{tabular}{|c|c|c|c|c|c|c|c|c|c|c|c|c|c|} \hline
Grade & A+ & A & A- & B+ & B & B- & C+ & C & C- & D & F \\ \hline
Score & 97 & 93 & 90 & 87 & 83 & 80 & 77 & 73 & 67 & 60 & \textless 60 \\ \hline
\end{tabular}
\begin{itemize}
\item \textit{Rounding of final grades} I am not in the habit of \textit{giving} grades, but I am sympathetic to students who put in effort. In lieu of rounding, after calculating each student's score and adding extra credit points, I will make one final adjustment to scores near a letter-grade cutoff:
\[adjustment = \left\{\begin{array}{cl}
0.50 & \mathrm{if\ all\ assignments\ completed} \\
0.005 \times \tiny{number\_of\_assignments\_completed} & \mathrm{otherwise}
\end{array}\right.\]
\end{itemize}
\end{itemize}
schedule.tex 0 → 100644
+ 5
− 0
View file @ 9f22af8a
\section*{Schedule}
Lecture
\begin{itemize}[noitemsep]
\item Section 002: MWF 2:30pm-3:20pm in Avery Hall 115
\end{itemize}
sequence.tex 0 → 100644
+ 51
− 0
View file @ 9f22af8a
\section*{Notional Sequence}
\begin{tabular}{rcl}
\textbf{Notional Lesson \#} & \textbf{Topic} & \textbf{Chapter} \\ \hline
01 & Introduction & 1 \\
02 & Software Lifecycle & 2.1-2.5.3 \\
03 & JUnit, Blackbox Testing &
\multirow{3}{*}{$\left. \begin{array}{l}
\\ \\ \\ \end{array}\right\}$ 3, 20} \\
04 & Configuration Control 1 & \\
05 & Whitebox Testing & \\
06 & Improving Test Benefits & \\
07 & UML &
\multirow{3}{*}{$\left. \begin{array}{l}
\\ \\ \\ \end{array}\right\}$ 5, 9, 11} \\
08 & Diversity & \\
09 & Domain Modeling \& Detailed Design & \\
10 & Software Architecture, Design Patterns & 6, 10 \\
11 & Code Reading, Thinking Ahead & \\
12 & Code Styles, Effective Comments & 18.1-18.4 \\
13 & Good/Bad Practices, Refactoring & \\
14 & Maintenance, Regression Testing & 21 \\
15 & Code Reviews & 19.4 \\
16 & Pair Programming \& TDD & 18.5-18.7 \\
17 & Business Communications & \\
18 & Exam Review & \\
19 & Wireframes, Mockups, \& Prototypes & 12 \\
20 & Configuration Control 2 & 22 \\
21 & Human Performance Testing & \\
22 & Requirements Elicitation & 4 \\
23 & Traditional Requirements, Use Cases & 7, 8 \\
\multicolumn{3}{c}{No class October 21-22} \\
24 & User Stories, Story Mapping & \\
25 & V\&V of Other Artifacts & 19 \\
26 & Ethics & \\
27 & Safety & \\
28 & Security & 24 \\
29 & Privacy, Accessibility & \\
30 & Meetings & 23 \\
31 & Database Design, ORM, \& Testing & \\
32 & Cloud Services, SOA & \\
33 & Incremental Development &
\multirow{2}{*}{$\left. \begin{array}{l}
\\ \\ \end{array}\right\}$ 2.5-2.8} \\
34 & Agile Development & \\
35 & Exam 2 & \\
\multirow{2}{*}{36-44}
& Capstone Project & \\
& and JIT \& Makeup Lessons & \\
\multicolumn{3}{c}{No class November 27-29} \\
\end{tabular} \\
\textbf{Note:} Because the capstone project replaces the final exam, I am exercising the clause in the university's \href{https://registrar.unl.edu/academic-standards/policies/fifteenth-week-policy/}{Fifteenth Week Policy} that allows ``if the instructor is replacing the final exam with either a project, paper, or speech, the due date for the assignment can be any time during the 15th week or during finals week.'' Most capstone project presentations will occur during Finals Week.
syllabus.pdf 0 → 100644
+ 0
− 0
View file @ 9f22af8a
File added
syllabus.tex 0 → 100644
+ 23
− 0
View file @ 9f22af8a
\documentclass[12pt]{article}
\usepackage{fullpage}
\usepackage{hyperref} \hypersetup{colorlinks=true}
\usepackage{enumitem}
\usepackage{multirow}
\usepackage[yyyymmdd]{datetime}
\raggedright
\begin{document}
\title{CSCE 361: Software Engineering}
\author{Fall 2019}
\date{}
\maketitle
\input{schedule}
\input{../../syllabus-boilerplate/instructor}
\input{TA}
\input{../../syllabus-boilerplate/textbook-csce361}
\input{../../syllabus-boilerplate/description-csce361}
\input{sequence}
\input{grading}
\input{../../syllabus-boilerplate/policies}
\vspace{1in}
Last updated: \currenttime-\today
\end{document}
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment