Differences

This shows you the differences between two versions of the page.

--- start [2016/09/05 20:59] – jonathan
+++ start [2017/09/28 00:06] (current) – jonathan
@@ Line 1: / Line 1: @@
 ~~NOTOC~~
-====== EECS4312  Fall 2016: Software Engineering Requirements======
+====== EECS4312  Fall 2017: Software Engineering Requirements======
-**Fall 2016: CSE4312 -- Software Engineering Requirements**
+**Fall 2017: CSE4312 -- Software Engineering Requirements**
 Please __**login**__ at the bottom of this page before proceeding.
@@ Line 8: / Line 8: @@
 ← Please read the **forum** regularly for course updates.
+Some of your work is submitted at the Moodle site
+[[https://moodle.yorku.ca/moodle/course/view.php?id=103600|Moodle EECS4312E-F17]]
 ===== Lecture Times =====
-<hi>The first lecture is on Thursday (Sep. 8) in MC-211 (McLaughlin College). After that, lectures will be in Bergeron Room 313. The first scheduled Lab will also be on Thursday, directly after the class, in (Bergeron 321)</hi>
+Lectures are in Bergeron Room 313. The first scheduled Lab will also be on Thursday, directly after the class, in LAS 1002/1004. **The first Lab is Thursday 7, September (first day of class)**.
-  * Tuesdays & Thursdays 4pm-5.30pm
+  * **Lectures**: Tuesdays & Thursdays 4pm-5.30pm
-    * Tuesday lectures are to be held in: Bergeron Room 313 (except for the first lecture).
+    * Tuesday lectures are to be held in: Bergeron Room 313.
     * Thursday lectures are to be held in: Bergeron Room 313.
-  * There is a formal Lab every Thursday in  Bergeron 321, from 5.30pm to 6.30pm. Labs start right away on the first day of class (with Lab0). Login with your Prism account, then do: ''~sel/retrieve/4312/lab0''.
+  * **Labs**: There is a formal Lab every Thursday in  LAS1004, from 5.30pm to 6.30pm. Labs start right away on the first day of class (with Lab0). Login with your Prism account, then do: ''~sel/retrieve/4312/lab0''.
-  * There is a graded Quiz each week during the Lab.
+  * **Quizzes**: There is a graded Quiz each week during the Lab.
-  * <hi>Office hours: Thursdays, 2pm-3pm in the SEL (LAS2056)</hi>
+===== Text Book and other Important Information =====
+[[:protected:text:|Self-paced Learning, PVS and Text Books]]
 ===== Learning outcomes =====
@@ Line 35: / Line 40: @@
 A work-intensive project will allow students to apply their knowledge to a small but non-trivial example.
-===== Self-paced learning =====
-Attendance at all lectures is obligatory as material not available elsewhere will be covered. If you Login at (see bottom of this page), you can access additional information such as notes and some slides (on the SVN).
-You are required to develop facility in the following, on your own, in order to elicit requirements and write precise requirements documents:
-  * The PVS system for mathematical specifications. See  [[https://wiki.eecs.yorku.ca/project/sel-students/p:tutorials:pvs:start|PVS]]. Please familiarize yourselves with this system for writing and checking specifications using logic and discrete mathematics. You might want to work through the Telephone Book Example (see Introductory Tutorial) if you are  keen to get started.
-  * There will be some notes available in the SVN. The main supplemental text that you must also master is [[https://www.faa.gov/aircraft/air_cert/design_approvals/air_software/media/AR-08-32.pdf| Requirements Engineering Management Handbook (2009)]]. Free PDF.
-  * Some UML diagrams/methods for requirements elicitation. The book "UML distilled" by Martin Fowler, is available from Steacie, but the web has many resources (e.g [[http://edn.embarcadero.com/article/31863|here]] and [[http://www.sparxsystems.com/uml-tutorial.html|here]]). In particular, you must familiarize yourself with Use Case Diagrams, Class Diagrams, Sequence Diagrams and Statecharts to help in the elicitation of requirements.
-  * Latex, for writing well formatted documents. (Word and other document systems do not do as well as Latex for formatting mathematics). See [[https://wiki.eecs.yorku.ca/project/sel-students/p:tutorials:latex:|LaTeX]] for more information.
-In class we will only cover some (but not all) of the above. So you will need to master the above material at your own pace. There will be some informal labs to help with PVS.
-Place the following in the .cshrc file in your home directory of your Prism account:
-  setenv PVS_LIBRARY_PATH "/cse/local/pkg/pvs/nasalib"
-  source /cs/local/packages/texlive/cshrc.texlive
-===== Virtual Machine with PVS/Latex =====
-PVS and Latex are available on the Prism/Linux workstations. There is also an SEL Linux-based Virtual Box Image. For instructions, see [[https://wiki.eecs.yorku.ca/project/sel-students/p:tutorials:vm:start:|here]] (use your Prism login)
-The SEL-VM is also available on red:
-  red:/vbox/eecs-vbox-sel.ova
-The VM has PVS, Latex, Eclipse, EiffeStudio, ETF, Rodin, etc. so that you can run all the software on your Laptop or home computer.
-===== Required Textbook =====
-The following textbook is required reading:
-[[https://www.faa.gov/aircraft/air_cert/design_approvals/air_software/media/AR-08-32.pdf| Requirements Engineering Management Handbook (2009)]] (146 pages including appendices). This text is made available without cost as a PDF by the U.S. Department of Transportation, Federal Aviation Administration.
-This Handbook describes the following 11 main-level recommended practices that allow developers to progress from an initial, high-level overview of a system to be developed to a detailed description of its behavioral and performance requirements.
-.  Develop the System Overview
-.  Identify the System Boundary
-.  Develop the Operational Concepts
-.  Identify the Environmental Assumptions
-.  Develop the Functional Architecture
-.  Revise the Architecture to Meet Implementation Constraints
-.  Identify System Modes
-.  Develop the Detailed Behavior and Performance Requirements
-.  Define the Software Requirements
-. Allocate System Requirements to Subsystems
-. Provide Rationale
-All the material in the text is required reading and may appear on the Final Exam. Read Chapter 1 in the first week of the course. Thereafter, each week, master the material in Section 2.1, Section 2.2 .. etc. The ideas are illustrated in the appendix using the Isolelete Thermostat example, the flight control and guidance system, and the autopilot system. You are required to understand these examples.
-===== Suggested Text =====
-This course cannot treat all the important topics in RE. If you want find out more about Requirements Engineering, the text [[http://i.f.alexander.users.btopenworld.com/reviews/lamsweerde.htm|Requirements Engineering: from system goals to UML models to software specifications]], Axel van Lamsweerde Wiley, 2009 ISBN 0470012706 (paper, 682 pages), is available in Steacie. ([[http://i.f.alexander.users.btopenworld.com/|Reviews of books on requirements engineering]]). Topics in the book include:
-  * A comprehensive introduction to the fundamentals of requirements engineering, including techniques for: requirements elicitation and reuse, risk analysis, conflict management, and requirements prioritization; requirements specification, inspection, validation, and verification; traceability management and change control.
-  * An in–depth treatment of system modelling for requirements engineering, including constructive techniques for modeling system goals, conceptual objects, responsibilities among system agents, operations, scenarios and intended behaviors, and countermeasures to anticipated hazards and threats.
-  * A variety of techniques for model–based evaluation of alternative options, model refinement checking, model animation, property verification, inductive model synthesis, and analysis of conflicts, hazards, and security threats.
-  * Use of standard UML notations wherever applicable. Most techniques are based on a solid formal framework, kept hidden throughout the major part of the book for wider accessibility.
-  * Numerous examples from running case studies in a variety of domains, including security– and safety–critical ones. Rich set of problems and exercises at the end of each chapter together with bibliographical notes for further study.