Continues to study the processes of developing large software systems. Requirements writing, software modeling, formal specifications, validation, verification, and global issues in computer science will be discussed. Students gain experience in these areas by working in groups on a software maintenance project that involves significant changes to a previously developed product. Prerequisite: SE3250W (2nd)

Expectations:

E1. Students learned basic error-handling, testing, and debugging techniques, with an emphasis on the responsibilities that computer professionals have for ensuring software quality. (CS 2106)

E2. Students have a basic understanding of object-oriented programming and can create programs using classes and objects in C++. (CS 2546)

E3.  Students are able to evaluate and select the appropriate data structure for a given problem. (CS 3316)

E4. Students learned and used proper unit testing techniques to ensure software quality.

E5. Students understand the purpose of data modeling and are able to model the logical data in a database. (CS 2656)

E6. Students can write basic Structured Query Language (SQL) data definition, data manipulation and data query statements. (CS 2656)

E7. Students are proficient in at least one database management system.  (CS 2656)

Course Outcomes:

R1. Students appreciate the benefits of planning, organizing, monitoring, and managing risks throughout the life cycle. (CS/SE 15)

R2. Students discussed societal and global issues in computing including information access and the digital divide. They have also written a paper related to society and technology and presented that paper to the class. (CS/SE 12)

R3. Students appreciate the importance of early and continuous involvement of all system stakeholders during the development cycle. (CS/SE 16)

R4. Students appreciate the need for and can adhere to a project coding standard, especially in the context of a maintenance project. (CS 6, SE 6, CS/SE 13, CS/SE 15, CS 17)

R5. Students can design between whitebox and blackbox testing. (CS/SE 15)

R6.Students can write and follow through a system test plan and test case descriptions. Students can report failures, correct faults, and resubmit test case results. (CS/SE 1, CS/SE 2, CS/SE 3, CS/SE 4, CS 6, SE 6, CS/SE 7, CS/SE 13, CS 14, CS/SE 15, CS 17)

R7. Students understand the importance of inspections and reviews and have played different roles in the review or inspection of various work products. (CS 6, SE 6)

R8. Students distinguish between validation and verification and have used methods for doing both. (CS/SE 6, CS/SE 9, CS/SE 15)

R9. Students understand the importance of software metrics and know the standard measurements such as person hours, lines of code, and function points. (CS/SE 13)

R10. Students have collected and used software metrics. (CS/SE 13)

R11. Students have experienced doing software maintenance in teams, have discussed effective group dynamics, including appropriate email etiquette. (CS/SE 2, CS/SE 7)