Informatics 113: Requirements Analysis and Engineering

Winter Quarter 2011

Last update: March 10, 2011

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:	Immediately after class, or by email appointment
Lectures:	Tuesday/Thursday ICS 180 at 9:30 a.m.
Reader	Oliver Wang: yiw2 [at] uci [dot] edu Office hours: TBD. 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/syllabusWQ11.html (main site) https://eee.uci.edu/11w/37040 (the EEE site: may end up having some files not publicly accessible)

What's New?

[February 25] The slides for goal orientation are now linked in to the syllabus below. And here is the example we worked through in class yesterday.
[February 17] Assignment #3 is now posted.
[February 15] Here is the sequence diagram (interaction diagram) that I did in class for one scenario from the FAS system.
[February 2] Here is the first cut I made at a statechart for the fingerprint reader device of the FAS example. I abandoned it and created version 2, then realized more was needed to account for more of the scenario, and so ended up with version 3. In class we did this version. ALL of these could be improved. And did you notice we didn't talk about "commuters" exiting the building via the FP reader? Should that be part of the same state machine?
[January 27] Here is the first cut I made at the use case diagram for the FAS example. Here is the "improved" version that I created next. And here is the version that I did in class today. I have tidied it up a little to remove crossing lines, but otherwise left it pretty much as it was in class. All of them could be improved further, of course.
Intro to Rational Systems Developer now available as a set of .ppt slides
Lecture notes for 1/6 and 1/11 are now available
Check back here for weekly updates and class announcements

Description - Schedule - Grading - Textbooks - 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 cooperative problem analysis, representation, and validation. Prerequisite: Informatics 43 or ICS 52 with a grade of C or better. Recommended: Philosophy 29.

Textbooks

Required Textbooks:

van Lamsweerde, A. Requirements Engineering. John Wiley & Sons, Ltd. UK 2009. (Unfortunately not in the UCI libraries.)
Pilone, D. UML 2.0 in a Nutshell. O'Reilly, 2005.

Schedule

Subject to change!

Week	Date		Discussion Topic	Reading	Assignments
1	January	4	Setting the Scene: Architecture and Design
1		6	Setting the Scene: RE and the SW Lifecycle	AvL: Ch.1
2		11	Domains, DSSAs, and Requirements	AvL: Ch.2
2		13	Requirements Evaluation Techniques DSSAs	AvL: Ch.3	Start reading the "getting started" slides on Rational Systems Developer.
3		18	Requirements Specification and Documentation.	AvL: Ch. 4.1 - 4.3
3		20	Requirements Specification and Documentation.
4		25	Diagrammatic Notations: SADT: John Mylopoulos and example: BatonExample Design Methods Comparison
4		27	UML 2.0: Use Case Diagrams; FAS	UML: Ch. 7	Assignment #1
5	February	1	UML 2.0: Statecharts and Activity Diagrams	UML: Ch. 8-9
5		3	UML 2.0: Interaction Diagrams	UML: Ch. 10	Assignment #2
6		8	Midterm
6		10	The COTRAN method of Requirements Engineering		Assignment #1 DUE
7		15	UML 2.0: Interaction Diagrams, cont.
7		17	Traceability; Change Management, Requirements Evolution	AvL: Ch. 6	Assignment #2 DUE Assignment #3
8		22	Goal Orientation	AvL: Ch. 7
8		24	Modeling System Objectives	AvL: Ch. 8
9	March	1	Midterm #2 (non-cumulative)
9		3	Requirements Verification
10		8	Requirements in Practice		Assignment #3 DUE
10		10	Exam review and Requirements in Practice, part II
Finals		17	Final. 8:00-10:00 (Cumulative)

Assignments

See the Schedule table above..

Grading and Evaluations

Assignments are 40% of your grade:

15% for assignment 1
10% for assignment 2
15% for assignment 3

Midterms and quizzes, aggregate, are 25% of your grade
Final is 35% of your grade

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

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.

(c) University of California, 2011.