به نام خدا

Fatal Error
Welcome To Fatal Error Weblog

  Content Management System Software Requirements Specification

Software Requirements Specification

1.      Introduction

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.

1.2 Scope

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 */

1.4 References

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.

Requirements Subsets

 

 

Organization Requirements (Content , meta data)

 

Presentation Requirements

 

Access Requirements(Internal , External , Authentication , Systems)

 

Preservation Requirements

User Characteristics

 

 

In This System users are grouped in 4 groups : end user , writer , administrator , manager.

 

Each user can do his defined actions.

 

3.      Specific Requirements

3.1 Functionality

 

1

The system must keep the original file’s name, size and created date.

2

Users must be able to download digital objects and all associated meta data from the system.

3

Writers(any user who writes in system) must be able to modify digital objects within the system.

4

System must provide online help.

5

System must be able to be accessible all the time.

6

System must provide a persistent unique URL for a digital object.

7

System must export content and meta data as original format.

8

It is desirable to transform one meta data schema to another meta data schema.

9

The system must provide a web-based interface for all its functionality.

10

The system should be able to present a unicode -compatible interface.

11

The system should be able to allow users to submit feedback on system problems.

12

The system must be able to notify users current state of the task.

13

The system must be able to provide statistical usage and relevant reports.

14

Users must be able to search content via meta data.

15

The system should provide full-text searching.

16

The system should provide Boolean (AND, OR, NOT)searching.

17

The system must display rights information to users.

18

The system must provide help documentation for access methods(API)

19

The system should provide other standard web services access to content and meta data.

20

The system must be able to support different roles.

21

The system must be able to support the feature that groups are assigned to one or more roles.

22

The system must be able to support the feature that users are assigned to one or more groups.

23

The system should support the following roles : End user , Writer , Administrator , Manager

24

Manager must be able to do ANYTHING within the system.

25

Administrator : must be able to create/add/delete writers.

26

Writers : must be able to create/edit/add/delete meta data and content in defined(not ALL) collections.

27

End user : only can browse and search meta data and content.

28

The system must use authorization to support different roles within this system.

29

The system must be ACID (Atomicity, Consistency, Isolation, Durability).

30

The system must be unicode compatible for all functionalities.

31

The system must store meta data records separately from content.

32

 The system must be able to store any file format.

33

The system must be able to keep error/usage/debug log files.

 

3.2 Usability

Required training time for a normal users and a power user to become productive at particular operations must be less than minutes or even seconds. If this system is going to work as Wikipedia.

System must use HTML standards to work which are more popular.

3.3 Reliability

System must be available all the time.

System must be able to answer to many users in the minimum turnaround time.

Mean Time Between Failures : (it depends on the hardware) but in the worst state it can be 3 months.

Mean Time To Repair : in the worst condition it must be near 36 hours.

Accuracy : ?

Maximum Bugs : ?

Maximum Defects : ?

3.4 Performance

The system must notify and update users’ request status within reasonable time.

The average response time for our system must be less than 3 seconds.

Throughput for our system must be 100 per second.

Capacity of the must be less more than 100 costumers transaction.

3.5 Supportability

The system must take a backup from contents every day.         

System must receive latest information about latest version of software.

3.6 Design Constraints

Designer must adopt a modular layout and approach, so as to facilitate a flexible management of content through a web content management system.

Designer must implementation and use of standard, and accessible, dynamic PHP.

Designer must prepare style sheet definitions and employ a moderate use of images.

 

3.7 Online User Documentation And Help System Requirements

system must provide an animated film to help managers and administrators to work better , this film can be presented after installing the system.

3.8 Purchased Components

/* As the system is going to be implement on internet or LAN or other types of networks the following list contains the purchased components */

Designer desired to implement the system on a hired Apache server or prepare a Apache server himself ( this item depends on the organization and the budget )

Designer must prepare a MySQL database for developers and the latest version for PHP and install them on the computer they are going to work , this computer acts as server , but it is not the main server , this server will simulate the real states for us. Even he must prepare these softwares for team members.(these softwares are available on internet)

Designer must prepare a computer as server to test the system.

3.9 Interfaces

3.9.1 User Interfaces

One of the user interfaces are built by PHP. And they can access to their account by internet. Each user according to his role in system has his own interface.

Somehow this software will offer a good interface for presenting contents and data on the system. And adding / deleting  or updating meta data and content for users.

3.9.2 Hardware Interfaces

Our system will be implemented in a server on internet so it must have some Hardware interfaces for its IP address and other requirements to make a host for our CMS. This software will be implemented by PHP , and Apache server and Our OS will make good interface for us to connect to those Hardware components(NIC , Ports , Modems , etc).

Another important interface for system is its report which is available  when the manager or administrators request them. Presenting this report in digital form is easy but for printing it on a paper we must make an interface for this problem.

/* As the Internet Explorer and other web browsers provide a good  interface to print. So the only important thing is to preview a printable or a PDF page on the internet */

3.9.3 Software Interfaces

One of the important software interfaces is a connection between our PHP application and Database. As PHP is consistent with My SQL , we must not be so worried about this matter. And the most important thing is to make a high secure and high performance system in our network configurations by using secure protocols and firewalls for our system.

/* These characteristics are special for hardware part of our system not software part */

3.9.4 Communications Interfaces

this part is explained in previous items.

3.10 Licensing Requirements , Legal , Copyright And Other Notices

As this system will be implemented by PHP , so the server which we are going to install our software on , can be Windows or Linux server. As the Linux server is cheaper than windows server so we will use Open Source Licensing such GFDL (GNU Free Documentation License) which allow other people to see , copy and establish it but they are not free to change it ! The main purpose of GFDL is to offer a good documentation or manual for users. This license is a sort of Copyleft.

تگ های این مطلب :content management system
و تگ های این مطلب :software requirements specification
و تگ های این مطلب :سیستم مدیریت محتوا
نویسنده : Fatal Error | ساعت ٢:۳٩ ‎ب.ظ روز ۱۳۸۸/۱/٤
پيام هاي ديگران () | لینک ثابت