Syllabus: ESOF 423
Software Engineering Applications
Spring Semester 2020
Schedule: Monday, Wednesday, Friday 10:00 - 10:50 am*
* Class meets live in A.J.M. Johnson Hall Room 238 and alternatively by WebEx.
|
Week |
Date |
Topic |
Notes |
Projects |
|
1 |
M Jan 11 W Jan 13 F Jan 15 |
Class introduction Overview of resources Scrum |
|
|
|
2 |
M Jan 18 W Jan 20 F Jan 22 |
MLK DAY - No classes |
Paul, Bill: clients pitch projects to class. |
Group, Project Choice |
|
3 |
M Jan 25 W Jan 27 F Jan 29 |
-- Version Controlling -- |
|
Sprint 0: Planning meeting |
|
4 |
M Feb 1 W Feb 3 F Feb 5 |
-- Local Development -- |
|
Weekly Scrum
Sprint review; ZFR, SRS |
|
5 |
M Feb 8 W Feb 10 F Feb 12 |
-- Continuous Integration -- |
|
Sprint 1: Planning meeting |
|
6 |
M Feb 15 W Feb 17 F Feb 19 |
PRESIDENTS DAY - No classes Black box testing -- |
|
Weekly Scrum
Sprint review; design doc |
|
7 |
M Feb 22 W Feb 24 F Feb 26 |
-- RESTful APIs -- |
|
Sprint 2: Planning meeting |
|
8 |
M Mar 1 W Mar 3 F Mar 5 |
-- Effective unit testing -- |
|
Weekly Scrum
Sprint review; Beta release |
|
9 |
M Mar 8 W Mar 10 F Mar 12 |
-- Software and Web App Testing -- |
|
Sprint 3: Planning meeting |
|
10 |
M Mar 15 W Mar 17 F Mar 19 |
-- Code Refactoring (async recording) -- |
|
Weekly Scrum
Sprint review (async recording) |
|
11 |
M Mar 22 W Mar 24 F Mar 26 |
-- TDD/PP -- |
|
Sprint 4: Planning meeting |
|
12 |
M Mar 29 W Mar 31 F Apr 2 |
-- Sprint Reviews; FCR demos UNIVERSITY DAY - No classes |
|
Weekly Scrum Sprint review; Feature complete release |
|
13 |
M Apr 5 W Apr 7 F Apr9 |
-- Static Code Analysis, Code reviews -- |
|
Sprint 5: Planning meeting
|
|
14 |
M Apr 12 W Apr 14 F Apr16 |
-- Guest Lecture: Carson Gross: HTMX -- |
|
Weekly Scrum
Sprint review; Release candidate |
|
15 |
M Apr 19 W Apr 21 F Apr23 |
-- Post Mortem: Class discussion (lessons learned) -- |
|
Sprint 6: Planning meeting |
|
Finals Week |
M Apr 26 W Apr 28 F Apr30 |
SpecialProject Presentations: Groups 3, 4, 6 VCPlayers Tickeing Presentations: Groups 5, 1, 2 no class |
Finals Week (no final)
|
Comments API Ticketing System Final release due |
Meetings
- Monday, Wednesday, Friday from 1:10 pm - 2:00 pm in A.J.M Johnson Hall Room 238.
Instructor
- Mr. Daniel DeFrance
- Office hours
- Office: Barnard Hall 358
- E-Mail: daniel.defrance@montana.edu
Course Assistants
- TBD
- Availability for Assistance: TBD, and by appointment.
- Location: Barnard Hall 259
- Email:
Course Policies
No cheating - The work you submit to be graded must be your own.
No late assignments - Assignments submitted after the due date will not receive credit. Please plan accordingly.
Medical emergencies - If there is a medical emergency, tragedy or sudden hardship, you will need to provide written confirmation in order to have consideration for an exception to any grading schedules.
Additional Course Information
Textbook (optional; recommended)
Object-Oriented Software Engineering - Practical software development using UML and Java, Timothy C. Lethbridge Robert Laganière, Second edition, 2005
Grading
Final letter grades will be based on the relative distribution of total scores and not on any preset numerical grade.
- Assignments: 20%
- Project Sprints: 50%
- Sprint planning meeting outcomes
- Scrum meeting participation
- Work done toward achieving the defined sprint goal
- Proper maintenance of the scrum artifacts (burn down charts and updated product backlog)
- Maintenance of the git workflow and the repository and continuous integration
- Testing and quality assurance
- Final project presentation + Portfolio – 10%;
- Presentation content: high level UML diagrams displaying the design, discussion on the design patterns used, discussion of code maintainability/extensibility and methods used to accomplish them, quality assurance methods and their evaluation.
- Final product – 20%;
- Will be divided among the intermediate releases Completed requirements, application of design patterns and refactoring, code maintainability/extensibility and quality assurance methods, continuous integration and delivery
At the end of the semester, grades will be determined (after any curving takes place) based on your class average as follows:
- 93% and higher: A Excellent quality and intellectual initiative
- 90% and higher: A-
- 87% and higher: B+ High quality and intellectual initiative
- 83% and higher: B
- 80% and higher: B-
- 77% and higher: C+ Acceptable quality, satisfactory achievement
- 73% and higher: C
- 70% and higher: C-
- 67% and higher: D+ Deficient quality, did not meet minimum requirements
- 63% and higher: D
- Otherwise: F
Additional MSU Resources
Copyright Notice
This syllabus, course lectures and presentations, and any course materials provided throughout this term are protected by U.S. copyright laws. Students enrolled in the course may use them for their own research and educational purposes. However, reproducing, selling or otherwise distributing these materials without written permission of the copyright owner is expressly prohibited, including providing materials to commercial platforms such as Chegg or CourseHero. Doing so may constitute a violation of U.S. copyright law as well as MSU’s Code of Student Conduct.
© 2021 Daniel DeFrance