Instructor: Janet E. Burge, 205V Benton Hall, 9-0346, burgeje-at-muohio.edu
Office Hours: M: 10am, T: 3:00 pm, W: 10 am, Th: 4:00 pm (subject to change)

Prerequisite: CSA 271 (Object Oriented Programming)
Required Text: Bruegge & Dutoit, Object-Oriented Software Engineering Using UML, Patterns, and Java, 3rd Edition
Additional References: See Course Documents and Assignments on Cascade (https://my.csi.muohio.edu/)

Catalog Description: Principles of software engineering: Introduction to all phases of the software development life cycle and associated tools and engineering methods including the unified modeling language (UML).

Student Learning Outcomes:

1: To provide students with a foundation for further study of software engineering, they will be able to:

• 1.1: Explain the role of a software engineer and software engineering as an engineering discipline.
• 1.2: Apply a contemporary analysis and design approach, such as object-oriented to a case study.
• 1.3: Describe software development life-cycle and need for associated processes: the life-cycle phases, engineering and management processes, and relationships between the phases and processes.
• 1.4: Describe and compare alternative software process standards and processes (e.g. waterfall, incremental, spiral, prototyping, empirical and agile methods)
• 1.5: Explain roles and responsibilities in a software team, and management issues of teams.

2: To develop clear, concise, and sufficiently formal life-cycle artifacts including requirements, design, implementation, and test documentation for software systems based on needs of users and stakeholders, students will be able to:

• 2.1: Explain the motivation for defining sufficiently explicit requirements.
• 2.2: Analyze and create a requirements specifications using scenarios, use cases and use case diagrams from a set of customer needs.
• 2.3 Brainstorm alternative solutions, select from alternatives, and create designs and appropriate documentation using UML class and sequence diagrams and other appropriate methods for the problem domain.

3: To explain the value of construction technologies such version control and design tools to assist the software development practice, students will be able to:

• 3.1: Explain the purpose of version control and apply it to manage software design or code artifacts.
• 3.2: Apply software tools to create design artifacts such as UML diagrams.

4: To explain software design concepts and apply them, students will be able to:

• 4.1: Review concepts and strategies in software design including architectural design, detailed design, and user interface design.
• 4.2: Create UML class diagrams that represent a problem domain from a requirement specification.
• 4.3: Create UML sequence diagrams to express class behavior.
• 4.4: Evaluate alternative designs at an introductory level through reviews (e.g. review of class diagrams).
• 4.5: Describe general design principles: coupling, cohesion, portability, design by responsibility, etc.
• 4.6: Describe several design patterns (GRASP, GoF, etc).
• 4.7: Describe strategies for mapping design to code (such as responsibility driven design)

5: To demonstrate the ability to work in a team and to communicate, orally and in writing, a software design to various audiences

• 5.1: Work in a team to experience a portion of the software development lifecycle.
• 5.2: Make oral presentations of system design artifacts to users or peers.
• 5.3: Compile well-written design artifacts for presentation to users, peers, or the instructor.
• 5.4: Students can document a project plan, document progress, and communicate progress to users, peers, or the instructor

6: To explain testing and quality assurance strategies, student will be able to:

• 6.1: Distinguish between program validation and verification.
• 6.2: Distinguish among the different types and levels of testing (unit, integration, systems, acceptance, regression, black box, white box).
• 6.3: Use abuse cases to identify potential security requirements.
• 6.4: Describe test-driven design.

Syllabus: Note: topics, dates, and assignments are subject to change at instructor's discretion. The TBD elements in the syllabus will be filled in after the start of the semester. Assignments are due at the time specified in Cascade. For individual projects, no late work will be accepted. For group projects, status reports must be received on time. For other group deliverables late assignments will be penalized 10% the first 24 hrs, 25% the next (reductions will be taken at the time of computing the final grades for the course). Assignments more than 48 hours late will not be graded. Laboratory exercises must be completed during the scheduled lab period and turned in at the end of that time. Labs can only be made up in the case of documented illnesses or other excused absences with prior instructor permission.

Grading: The final grade for CSA348 is based on the following:

Grading Policy:

Numeric grades will be given for all assignments.

98-100 = A+	92-97.9 = A	90-91.9 = A-
88-89.9 = B+	82-87.9 = B	80-81.9 = B-
78-79.9 = C+	72-77.9 = C	70 - 71.9 = C-
68-69.9 = D+	62-67.9 = D	60-61.9 = D-
< 59.9 = F

Group Projects: In your future careers as software professionals, you will need to be able to work with others. This means an often difficult balancing of personalities, abilities, schedules, and motivation levels. You are unlikely to have the ability to fire a co-worker (although you may want to) and are even less likely to get your supervisor's permission to break from the group to do your own, parallel, version of the project. That won't happen here either. It is important to know that group members will be assessing each other and that not all members of the group will necessarily receive the same grade for the project.

Groups:

The A Team: Kyle Daigle, Tom Gordon, Todd Dickson, Derek Naylor - Operation/Building game

The B Team: Amanda Smith, Josh Wonser, Tyler Watson, Thomas Barber - Touch part, hear name/Hear name, touch part

Channel 5 News Team: Annika Klopfer, Jordan Brooker, Jon Jekeli, Parker Johnson - Simon Says

The Red Team: Mark Koeninger, Keith Rankin, Taylor Young, Joe McAbee = Matching Game

Team Spaghetti: Andrew Favia, William Morrison, Yechen Qiao, Tim Russo - Word Search/Crossword

Team Henry: Andrew Hehe, Andrew Ward, David Schrumpf, Henry Talamini - Trivia Game

Academic Honesty: All work assigned as individual work must be done as individual work and in accordance with the departmental Academic Integrity statement. Violations will be handled in accordance with the Miami University Academic Honesty Policy.