CSIS 490 Applied Software Development


Course Description

Special software development projects are designed and completed by the student in an area that applies computing and software. This is an independent-study course and is supervised by staff in both the computer area as well as in the selected area of study.

This course is for upper-division CSIS majors and by instructor permission only.


Instructor

Brian R. Snider
Office hours: Wood-Mar 223 (see schedule)

Resources


Objectives

This course further explores software engineering and human–computer interactions methodologies in detail, and assumes mastery of topics covered in those courses.

Students will gather requirements for and then design a non-trivial software system in their chosen domain.

Students will utilize one or more high-level languages to implement a substantial and cohesive software system.

Students will be familiar with modern version control systems (e.g., Git) and related services (e.g., issue trackers).

Students will be familiar with modern software development processes (e.g., Scrum).

Students will be familiar with various development artifacts (e.g., UML diagrams, test matrices, software requirements specifications).


Course Organization

The course will include regular homework and/or programming assignments. There will be no credit given for late assignments (without an excused absence)—turn in as much as you can. Unless otherwise specified, no handwritten work will be accepted.

Reading should be completed before the lecture covering the material per the provided schedule. 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.


Collaboration and Academic Integrity

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 or other academic integrity violations such as plagiarism in programming—please do not test us! Remember: you always have willing and legal collaborators in the faculty. We encourage you to ask questions in class, ask for help in the CS lab, use the class mailing list, and visit office hours for assistance.

Unless otherwise specified (e.g., for a group assignment or project), you are expected to do your own work. This also applies to the use of online resources (e.g., StackOverflow, ChatGPT). Put simply: if you are representing someone else's work as your own, you are being dishonest. Any suspected incidents of academic integrity violations will be investigated and reported to the Academic Affairs Office as they arise.

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.


University Resources

Accessibility and Disability

If you have specific physical, psychiatric, or learning disabilities and require accommodations, please contact Disability & Accessibility Services (DAS) as early as possible so that your learning needs can be appropriately met. For more information, go to georgefox.edu/das or contact das@georgefox.edu).

My desire as a professor is for this course to be welcoming to, accessible to, and usable by everyone, including students who are English-language learners, have a variety of learning styles, have disabilities, or are new to online learning systems. Be sure to let me know immediately if you encounter a required element or resource in the course that is not accessible to you. Also, let me know of changes I can make to the course so that it is more welcoming to, accessible to, or usable by students who take this course in the future.

Academic Resource Center

The Academic Resource Center (ARC) on the Newberg campus provides all undergraduate students with free writing consultation, academic coaching, and learning strategy review (e.g., techniques to improve reading, note-taking, study, time management). The ARC offers in-person appointments; if necessary, Zoom appointments can be arranged by request. The ARC, located on the first floor of the Murdock 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 traccloud.georgefox.edu, call 503-554-2327, email the_arc@georgefox.edu, 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.

Student Support Network

George Fox University uses a robust referral and support system, Fox360, to learn about students who are experiencing various student success concerns. Students who are referred by a professor, other employee, or fellow student will be contacted by a member of our Student Support Network to explore the student's situation, develop a plan, and connect with relevant campus resources. GFU community members who have a concern about a student's well-being can submit an aleart by going to fox360.georgefox.edu. Our goal is to provide 360° care for students as they navigate their college experience. For more information see ssn.georgefox.edu or contact Rick Muthiah, Director of Learning Support Services.


Health and Safety Considerations

Please review the entirety of the university's official COVID-19 web page for the most up-to-date community guidance.


Grading

Grading Scale

The final course grade will be based on:


Tentative Schedule

Week 1

Project Planning

Week 2

Software Development Process

Week 3

Version Control

Week 4

Requirements

Week 5

Design: Sketching & Mockups

Week 6

Design: Prototyping

Week 7

Implementation: Languages & APIs

Week 8

Implementation: Design Patterns

Week 9

Implementation: Dependencies & Resources

Week 10

Implementation: Toolchains

Week 11

Unit & Regression Testing

Week 12

Spring break — no class

Week 13

Integration & User Acceptance Testing

Week 14

Documentation

Week 15

Maintenance & Support

Finals week

Final Presentation


This page was last modified on 2020-07-30 at 18:28:28.

Copyright © 2015–2024 George Fox University. All rights reserved.