(r15) CSC340SylF2021 < CenterForComputing

Tags: view all tags
%INCLUDE{CSC340ForSyllabus}%

---++Details
   * Professor:  Dr. Cathy Bareiss
   * Office SB 031
   * Class Time: TR 9:30-10:20
   * Lab Time: R : 2:00-4:50
   * Class Location:  S 030
   * Lab Location: S 030
   * Textbook: Membership in ACM

---++Course Content
---+++Policies
   * [[AcceptableWork][Integrity]]
   * [[LatePolicy ][Late work ]]
   * [[SoftwareStandards ][Software Standards]]
   * [[SoftwareDevelopmentReport ][Software Development Report]]:  A sample software development report: [[https://twiki.betheluniversity.edu/pub/CenterForComputing/WebHome/SDRDemo1.pdf][Sample SDR report]]
---+++Assignments
   * The majority of the assignments will be the group work.  Grades will be given throughout the semester and there will be a combination of a group grade and individual grade

---+++Grades
   * Project work is worth 60% of the final grade, with the group grade being 30% and individual grades being 30%
   * Exams are worth 40% with the cumulative final being weighted twice a normal exam
   * If the need arises for additional homework, these number may be adapted
   * Grade scale
      * 93% <= average <= 100% ->	A
      * 90% <= average < 93% ->	A-
      * 87% <= average < 90% ->	B+
      * 83% <= average < 87% ->	B
      * 80% <= average < 83% ->	B-
      * 77% <= average < 80% ->	C+
      * 73% <= average < 77% ->	C
      * 70% <= average < 73% ->	C-
      * 67% <= average < 70% ->	D+
      * 63% <= average < 67% ->	D
      * 60% <= average < 63% ->	D-
      * 0% <= average < 60% ->	F

---+++Tentative Schedule
| *Tuesday*             | *Thursday*            | *Thursday: Lab*       |
| 8/17:                 | 8/19: Topic:  Course, overview of S.E.<br>Lesson for flipped classroom: Introduction to Agile Software Development course in !SkillSoft               | 8/19: Introduction of project and setting up teams and starting the work |
| 8/24:  Discussion of Introduction<br>Where should we be doing next?               | 8/26:                 | 8/26: |
| 8/31:                 | 9/2:                  | 9/2: |
| 9/7:                  | 9/9:                  | 9/9: |
| 9/14:                 | 9/16:                 | 9/16: |
| 9/21:                 | 9/23:  Pair programming and individual contracts                | 9/23: |
| 9/28: Service Day  | 9/30:   review and 2 presentations              | 9/30: CCSC:MW |
| 10/5: Exam 1                | 10/7:  fall break               | 10/7:  Fall Break |
| 10/12:  final presentations and decision matrices              | 10/14:                | 10/14: |
| 10/19:                | 10/21:                | 10/21: |
| 10/26:                | 10/28:                | 10/28: |
| 11/2:                 | 11/4:  tasks assigned<br>Database items              | 11/4: |
| 11/9:  Backlogs current<br>Testing Overview        | 11/11: Software metrics<br>Creating interface designs           | 11/11: |
| 11/16:  Testing 1 & 2<br>Testing 3 & 4         | 11/18:  Risks              | 11/18: |
| 11/23:   PHP<br>Trelio              | 11/25: Thanksgiving Break | 11/25: Thanksgiving Break |
| 11/30:  HTML guidelines<br>Accessibility              | 12/2: Rolling out software          | 12/2: Project presentations |
| 12/7: Final Exam week | 12/9: Final Exam:<br> 8:00-10:00      | 12/9:Final Exam week |
---+++Things learned
   1. What is agile?
      a. A software engineering methodology
      a. Based on team work
      a. Incremental process for developing software
      a. Adjustable based on
         * Users feedback
         * Situational changes
         * Discovery of roadblocks
      a. Characterize by sprints which are short term efforts always resulting in working software
      a. The twelve principles of agile (https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/)
      a. The four core values of agile are:
         * individuals and interactions over processes and tools;
         * working software over comprehensive documentation;
         * customer collaboration over contract negotiation; and.
         * responding to change over following a plan.
   1. How one "does" Agile (and/or its components)
      a. A backlog which is a list of tasks to be performed
      a. A sprint is composed of:
         * A meeting to determine the tasks of that sprint and assigning them to team members
         * "Regular" scrum meetings (daily in the real world)
            * short (often less than 15 minutes) and often done standing to ensure it is short
            * 3 questions answered by each team member:  What has been done since the last scrum meeting; What needs to be done by the next scrum meeting, What are any real/potential roadblocks to getting the work done.
         * A review which is where the team presents the working software developed during the spring
         * A retrospective meeting where the team reflects on its agile techniques (not the product)
   1. The makeup of an agile team
      a. Roles should be easily swapped to anyone on the team (few if any irreplaceable members)
      a. User/product owner is essential to the team.  However, there was limited experience of this on our project
   1. The components of a backlog
      a. A list of prioritize tasks whose priority can change
      a. Who is responsible for what
   1. Additional software engineering techniques
      a. pair programming
      a. the four L's for a retrospective
      a. code review
      a. reading ER diagrams
      a. UML diagrams, specifically: use cases, sequence, activity
      a. decision matrix
      a. Pert and Gantt charts
      a. User interface characteristics




%INCLUDE{CampusPolicies2021}%
Topic revision: r15 - 2021-11-04 - cathybareiss