1. 29 January 2008 1 Requirement Specification Assignment 1, Software Engineering, VT08 Sabesan Information Technology Uppsala University

2. Information Technology 29 January, 2008 2 Assignment 1, Overview Input document http://www.it.uu.se/edu/course/homepage/pm2/vt08/inlupp-en.pdf http://www.it.uu.se/edu/course/homepage/pm2/vt08/inlupp-en.pdf Deadline 15 February You will get rework Your assignment is to reformulate the input document to a requirement specification 1) Structure the document 2) Find requirements 3) Partition the requirements 4) Formal document ( Complete & Consistent) 5) Clear limitations 6) Traceability 7) Testability

3. Information Technology 29 January, 2008 3 Structure of your RS (page 139) Preface formalities Introduction (the "strategic objective" of the system is to satisfy the teacher of Methods of Programming) Glossary System Requirements Specification. This is the core of your work. System models. Draw a small data-flow model. System evolution. Here you are allowed to speculate about possible extensions. Don't make too much of this. Appendices. Probably not needed. The overview of the mathematics of ray-tracing and perhaps the PPM and XML formats would otherwise go here. Index.

4. Information Technology 29 January, 2008 4 Find and Trace Requirements Example of requirements There shall be three types of bottles red, green, and blue. After remake 1. There shall be three types of bottles a) Red b) Green c) Blue  Referred to as Req. 1a etc.

5. Information Technology 29 January, 2008 5 Partition Requirements (6.1) Functional Requirements (Describes the functionality of the product) Non-Functional Requirements  Product Requirements (Portability, usability, timing, and space)  Process (or Organizational requirements) (Delivery, Implementation, Standards)

6. Information Technology 29 January, 2008 6 Limitations and Testability We know that no system is supposed to handle infinitely many items How many shall we test? Requirements sets an under limit or an input domain, e.g., x in [0..1000] Specify exact what shall happen in case of exception, e.g., if x not in [0..1000] an error message “the value of x is not in the input domain” shall be printed. Border values are interesting for testing …

7. Information Technology 29 January, 2008 7 Formalities Author Version of document 1.0A … 1.0C will be 1.0 Date Revision history, e.g., Distribution, e.g., PM2 group, Sabesan … References You do not need Rules for documents DateVersionAuthorDescription 2006-01-251.0AAnders HesselFirst version 2006-01-261.0BAnders HesselUpdated according to assistants comments

8. Information Technology 29 January, 2008 8 Part II, and Part III Specify two versions  Part II  Part III You have to specify (and separate) which requirement belongs to which version

9. Information Technology 29 January, 2008 9 Leave out MP2 administration, assignment, grading, etc. Part 1, 4, and 5 The mathematics of ray tracing (chapters 3-8) The details of the PPM and XML formats