Showroom Srs Document
DIDIT CAR-SHOWROOM SYSTEM
FOR ALMULLA SHOWROOM
_________________ Manager IT AlMulla Group
Date:
Table of Contents
1. Introduction
1.1 Scope
2. General Description
2.1 Product perspective
2.2 Product features
2.3 User characteristics
2.4 Constraints
3. System Models 3.3 Stimulus/response model 3.3.1 Language State Diagram (Visitor)
4. System Requirements
4.1 Functional Requirements
4.1.1 Use case model
4.1.2 Use case specification
4.2 Nonfunctional Requirements
4.2.1 Usability
4.2.2 Performance
4.2.3 Availability
4.2.4 Security
4.3 Interface Requirements
4.3.1 Hardware interfaces
4.3.2 Software interfaces
4.3.3 I/O formats
5. Appendices
5.1 Issues and Tradeoffs
DIDIT Software Requirements Specification
Introduction
The purpose of the SRS document is to provide all requirements, including functional and non-functional, needed to fully understand the didit car-showroom guide.
.
1 Scope
The didit system allows visitors to search for different car items located in the car showroom. Visitors are able to navigate through various information, facts, pictures, and videos of these items.
Its dynamic programming allows employees to update, add, or delete data of selected items.
General Description
1 Product perspective
The didit showroom system is intended to be an independent system that will replace any current systems available.
3 Product features
The didit showroom System provides an open, flexible solution for managing collections of all sizes and disciplines. The system enables clients to catalogue, view their current location and watch relevant videos.
The main features are:
- COLLECTIONS AND CONTENT MANAGEMENT Record and publish complete information on cataloguing, documentation, location, and manage the museum collections.
- MODIFYING
FOR ALMULLA SHOWROOM
_________________ Manager IT AlMulla Group
Date:
Table of Contents
1. Introduction
1.1 Scope
2. General Description
2.1 Product perspective
2.2 Product features
2.3 User characteristics
2.4 Constraints
3. System Models 3.3 Stimulus/response model 3.3.1 Language State Diagram (Visitor)
4. System Requirements
4.1 Functional Requirements
4.1.1 Use case model
4.1.2 Use case specification
4.2 Nonfunctional Requirements
4.2.1 Usability
4.2.2 Performance
4.2.3 Availability
4.2.4 Security
4.3 Interface Requirements
4.3.1 Hardware interfaces
4.3.2 Software interfaces
4.3.3 I/O formats
5. Appendices
5.1 Issues and Tradeoffs
DIDIT Software Requirements Specification
Introduction
The purpose of the SRS document is to provide all requirements, including functional and non-functional, needed to fully understand the didit car-showroom guide.
.
1 Scope
The didit system allows visitors to search for different car items located in the car showroom. Visitors are able to navigate through various information, facts, pictures, and videos of these items.
Its dynamic programming allows employees to update, add, or delete data of selected items.
General Description
1 Product perspective
The didit showroom system is intended to be an independent system that will replace any current systems available.
3 Product features
The didit showroom System provides an open, flexible solution for managing collections of all sizes and disciplines. The system enables clients to catalogue, view their current location and watch relevant videos.
The main features are:
- COLLECTIONS AND CONTENT MANAGEMENT Record and publish complete information on cataloguing, documentation, location, and manage the museum collections.
- MODIFYING