CS 321: Software Requirements/Design Modeling

(Fall 2016)

Contact Information

Dr. Shvetha Soundararajan

Email: shvetha@gmu.edu
Office: Engineering 4436
Phone: 703-993-6219
Office Hours: Tuesdays and Thursdays: 12:15 - 1:15 pm and by appointment

GTA: See Blackboard for contact information.


An introduction to concepts, methods, and tools for the creation of large-scale software systems. Methods, tools, notations, and validation techniques to analyze, specify, prototype, and maintain software requirements. Introduction to object-oriented requirements modeling, including use case modeling, static modeling, and dynamic modeling using the Unified Modeling Language (UML) notation. Concepts and methods for the design of large-scale software systems. Fundamental design concepts and design notations are introduced. A study of object-oriented analysis and design modeling using the UML notation. Students participate in a group project on software requirements, specification, and object-oriented software design.

Course Outcomes

Upon completion of this course, students should have:

CS 321 will have a software engineering project that requires student to participate in working teams where students organize, manage, and practice a software engineering project. The team project will cover software requirements, design, coding and testing.

CS 321 includes Writing Intensive (WI) activities that, together with those of CS 306, meet the GMU WI Requirements in the BS CS Program (http://wac.gmu.edu). This means you will write 1750 graded words (or about 7 standard pages). You will get feedback on some writing assignments and you will be able to resubmit revisions based on the feedback. For this course, part of the writing will include an individual essay on your experiences working with your team.


Grade of C or better in CS 310 AND ENGH 302


While there is no specifically required textbook for this class, there are required readings. Readings will be either provided to you or be listed as chapters from the recommended textbooks.

Recommended: Software Modeling and Design: UML, Use Cases, Patterns, and Software Architectures, H. Gomaa (ISBN 10: 0521764149 / ISBN 13: 978-0521764148)

Recommended: Software Engineering, Ian Sommerville, 9th Edition, Addison-Wesley / Pearson Education Limited.

Grading Policy

Class Participation 5%
Presentation and Discussion 10%
Pop Quizzes 10%
Team Project 40%
Project Report 10%
Final Exam 25%
Class Participation

Completing the peer reviews for the presentations and providing constructive comments the presenters, participating in in-class discussions, completing polls/ short quizzes if assigned.

Presentation and Discussion

For this activity, you will work in pairs. You can pick your partner. This will be a 20 minute presentation.

You will discuss with your partner and select a short paper, article, white paper etc. and present it in class. You should provide details of the material to be presented ahead of time. Everyone in class should read the material to be presented.

Both you and your partner will present the material that you have chosen. It can be a powerpoint presentation or a talk followed by a discussion session. You and your partner will facilitate the discussion.

The first presentation will be on September 20

Pop quizzes

In-class. Can be assigned anytime. If you miss a pop quiz, you cannot retake it at another time.

Contesting of grades on any/all submissions must be requested within one week of the item's return. No grade changes will be considered subsequent to that deadline, or after the final exam meeting.

Final grades are calculated on a 10-point scale per letter grade, with the upper and lower 2% of each 10% earning a + or -.

A+ (>= 98.0%) A (>= 92.0%) A- (>= 90.0%)
B+ (>= 88.0%) B (>= 82.0%) B- (>= 80.0%)
C+ (>= 78.0%) C (>= 72.0%) C- (>= 70.0%)
D (>= 60.0%)
F (< 60.0%)

Honor Code

All students are expected to abide by the GMU Honor Code. This policy is rigorously enforced. All class-related assignments are considered individual efforts unless explicitly expressed otherwise (in writing). Review the university honor code and present any questions regarding the policies to instructor. Cheating on any assignment will be prosecuted and result in a notification of the Honor Committee as outlined in the GMU Honor Code.

Disability Accommodations

Students with a learning disability or other condition (documented with GMU Office of Disability Services) that may impact academic performance should speak with me ASAP to discuss accommodations.