DOC PREVIEW
WVU CS 430 - ESEI Requirement Specifications

This preview shows page 1-2-19-20 out of 20 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 20 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 20 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 20 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 20 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 20 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

1 Introduction1.1 Goals and Objectives1.2 Scope1.4 Major Constraints2 Data Design2.1 Internal Software Data Structures2.2 Global data structure2.3 Temporary data structures2.4 Database description2.4.1 Chair Questions2.4.2 Dean Questions2.4.4 Provost Questions2.4.5 Questions2.4.6 Response Evaluation2.4.7 Term3 Architectural and Component-Level Design3.1 Program Structure3.1.2 Alternatives3.2 Description of Components3.2.1 User Interface3.2.1.1 User Interface Processing Narrative (PSPEC)3.2.1.2 User Interface Description3.2.1.3.1 Login and Authentication3.2.1.3.1.1 Login Interface3.2.1.3.1.2 Algorithmic Model3.2.1.3.1.3 Restrictions/limitations3.2.1.3.1.4 Local data structures3.2.1.3.1.5 Performance issues3.2.1.3.1.6 Design constraints3.2.1.3.2 Option Generation3.2.1.3.2.1 Option Generation3.2.1.3.2.2 Algorithmic Model3.2.1.3.2.3 Restrictions/limitations3.2.1.3.2.4 Local data structures3.2.1.3.2.5 Performance issues3.2.1.3.2.6 Design constraints3.2.1.3.3 Perform Data Operations3.2.1.3.3.1 Data Operations Interface3.2.1.3.3.2 Algorithmic Model3.2.1.3.3.3 Restrictions/limitations3.2.1.3.3.4 Local data structures3.2.1.3.3.5 Performance issues3.2.1.3.3.6 Design constraints3.2.2 Communication Interface3.2.2.1 Communication Interface Processing Narrative3.2.2.2 User Interface Description3.2.2.3.1.1 Request/Receive Data3.2.2.3.1.2 Algorithmic Model3.2.2.3.1.3 Restrictions/limitations3.2.1.3.1.4 Local data structures3.2.2.3.2.5 Performance issues3.2.2.3.1.6 Design constraints3.3 Software Interface Description3.3.1 External machine interfaces3.3.2 External system interfaces4 User Interface Design4.1 Description of the user interface4.1.1 Screen imagesFigure 1Figure 2Figure 3Figure 44.1.2 Objects and actions4.1.2.1 Figure 14.1.2.2 Figure 24.1.2.3 Figure 34.1.2.4 Figure 44.2 Interface design rules4.3 Components available4.3.1 Forms4.3.2 Menus4.3.3 Tables4.4 UIDS description5 Restrictions Limitations and Constraints6 Testing Issues 6.1 Classes of tests6.2 Expected software response6.3 Performance bounds6.4 Identification of critical components7 Appendices7.1 Requirements traceability matrix7.2 Packaging and installation issuesThe ESEI system is not as simple as a “plug and play” application. Although allconfigurations necessary will be documented and relatively easy to perform, the client still has some decisions to make regarding what database system to use, what web server to use, and how they want to incorporate their other systems into the ESEI system.For the client who chooses not to purchase the full ESEI support, the system package will be available for download rather than shipped on a physical medium. The system database design will be described in the documentation so the client may create the database using any database management system they wish. The documentation for the ESEI system will be available by download.For the client who wishes to purchase full support, the ESEI team will arrive on-site and install the software as necessary. The same packaging scheme can be used above will be used in this scenario, but the ESEI team will also write the communication clients for the customer’s existing systems.7.3 Design metrics to be used7.4 ReferencesESEI Requirement SpecificationsMarch 11, 2008Trevor [email protected] [email protected] [email protected] [email protected] Introduction 41.1 Goals and Objectives 41.2 Scope 41.4 Major Constraints 52 Data Design 52.1 Internal Software Data Structures 52.2 Global data structure 72.3 Temporary data structures 72.4 Database description 72.4.1 Chair Questions 72.4.2 Dean Questions 72.4.4 Provost Questions 82.4.5 Questions 82.4.6 Response Evaluation 82.4.7 Term 83 Architectural and Component-Level Design 93.1 Program Structure 93.1.2 Alternatives 103.2 Description of Components 103.2.1 User Interface 103.2.1.1 User Interface Processing Narrative (PSPEC) 103.2.1.2 User Interface Description 103.2.2 Communication Interface 133.2.2.1 Communication Interface Processing Narrative 133.2.2.2 User Interface Description 133.3 Software Interface Description 143.3.1 External machine interfaces 143.3.2 External system interfaces 144 User Interface Design 144.1 Description of the user interface 144.1.1 Screen images 14Figure 1 14Figure 2 15Figure 3 15Figure 4 164.1.2 Objects and actions 164.1.2.1 Figure 1 164.1.2.2 Figure 2 164.1.2.3 Figure 3 164.1.2.4 Figure 4 174.2 Interface design rules 174.3 Components available 174.3.1 Forms 174.3.2 Menus 174.3.3 Tables 174.4 UIDS description 175 Restrictions Limitations and Constraints 186 Testing Issues 186.1 Classes of tests 186.2 Expected software response 196.3 Performance bounds 196.4 Identification of critical components 197 Appendices 197.1 Requirements traceability matrix 197.2 Packaging and installation issues 20The ESEI system is not as simple as a “plug and play” application. Although all 20configurations necessary will be documented and relatively easy to perform, the client still has some decisions to make regarding what database system to use, what web server to use, and how they want to incorporate their other systems into the ESEI system. 20For the client who chooses not to purchase the full ESEI support, the system package will be available for download rather than shipped on a physical medium. The system database design will be described in the documentation so the client may create the database using any database management system they wish. The documentation for theESEI system will be available by download. 20For the client who wishes to purchase full support, the ESEI team will arrive on-site and install the software as necessary. The same packaging scheme can be used above will be used in this scenario, but the ESEI team will also write the communication clients for the customer’s existing systems. 207.3 Design metrics to be used 207.4 References 201 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 permitthe 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


View Full Document

WVU CS 430 - ESEI Requirement Specifications

Documents in this Course
Lecture

Lecture

28 pages

Design

Design

27 pages

Load more
Download ESEI Requirement Specifications
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view ESEI Requirement Specifications and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view ESEI Requirement Specifications 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?