CptS 423: Software Design Project II

Course Information
Course Name: 
Software Design Project II
Course Number: 
Lecture Hours: 
Course materials
Textbook(s) (title, author, year): 


Supplemental Materials: 

1.    Software Engineering: A Practitioner's Approach, 6th edition, by R. Pressman, McGraw Hill, 2005
2.    Software Engineering, by Ian Sommerville, 9th Edition, Addison Wesley, 2012
3.    Software Testing: A Craftsman’s Approach, 3rd edition, by Auerbach Publications, 2008.
4.    IEEE Standards for Software Engineering

Course Description: 
Catalog Description: 

Group project for developing large-scale software systems; software life cycle process including: project scheduling/planning, requirements analysis, design, verification, and project management; writing product specifications; working in teams; writing reports and making presentations.

Specific Course Information
Course Prerequisites: 
  • CptS 323 Software Design;
  • Certified major in Computer Science, Computer Engineering, or Electrical Engineering.
Prerequisite Grade Requirements: 
C or better
Topic Prerequisites: 

You should have a thorough understanding of software engineering principles (software development processes, requirements engineering, software design, and software testing).

CptS Course Required/Elective: 
Overview and Course Goals
Overview and Course Goals: 

Senior design courses allow senior-level students to integrate their software engineering knowledge and produce a useful engineering artifact. Students practice major activities in software development process, including communication, planning, modeling and design, construction, and deployment.  It serves as a final preparation for students entering into industry. Students get experience in working as teams, participating in project planning and scheduling, writing reports, giving presentations, and dealing with uncertainties in a professional manner.
This is a two-semester senior design sequence.  The first semester (CptS 421) is a three-credit course in which the design teams are formed; mentors are interviewed; and the design process and project development are started. A series of assignments are completed that results in written documents, audio/visual presentations, and an alpha prototype implementation. The second semester (CptS 423) is a three-credit course in which the latter phases of the project is documented, project design is completed and tested, and the final software product is presented to external constituencies such as industry representatives, other students, and faculty in general.  

Outcomes of instruction:
*    experience in large-scale software development;
*    communication with clients and other stakeholders;
*    gathering of project requirements;
*    designing of software according to requirements;
*    implementing the design;
*    performing adequate verification, validation, and testing procedures;
*    delivering a professional quality software that meets the client's requirements;
*    writing product specifications, documenting different phases of the project;
*    using software development and maintenance tools
*    planning and developing project timelines;
*    demonstrating an awareness of professional responsibilities;
*    negotiating team dynamics;
*    making presentations, using audio/visual tools, at different stages of the project.

Course Topics
Topics [with corresponding ABET outcomes]: 

1.    Team design project [a, b, c, d, e, g, h, i].
2.    Weekly oral progress evaluation of teams by instructor and industry mentors [d, e, f].
3.    Written reports on project description, solution approach, alpha prototype, beta prototype, test plans and results [a, b, c, d, e, f, g, h, i].
4.    Formal final presentations to instructor and industry mentors [d, e, f].
5.    Senior design poster preparation and poster presentations, judged by industry panel. [d, e, f].

Course Rules
Course Rules: 

Late delivery of deliverables:
Late deliverables (documents, reports, code, etc) will be accepted with instructor's permission only. Late penalty for each deliverable is 10% point deduction per day. Project teams must notify the instructor beforehand for the late submission of project deliverables. Exceptions may be provided to teams with valid, documented excuses.
Academic Integrity:
Integrity and honesty are fundamental to obtaining knowledge at any academic institution. These core values are essential to the function of the academic community at WSU. You are expected to know and understand Washington State University Academic Integrity Policies. All work submitted for grading is to be original or source of the material is to be cited in the work regardless of whether the material is quoted directly, paraphrased or summarized. Any student caught cheating on any assignment, or deliverable, will be given an F grade for the course and will be reported to the university authorities.

Students with Disabilities
Statement Concerning Accommodations: 

Reasonable accommodations are available for students with documented disability. If you have a disability and may need accommodations to fully participate in this class, please visit the Access Center (Washington Building 217) to schedule an appointment with an Access Advisor. All accommodations MUST be approved through the Access Center. Additional information can be viewed at the URL http://drc.wsu.edu.

Grading framework: 

Grades are based on
-    Weekly oral team progress review
-    Evaluation of written reports
-    Project poster presentations
-    Socialcast activity evaluations
-    Peer/mentor evaluations

Contact us: webmaster@eecs.wsu.edu | Telephone: 509 335 6602 Fax: 509 335 3818 | Accessibility | Copyright | Policies
School of Electrical Engineering and Computer Science, PO BOX 642752, Washington State University, Pullman, WA, 99164-2752 USA