CS 3750 Software Engineering II - Fall 2013 (A CEL Credit ...icarus.cs.weber.edu/syllabus/Fall_2013/Fal_13_CS3750_Fry.pdf · CS 3750 Software Engineering II - Fall 2013 (A CEL Credit

CS 3750 Software Engineering II - Fall 2013 (A CEL Credit Course)

Department of Computer Science Weber State University

Professor: Dr. Richard Fry, Associate Professor of Computer Science Office Location: WSU Main Campus, Technical Education Building, Room 110K

Office Hours: Tuesdays and Thursdays 930-1130 AM (check in with secretary first) E-mail: [email protected] (Preferred) or [email protected] (Forwarded) Class Meetings: WSU Main Campus, Technical Education Building, Room 202S Tuesdays and Thursdays 730AM (Please, be on time) - 920 AM Required Textbook: None

Course Description

This course is the second in a series, taken after CS 2450, in which we study a collection of methods which embody an "engineering" approach to the development of computer software. This course will study the principles, methods, and tools for implementation, testing, release, maintenance and documentation of large, complex software systems.

The majority of work in the course is in the context of a group project. The class meeting times are divided into lecture days and team meeting days. During lectures we will discuss concepts and principals of software engineering – as they relate to your projects, and on team days we will practice specific techniques in the context of a building the project. Students will be divided into groups of about five to ten students to carry out the course’s various projects.

Projects are chosen to provide a Community Engaged Learning (CEL) component with project proposals being solicited from the global community at large. Therefore, team work is required for the project, and 100% participation with your community partner outside of classroom is expected. The course will put a great emphasis on developing several demonstrable software prototypes for the clients by the end of the semester.

Course Objectives

build and test production-quality software prototypes (technical, operational, functional) gather (or refine existing) requirements from a community partners and project sponsors refine existing (or formally document new) system and software requirements continuously test the requirements, prototypes, and models as the development progresses improve understanding of the software development process improve technical communication skills, both oral and written refine the art of working effectively in a technical project team practice time and project management as well as personal accountability

http://www.weber.edu/CS/Sidebar/Fry_Richard.html

mailto:[email protected]

mailto:[email protected]

Course Prerequisites

Every student is required to have taken CS 2450 and CS 2420. Other pre-requisites will vary depending on your catalog year. However, regardless of catalog year, this course is intended to be taken in your junior or senior (preferred) year for you to get the most out of the experience (and to be able to adequately contribute to your team project). At a minimum, you should feel comfortable programming in an object-oriented language. Having an upper division programming class like CS 3230 (JAVA) or CS 3280 (C#) and/or practical experience programming outside the classroom is highly desirable (and required for all 2013 and higher catalog students). Finally, you should be comfortable with HTML (CS 2350) and database principles (CS 2550). Again, having upper division database coursework (CS 3550) is highly desirable (and, again, required for newer catalog students).

Course Projects

All students will be required to submit a resume and “interview” to be assigned to a particular project (below) during the first two weeks of the course. This semester’s projects include: 1) Runway Ruby’s Restaurant (Hill AFB) Project: Point of Sale (POS) & Order Queuing System Description: Develop a POS and Order Queuing system for a restaurant located on Hill AFB. The workers have various “disabilities” making the design and implementation a little more challenging. We will focus primarily on building four distinct programming prototypes – a POS (C# for Windows), a queuing system (ASP.NET or PHP webpages displayed on 7” android tablets), a website ordering (ASP.NET or PHP) interface, and a daily special display board with administration interface (ASP.NET or PHP webpages). Light database design and programming (SQL Server or MySQL) will be required. This project already has all the requirements documented, and will only require a review of existing documentation. The team will not be required to perform additional documentation, but there may be the need for occasional meetings with clients any M-F between 12:30 and 3PM (no problem getting on HAFB). This project will continue in CS 4750 (Spring 2014). Max Team Size: 10 (two sub teams of 5). 2) Recreation Outlet – Salt Lake City (Warehouse) and Ogden (Store) Project: Inventory Management and Point of Sale (POS) System

Description: We will focus primarily on building two distinct programming prototypes – a POS (C# for Windows) and an inventory / purchase order / item control interface (ASP.NET or PHP webpages). Heavy database design and programming (SQL Server or MySQL) will be required. This project already has all the requirements documented, and will only require a review of existing documentation. The team will not be required to perform additional documentation, but there will be the need for frequent meetings with clients (at the beginning of the semester) any Tuesday through Thursday between 10AM and 4PM (primarily at the SLC Warehouse location near the airport). This project will continue in CS 4750 (Spring 2014). Max Team Size: 8 (two sub teams of 4).

3) Century 21 - Chiang Mai, Thailand Project: Property Asset Management and Billing System with BONUS STUDY ABROAD OPPORTUNTY Description: This project involves building a Property Asset, Management and Billing system for a Century 21 office in Chiang Mai, Thailand that manages 900+ condominiums. There is a bonus (not required) opportunity to travel to Thailand for 10 days at the end of the semester (Dec 11-21) for an additional 2 credits of Upper Division course work (which can substitute for an elective class when combined with a 2 credit Independent project). The additional cost of the Study Abroad trip is approximately $2875 (added to your normal fall 2013 tuition, and can have financial aid applied to it). The cost includes almost everything - course credit, airfare, several tours and activities, hotel accommodations, meals, and attendance at a three day software engineering conference. It is not required you go to Thailand to participate in this project, but preference will be given to students who can commit to go. Heavy database design and programming (SQL Server or MySQL) will be required. The web application may be built in PHP or ASP.NET. This project does not have the requirements documented. Consequently, the team will need to gather and document requirements in the form of an SRS document (similar to CS 2450). There will be the need for frequent meetings with clients via Skype on various Sunday-Thursday evenings (accounting for the 13 hour time difference). There will be more frequent meetings towards the end, as the interface will need to be translated in Thai as well as English. This project is one semester only, with optional Independent Study support in spring 2014. Max Team Size: 6. 4) Fantasy Immortals – Bountiful, Utah Project: Fantasy Sports Website Description: Develop a fantasy sports (multiple sports) website with a unique twist. Must have a love for sports and understanding of fantasy leagues. Heavy database design and programming (SQL Server or MySQL) will be required. The web application may be built in PHP or ASP.NET. This project does not have the requirements documented. Consequently, the team will need to gather and document requirements in the form on an SRS document (similar to CS 2450). There will also be the need for frequent meetings with clients available 7 days a week (split between meeting in Bountiful and the main campus). Max Team Size: 5. 5) The Pioneer Adult Rehabilitation Clinic (PARC) - Clearfield, Utah Project: Pathway to Careers Human Resource Application (Module II) Description: Develop an extension module to SPEED (a continuation of an existing system built by last year’s 3750 class - written with PHP/MySQL/JavaScript technologies with an MVC framework). This project already has the requirements documented, and only requires a review of existing documentation (and getting familiar with the existing code and application). The team will not be required to perform additional documentation. There will be the need for frequent meetings (at the beginning of the semester) with clients any M-F between 9AM and 4PM (in Clearfield). This project is one semester only – and is a good candidate for students who do not need CS 4750. Max Team Size: 4.

All teams will be formed at the end of WEEK #2 based on the following criteria: 1) Project Preference and Student Qualifications – it is okay if you are not a strong programmer (each team will need to have senior and junior programmers, database engineers, testers, documenters, UI specialists, configuration managers, and system analysts as well. Each student will be assigned at least two different roles). 2) Student Schedule (to ensure all students on a team can meet together and with their teammates and clients, in person (or virtually) at least 4 hours outside of class each week). 3) Student’s desire to participate in the Study Abroad (Thailand Project Only). 4) Student’s need/desire to continue in CS 4750 next semester.

Course Schedule (Subject to Change – See LIVE calendar on course website)

Week 1: The Process of Software Development

Date In Class Outside of Class

Tuesday, 8/27 Course Overview and Policies Presentation: Introduction to Software Engineering

Project Introductions and Requirements

READ: Software Development Methodologies: Be prepared to discuss next class

COMPLETE: Team Project Questionnaire, Personality Test & Student Resume

Thursday, 8/29 Presentation: Software Processes Students wishing to work on Thailand Project must see me, in person, during or after class today

COMPLETE: Team Project Questionnaire, Personality Test & Student Resume

FRY day, 8/30 (by midnight)

DUE: Team Project Questionnaire, Personality Test & Student Resume

Relax and enjoy your LABOR DAY WEEKEND!

Week 2: Software Engineering Tools


Tuesday, 9/3 Team Assignments and Client Contact Information Presentation: Software Engineering Tools (Version Control Software, TeamViewer and Google Sites/Docs)

ALL TEAMS IMMEDIATELY SCHEDULE YOUR Team Meetings with your group and with your client between 9/4 and 9/20 COMPLETE: Team Websites, Project Charter

Thailand and Fantasy Only: Watch Requirements 1. Review Software Requirements Specification (SRS) Template PARC: Review existing code and software. Meet with client before Tuesday 9/10, so we can discuss. Others: Watch DB Design/ Class Design

Thursday, 9/5 Ruby’s and Recreation: Mandatory Meetings with Instructor (Conference Room) to discuss technical prototypes and database design 7:35-8:25 Runway Ruby’s 8:30-9:20 Recreation Outlet All Others: Team Meetings (in class) to work on project charter and website. Schedule requirements gathering with client outside of class ASAP (before 9/20). NOTE: INSTRUCTOR IS AVAILABLE immediately after class (9:30-10:30) for additional Q&A – (Send project representatives to meet, on behalf of the entire team, with your issues).

ALL TEAMS CONINUE Team Meetings with group and with your client between 9/4 and 9/20 Thailand and Fantasy Only: Watch UML Use Cases & Activity Diagrams, READ: Practical UML Tutorial PARC: Review existing code and software. Meet with client before Tuesday 9/10, so we can discuss. PHP/MVC tutorials as needed. Outline questions. Others: Watch DB Design/ Class Design. Start discussing/revising DB requirements. Recreation get Panorama database schemas.

Week 3: Project and Risk Management


Tuesday, 9/10 Presentation: Project and Risk Management PARC: Mandatory Meetings with Instructor (Conference Room) 8:50-9:20AM to discuss status of project

COMPLETE: Project & Risk Management Plan COMPLETE: Team Websites, Project Charter ALL TEAMS CONINUE Team

NOTE: INSTRUCTOR IS AVAILABLE immediately after class (9:30-10:30) for additional Q&A – (Send project representatives to meet, on behalf of the entire team, with your issues).

Meetings with group and with your client between now and 9/20

Thursday, 9/12 Thailand and Fantasy: Mandatory Meetings with Instructor (Conference Room) to discuss requirements and document deliverables 1 7:35-8:25 Thailand 8:30-9:20 Fantasy All Others: Team Meetings (in class) to work on project charter and website. Schedule meetings with client outside of class ASAP (before 9/15). NOTE: INSTRUCTOR IS AVAILABLE immediately after class (9:30-10:30) for additional Q&A – (Send project representatives to meet, on behalf of the entire team, with your issues).

FRY day, 9/13 by midnight

DUE: Project Charter, Team Websites

Week 4: Requirements Modeling / Technical Prototyping

Date In class Outside of Class

Tuesday, 9/17 Ruby’s, PARC, and Recreation: Mandatory Meetings with Instructor (Conference Room) – Technical Prototypes 7:35-8:10 Recreation Outlet 8:10-8:45 PARC 8:45-9:20 Runway Ruby’s All Others: Group Meetings (in class) to work on Document Deliverables 1. NOTE: INSTRUCTOR IS AVAILABLE immediately after class (9:30-10:30)

COMPLETE: Document Deliverables 1 or Technical Prototype 1 (varies by team)

for additional Q&A – (Send project representatives to meet, on behalf of the entire team, with your issues).

Thursday, 9/19 Ruby’s, PARC, and Recreation: Mandatory Meetings with Instructor (Conference Room) – Document Deliverables 1 7:35-8:20 Fantasy 8:35-9:20 Thailand All Others: Group Meetings (in class) to work Technical Prototype. NOTE: INSTRUCTOR IS AVAILABLE immediately after class (9:30-10:30) for additional Q&A – (Send project representatives to meet, on behalf of the entire team, with your issues).


FRY day, 9/20 by midnight

Project & Risk Management Plan

Week 5: Requirements Modeling / Technical Prototyping


Tuesday, 9/24 Presentation: Prototyping Group Meetings to work on documentation or technical prototype.

Thursday, 9/26 Group Meetings (in class) to work on documentation or technical prototype.

Group Meetings to work on documentation or technical prototype.

Week 6: System Architecture and Design


Tuesday, 10/1 MANDATORY MS1 MEETING WITH DR. FRY (Document Deliverables 1): Team PARC (7:35-8:05), Team Rubys (8:10-8:40), Team Recreation (8:45-9:15). DUE BY MIDNIGHT: Peer Review 1

READ: Software Design Document (SDD)

Thursday, 10/3 MANDATORY MS1 MEETING WITH DR. FRY (Document Deliverables 1): Team Fantasy (7:30-8:25), Team Thailand (8:30 – 9:20). DUE BY MIDNIGHT: Peer Review 1


Week 7: System Architecture and Design


Tuesday 10/8 Presentation: Testing Test Plans

Thursday 10/10 Group Meetings (in class) to work on documentation or technical prototype.


Week 8: Functional Prototyping and Testing


Tuesday, 10/15 MANDATORY MS2 MEETING WITH DR. FRY (Technical Prototype 1): Team PARC (7:45-9:15) DUE BY MIDNIGHT: Peer Review 2

Thursday, 10/17 MANDATORY MS2 MEETING WITH DR. FRY (Technical Prototype 1): Team Rubys (7:45-9:15) DUE BY MIDNIGHT: Peer Review 2



Tuesday, 10/22 MANDATORY MS2 MEETING WITH DR. FRY (Technical Prototype 1): Team Recreation (7:45-9:15) DUE BY MIDNIGHT: Peer Review 2

Thursday, 10/24 MANDATORY MS2 MEETING WITH DR. FRY (Design): Team Thailand (7:35-8:15) Team Fantasy (8:35-9:15) DUE BY MIDNIGHT: Peer Review 2



Tuesday, 10/29 Group Meetings (in class) to work on documentation or technical prototype.


Thursday, 10/31 Group Meetings (in class) to work on documentation or technical prototype.




Tuesday, 11/5 Group Meetings (in class) to work on documentation or technical prototype.


Thursday, 11/7 MANDATORY MS3 MEETING WITH DR. FRY (Technical Prototype 2): Team PARC (7:45-9:15) DUE BY MIDNIGHT: Peer Review 3



Tuesday, 11/12 MANDATORY MS3 MEETING WITH DR. FRY (Technical Prototype 2): Team Rubys (7:35-8:15) Team Recreation (8:35-9:15) DUE BY MIDNIGHT: Peer Review 3

Test Plans

Thursday, 11/14 MANDATORY MS3 MEETING WITH DR. FRY (Technical Prototype 2): Team Fantasy (7:35-8:15) Team Thailand (8:35-9:15) DUE BY MIDNIGHT: Peer Review 3

Weeks 13-16: Final Testing and Documentation


Tuesday, 11/19 & Thursday 11/21

EVERYONE – Mandatory in-class testing

Work on Final Demos and Final Website and Electronic Project Archive

Tuesday, 11/26 & Thursday 11/28

THANKSGIVING WEEK

Tuesday, 12/3

MANDATORY MS4 MEETING WITH DR. FRY (Technical Prototype 3): Team PARC (7:45-9:15) DUE BY MIDNIGHT: Final Peer Reviews

Thursday 12/5

MANDATORY MS4 MEETING WITH DR. FRY (Technical Prototype 1): Team Recreation (7:35-8:15) Team Rubys (8:35-9:15) DUE BY MIDNIGHT: Final Peer Reviews

Tuesday, 12/10

MANDATORY MS4 MEETING WITH DR. FRY (Technical Prototype 2): Team Fantasy (7:35-8:15) Team Thailand (8:35-9:15) DUE BY MIDNIGHT: Final Peer Reviews ALL TEAMS: Final Website and Electronic Project Archive DUE BY MIDNIGHT

Course Project Deliverables

The project deliverables and deadlines are listed below

MAJOR Project Deliverables (not all details shown) Absolute Deadline*

I t e r. #1

1. Project Charter and Website September 13 (FRY day at Midnight)

2. Project & Risk Management Plan September 20 (FRY day at Midnight)

3. MS 1 Deliverables (varies by team) due in class followed by Peer Review 1 (by midnight)*

October 1-3 (In class – see schedule)


Oct 15-24 (In class – see schedule)

I t e r #2


November 7-14 (In class – see schedule)


December 3-10 (In class – see schedule)

7. Final Website and Electronic Project Archive by NOON*

December 10 (Final’s Week – Tuesday at Noon)

*Late submissions penalties 1min-12 hours (10%), 12-24 hrs (25%), 25-48 hrs (50%), 49-72 hrs (75%)

Grading Criteria

Assessment Team or

Individual Points Percentage

Project Charter, PM/Risk Mgmt, Test Plans & Website Team 50 Points 10%

Additional documentation (10% - PARC, 25% Runway and Recreation, 40% Thailand and Fantasy)

Team 25-100 Points 10-20%

2-3 Prototypes (90% - PARC, 75% Runway and Recreation, 60% Thailand and Fantasy)

Team 125-225 Points 25-45%

Milestone Peer Reviews (4) Individual 100 Points 20%

Individual Evaluation, Participation, & Adjustment (2) Individual 70 Points 14%

Monthly CEL Hours (Logged at the Community Center for Engaged Learning – Student Center) (3)

Individual 30 Points 6%

TOTAL 60% Team,

40% Individual 500 Points 100%

A-/A = 90-100% of the total points, B- to B+ = 80-89% of total points, C to C+ = 72-79% of total points. You need 360 points or more to pass the course with at least a “C”.

Observe that 40 % of your total grade is individual-based, and 60 % is team-based (project deliverables). It is quite possible for the team to get a passing grade (above 72% for their project), but each individual will ultimately receive a different grade (because of peer reviews and instructor evaluation). During mandatory meetings with the professor (Milestones 1-3), you are expected to be prepared, professional, and on-time for your presentation. These will be formal meetings with each team member responsible for reporting on his/her particular activities and the status of their individual deliverables since the last milestone progress check. Attendance at these meetings will be mandatory unless specifically excused. Failure to attend or chronic inactivity as determined from the weekly status report will reflect on an individual team member's individual grade.

Other Course Policies

Accommodations

Any student requiring accommodations or services due to a disability must contact Services for Students with Disabilities (SSD) in room 181 of the Student Services Center. SSD can also arrange to provide course materials (including this syllabus) in alternative formats if necessary.

Cell Phones

For obvious reasons, cell phones should be set to silent or vibrate during class. If you must take a phone call, please excuse yourself from the classroom. Also, NO TEXT MESSAGING DURING CLASS LECTURES OR DEMONSTRATIONS. It's a distraction to me and others around you. Violators will be asked to leave the classroom immediately.

Cheating

Weber State University requires that students be honest in their academic work. Academic dishonesty is an ethical issue and the violation of the principles expressed in the University's Statement of Educational Mission. It defrauds all those who depend upon the integrity of the University, its courses, and its degrees. The term "cheating" is the act of obtaining or attempting to obtain, or helping in obtaining, credit for academic work through any dishonest, deceptive, or fraudulent means. Effective 8/23/2012: CS Department policy dictates that any verifiable evidence of student academic cheating, as defined and determined by the instructor, will result in: 1) an automatic failing grade for the class and 2) a report to the Dean of Students that will include the student's name and a description of the student's dishonest conduct.

Class Notifications / Cancellations

For all official announcements regarding this class, or any cancellations, I will notify you via your Weber E-mail Account. I strongly suggest that you forward your WSU mail to your regular mailbox, so you do not miss these important announcements.

Surfing the Net (and other inappropriate behavior) during class/labs

Please don't waste my time or yours by surfing the internet, playing video games, instant messaging, working on assignments from other classes, etc., while class or labs are in session. It distracts me and other students. If I see you doing something else during my lectures, I will ask you to leave the classroom. If I were your boss, I'd fire you.

Next Semester and CS 4750

The Runway Ruby, Recreation Outlet, and Fantasy projects started in CS 3750 will continue in CS 4750: Advanced Software Engineering, next semester with the possibility of new team rotations and challenges during the implementation and delivery phases of your projects.

Although it is not absolutely necessary that you continue CS 4750 consecutively, it will be to your advantage, since you already started the project and have a firm grasp on the requirements as well as (hopefully a good) working relationship with your teammates. However, if there are problems with team cohesion, I can reassign the team members in CS 4750 before continuing.

Please note: CS 4750 is a capstone course, with no new material presented. It is simply a continuation of CS 3750 – with heavy focus on programming, testing, and the final implementation of the prototypes you started in CS 3750. However, the CS 4750 section (taught by me) in the spring of 2014 will be delivered as an ON-LINE Hybrid instead of an “in-residence” course, as I will not be physically in Utah January-March 2014.

What this means to you: if you continue CS 4750 with me as your instructor, your course will be advertised as a hybrid classroom – with scheduled meetings on Tuesday / Thursday EVENINGS at DAVIS (from 5:30-7:20PM). While you really won’t be expected to show up for class during that time or location (it’s been set aside for you), it will still be the time you need to be guaranteed to be available for on-line feedback and mentoring sessions, via Skype. Your entire team will be expected to meet with me online approximately every other week, on either Tuesday or Thursday nights. You cannot have other classes or obligations during this time window. Beyond this reserved time and location, you will continue meeting and working together on the project at a time convenient to your group. However, regardless of when or where you meet, it will be imperative that you allocate the appropriate time towards programming and testing, as 100% of your final grade will be based solely on the final working products for the client.

Although I successfully taught CS 4750 this way last year, I understand not all students may feel comfortable with the hybrid class format. Therefore, alternative sections of CS 4750 will be offered at the Davis and SLCC campuses (also in the evenings). CS 4750 is also NOT required for 2011 and newer students. It is one of several capstone electives, so you have a choice.

Thanks, and have a great semester! Last Updated: August 26, 2013

Documents

CS 3750 Software Engineering II - Fall 2013 (A CEL Credit ...icarus.cs.weber.edu/syllabus/Fall_2013/Fal_13_CS3750_Fry.pdf · CS 3750 Software Engineering II - Fall 2013 (A CEL Credit