Requirement Specification Assignment 1 Software Engineering VT 08

Requirement Specification Assignment 1, Software Engineering, VT 08 Sabesan Information Technology Uppsala University 29 January 2008 1

Assignment 1, Overview n Input document Information Technology http: //www. it. uu. se/edu/course/homepage/pm 2/vt 08/inlupp-en. pdf n n n 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 2 7) Testability 29 January, 2008

Structure of your RS (page 139) n Information Technology n n n n 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. 3 29 January, 2008

Find and Trace Requirements Information Technology n n 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. 1 a etc. 4 29 January, 2008

Partition Requirements (6. 1) Information Technology n n 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) 5 29 January, 2008

Limitations and Testability Information Technology n n n 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 … 6 29 January, 2008

Formalities n Information Technology n n n Author Version of document 1. 0 A … 1. 0 C will be 1. 0 Date Revision history, e. g. , Date Version Author Description 2006 -01 -25 1. 0 A Anders Hessel First version 2006 -01 -26 1. 0 B Anders Hessel Updated according to assistants comments Distribution, e. g. , PM 2 group, Sabesan … n References You do not need n Rules for documents n 29 January, 2008 7

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

Leave out Information Technology n n MP 2 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 9 29 January, 2008