Informatics 113: Requirements Analysis and Engineering

Winter Quarter 2010

Last update: March 12, 2010

Instructor:	Richard N. Taylor
Email:	(taylor [at] ics [dot] uci [dot] edu) To ensure a response to your email, please include "Informatics 113" in the subject line and send your email from a UCI account.
Office hours:	After class, or by email appointment
Lectures:	M, W, F 2:00-2:50, DBH 1300
TA	Leyna Cotran (leynacotran [at] gmail [dot] com). Office hours: Fridays, 3-5pm DBH 5^th floor (lab) or send your questions via email. To ensure a response to your email, please include “Informatics 113” in the subject line and send your email from a UCI account.
Web site:	http://www.ics.uci.edu/~taylor/classes/113/syllabusWQ10.html (main site) https://eee.uci.edu/10w/37040 (the EEE site: has some files not publicly accessible)

What's New?

[February 19] Numerous updates; addition of Assignment 2.
[January 18] The "official" course website is now on EEE. It links to this website as the "real syllabus". The main purpose of the EEE site is that it contains a variety of files that you will find useful, but which for various reasons cannot be made publicly accessible. Copies of many of the slides used in class are available there now, and some homework assignment related files are also there. Some email/announcements on these topics will be forthcoming.
[January 12] Some Cranium links added.
Syllabus updated! New dates for exams, new assignment structure, no quizzes...
Check back here for weekly updates and class announcements

Description - Schedule - Grading - Readings - Policies

Description

Catalog description:

Aims to equip students to develop techniques of software-intensive systems through successful requirements analysis techniques and requirements engineering. Students learn systematic process of developing requirements through co-operative problem analysis, representation, and validation. Prerequisite: In4Mtx 43 or ICS52 with a grade of C or better.

Textbook and Assigned Readings

Required Textbooks:

Van Lamsweerde, A. Requirements Engineering. John Wiley & Sons, Ltd. UK 2009.

Articles (for further study)

Nuseibeh, B. and Easterbrook, S. 2000. Requirements engineering: a roadmap. In Proceedings of the Conference on the Future of Software Engineering (Limerick, Ireland, June 04 - 11, 2000). ICSE '00. ACM, New York, NY, 35-46. DOI= http://doi.acm.org/10.1145/336512.336523NSB
Brooks, F. P. 1987. No Silver Bullet Essence and Accidents of Software Engineering. Computer 20, 4 (Apr. 1987), 10-19. DOI= http://dx.doi.org/10.1109/MC.1987.1663532
Hall, J. G., Jackson, M., Laney, R. C., Nuseibeh, B., and Rapanotti, L. 2002. Relating Software Requirements and Architectures Using Problem Frames. In Proceedings of the 10th Anniversary IEEE Joint international Conference on Requirements Engineering (September 09 - 13, 2002). RE. IEEE Computer Society, Washington, DC, 137-144.
Gotel, O. & Finkelstein, A. (1994). An Analysis of the Requirements Traceability Problem. 1st International Conference on Requirements Engineering (ICRE'94), Colorado Springs, April 1994, pp. 94-101.
Cao, L. and Ramesh, B. 2008. Agile Requirements Engineering Practices: An Empirical Study. IEEE Softw. 25, 1 (Jan. 2008), 60-67. DOI= http://dx.doi.org/10.1109/MS.2008.1
Janzen, D. and Saiedian, H. 2005. Test-Driven Development: Concepts, Taxonomy, and Future Direction. Computer 38, 9 (Sep. 2005), 43-50. DOI= http://dx.doi.org/10.1109/MC.2005.314
Scacchi, W. 2002. Understanding the Requirements for Developing Open Source Software Systems. IEE PROC SOFTWARE. Vol. 149, no. 1, pp. 24-39. Feb. 2002
Leveson, N. G. and Turner, C. S. 1993. An Investigation of the Therac-25 Accidents. Computer 26, 7 (Jul. 1993), 18-41. DOI= http://dx.doi.org/10.1109/MC.1993.274940

Schedule

Subject to change!

Week	Date		Discussion Topic	Reading	Assignments Due
1	January	4	Setting the Scene: Architecture and Design
		6	Setting the Scene: RE and the SW Lifecycle	Ch.1
		8	Setting the Scene: RE Fundamentals
2		11	Domains, DSSAs, and Requirements	Ch.2
		13	Requirements Elicitation Techniques	Ch.2,
		15	Requirements Evaluation	Ch. 3
3		18	MLK Jr. Day - no class!		(Email TA re: group membership by January 19th; teams confirmed by the 20th) Assignment 1 emailed by the 19th.
		20	Requirements Specification and Documentation. Ex ad A7-E example	Ch.4 - 4.1 and 4.2
		22	Diagrammatic Notations	Ch.4 - 4.3
4		25	Diagrammatic Notations Use case example	Ch.4 -4.3-4.4*
		27	Diagrammatic Notations: SADT John Mylopoulos DMsite BatonExample
		29	RE QA	Ch. 5	Assignment 1: Cranium project due
5	February	1	Traceability; Change Management, Requirements Evolution	Ch. 6
		3	Traceability, continued
		5	Review for Exam
6		8	Midterm #1 (through Chapter 6)
		10	"Snow Day"
		12	Goals	Ch.7
7		15	President's Day - no class!
		17	Modeling System Objectives	Ch. 8
		19	Discussion of Assignment 2		Assignment 2
8		22	Modeling system objectives, continued
		24	Modeling system objectives, continued
		26	Verification and Validation/ Review for Exam [LC]
9	March	1	Midterm #2 (Chapter 6, 7, and 8 )
		3	Requirements in Practice
		5	Requirements in Practice, part II
10		8	Exam review and Requirements in Practice, part III
		10	A Computational Web
		12	Last class - final prep		Assignment 2 due March 11
Finals		19	Final. 1:30-3:30 in DBH1300 (Cumulative)

Assignments

1) Cranium! Some links: Game instructions Manufacturer's main site and a not very useful Wikipedia article

2) See link in schedule table above.

Grading and Evaluations

Assignments are 50% of your grade:

20% for assignment 1
30% for assignment 2

Midterms are 30% of your grade: 15% each
Final is 20% of your grade

Policies

Course Evalutions. The window for winter quarter online evaluations will open at @@TBD.

Cheating. The UCI academic honesty policy applies. Consequences of cheating in this class: a letter in your UCI file, and the course grade is lowered to an F. Material that is copied from books or Web pages needs to be quoted and the source must be given. If you plagiarize, you run the severe risk of failing the class, in a most disgraceful manner. You will be removed from the class for the rest of the quarter. So just say no to cheating and plagiarism.

Disabilities. If you need an accommodation because of a disability, please contact the instructor and the Disability Services Center as soon as possible.