SYSTEM SPECIFICATION
1.0 Introduction
This section provides an overview of the entire system or product. This document describes all subsystems including hardware, software, human activities, documents, and process.
1.1 Goals and objectives
Overall business s goals and project objectives are described.
1.2 System statement of scope
A description of the entire system is presented. Major inputs, processing functionality and outputs are described without regard to implementation detail.
1.3 System context
The system is placed in a business or product line context. Strategic issues relevant to context are discussed. The intent is for the reader to understand the "big picture."
1.4 Major constraints
Any business or product line constraints that will impact the manner in which the system is to be specified, designed, implemented or tested are noted here.
2.0 Functional and Data Description
This section describes overall system function and the information domain in which it operates.
2.1 System architecture
A context-level model of the system architecture is presented.
2.1.1 Architecture model (e.g., ACD)
A context-level model of the system architecture is presented.
2.1.2 Subsystem overview
Each subsystem noted in the architecture model is described briefly.
2.2 Data Description
Top-level data objects that will be managed/manipulated by the system or product are described in this section.
2.2.1 Major data objects
Data objects and their major attributes are described.
2.2.2 Relationships
Relationships among data objects are described using an ERD- like form. No attempt is made to provide detail at this stage.
2.2.3 System level data model
An ERD for the system is developed (this section may be omitted).
2.3 Interface Description
The system's interface(s) to the outside world are described.
2.3.1 Machine interfaces
Interfaces to other machines (computers or devices) are described.
2.3.2 External system interfaces
Interfaces to other systems, products or networks are described.
2.3.3 Human interface
An overview of any human interfaces to be designed for the system/product is presented.
3.0 Subsystem Description
A description of each subsystem is presented.
3.1 Description for Subsystem n
A detailed description of each subsystem is presented. Section 3.1 is repeated for each of n subsystems.
3.1.1 Subsystem scope
A statement of scope for subsystem n is presented.
3.1.2 Subsystem flow diagram
A diagram showing the flow of information through the subsystem and the transformation that it undergoes is presented.
3.1.3 Subsystem n components
A detailed description for each component of subsystem n is presented. Section 3.1.3 is repeated for each of k components.
3.1.3.1 Component k description (processing narrative)
3.1.3.2 Component k interface description
3.1.4 Performance Issues
Special performance required for the subsystem is specified.
3.1.5 Design Constraints
Any design constraints that will impact the subsystem are noted.
3.1.6 Allocation for Subsystem n
The allocation for implementation (e.g., will the subsystem be implemented in hardware, software, by a human, etc.) is described.
3.2 Diagrammatic model for Subsystem n
A diagrammatic model for each subsystem is presented. Section 3.2 is repeated for each of n subsystems.
4.0 System Modeling and Simulation ResultsIf system modeling and simulation and/or prototyping is conducted, these are specified here.
4.1 Description of system modeling approach (if used)
The system modeling approach (including tools and/or mathematical models) is described.
4.2 Simulation results
The results of any system simulation are presented with specific emphasis on data throughput, timing, performance, and/or system behavior.
4.3 Special performance issues
Special performance issues are identified.
4.4 Prototyping requirements
If a system prototyping is to be built, its specification and implementation environment are described here.
5.0 Project IssuesAn overview of the overall system/product project plan is presented.
5.1 Projected development costs
The results of system-level cost estimates are presented.
5.2 Project schedule
A top-level schedule for the development project is proposed.
6.0 AppendicesPresents information that supplements the System Specification.
6.1 Business Process Descriptions
If the specification is developed for a business system, a description of relevant business processes is presented here.
6.2 Product Strategies
If the specification is developed for a product, a description of relevant product strategy is presented here.
6.3 Supplementary information (as required)
1.0 Introduction
This section provides an overview of the software engineering project.
1.1 Project scope
A description of the software is presented. Major inputs, processing functionality and outputs are described without regard to implementation detail.
1.2 Major software functions
A functional decomposition of the software (for use during estimation and scheduling) is developed here.
1.3 Performance/Behavior issues
Any special requirements for performance or behavior are noted here.
1.4 Management and technical constraints
Any special constraints that affect the manner in which the project will be conducted (e.g., limited resources or 'drop dead' delivery date) or the technical approach to development are noted here.
2.0 Project Estimates
This section provides cost, effort and time estimates for the projects
2.1 Historical data used for estimates
Describes the historical data that is relevant to the estimates presented.
2.2 Estimation techniques applied and results
A description of each estimation technique and the resultant estimates are presented here.
2.2.1 Estimation technique m
Tables or equations associated with estimation technique m are presented. Section 2.2.1 is repeated for each of m techniques.
2.2.2 Estimate for technique m
Estimate generated for technique m.
2.3 Reconciled Estimate
The final cost, effort, time (duration) estimate for the project (at this point in time) is presented here.
2.4 Project Resources
People, hardware, software, tools, and other resources required to build the software are noted here.
3.0 Risk Management
This section discusses project risks and the approach to managing them.
3.1 Project Risks
Each project risk is described. The CTC format may be used.
3.2 Risk Table
The complete risk table is presented. Name of risk, probability, impact and RM3 pointer are provided.
3.3 Overview of Risk Mitigation, Monitoring, Management
An overview of RM3 is provided here. The Complete RM3 is provided as a separate document or as a set of Risk Information Sheets.
4.0 Project ScheduleThis section presents an overview of project tasks and the output of a project scheduling tool.
4.1 Project task set
The process model, framework activities and task set that have been selected for the project are presented in this section.
4.2 Functional decomposition
A functional breakdown to be used for scheduling is presented here.
4.3 Task network
Project tasks and their dependencies are noted in this diagrammatic form.
4.4 Timeline chart
A project timeline chart is presented. This may include a time line for the entire project or for each staff member.
5.0 Staff OrganizationThe manner in which staff are organized and the mechanisms for reporting are noted.
5.1 Team structure
The team structure for the project is identified. Roles are defined.
5.2 Management reporting and communication
Mechanisms for progress reporting and inter/intra team communication are identified.
6.0 Tracking and Control MechanismsTechniques to be used for project tracking and control are identified.
6.1 Quality assurance and control
An overview of SQA activities is provided. Note that an SQA Plan is developed for a moderate to large project and may be a separate document or included as an appendix.
6.2 Change management and control
An overview of SCM activities is provided. Note that an SCM Plan is developed for a moderate to large project and may be a separate document or included as an appendix.
7.0 Appendix
Supplementary information is provided here.
SOFTWARE REQUIREMENTS SPECIFICATION
1.0 Introduction
This section provides an overview of the entire requirement document. This document describes all data, functional and behavioral requirements for software.
1.1 Goals and objectives
Overall goals and software objectives are described.
1.2 Statement of scope
A description of the software is presented. Major inputs, processing functionality and outputs are described without regard to implementation detail.
1.3 Software context
The software is placed in a business or product line context. Strategic issues relevant to context are discussed. The intent is for the reader to understand the 'big picture'.
1.4 Major constraints
Any business or product line constraints that will impact the manner in which the software is to be specified, designed, implemented or tested are noted here.
2.0 Usage scenario
This section provides a usage scenario for the software. It organized information collected during requirements elicitation into use-cases.
2.1 User profiles
The profiles of all user categories are described here.
2.2 Use-cases
All use-cases for the software are presented.
2.3 Special usage considerations
Special requirements associated with the use of the software are presented.
3.0 Data Model and Description
This section describes information domain for the software
3.1 Data Description
Data objects that will be managed/manipulated by the software are described in this section.
3.1.1 Data objects
Data objects and their major attributes are described.
3.1.2 Relationships
Relationships among data objects are described using an ERD- like form. No attempt is made to provide detail at this stage.
3.1.3 Complete data model
An ERD for the software is developed
3.1.4 Data dictionary
A reference to the data dictionary is provided. The dictionary is maintained in electronic form.
A description of each major software function, along with data flow or class hierarchy (OO) is presented.
4.1 Description for Function n
A detailed description of each software function is presented. Section 4.1 is repeated for each of n functions.
4.1.1 Processing narrative (PSPEC) for function n
A processing narrative for function n is presented.
4.1.2 Function n flow diagram
A diagram showing the flow of information through the function and the transformation it undergoes is presented.
4.1.3 Function n interface description
A detailed description of the input and output interfaces for the function is presented.
4.1.4 Function n transforms
A detailed description for each transform (subfunction) for function n is presented. Section 4.1.4 is repeated for each of k transforms.
4.1.4.1 Transform k description (processing narrative, PSPEC)
4.1.4.2 Transform k interface description
4.1.4.3 Transform k lower level flow diagrams
4.1.4.4 Transform k interface description
4.1.5 Performance Issues
Special performance required for the subsystem is specified.
4.1.6 Design Constraints
Any design constraints that will impact the subsystem are noted.
4.2 Software Interface Description
The software interface(s)to the outside world is(are) described.
4.2.1 External machine interfaces
Interfaces to other machines (computers or devices) are described.
4.2.2 External system interfaces
Interfaces to other systems, products or networks are described.
4.2.3 Human interface
An overview of any human interfaces to be designed for the software is presented.
4.3 Control flow description
The control flow for the system is presented with reference to Section 5.0 of this document.
5.0 Behavioral Model and Description
A description of the behavior of the software is presented.
5.1 Description for software behavior
A detailed description of major events and states is presented in this section.
5.1.1 Events
A listing of events (control, items) that will cause behavioral change within the system is presented.
5.1.2 States
A listing of states (modes of behavior) that will result as a consequence of events is presented.
5.2 State Transition Diagrams
Depict the overall behavior of the system.
5.3 Control specification (CSPEC)
Depict the manner in which control is managed by the software.
6.0 Restrictions, Limitations, and Constraints
Special issues which impact the specification, design, or implementation of the software are noted here.
7.0 Validation Criteria
The approach to software validation is described.
7.1 Classes of tests
The types of tests to be conducted are specified, including as much detail as is possible at this stage. Emphasis here is on black- box testing.
7.2 Expected software response
The expected results from testing are specified.
7.3 Performance bounds
Special performance requirements are specified.
8.0 Appendices
Presents information that supplements the Requirements Specification
8.1 System traceability matrix
A matrix that traces stated software requirements back to the system specification.
8.2 Product Strategies
If the specification is developed for a product, a description of relevant product strategy is presented here.
8.3 Analysis metrics to be used
A description of all analysis metrics to be used during the analysis activity is noted here.
8.4 Supplementary information (as required)
1.0 Introduction
This section provides an overview of the entire design document. This document describes all data, architectural, interface and component-level design for the software.
1.1 Goals and objectives
Overall goals and software objectives are described.
1.2 Statement of scope
A description of the software is presented. Major inputs, processing functionality, and outputs are described without regard to implementation detail.
1.3 Software context
1.3 Software context
The software is placed in a business or product line context. Strategic issues relevant to context are discussed. The intent is for the reader to understand the 'big picture'.
1.4 Major constraints
Any business or product line constraints that will impact he manner in which the software is to be specified, designed, implemented or tested are noted here.
2.0 Data designA description of all data structures including internal, global, and temporary data structures.
2.1 Internal software data structure
Data structures that are passed among components the software are described.
2.2 Global data structure
Data structured that are available to major portions of the architecture are described.
2.3 Temporary data structure
Files created for interim use are described.
2.4 Database descriptio
Database(s) created as part of the application is(are) described.
3.0 Architectural and component-level designA description of the program architecture is presented.
3.1 Program Structure
A detailed description the program structure chosen for the application is presented.
3.1.1 Architecture diagram
A pictorial representation of the architecture is presented.
3.1.2 Alternatives
A discussion of other architectural styles considered is presented. Reasons for the selection of the style presented in Section3.1.1 are provided.
3.2 Description for Component n
A detailed description of each software component contained within the architecture is presented. Section 3.2 is repeated for each of n components.
3.2.1 Processing narrative (PSPEC) for component n
A processing narrative for component n is presented.
3.2.2 Component n interface description.
A detailed description of the input and output interfaces for the component is presented.
3.2.3 Component n processing detail
A detailed algorithmic description for each component is presented. Section 3.2.3 is repeated for each of n components.
3.2.3.1 Interface description
3.2.3.2 Algorithmic model (e.g., PDL)
3.2.3.3 Restrictions/limitations
]3.2.3.4 Local data structures
3.2.3.5 Performance issues3.2.3.6 Design constraints
3.3 Software Interface Description
The software's interface(s) to the outside world are described.
3.3.1 External machine interfaces
Interfaces to other machines (computers or devices) are described.
3.3.2 External system interfaces
Interfaces to other systems, products, or networks are described.
3.3.3 Human interface
An overview of any human interfaces to be designed for the software is presented. See Section 4.0 for additional detail.
4.0 User interface designA description of the user interface design of the software is presented.
4.1 Description of the user interface
A detailed description of user interface including screen images or prototype is presented.
4.1.1 Screen images
Representation of the interface form the user's point of view.
4.1.2 Objects and actions
All screen objects and actions are identified.
4.2 Interface design rules
Conventions and standards used for designing/implementing the user interface are stated.
4.3 Components available
GUI components available for implementation are noted.
4.4 UIDS description
The user interface development system is described.
5.0 Restrictions, limitations, and constraintsSpecial design issues which impact the design or implementation of the software are noted here.
6.0 Testing Issues
Test strategy and preliminary test case specification are presented in this section.
6.1 Classes of tests
The types of tests to be conducted are specified, including as much detail as is possible at this stage. Emphasis here is on black-box and white-box testing.
6.2 Expected software response
The expected results from testing are specified.
6.3 Performance bounds
Special performance requirements are specified.
6.4 Identification of critical components
Those components that are critical and demand particular attention during testing are identified.
Presents information that supplements the design specification.
7.1 Requirements traceability matrix
A matrix that traces stated components and data structures to software requirements is developed.
7.2 Packaging and installation issues
Special considerations for software packaging and installation are presented.
7.3 Design metrics to be used
A description of all design metrics to be used during the design activity is noted here.
7.4 Supplementary information (as required)
TEST SPECIFICATION
1.0 Introduction
This section provides an overview of the entire test document. This document describes both the test plan and the test procedure.
1.1 Goals and objectives
Overall goals and objectives of the test process are described.
1.2 Statement of scope
A description of the scope of software testing is developed. Functionality/features/behavior to be tested is noted. In addition any functionality/features/behavior that is not to be tested is also noted.
1.3 Major constraints
Any business, product line or technical constraints that will impact the mannerin which the software is to be tested are noted here.
This section describes the overall testing strategy and the project management issues that are required to properly execute effective tests.
2.1 Software (SCIís) to be tested
The software to be tested is identified by name. Exclusions are noted explicitly.
2.2 Testing strategy
The overall strategy for software testing is described.
2.2.1 Unit testing
The strategy for unit tested is described. This includes an indication of the components that will undergo unit tests or the criteria to be used to select components for unit test. Test cases are NOT included here.
2.2.2 Integration testing
The integration testing strategy is specified. This section includes a discussion of the order of integration by software function. Test cases are NOT included here.
2.2.3 Validation testing
The validation testing strategy is specified. This section includes a discussion of the order of validation by software function. Test cases are NOT included here.
2.2.4 High-order testing
The high-order testing strategy is specified. This section includes a discussion of the types of high order tests to be conducted, the responsibility for those tests. Test cases are NOT included here.
2.3 Testing resources and staffing
Specialized testing resources are described and staffing is defined. The role of any ITG is also defined.
2.4 Test work products
The work products produced as a consequence of the testing strategy are identified.
2.5 Test record keeping
Mechanisms for storing and evaluating test results are specified.
2.6 Test metrics
A description of all test metrics to be used during the testing activity is noted here.
2.7 Testing tools and environment
A description of the test environment, including tools, simulators, specialized hardware, test files, and other resources is presented here.
2.8 Test schedule
A detailed schedule for unit, integration, and validation testing as well as high order tests is described.
3.0 Test Procedure
This section describes as detailed test procedure including test tactics and test cases for the software.
3.1 Software (SCIís) to be tested
The software to be tested is identified by name. Exclusions are noted explicitly.
3.2 Testing procedure
The overall procedure for software testing is described.
3.2.1 Unit test cases
The procedure for unit testing is described for each software component (that will be unit tested) is presented. This section is repeated for all components i.
3.2.1.2 Stubs and/or drivers for component i
3.2.1.3 Test cases component i
3.2.1.4 Purpose of tests for component i
3.2.1.5 Expected results for component i
3.2.2 Integration testing
The integration testing procedure is specified.
3.2.2.1 Testing procedure for integration
3.2.2.2 Stubs and drivers required
3.2.2.3 Test cases and their purpose
3.2.2.4 Expected results
3.2.3 Validation testing
The validation testing procedure is specified.
3.2.3.1 Testing procedure for validation
3.2.3.3 Expected results
3.2.3.4 Pass/fail criterion for all validation tests
3.2.4 High-order testing (a.k.a. System Testing)
The high-order testing procedure is specified. For each of the high order tests specified below, the test procedure, test cases, purpose, specialized requirements and pass/fail criteria are specified. It should be noted that not all high-order test methods noted in Sections 3.2.4.n will be conducted for every project.
3.2.4.1 Recovery testing
3.2.4.2 Security testing
3.2.4.3 Stress testing
3.2.4.4 Performance testing
3.2.4.5 Alpha/beta testing
3.2.4.6 Pass/fail criterion for all validation tests
3.3 Testing resources and staffing
Specialized testing resources are described and staffing is defined. The role of any ITG is also defined.
3.4 Test work products
The work products produced as a consequence of the testing procedure are identified.
3.5 Test record keeping and test log
Mechanisms for storing and evaluating test results are specified. The test log is used to maintain a chronological record of all tests and their results.
http://www.softwareqatest.com/qatfaq1.html
Test identifier
Test case name
3.objective means what u r going to do
4.test conditions
5.input data or requirements
6.expected result
okay now for login
1. identifier means test case 1 or 1.1 or what ever it is
2. test case name : login screen testing
3. objective is testing whether username and password buttons r working
4. test conditions : for user name both positive and negative testing and for password also the same
5. input data: for username for positive testing u give correct data just the letters okay for negative testing u give letters with spaces
see whether it is giving any message or not for password also the same
6. expected result : eg. yahoo home page we should see inbox or send or trash whatever it is
i
No comments:
Post a Comment