Software Engineering CMPS 3350 - Fall 2020 Gordon Griesel Office:Sci III 337No office on campus this semester Office Hours: see my schedule, or make an appointment Email: gordon@cs.csub.edu Course web site: https://www.cs.csub.edu/~gordon/3350/ Class meets virtually on Zoom: MWF 11:00am - 11:50am (lecture 81292) Thur 10:20am - 12:30pm (lab 81293) Course Description This course introduces the fundamentals of Software Engineering. From the catalog: This course is a general introduction to Software Engineering. The course will cover the specification, development, management, and evolution of complex software systems. Students will learn how to cost-effectively apply the methods and theory from Computer Science to solve difficult problems. The course presents a broad perspective on software and system engineering and surveys a wide spectrum of tools and techniques. Students are required to complete a project as part of a small software engineering team. Students will form groups and choose a software project early in the course, then apply methodologies learned in the course to complete their project. Each day lecture meets for 50 minutes and lab meets for 150 minutes. Prerequisite: CMPS 2020 with a grade of C- or better. Lecture Topics and Rough Schedule The topics below are the general subjects of the course, and will be introduced and discussed sequentially as the course progresses. Subjects could be added or removed. . Source and Version Control . Git and Github . The Software Engineering Lifecycle . Waterfall, Incremental, etc. . Agile Methodology . Open Source . Requirements Engineering . SRS - Software Requirements Specification . Design - Architecture and Methodologies . MVC - Model, View, Controller . Coupling and Cohesion . Software Design Specification . Programming a Complex Algorithm . Implementation Phase of Development . Program Debugging . Program Optimization . Testing and Quality Assurance . Testing Techniques . Specific Programming Techniques . Mobile development . Android . Android APK Creation . Profession and Ethics . Job Interview Day . Group Project Presentations . Project Completion Textbooks: Our textbook material will come from the school's Safari website. These books are provided free by the CSUB Library. Sections of the following books will be used: Essentials of Software Engineering, 4th Edition By: Tsui Publisher: Jones & Bartlett Learning Pub. Date: December 5, 2016 Print ISBN-13: 978-1-284-10600-8 Web ISBN-13: 978-1-284-10607-7 Pages in Print Edition: 334 Android Studio 2 Essentials - Second Edition By: Belaon Cruz Zapata Publisher: Packt Publishing Pub. Date: June 28, 2016 Print ISBN-13: 978-1-78646-795-9 Web ISBN-13: 978-1-78646-021-9 Pages in Print Edition: 172 All books above are current and up-to-date. link Additional book not provided free: The Mythical Man-Month Frederick P. Brooks, Jr. ISBN: 0-201-83595-9 Addison-WesleyGrading Policy Weekly assignments 50% . labs . homework . quizzes . attendance Exams 25% Project 25% ------------------------ Total 100% Grading scale used during the semester... A 93% A- 90% B+ 87% B 83% B- 80% C+ 77% C 73% C- 70% D+ 67% D 63% D- 60% F 0%
Zoom class sessions Class sessions will be held online using Zoom. Class attendance will sometimes require student use of a webcam. The following statement is justification for requiring the use of a webcam by students, and was provided by CSUB administration. -------- Because nonverbal feedback is helpful in human interactions, I expect students in this class to keep their cameras on during synchronous portions of online instruction. With this in mind, please plan where you will be during class time so you can participate in a setting that is free from visual distractions. If you believe you have a legitimate reason not to have your camera turned on, please consult with me well in advance of the class period, and I will make a determination. -------- When class starts each day, you should be logged in to the Odin server. Many class sessions will include some programming or a task to complete using a text file on Odin. Attendance Class attendance is required. Attendance will sometimes be recorded using Zoom session log files. Log into Zoom a few minutes before our class time so that you are in class when the class period begins. You may be asked to respond to questions or perform a task during class. Labs Labs are hands-on assignments to be done during a lab class period. Lab Rules: 1. Must not be late to lab. 2. Must work the entire lab period, unless excused by instructor. 3. Your program must compile and run at the end of lab period, when it is collected for scoring. A program that does not compile can receive a score of zero. Homework Homework assignments are posted on our web page. Instructions will be given for each assignment. Homework Rules: 1. Your program must compile and run when it is due, and collected by the instructor. General requirements of all assignments . Your name at the top . Correct file name . Correct file location Programming assignments: . No compile warnings or errors . Program must run . Program output must be neat, clean, and complete. . C program code must follow the K&R coding style. . C program code must have consistent and correct indenting. Text file written assignments: . Neatly written text . Correct spelling and grammar Each assignment will also have some specific requirements in addition to those listed above. Your name on all assignments Now that CSUB has become a virtual campus, some of the rules for writing and handing-in assignments are more important. Please read the rules below and follow them. ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- Amendment Fri Sep 11, 2020 ----------------------------------------------------------------------------- Your name must be at the top of every asssgnment. First and last name. An assignment file is any file that you modify as part of an assignment. In addition to your name, add the following information: 1. Just below your name put the date you did the work. 2. Just below that give a brief description of what this assignment is. 3. Just below that you may add special comments regarding your specific work on the assignment. Include in your special comments: Sources that you used to work on and complete the assignment such as web, textbook, lecture notes, lab, homework, tutoring center, etc. ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- Rules for all assignments... 1. Your name must be on every assignment. C and C++ programs: Put your name on the top line of every program you write. In a comment, write just your name. Forgetting your name can result in a score deduction. Forgetting your name can also result in a score of zero. Misspelling your own name will result in a deduction. Text files: Your name must be at top of any text file that you turn in. Forgetting your name can result in a score of zero. Quizzes: Your name must be at top of any written quiz. Your name must be at top of any quiz text file. Exams: Your name must be at top of any written exam. Your name must be at top of any exam text file. Your Project: Your name must be listed in your project proposal. Your name must be at the top of all programs written for your project. Original author: · If your program already has an original author listed, do not erase or change the author's name. · Put your name at the top as usual. Just below that, briefly explain that you are modifying the program. Notes: Your name on an assignment is not optional. Your name on an assignment indicates: • The assignment is your work. • You take responsibility for the assignment. An assignment with no name will not be accepted. The score given will be zero. Putting your name on an assignment after it has been collected does not help, because the assignment has already been collected. In some cases an assignment may be collected late with a no-name penalty. There are things in life that require protest and rebellion, but putting your name on an assignment is not one of them. 2. Good coding style must be used. C and C++ programs: The linux kernel coding style is used in this course. https://www.kernel.org/doc/html/v4.10/process/coding-style.html K&R indent and bracing style is recommended in your programs. Poor coding style can result in a score deduction. Unreadable code due to poor indenting will cause a score deduction. Choose spaces or tabs for indenting, but do not mix them. Note: Some assignments may ask you to maintain the style of the program's original author. 3. Spelling and grammar. Please write carefully on all assignments. Carelessness can cause a score deduction. 4. File locations. All work done on the Odin server must be done in your course folder. The folder name is the 4-digit name of this course, and will be setup by running a script provided by your instructor. Examples: 2240/, 3350/, 3480/ Any coursework stored outside the course folder must be stored in a folder with permission 700. Assignments stored in general folders or home folder will be submitted to the system administrator for deletion. Continued violations will be submitted to our school's department of Academic Integrity for consideration. Final Exam A final exam will be given. A date and time for the final exam will be posted. The Semester Project The semester project will ask you to write a somewhat complex program using all the assembly language knowledge you have learned throughout this course. A complete description of the project requirements will be available around week-3 of the course. The project could take 20 to 40 hours of programming work to complete, depending upon the grade level you wish to achieve. Late Assignment Policy Late assignments will not be accepted and result in a score of zero. Individual Work Policy All work done in this course is individual work. Sharing of source code is not allowed. Possession of code written by other students is not allowed. Copying another student's work is plagiarism. Copying answers or source code from the Internet is also plagiarism. Academic Integrity Policy All work done in this course is individual work. Please do not share your work with other students. You may discuss assignments with other students, but sharing of source code is simply not allowed. Refer to the Academic Integrity policy printed in the campus catalog and class schedule. Violations are enforced in accordance with the Department's policy on academic honesty. Absence from class A student's responsibilities include attending classes. If you miss a class, it is your responsibility to inform Gordon of the reason for the missed class (documentation may be required) and to arrange to make up any missed assignments, exams, quizzes, and class work, to the extent that this is possible. Excusable absences include, but are not limited to: Illness, injury, death of an immediate family member, etc. See a complete list at CSUB Catalog page 64. Amendments The teaching methods and rules are different than usual this semester. Students may find errors or loopholes in the rules. Your instructor reserves the right to amend this syllabus during the semester. Amendments added under 'Labs' Amendments added under 'Homework' Amendments added under 'Your name on all assignments'