Content Management System Software Requirements Specification
Software Requirements Specification
1. Purpose :
The purpose of this SRS is to make a good perspective about the system and allow the team members to focus on the functional requirements. As the result this document can help the programmers to implement the software easier.
This document provides a good landscape from project and helps the costumer learn more about this document.
The scope of this document is rest of the project It means that the rest of the project is influenced by this document and this document's change can change the path of the project.
Here we have listed some of functional and non-functional requirements of the system for the first step of the project.
1.3 Definitions , Acronyms And Abbreviations
See The Glossary.
/* Notice : This definition can be changed by other teams . We can remove administrator from system and allow writers to write in systems or we can let any user to register as writer without any limitation and provide us some content */
Digital Content Management System ,Yan Han,Systems Librarian University Of Arizona 2004.
2. Overall Description
Product Perspective & Function
Provide a stable and extensible foundation to provide preservation and access services for end users .
Provide a stable and extensible foundation to provide preservation access and information sharing for other information systems .
Provide a long-term strategy for preserving , organizing and disseminating locally developed and external content .
Provide a long-term strategy for preserving , organizing and disseminating meta data associated with the content .
Provide a stable and extensible foundation to support reuse able content.
Organization Requirements (Content , meta data)
Access Requirements(Internal , External , Authentication , Systems)
In This System users are grouped in 4 groups : end user , writer , administrator , manager.
Each user can do his defined actions.
3. Specific Requirements
The system must keep the original file’s name, size and created date.
Users must be able to download digital objects and all associated meta data from the system.
Writers(any user who writes in system) must be able to modify digital objects within the system.
System must provide online help.
System must be able to be accessible all the time.
System must provide a persistent unique URL for a digital object.