1 Introduction1.1 Goals and Objectives1.2 Scope1.3 Software Context1.4 Major Constraints2 Usage Scenerio2.1 User Profiles2.2 Use-Case Diagrams2.3 Special Usage3 Data Model3.1 Entity Relationship Diagram4 Functional Model and Description4.1 Functions4.1.1 Login4.1.2 Logout4.1.3 Add Question to Question Pool4.1.4 Add Question to Question Pool4.1.5 Remove a Question from Pool4.1.6 Fill Out Evaluation4.1.7 Create Evaluation4.1.8 View Reports4.2 Software Interface Description4.2.1 External Machine Interfaces4.2.2 External System Interfaces4.2.3 Human Interface 4.3 Control flow description5 Behavioral Model and Description 5.1 Description for software behavior. 5.1.1 Events 5.1.2 States 5.2 State Transition Diagrams 5.3 Control specification (CSPEC)6 Restrictions, Limitations, Constraints7 Validation Criteria 7.1 Classes of tests 7.2 Expected software response 7.3 Performance bounds8 Appendices8.1 Traceability Matrix8.2 Product Strategy8.3 Analysis metrics to be used8.3.1 Number of Static Web Pages8.3.2. Number of Dynamic Web Pages8.3.3 Number of Transactions between Database and Site8.3.4 Number of Differences between BrowsersCS 430 ESEISoftware Requirements SpecificationFeb. 14th, 2008Trevor KempChet TobreyMark ViewegMatt Williamson 1Table of Contents1 Introduction 31.1 Goals and Objectives 31.2 Scope 31.3 Software Context 41.4 Major Constraints 42 Usage Scenerio 42.1 User Profiles 42.2 Use-Case Diagrams 52.3 Special Usage 63 Data Model 73.1 Entity Relationship Diagram 74 Functional Model and Description 84.1 Functions 84.1.1 Login 114.1.2 Logout 134.1.3 Add Question to Question Pool 144.1.4 Add Question to Question Pool 154.1.5 Remove a Question from Pool 154.1.6 Fill Out Evaluation 164.1.7 Create Evaluation 194.1.8 View Reports 204.2 Software Interface Description 224.2.1 External Machine Interfaces 224.2.2 External System Interfaces 224.2.3 Human Interface 224.3 Control flow description 225 Behavioral Model and Description 235.1 Description for software behavior. 235.1.1 Events 235.1.2 States 25 5.2 State Transition Diagrams 275.3 Control specification (CSPEC) 286 Restrictions, Limitations, Constraints 287 Validation Criteria 287.1 Classes of tests 287.2 Expected software response 297.3 Performance bounds 298 Appendices 298.1 Traceability Matrix 298.2 Product Strategy 308.3 Analysis metrics to be used 308.3.1 Number of Static Web Pages 308.3.2. Number of Dynamic Web Pages 308.3.3 Number of Transactions between Database and Site 308.3.4 Number of Differences between Browsers 30231 Introduction1.1 Goals and ObjectivesThe Electronic Student Evaluation of Instructor is a generic implementation of an ESEI that will permit a college or university to drop a computer running the ESEI system onto the network and make minor or no configuration changes to the network. This will permit the ESEI system to automatically obtain a list of classes from the school’s registrar, automatically email students that an evaluation is ready for completion, and also permit the ESEI to integrate with the current school’s login system.1.2 ScopeThe Electronic Student Evaluation of Instructor is the software chosen to fulfill the requirements of a generic implementation of an electronic evaluation of instructor. The system will be capable of being employed in nearly any college setting with little or no modification to the client network. The product will compile simple statistics for the faculty and administration of the college or university. The statistics will be gathered from the student evaluations. Instructors and other faculty in charge of a particular instructor may add questions to an evaluation before it is dispatched to students. The system is used for information gathering. It will automatically compile statistics for viewing by faculty and administration and display them in a graphically pleasing manner.It will provide for secure transmission of evaluations by students as well as secure viewing by faculty and administration.The system will not permit students to view their own, or other's, submissions. It will not permit faculty to view the evaluations of other faculty members unless he or she is a supervisor of that faculty member. The system will not permit departmental chairs to view evaluations outside of their own departments.The system will authenticate logins with current authentication system on the client network after a user has entered a username and password to login to the ESEI system. It will also obtain a roster and instructor information for each class from the registrar’s office. It will then communicate with current email systems to provide a means to inform students that they have an evaluation to fill out for a class.The system will benefit the faculty and administration of colleges and universities in several ways. Computer resources are easier to fund than personnel resources, and the Electronic Student Evaluation of Instructor will promote more efficient use of personnel to manage Student Evaluation of Instructors by doing much of the difficult work automatically. Fewer errors will be generated when using the software because no calculations will be done by hand. As long as the input data is correct, the software will produce a correct result. The information gleaned from these reports can be stored and easily recalled from anywhere, without need of maintaining paper files. The last large benefit of the electronic system is one of security and privacy. There will be features integrated that prevent the spread of private or proprietary information.41.3 Software ContextThe ESEI system is intended to be used as a base product for business operations. The product and be sold alone, or as part of a package that will give support to the client. If the client wants to purchase just the ESEI system and integrate it themselves, the system can be sold for a relatively inexpensive amount. In this circumstance, limited support will come with the ESEI system. This support will include application communications documentation to provide the client a means to extend their applications, and support for the core ESEI system. The client could optionally purchase a more encompassing support which includes extension of client registrar, email, and login systems to support the new ESEI system. This extension would be implemented by the ESEI team.1.4 Major ConstraintsThe communications system that comes with the ESEI system can be tested extensively for errors, but can not