diff --git a/Day 1 (intro, project selection)/notes.txt b/Day 01 (intro, project selection)/notes.txt
similarity index 100%
rename from Day 1 (intro, project selection)/notes.txt
rename to Day 01 (intro, project selection)/notes.txt
diff --git a/Day 2 (project selection, requirements role play)/URD_Dioscuri_KBNA_v1_1_en.pdf b/Day 02 (project selection, requirements role play)/URD_Dioscuri_KBNA_v1_1_en.pdf
similarity index 100%
rename from Day 2 (project selection, requirements role play)/URD_Dioscuri_KBNA_v1_1_en.pdf
rename to Day 02 (project selection, requirements role play)/URD_Dioscuri_KBNA_v1_1_en.pdf
diff --git a/Day 2 (project selection, requirements role play)/notes.txt b/Day 02 (project selection, requirements role play)/notes.txt
similarity index 100%
rename from Day 2 (project selection, requirements role play)/notes.txt
rename to Day 02 (project selection, requirements role play)/notes.txt
diff --git a/Day 2 (project selection, requirements role play)/requirementsspecsexample.pdf b/Day 02 (project selection, requirements role play)/requirementsspecsexample.pdf
similarity index 100%
rename from Day 2 (project selection, requirements role play)/requirementsspecsexample.pdf
rename to Day 02 (project selection, requirements role play)/requirementsspecsexample.pdf
diff --git a/Day 3 (brainstorming session)/brainstorming session.txt b/Day 03 (brainstorming session)/brainstorming session.txt
similarity index 100%
rename from Day 3 (brainstorming session)/brainstorming session.txt
rename to Day 03 (brainstorming session)/brainstorming session.txt
diff --git a/Day 3 (brainstorming session)/notes.txt b/Day 03 (brainstorming session)/notes.txt
similarity index 100%
rename from Day 3 (brainstorming session)/notes.txt
rename to Day 03 (brainstorming session)/notes.txt
diff --git a/Day 4 (initial stakeholder meeting prep)/notes.txt b/Day 04 (initial stakeholder meeting prep)/notes.txt
similarity index 100%
rename from Day 4 (initial stakeholder meeting prep)/notes.txt
rename to Day 04 (initial stakeholder meeting prep)/notes.txt
diff --git a/Day 6-9 (writing a requirements document)/Campus visits.html b/Day 06-09 (writing a requirements document)/Campus visits.html
similarity index 100%
rename from Day 6-9 (writing a requirements document)/Campus visits.html
rename to Day 06-09 (writing a requirements document)/Campus visits.html
diff --git a/Day 6-9 (writing a requirements document)/CampusVisits.md b/Day 06-09 (writing a requirements document)/CampusVisits.md
similarity index 98%
rename from Day 6-9 (writing a requirements document)/CampusVisits.md
rename to Day 06-09 (writing a requirements document)/CampusVisits.md
index 015087e..33f11c7 100644
--- a/Day 6-9 (writing a requirements document)/CampusVisits.md
+++ b/Day 06-09 (writing a requirements document)/CampusVisits.md
@@ -1,8 +1,8 @@
-# Campus visits
+# Campus visits requirements document
Prepared by: Michael Kowalczyk
-Revision date: 9/12/2024
+Revision date: 9/28/2024
## Overview
@@ -39,7 +39,6 @@ We would like a system to address the following:
- *Faculty* - a user who can do campus visits for Computer Science.
- *Available times* - (for faculty only) a weekly schedule of regularly available times for campus visits
- Visit
- - *Visitors* - a list of people in the visiting group
- *Possible times* - a list of time intervals in which the visitors are available on the visit day
- *Day* - the calendar day for which the visit has been scheduled with the campus visit office
- *DecidedTime* - the time at which the faculty member has agreed to meet for this visit
@@ -80,7 +79,7 @@ There are a few problem domain events of interest. For each of these a source i
- *ConfirmVisit* - the department secretary contacts the Campus Visit office that someone has taken the visit. Parameters: visit's *decidedGuide* and *decided time*. *Source:* department secretary (coordinator role).
- *CancelVisit* - the campus visit office notifies the department secretary that the visit has been cancelled by the student. *Parameters:* Visit. *Source:* department secretary (coordinator role).
- *AbaondonVisit* - some circumstance has caused the faculty member to vacate the guide position for a visit. *Parameters:* Visit. *Source:* faculty member.
-- *VisitTimePassed* - the *decidedTime* for the visit plus an hour has passed in Eastern Time.
+- *VisitTimePassed* - the *decidedTime* for the visit plus an hour has passed in Eastern Time; the visit is assumed to be completed.
- *AdjustNotificationFrequency* - *Parameters:* Visit, numberOfDays. Sets the frequency for periodic notifications to the given number of days. *Source:* department secretary (coordinator role)
- *SetCommittmentLevel* - a faculty member sets (or clears) their committment level for a particular visit. *Parameters:* faculty, visit, level. *Source:* faculty. Invariant: The committment level must always be "can do" for the assigned guide, if any.
- *EditAvailableTimes* - *Parameters:* faculty, subset of daytime hours for each weekday. Sets the available times for that faculty member.
diff --git a/Day 6-9 (writing a requirements document)/entityRelationships.png b/Day 06-09 (writing a requirements document)/entityRelationships.png
similarity index 100%
rename from Day 6-9 (writing a requirements document)/entityRelationships.png
rename to Day 06-09 (writing a requirements document)/entityRelationships.png
diff --git a/Day 6-9 (writing a requirements document)/entityRelationships.puml b/Day 06-09 (writing a requirements document)/entityRelationships.puml
similarity index 100%
rename from Day 6-9 (writing a requirements document)/entityRelationships.puml
rename to Day 06-09 (writing a requirements document)/entityRelationships.puml
diff --git a/Day 6-9 (writing a requirements document)/eventsAndVisitStates.png b/Day 06-09 (writing a requirements document)/eventsAndVisitStates.png
similarity index 100%
rename from Day 6-9 (writing a requirements document)/eventsAndVisitStates.png
rename to Day 06-09 (writing a requirements document)/eventsAndVisitStates.png
diff --git a/Day 6-9 (writing a requirements document)/eventsAndVisitStates.puml b/Day 06-09 (writing a requirements document)/eventsAndVisitStates.puml
similarity index 100%
rename from Day 6-9 (writing a requirements document)/eventsAndVisitStates.puml
rename to Day 06-09 (writing a requirements document)/eventsAndVisitStates.puml
diff --git a/Day 13-14 (prototyping)/Campus Visit Prototype.epgz b/Day 13-14 (prototyping)/Campus Visit Prototype.epgz
new file mode 100644
index 0000000..c5e09a6
Binary files /dev/null and b/Day 13-14 (prototyping)/Campus Visit Prototype.epgz differ
diff --git a/Days 13-14 (prototyping)/UI design principles.txt b/Day 13-14 (prototyping)/UI design principles.txt
similarity index 100%
rename from Days 13-14 (prototyping)/UI design principles.txt
rename to Day 13-14 (prototyping)/UI design principles.txt
diff --git a/Days 13-14 (prototyping)/boxes.png b/Day 13-14 (prototyping)/boxes.png
similarity index 100%
rename from Days 13-14 (prototyping)/boxes.png
rename to Day 13-14 (prototyping)/boxes.png
diff --git a/Days 13-14 (prototyping)/clickable prototype/Resources/expand.png b/Day 13-14 (prototyping)/clickable prototype/Resources/expand.png
similarity index 100%
rename from Days 13-14 (prototyping)/clickable prototype/Resources/expand.png
rename to Day 13-14 (prototyping)/clickable prototype/Resources/expand.png
diff --git a/Days 13-14 (prototyping)/clickable prototype/Resources/fit.png b/Day 13-14 (prototyping)/clickable prototype/Resources/fit.png
similarity index 100%
rename from Days 13-14 (prototyping)/clickable prototype/Resources/fit.png
rename to Day 13-14 (prototyping)/clickable prototype/Resources/fit.png
diff --git a/Days 13-14 (prototyping)/clickable prototype/Resources/script.js b/Day 13-14 (prototyping)/clickable prototype/Resources/script.js
similarity index 100%
rename from Days 13-14 (prototyping)/clickable prototype/Resources/script.js
rename to Day 13-14 (prototyping)/clickable prototype/Resources/script.js
diff --git a/Days 13-14 (prototyping)/clickable prototype/Resources/style.css b/Day 13-14 (prototyping)/clickable prototype/Resources/style.css
similarity index 100%
rename from Days 13-14 (prototyping)/clickable prototype/Resources/style.css
rename to Day 13-14 (prototyping)/clickable prototype/Resources/style.css
diff --git a/Day 13-14 (prototyping)/clickable prototype/index.html b/Day 13-14 (prototyping)/clickable prototype/index.html
new file mode 100644
index 0000000..bd19ce2
--- /dev/null
+++ b/Day 13-14 (prototyping)/clickable prototype/index.html
@@ -0,0 +1,2 @@
+
\ No newline at end of file
diff --git a/Day 13-14 (prototyping)/clickable prototype/pages/availability.png b/Day 13-14 (prototyping)/clickable prototype/pages/availability.png
new file mode 100644
index 0000000..0e991d4
Binary files /dev/null and b/Day 13-14 (prototyping)/clickable prototype/pages/availability.png differ
diff --git a/Days 13-14 (prototyping)/clickable prototype/pages/confirmnonvolunteer.png b/Day 13-14 (prototyping)/clickable prototype/pages/confirmnonvolunteer.png
similarity index 100%
rename from Days 13-14 (prototyping)/clickable prototype/pages/confirmnonvolunteer.png
rename to Day 13-14 (prototyping)/clickable prototype/pages/confirmnonvolunteer.png
diff --git a/Day 13-14 (prototyping)/clickable prototype/pages/deleteuser.png b/Day 13-14 (prototyping)/clickable prototype/pages/deleteuser.png
new file mode 100644
index 0000000..5e2ac12
Binary files /dev/null and b/Day 13-14 (prototyping)/clickable prototype/pages/deleteuser.png differ
diff --git a/Day 13-14 (prototyping)/clickable prototype/pages/editavailability.png b/Day 13-14 (prototyping)/clickable prototype/pages/editavailability.png
new file mode 100644
index 0000000..261c585
Binary files /dev/null and b/Day 13-14 (prototyping)/clickable prototype/pages/editavailability.png differ
diff --git a/Days 13-14 (prototyping)/clickable prototype/pages/emailchoice.png b/Day 13-14 (prototyping)/clickable prototype/pages/emailchoice.png
similarity index 100%
rename from Days 13-14 (prototyping)/clickable prototype/pages/emailchoice.png
rename to Day 13-14 (prototyping)/clickable prototype/pages/emailchoice.png
diff --git a/Days 13-14 (prototyping)/clickable prototype/pages/emailchoiceconfirmed.png b/Day 13-14 (prototyping)/clickable prototype/pages/emailchoiceconfirmed.png
similarity index 100%
rename from Days 13-14 (prototyping)/clickable prototype/pages/emailchoiceconfirmed.png
rename to Day 13-14 (prototyping)/clickable prototype/pages/emailchoiceconfirmed.png
diff --git a/Day 13-14 (prototyping)/clickable prototype/pages/emailclient.png b/Day 13-14 (prototyping)/clickable prototype/pages/emailclient.png
new file mode 100644
index 0000000..266103c
Binary files /dev/null and b/Day 13-14 (prototyping)/clickable prototype/pages/emailclient.png differ
diff --git a/Day 13-14 (prototyping)/clickable prototype/pages/emailsettings.png b/Day 13-14 (prototyping)/clickable prototype/pages/emailsettings.png
new file mode 100644
index 0000000..298c2cc
Binary files /dev/null and b/Day 13-14 (prototyping)/clickable prototype/pages/emailsettings.png differ
diff --git a/Day 13-14 (prototyping)/clickable prototype/pages/login.png b/Day 13-14 (prototyping)/clickable prototype/pages/login.png
new file mode 100644
index 0000000..88821a9
Binary files /dev/null and b/Day 13-14 (prototyping)/clickable prototype/pages/login.png differ
diff --git a/Day 13-14 (prototyping)/clickable prototype/pages/metamenu.png b/Day 13-14 (prototyping)/clickable prototype/pages/metamenu.png
new file mode 100644
index 0000000..d00a966
Binary files /dev/null and b/Day 13-14 (prototyping)/clickable prototype/pages/metamenu.png differ
diff --git a/Day 13-14 (prototyping)/clickable prototype/pages/users.png b/Day 13-14 (prototyping)/clickable prototype/pages/users.png
new file mode 100644
index 0000000..46336e2
Binary files /dev/null and b/Day 13-14 (prototyping)/clickable prototype/pages/users.png differ
diff --git a/Day 13-14 (prototyping)/clickable prototype/pages/visitdetails.png b/Day 13-14 (prototyping)/clickable prototype/pages/visitdetails.png
new file mode 100644
index 0000000..a767ab6
Binary files /dev/null and b/Day 13-14 (prototyping)/clickable prototype/pages/visitdetails.png differ
diff --git a/Day 13-14 (prototyping)/clickable prototype/pages/visits.png b/Day 13-14 (prototyping)/clickable prototype/pages/visits.png
new file mode 100644
index 0000000..fd7b8ec
Binary files /dev/null and b/Day 13-14 (prototyping)/clickable prototype/pages/visits.png differ
diff --git a/Day 21 (lifecycle models)/notes.md b/Day 21 (lifecycle models)/notes.md
new file mode 100644
index 0000000..f71adc3
--- /dev/null
+++ b/Day 21 (lifecycle models)/notes.md
@@ -0,0 +1,39 @@
+# Software development life cycles (SDLC)
+
+Here are several popular SDLC models:
+
+## Waterfall
+The waterfall model is best suited for well-defined complex projects, where problems can be spotted early and complexity is dealt with in an orderly way. Key distadvantages include low customer visibility and low flexibility to mid-project changes.
+
+## Incremental development
+"Incremental" here refers to adding to the work products (requirements, source code, etc.) in stages. In each stage, more functionality is added (core functionality first).
+
+## Iterative development
+In iterative development one iterates through the whole process (requirements → ... → deployment) multiple times. Iterative and incremental development often go together.
+
+## Spiral
+Spiral is a type of incremental and iterative development where risk assessment occurs at the start of each cycle.
+
+## Agile
+Agile is a form of incremental and iterative development with emphasis on frequent face-to-face communication, high customer visibility, adaptability to change, and minimizing non-software work products.
+
+## Evolutionary
+In an evolutionary model, deliverables are given to the customer frequently and incrementally. The focus is on high-value features first and getting customer feedback early and often.
+
+## Code & Fix
+This is a kind of incremental development where life cycle phases other than coding and debugging (requirements analysis, software design, testing, etc.) are skipped, and code refactoring is often neglected.
+
+## Prototyping
+This isn't really a life cycle on its own (although it can be adapted as such, as with "evolutionary prototyping"). Rather, it's a technique that is good for dealing with unclear requirements, assisting in communication, or in developing initial user interface design.
+
+# Questions guiding the choice of SDLC model
+This list is adapted from *Rapid Development* by Steve McConnell.
+- How well do the customer and development team understand the requirements?
+- How likely are requirements to change?
+- Are major archiectural changes likely?
+- Are there hard schedule constraints?
+- Are the relevant tools and technologies well-understood by the development team?
+- Is high visibility important to customers and/or management?
+- How will human factors affect the project (discipline, skills, training, and intellectual limits)?
+- What opportunities are there to parallelize work phases?
+
diff --git a/Days 13-14 (prototyping)/Campus Visit Prototype.epgz b/Days 13-14 (prototyping)/Campus Visit Prototype.epgz
deleted file mode 100644
index f2d6b64..0000000
Binary files a/Days 13-14 (prototyping)/Campus Visit Prototype.epgz and /dev/null differ
diff --git a/Days 13-14 (prototyping)/clickable prototype/index.html b/Days 13-14 (prototyping)/clickable prototype/index.html
deleted file mode 100644
index c9fb644..0000000
--- a/Days 13-14 (prototyping)/clickable prototype/index.html
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Campus Visit Prototype