CS 345 - Software Engineering - Spring 2013
Course description
While you have put together some programs to meet some individual requirements, have you ever wondered how the "big" systems are built? Have you ever thought about what it takes to produce something like Microsoft Office or PeopleSoft? This class lets you explore the "business" of software. This course provides a conceptual framework and practical experience in
a full range of stoftware development and assessment activities from a
systems engineering approach. By examining real-world examples
and employing professionally accepted techniques, students should
become conversant with issues confronting software practitioners and
the wider public.
The "official" description: Study of means for the development and maintenance of high quality software products delivered on time and within budget. Topics include requirements analysis and specification, software design, implementation, testing, maintenance, project management, ethics and the responsibilities of software engineering professionals. Prerequisites: CS 139 or ISAT 340 with sophomore standing in the ISAT major.
Your professor
Lecture – T/Th 3:30 - 4:45pm
Professor Harris worked for a software company for 16 years prior to joining the faculty at JMU. This company changed from a small "mom and pop" operation where each software installer did everything from developing code to writing documentation to training into a larger company where specialties were used, each person taking on a particular role in the development and deployment of the product. |
|||||||||
Prerequisites
CS 139 or ISAT 340 with sophomore standing
Overall Objectives
This course supports the following Computer Science departmental objectives:- Communications - Students can express themselves clearly on technical matters orally and in writing. They can communicate effectively with individuals that do not have a technical background.
- Professional and Ethical Issues - Students can provide an overview of the professional and ethical challenges faced by individuals and organizations in the information age.
- Software Engineering - Students can explain the software development lifecycle, software project management, development tools and methods. software quality assurance and the challenges of producing quality software products.
- Problem Solving Methods - Students can apply one or more problem solving methods in defining solution requirements and in designing, coding, testing, and documenting a software product.
- Teamwork - Students can work effectively in a team to develope a software product.
- In addition, I hope that students gain an appreciation of the software engineering industry and practice and gain a better understanding of the people side of computing.
Description of course policies and practices
I believe that the role of the instructor of a course is to guide students to develop their interest in and understanding of the course material. Within that philosophy, you will find that I don't lecture a lot, nor do I provide students with "the answer". Discovering the answers is part of the job of being a student.To that end, students should read the assigned readings BEFORE the class period in which we will discuss them. Generally, there will be a written preparation assignment to go with the reading. These preparations may be collected. Class attendance is mandatory and attendance will be taken. Classroom work will include some lecture, some activity and problem solving on the part of the students, and in some cases, opportunities to work on a part of the project with your team.
There will be a major software development project included as a major grade for this class. This project is yet to be determined but is designed to take you through all phases of a software development life cycle.
We will use Blackboard and the web as a means of communicating. Announcements for class will be made on the Blackboard announcements page or the course web page if Blackboard is unavailable. Any other announcement that you receive through other means (such as e-mail) is suspect unless confirmed by Blackboard or the course web page. If I send an e-mail to the class as a whole, I will also put the text into a Blackboard or web announcement.
For a full set of my class policies, see the general policies link to the left of this page.
NOTE: Collaboration will be a major component of this class. Work that is turned in for credit should include the names of ALL of the contributors to that assignment. Work that must be done individually will be noted as such in the assignment and must be the student's own work. Cheating in any form will be dealt with within the policies of the JMU Honor Code.
Textbook and Required Material
REQUIRED: Sommerville Ian: Software Engineering, Ninth Edition, Addison-Wesley, ISBN10:0-13-703515-2. - Additional book materials:
- http://www.SoftwareEngineering-9.com
- JAC Card
- There may be times that you need to print a worksheet, a completed assignment or other work. You must have your JAC card with you and some money on it for printing. Make sure that you have a couple of dollars on the card each day. JAC cards can be loaded in cash at the DART machine located in the HHS basement and other places around campus. Printing can also be done in the Copy Center located on the first floor of the HHS building.
Grading
Midterm (take home) - 20%
Final Exam(take home) - 20%
Project - 30%
In class activities(including attendance) - 20%
Homework - 10%
Class Policies and Student Success
See the link to the left for general instructor policies. Specific policies and items which will insure your success in this class are:
- Come to class, prepared. As with the jobs you will have when you leave JMU, attendance and preparation are expected. You will get points for regular attendance and doing the assigned work.
- Planned Absence - If you must be absent for class for legitimate reasons (school related activity, religious observance, important family event) see me BEFORE the absence if you need to turn work in on a different schedule.
- Unplanned Absence - If you are ill, please do not come to class. Let me know as soon as possible so that you can obtain any missed work. I will try to work with you to make up missed work in the case of illness. There are 2 allowed absences during the course of the semester.
- Late assignments - All homework is due at the beginning of class on the day that it is due. No late assignments will be accepted for credit, although I will review late assignments at your request to help you learn. For project deliverables, late assignments will have a per day late penalty associated with them.
- Exams - We have three performance appraisals during the semester, two mid semester and one final.
- Honor Code - I report ALL incidents of academic dishonesty to the Honor Council. If the violation is severe, I will refer it to the Honor Council for formal resolution. Less severe violations may be handled informally. If you know of cheating in this class, it is your responsibility to let the instructor know as soon as possible. If you are involved in a situation where you are not sure if what you did was right, please see me.
- Extra Credit - I generally do not have extra credit opportunities.
- Student Success - You will be successful in this
class if you:
- Attend class each day.
- Ask for help when you need it. I have plenty of office hours and am happy to make a special appointment if you cannot meet during normal office hours.
- If you need additional resources to help you with your learning, let me know. Additional reference books may be placed in the library upon request or I may loan books to individuals. I have gathered a number of materials both through my education and as an employee related to software engineering, management, quality, and other related topics.
The fine print:
Students with Disabilities: If you are a student with a documented disability, who will be requesting accommodations in my class, please make sure you are registered with the Office of Disability Services, Wilson Hall, Room 107 (568-6705) and provide me with a copy of your Access Plan letter outlining your accommodations. I will be glad to meet with you privately during my office hours to discuss your special needs. The sooner you can do this, the better I can assist you in meeting your learning goals in this course. More information: http://www.jmu.edu/syllabus/#Disability
Attendance: Since this class is based on POGIL activities and the process of engaging with other students and the material in class, attendance is mandatory. I will take attendance each day through a check off sheet (and turning in activity materials). 4 attendance days will count as one in-class activity. This will be in addition to any material that may be collected from that day. You will get credit for up to 2 absences during the semester.
"Excused" absences: Students who are unable to attend class due to JMU sponsored activities (such as sports, band, academic competition, academic field trips, etc) or personal religious observance may request deadline extensions BEFORE the expected absence. I will do my best to accommodate your special circumstances. Students with an excused absence will also be exempted from the attendance policy above for that day.
School closing for weather or other unexpected circumstances: Watch our Blackboard site for announcements relating to make up work. Project and exam dates will be adjusted as needed. For online make-up, I will make provision for students who do not have access to the internet or Blackboard. See me on the first class day after the missed class.
Dates and deadlines: http://www.jmu.edu/syllabus/#AddingDropping You are responsible for knowing and abiding by the registration dates and deadlines in effect for this and all other classes. See the link to those deadlines here.
Updated 01/03/2013- NLH