An introduction to the strategies used in producing quality software. The life cycle of software development is presented and utilized. Larger projects are undertaken by teams of students in the initial phases.
This course will introduce you to the theories and practices of software engineering. This course is the near end-product of a computer science degree. The vast majority of the CSIS degree is obtaining knowledge and tools which you apply in some capacity to solve problems. Software engineering is the application of that knowledge and those tools.
A formal definition: software engineering (SWE) is the systematic development, operation, maintenance, and retirement of software. This course is designed to give you the "big overview" of SWE. Each topic within this course could easily be (and is at some large universities) the topic of an entire semester-long course.
Attendance and participation are critical in this course. This course requires group work; group membership is therefore mandatory. Initially, groups will be formed randomly and assigned by the instructor. Once the large-scale projects start, groups will be set for the remainder of the course. You will have the opportunity to vote for your preferred project and team role. Your votes will be used to assign students to project teams and roles within each team.
The course will include regular homework and/or programming assignments. Unless otherwise specified, assignments are due before the beginning of class on the due date. There will be no credit given for late assignments (without an excused absence)—turn in as much as you can.
Reading assignments should be completed before the lecture covering the material. Not all reading material will be covered in the lectures, but you will be responsible for the material on homework and exams. Quizzes over the assigned reading may be given at any time.
See the GFU CS/IS/Cyber policies for collaboration and discussion of collaboration and academic integrity. Most students would be surprised at how easy it is to detect collaboration in programming—please do not test us! Remember: you always have willing and legal collaborators in the faculty.
Almost all of life is filled with collaboration (i.e., people working together). Yet in our academic system, we artificially limit collaboration. These limits are designed to force you to learn fundamental principles and build specific skills. It is very artificial, and you'll find that collaboration is a valuable skill in the working world. While some of you may be tempted to collaborate too much, others will collaborate too little. When appropriate, it's a good idea to make use of others—the purpose here is to learn. Be sure to make the most of this opportunity but do it earnestly and with integrity.
The mission and vision statement of the Computer Science & Information Systems (CSIS) program states that our students are distinctive by "bringing a Christ-centered worldview to our increasingly technological world."
As one step towards the fulfillment of this objective, each semester, the engineering faculty will collectively identify an influential Christian writing to be read and reflected upon by all engineering faculty and students throughout the term. As part of the College of Engineering, CSIS students participate in this effort, known as Engineering Your Soul (EYS). This exercise will be treated as an official component of every engineering course (including CSIS courses) and will be uniquely integrated and assessed at my discretion, typically as a component of the quiz grade.
Students should read the assigned reading each week. Regular meetings will be scheduled throughout the semester that can be attended for chapel elective credit. Students should attend these meetings prepared to discuss the assigned reading, or email a reflection on the assigned reading on or before each meeting date.
It is our hope that students will not view this as one more task to complete, but as a catalyst for continued discussion ultimately leading to a deeper experience of Jesus Christ.
All students in the College of Engineering are required to create and maintain an online portfolio on Portfolium to showcase their best work. Portfolium is a "cloud-based platform that empowers students with lifelong opportunities to capture, curate, and convert skills into job offers, while giving learning institutions and employers the tools they need to assess competencies and recruit talent."
Students will post portions of their coursework to Portfolium as directed by their instructor. For example, a portfolio entry might be PDF of poster or presentation content, screenshots or a video demonstration of a software or hardware project, or even an entire source code repository. In addition to required portfolio entries, students are encouraged to post selected work to their portfolios throughout the year.
Students will work with their faculty advisor to curate and refine their portfolios as they progress through the program. Students shall ensure that all portfolio entries are appropriate for public disclosure (i.e., they do not reveal key components of assignment solutions to current or future students).
If you have specific physical, psychiatric, or learning disabilities and require accommodations, please contact the Disability Services Office as early as possible so that your learning needs can be appropriately met. For more information, go to ds.georgefox.edu or contact Rick Muthiah, Director of Learning Support Services (503-554-2314 or firstname.lastname@example.org).
The Academic Resource Center (ARC) on the Newberg campus provides all students with free writing consultation, academic coaching, and learning strategies (e.g., techniques to improve reading, note-taking, study, time management). The ARC, located in the Murdock Learning Resource Center (library), is open from 1:00–10:00 p.m., Monday through Thursday, and 12:00–4:00 p.m. on Friday. To schedule an appointment, go to the online schedule at arcschedule.georgefox.edu, call 503-554-2327, email email@example.com, or stop by the ARC. Visit arc.georgefox.edu for information about ARC Consultants' areas of study, instructions for scheduling an appointment, learning tips, and a list of other tutoring options on campus.
The final course grade will be based on:
|Week 1||Introduction to Software Engineering||-||-|
|Week 2||Small-Scale Programs and Projects||Ch. 1||Ch. 1–2|
|Week 3||Software Project Management||Ch. 13||Ch. 3–4|
|9/13||Serve Day — no classes||-||-|
|Week 4||Large-Scale Systems||Ch. 2||Ch. 5–6|
|Week 5||Outcomes, Ethics, and Principles||Ch. 3||Ch. 7|
|Week 6||Software Process Models||Ch. 4||Ch. 8–9|
|Week 7||Modern Process Methodologies||Ch. 5||Ch. 10–11|
|Week 8||Requirements||Ch. 6||Ch. 12–13|
|Week 9||Mid-term exam||Ch. 1–6, 13||Ch. 1–13|
|Week 10||Design: Architecture and Methodology||Ch. 7||Ch. 14|
|Week 11||Design: Characteristics and Metrics||Ch. 8||Ch. 15–16|
|Week 12||Implementation||Ch. 9||Ch. 17|
|Week 13||Testing and Quality Assurance||Ch. 10||Ch. 18–19|
|Week 14||Configuration Management, Integration, and Builds||Ch. 11||Ch. 20|
|Week 15||Support, Maintenance, and Security||Ch. 12, 14||Ch. 21|
|TBD||Final exam||Ch. 7–12, 14||Ch. 14–21|
This page was last modified on 2017-08-18 at 14:01:51.
George Fox University · 414 N Meridian St · Newberg, Oregon 97132 · 503-538-8383
Copyright © 2015–2017 George Fox University. All rights reserved.