auto update

content/notes/08-personas-and-scenarios.md

@@ -1,7 +1,7 @@
 ---
 title: "08-personas-and-scenarios"
-sr-due: 2022-04-05
+sr-due: 2022-04-30
-sr-interval: 8
+sr-interval: 23
 sr-ease: 250
 tags: 
 - info203 

content/notes/info-201-outline.md

@@ -12,6 +12,7 @@ links: [[notes/info-201]]
 - [systems-development-life-cycle](notes/systems-development-life-cycle.md)
 - [agile-development](notes/agile-development.md)
 - [predictive-adaptive-spectrum](notes/predictive-adaptive-spectrum.md)
+- 
 - [requirements-elicitation](notes/requirements-elicitation.md)
 - [approaches-to-systems-development](notes/approaches-to-systems-development.md)
 - [business-functions](notes/business-functions.md)

content/notes/info-203-outline.md

@@ -13,7 +13,7 @@ links: [[notes/info-203]]
 - [participant-observation](notes/participant-observation.md)
 - [interviewing](notes/interviewing.md)
 - [user-experience](notes/user-experience.md)
-- [usbability](notes/usbability.md)]
+- [usbability](notes/usbability.md)
 - [hci](notes/hci.md)
 - [storyboards](notes/storyboards.md)
 - [personas-and-scenarios](notes/personas-and-scenarios.md)

content/notes/requirements-document.md

@@ -0,0 +1,16 @@
+---
+title: "requirements-document"
+tags: 
+- info201
+---
+
+The requirements document is used to keep track of the requirements of a system. It hold information such as: constraints, the environment of the system, information about the domain of the system, and constraints
+
+The requirements document should include:
+- contraints
+- requirements
+- overall properties
+- systems env incl. related sys's
+- application domain information
+- constraints of development process
+

content/notes/requirements.md

@@ -0,0 +1,32 @@
+---
+title: "requirements"
+tags: 
+- info201
+---
+
+> “…descriptions of how the system should behave, application domain information, constraints on the system’s operation, or specifications of a system property or attribute.”  - Kotonya and Sommerville, 2001, p. 6
+
+> “…a statement of need, something that some class of user or other stakeholder wants.” - Alexander and Stevens, 2002, p. 8
+
+Requirements are something an information system should do, or some constraint it should adhere to
+
+# 1 Requirements engineering
+
+> “…to cover all of the activities involved in discovering, documenting, and maintaining a set of requirements for a computer-based system.” - Kotonya and Sommerville, 2001, p. 8
+
+Requirements engineering is a robust methodology for the development of requirements. It is made  up of three key concepts.
+
+## 1.1 Discovery
+
+This is where you identify all the requirments of the system. [requirements-elicitation](notes/requirements-elicitation.md) is done here. Many techniques such as [interviewing](notes/interviewing.md), [participant-observation](notes/participant-observation.md), [prototyping](notes/prototyping.md), and more are used here.
+
+
+## 1.2 Documenting
+
+This is where the requirements are specified and refined, and models are created. All the requirements are compiled into a [requirements document](notes/requirements-document)
+
+
+## 1.3 Maintenance
+
+This occurs throughout development and is primarly focuses on manageing changes in the environment of the system
+