Documents about User Interface Standards Requirements
SSRD_LCO_F05a_T11_V01.00
USC, CSCI 577
Excerpt: ... .3 A.2.2 Development Requirements.3 A.2.3 Deployment Requirements.6 A.2.4 Transition Requirements.8 A.2.5 Support Environment Requirements .9 A.3. Capability (Functional) Requirements.10 A.4. System Interface Requirements.14 A.4.1 User Interface Standards Requirements .14 A.4.2 Hardware Interface Requirements.14 A.4.3 Communications Interface ...
|
|
leanmbase_vbr_checklist_new_ssrd_v3_2_tkhare_10...
USC, CSCI 577
Excerpt: ... ritten down yet. 4.1 User Interface Standards Requirements Note: Use the general Value-Based Checklist in reviewing for completeness, consistency/feasibility, ambiguity, conformance, and risk. 4.2 Hardware Interface Requirements Question Are specific constraints (e.g., screen size) included? Criticality 3 4.3 Communications Interface Requirements Question Criticality 3 Are network security constraints (e.g., no CGI scripts) included? 4.4 Other Software Interface Requirements Question Are appropriate interfaces to common campus services (directories, catalogs) included? 5 Criticality 3 Level of Service (L.O.S.) Requirements Question Are the level of service requirements prioritized (High, Medium, Low) Criticality 3 3 1-3 Are the prioritizes consistent with those in OCD 3.2.3 Do the levels of service requirements specify more detail than the levels of 6 service in OCD 3.2.3? In particular, do they reference workload characteristics (normal load, peak load)? Are there no system requirements SS ...
|
|
SSRD_Draft_DC_ExitCriteria_IIVVa_F08a_T14_V2.0
USC, CSCI 577
Excerpt: ... Exit Criteria for SSRD V1.5 1. Introduction 1.1 Purpose of SSRD: Identify the need and the use of SSRD. 1.2 Status of SSRD: Identify the content of this version of the document. 2. Expected Benefits: it is optional to identify the expected benefits from the system. 3. Product Requirements 3.1 Capability Requirements: state an accurate and detailed description in a tabular form, of the capabilities/functions that the system being developed is required, by its stakeholders. 3.2 Level Of Service (L.O.S.) Requirements: state an accurate and detailed description in a tabular form, of the levels of service that the system being developed must attain in order to satisfy quality. 4. Interface Requirements: 4.1 User Interface Standards Requirements : a detailed description in a tabular form, of how the user interfaces will look like. 4.2 Hardware Interface Requirements: a detailed description in a tabular form, of the hardware interfaces that the proposed system may have. 4.3 Communications Interface Requirements: a de ...
|
|
SSRD_DraftFC_ExitCriteria_IIVVa_F08a_T14_V1.0
USC, CSCI 577
Excerpt: ... Exit Criteria for SSRD V1.1 1. Introduction 1.1 Purpose of SSRD: Identify the need and the use of SSRD. 1.2 Status of SSRD: Identify the content of this version of the document. 2. Product Requirements 2.1 Capability Requirements: state an accurate and detailed description in a tabular form, of the capabilities/functions that the system being developed is required, by its stakeholders. 2.2 Level Of Service (L.O.S.) Requirements: state an accurate and detailed description in a tabular form, of the levels of service that the system being developed must attain in order to satisfy quality. 3. Interface Requirements: 3.1 User Interface Standards Requirements : a detailed description in a tabular form, of how the user interfaces will look like. 3.2 Hardware Interface Requirements: a detailed description in a tabular form, of the hardware interfaces that the proposed system may have. 3.3 Communications Interface Requirements: a detailed description in a tabular form, of the communications interfaces the proposed syst ...
|
|
SSRD_FCPackage_ExitCriteria_IIVVa_F08a_T14_V1.0
USC, CSCI 577
Excerpt: ... Exit Criteria for SSRD V1.3 1. Introduction 1.1 Purpose of SSRD: Identify the need and the use of SSRD. 1.2 Status of SSRD: Identify the content of this version of the document. 2. Product Requirements 2.1 Capability Requirements: state an accurate and detailed description in a tabular form, of the capabilities/functions that the system being developed is required, by its stakeholders. 2.2 Level Of Service (L.O.S.) Requirements: state an accurate and detailed description in a tabular form, of the levels of service that the system being developed must attain in order to satisfy quality. 3. Interface Requirements: 3.1 User Interface Standards Requirements : a detailed description in a tabular form, of how the user interfaces will look like. 3.2 Hardware Interface Requirements: a detailed description in a tabular form, of the hardware interfaces that the proposed system may have. 3.3 Communications Interface Requirements: a detailed description in a tabular form, of the communications interfaces the proposed syst ...
|
|
EWW_LCO_F04a_T04
USC, CSCI 577
Excerpt: ... 4. Transition requirements 5. Support Environment Requirements 2. Capabilities 1. Nominal Requirements 2. Off-nominal Requirements 3. System Interface 1. User Interface Standards Requirements 1.1. Graphical User Interface Standards 2. Communications Interface requirements 3. Other Software Requirements Interface 4. Level of Service 1. Dependability 2. Usability 3. Performance 4. Security 5. Evolution 1. Capability Evolution Requirements 2. Interface Evolution Requirements 3. Level of Service Evolution requirements 4. Workload and Environment Evolution Requirements 3. Classify Win Conditions by Priority 1. Project requirements 1. Minimal budget for hardware and licenses - $500 [LHF, Agreed, Budget and Schedule] 2. Server will run on Mac OS G4 [IWH, Hardware Requirements] 3. Even though project done last year, no legacy system requirements - A completely new deployment which need not cater to existing ones [LHF, Agreed, Dependability, Transition requirements, Deployment Requirements] 4. Input format will be ...
|
|
SSRD_FC_ExitCriteria_IIVVb_F08a_T06_V1.0
USC, CSCI 577
Excerpt: ... Exit Criteria for SSRD FC Package (Core) a) Introduction section: (i) Purpose of SSRD subsection (ii) Status of SSRD subsection b) Product Requirements section: (i) Capability (Functional) Requirements subsection (ii) Level of Service (L.O.S.) Requirements subsection c) Interface Requirements section (i) User Interface Standards Requirements subsection (ii) Hardware Interface Requirements subsection (iii) Communications Interface Requirements subsection (iv) Other Software Interface Requirements subsection d) Project Requirements section (i) Tools requirements subsection (ii) Language Requirements subsection (iii) Computer Hardware Requirements subsection (iv) Computer Software Requirements subsection (v) Computer Communications Requirements subsection (vi) Deployment Requirements subsection (vii) Transition Requirements subsection (viii) Support Environment Requirements subsection (ix) Budget and Schedule Requirements subsection e) Evolutionary Requirements section (i) Capability Requirements subsection (ii) ...
|
|
EWW_LCO_F04a_T04
USC, CSCI 577
Excerpt: ... Transition requirements 5. Support Environment Requirements 2. Capabilities 1. Nominal Requirements 2. Off-nominal Requirements 3. System Interface 1. User Interface Standards Requirements 1.1. Graphical User Interface Standards 2. Communications Interface requirements 3. Other Software Requirements Interface 4. Level of Service 1. Dependability 2. Usability 3. Performance 4. Security 5. Evolution 1. Capability Evolution Requirements 2. Interface Evolution Requirements 3. Level of Service Evolution requirements 4. Workload and Environment Evolution Requirements 3. Classify Win Conditions by Priority 1. Project requirements 1. Minimal budget for hardware and licenses - $500 [LHF, Agreed, Budget and Schedule] 2. Server will run on Mac OS G4 [IWH, Hardware Requirements] 3. Even though project done last year, no legacy system requirements - A completely new deployment which need not cater to existing ones [LHF, Agreed, Dependability, Transition requirements, Deployment Requirements] 4. Input format will be in ...
|
|
LCOCore_IVVa_LCO_F06a_T16_V1.00
USC, CSCI 577
Excerpt: ... e5a59a442283cc6e317774f5826139383f154a07.xls Areas of Concern Log - Project Name: Artifact: Module: MBASE Phase/level: Team 16 (USC CONIPMO) LCO Core N/A Inception Review # Review Date: Review Time: LCO Core 1 10/68/2006 15 hours Activity: A ...
|
|
ec-13
USC, CSCI 577
Excerpt: ... any applicable requirements on how the software should interface with other software systems or users for input or output> <Describe what the priority of the requirement is; using the MSCW (MoSCoW) prioritization scheme: M (Must have), S (Should have), C (Could have), W (Want to have)> <Give the win-win agreement(s) this interface requirement is traced from> Priority: Win-Win Agreement(s): USC-CSE 13 USC C S E University of Southern California Center for Software Engineering Note on Tabular Format for System Interface Requirements The tabular format shown on the previous slide is used for all the various different types of System Interface Requirement in Section 4 of the SSRD, e.g.: 4.1 User Interface Standards Requirements 4.2 Hardware Interface Requirements 4.3 Communication Interface Requirements 4.4 Other Interface Requirements USC-CSE 14 USC C S E University of Southern California Center for Software Engineering 5. Level of Service (L.O.S.) Requirements Specify both th ...
|
|
ExplanationLog_LCOCore_IVV_LCO_F06a_T16_V1.1
USC, CSCI 577
Excerpt: ... ient's organization. Spreadsheet interface should be in the system environment. # Location Areas of Concern M/W/E Priority SSRD section 1 2.2.1 Visual Basic has been negotiatied as a language tool to be used for development M HIGH SSRd section 2 2.2.4 Windows Xp as the base or target platform was always agreed upon when asked by the client. W HIGH SSRD section 3 2.5 The support environment gives the interaction of the product with its interfacing entities W Medium SSRD section 4 4.1 The user interface standards requirements . M Medium Criticality MEDIUM Explanation The win condition was not in the ewasy win win report because during negotiations , the tool operations were not working. But it was duly noted in the client reports It was already an agreed case with both the parties but as per the win win tool, during interface and system specifications , we had to show this. It was later on added to the Easy win win tool. At this point of time only a VB compiler is our concern, if any ...
|
|
ProblemList_LCOCore_IVV_LCO_F06a_T16_V1.1
USC, CSCI 577
Excerpt: ... ient's organization. Spreadsheet interface should be in the system environment. # Location Areas of Concern M/W/E Priority SSRD section 1 2.2.1 Visual Basic has been negotiatied as a language tool to be used for development M HIGH SSRd section 2 2.2.4 Windows Xp as the base or target platform was always agreed upon when asked by the client. W HIGH SSRD section 3 2.5 The support environment gives the interaction of the product with its interfacing entities W Medium SSRD section 4 4.1 The user interface standards requirements . M Medium Criticality MEDIUM Explanation The win condition was not in the ewasy win win report because during negotiations , the tool operations were not working. But it was duly noted in the client reports It was already an agreed case with both the parties but as per the win win tool, during interface and system specifications , we had to show this. It was later on added to the Easy win win tool. At this point of time only a VB compiler is our concern, if any ...
|
|
SSRD_FC_ExitCriteria_IIVVa_F08a_T07_V1.0
USC, CSCI 577
Excerpt: ... Gabriel Alcocer CSCI 577a, Fall 2008 Exit Criteria- System and Software Requirements (SSRD) 1. An introduction containing: a. The purpose of the SSRD b. Status of the SSRD 2. Product requirements in tabular format containing for the following: a. Capability requirements containing: the requirement name, description, priority, input(s), source(s), output(s), destination(s), precondition(s), post condition(s), and win-win agreement(s) b. Level of service requirements containing the requirement name, description, priority, desired level, accepted level, measurable, achievable, relevant, specific, and win-win agreement(s) 3. Interface requirements in tabular format for the following containing the requirement name, requirement description, priority, and win-win agreement: a. User interface standards requirements b. Hardware interface requirements (if applicable) c. Computer software requirements (if applicable) d. Computer communication requirements (if applicable) e. Deployment requirements (if applicable) f. T ...
|
|
SSRD_Draft_DC_ExitCriteria_IIVVa_F08a_T07_V1.3
USC, CSCI 577
Excerpt: ... Gabriel Alcocer CSCI 577a, Fall 2008 Exit Criteria- System and Software Requirements (SSRD) 1. An introduction containing: a. The purpose of the SSRD b. Status of the SSRD 2. Product requirements in tabular format containing for the following: a. Capability requirements containing: the requirement name, description, priority, input(s), source(s), output(s), destination(s), precondition(s), post condition(s), and win-win agreement(s) b. Level of service requirements containing the requirement name, description, priority, desired level, accepted level, measurable, achievable, relevant, specific, and win-win agreement(s) 3. Interface requirements in tabular format for the following containing the requirement name, requirement description, priority, and win-win agreement: a. User interface standards requirements b. Hardware interface requirements (if applicable) c. Computer software requirements (if applicable) d. Computer communication requirements (if applicable) e. Deployment requirements (if applicable) f. T ...
|
|
readme
TCU, BJONES 20263
Excerpt: ... pp-lecture The PowerPoint slides in this folder are designed to be used to support lectures on the textbook contents. They include the text figures plus bulleted lists and other slides that reflect the narrative. Some instructors choose to post the ...
|
|
StudyGuideS08C
Illinois Tech, MATH 149
Excerpt: ... <STUDYGUIDES08C.TXT> {5-9-2008} Math 149 Spring 2008 Final Study Guide, Part III - Chapter 6 Concept Check, p. 378: 1,2,3,4,5 Exercises: 1-6, 7-11, 12-16 Chapter 9 Concept Check, p. 598: 1 Exercises: 1, 3a, 7 ...
|
|
SSRD_LCO_F05a_T11_V01.20
USC, CSCI 577
Excerpt: ... .8 A.2.5 Support Environment Requirements .8 A.3. Capability (Functional) Requirements.9 4. System Interface Requirements.13 4.1 User Interface Standards Requirements .13 4.2 Hardware Interface Requirements.13 4.3 Communications Interface Requirements.13 4.4 Other Software Interface Requirements.14 5. Level of Service (L.O.S.) Requirements.14 6. Versions, States and Modes. ...
|
|
SSRD_LCO_F05a_T22_V1.5
USC, CSCI 577
Excerpt: ... Schedule.2 2.2 Development Requirements.2 2.3 Deployment Requirements.4 2.4 Transition Requirements.5 2.5 Support Environment Requirements .5 3 Capability (Functional/Product) Requirements.6 4 System Interface Requirements.10 4.1 User Interface Standards Requirements .10 4.2 Hardware Interface Requirements. ...
|
|
SSRD_LCO_F05a_T22_V1.5
USC, CSCI 577
Excerpt: ... 2 Development Requirements. 2 Deployment Requirements. 4 Transition Requirements. 5 Support Environment Requirements. 5 Capability(Functional/Product) Requirements . 6 System Interface Requirements . 10 4.1 4.2 4.3 4.4 User Interface Standards Requirements . 10 Hardware Interface Requirements . 10 Communications Interface Requirements. 11 Other Software Int ...
|
|
SSRD_DraftFC_ExitCriteria_IIVV_F08a_T02_V2.0
USC, CSCI 577
Excerpt: ... .2, 3.3, 3.4]; 3.1 User interface standards requirements having tables with the following fields; System Interface Requirement ID, description, priority, winwin agreements 3.2 Hardware interface requirements having tables if any 3.3 Communications interface requirements if any 3.4 Other software interface requirements if any 4. Project requirements with [SfA ICM EPG SSRD Sections 4.1 4.10]; 4.1 Tools requirements describing each of the tools required for the project 4.2 Language requirements describing the various programming languages to be used 4.3 Computer hardware requirements (if any) 4.4 Computer software requirements (if any) 4.5 Computer communication requirements (if any) 4.6 Deployment requirements (if any) 4.7 Transition requirements (if any) 4.8 Support environment requirements (if any) 4.9 Budget and Schedule according to the required schedule and budget constraints of the project 4.10 Miscellaneous development requirements 5. Evolutionary Requirements for each of the above requirements i ...
|
|
StudyGuideS08A
Illinois Tech, MATH 149
Excerpt: ... <STUDYGUIDES08A.TXT> {5-5-2008} Math 149 Spring 2008 Final Exam Study Guide, Part I - Chapter 3 Review Concept Check, p. 196: 1 - 11 True-False Quiz, p. 196. Exercises: 10,11 & 12-40 - Chapter 4 Review Concept Check, p. 281: 1,2,3,4,5,6, ...
|