Sei sulla pagina 1di 14

Software Requirements Specification

for

E- journal
Version 1.0 approved

Prepared by <author>

<organization>

<date created>

eLearning versions of several popular Process Impact training seminars are available at www.processimpact.com/elearning.shtml, including In Search of Excellent Requirements, Exploring User Requirements with Use Cases, Writing High-Quality Requirements, Software Inspections and Peer Reviews, and Project Management Best Practices. Single-user and corporate-wide site licenses are both available.
Copyright 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

Software Requirements Specification for E-journal

Page ii

Table of Contents
1. INTRODUCTION......................................................................................................................1
1.1 PURPOSE .......................................................................................................................................... 1.2 DOCUMENT CONVENTIONS....................................................................................................... 1.3 INTENDED AUDIENCE AND READING SUGGESTIONS...................................................... 1.4 PROJECT SCOPE............................................................................................................................ 1.5 REFERENCES.................................................................................................................................... 1 1 1 2 3

2. OVERALL DESCRIPTION.................................................................................................... 4
2.1 PRODUCT PERSPECTIVE............................................................................................................. 4 2.2 PRODUCT FEATURES................................................................................................................... 4 2.3 USER CLASSES AND CHARACTERISTICS.............................................................................. 5 2.4 OPERATING ENVIRONMENT....................................................................................................... 5 Operating System -: Window XP,7, vista.............................................................................................. 5 Browser -: internet explorer above 6.0, Mozilla firefox & opera above 7.0..........................5 The user/writers/readers must be compatible with the Internet applications. ...................................6 The E-Journal System is connected to the internet server and is running all 24 hours a day. The users access the E-journal System from any computer that has Internet browsing capabilities and an Internet connection................................................................................................................................................. 6 The users must have their correct usernames and passwords to enter into the E-Journal System website....................................................................................................................................................... 6 2.5 USER DOCUMENTATION............................................................................................................. 6 2.6 ASSUMPTIONS AND DEPENDENCIES...................................................................................... 6

3. SYSTEM FEATURES..............................................................................................................7
3.1 DESCRIPTION AND PRIORITY................................................................................................... 7 3.2 FUNCTIONAL REQUIREMENTS.................................................................................................. 7

4. EXTERNAL INTERFACE REQUIREMENTS...................................................................9


4.1 USER INTERFACES:....................................................................................................................... 9 4.2 HARDWARE INTERFACES........................................................................................................... 9 4.3 SOFTWARE INTERFACES........................................................................................................... 10 4.4 COMMUNICATIONS INTERFACES........................................................................................... 10 The Customer must connect to the Internet to access the Website:....................................................... 10 Dialup Modem of 52 kbps..................................................................................................................... 10

5. OTHER NONFUNCTIONAL REQUIREMENTS............................................................ 10


5.1 PERFORMANCE REQUIREMENTS............................................................................................ 5.2 SAFETY REQUIREMENTS........................................................................................................... 5.3 SECURITY REQUIREMENTS...................................................................................................... 5.4 SOFTWARE QUALITY ATTRIBUTES....................................................................................... 10 11 11 11

6. OTHER REQUIREMENTS................................................................................................... 11

Software Requirements Specification for E-journal sytem

Page 1

1.
1.1

INTRODUCTION
PURPOSE

E-journal system assist with every stage of the publishing process from submission to online publication on the indexing. E-journal is an open source made freely available to journals world for the purpose of making open access publishing available option for more journals. Readers from all over the world can obtain & read our journals without printing copies to be mailed to all over the world, which can be both expensive and slow. An online journals has a great advantage over printed journal , as it is possible to publish an issue as soon as it is ready. It offers the potential to provide reader with more functionality. 1.2 DOCUMENT CONVENTIONS The document follows the following convention while it is being written. The document is written in Times new roman, 14 Text Size Every Document sub heading is written in Bold letter, Times New Roman, 14 Text Size Every document heading is written in bold letter, Times New Roman, 18 text size 1.3 INTENDED AUDIENCE AND READING SUGGESTIONS We are developing our project E-Journal System for all the magazine reader to read journal in internet. This SRS is mainly developed for the project development team. In this team there are developer, coder, tester and documentation writer and the user of the project also. User (Customer): This document is intended to user and customer to make them ensure that this document is well meeting the need of the users.

Software Requirements Specification for E-journal sytem

Page 2

Project Developer: The project developer will refer to the SRS document to make sure that they developed exactly what the online readers requires. Tester: The tester will read this SRS document and he will ensure that the requirements are understandable from functionality point of view so that he can test the software and validate its working. Document Writer: The document writer is reading the SRS document to ensure that they understand the document well enough to be able to write the users manuals. Maintenance: The SRS document helps the maintenance engineers to understand functionality of the system, a clear knowledge of the functionality can help them to understand design and code. Suggestions 1. The user can read the whole SRS document but for him Introduction, Overall description and System features is much required the software performance. 2. The developer must go through the whole SRS for understanding the requirement and functioning of software. 3. The designer and coder must see the class and object diagram and state transmission diagram for coding the modules. 4. A tester must be aware of coding language and visit through the code section and check the required output. 5. The document writer should write the qualitative document so that it becomes easy and understand to every one.

1.4

PROJECT SCOPE The Software Requirements Specification captures all the requirements in a single document. The E-journal System that is to be developed provides the public and magazine reader with journals on various subjects, online

Software Requirements Specification for E-journal sytem

Page 3

reading & uploading of new or old journals and many other facilities . The E-Journal System is supposed to have the following features. The product provides the public members with online reading & uploading new journals capabilities and the E-Journal System is up and running all day. The system provides logon facility to the users.

The system provides the members with the option to check their account and/or change their options like password of the account whenever needed all through the day . The system allows the users for uploading & accessing journals 24 hours a day The system lets the adminstrater/expert/editor to check which all members have uploaded the journals and whether they can upload the journals or not. The system allows the expert to see all the journals uploaded & check them to accept or reject for publishing online.

We have a editorial department, which manages the journals to be placed on the online publication. The features that are described in this document are used in the future phases of the software development cycle. The features described here meet the needs of all the users. The success criteria for the system are based in the level up to which the features described in this document are implemented in the system. 1.5

REFERENCES http://pkp.sfu.ca www.google.co.in www.wikipedia.com www.scribd.com

Software Requirements Specification for E-journal sytem

Page 4

2.
2.1

OVERALL DESCRIPTION
PRODUCT PERSPECTIVE

The E-Journal System is a package to be used by magazine or any journals publishers to improve the efficiency of readers, journal writters and Users( editor, administrater). The E-Journal System to be developed benefits greatly the magazine or different journal readers, obviously great writters and the editor or administrater of magazine. The system provides subject catalog and information to members and helps them to decide on the subject on which they would give their writtings. The editor can keep the catalog updated all the time so that the members (mainly the public readers & writters) get the updated information all the time. 2.2 PRODUCT FEATURES The E-journal System provides online journals about a topic available in the publishing phase, posting of new journals and the user information. The Product functions are more or less the same as described in the product perspective. The functions of the system include the system providing different type of services based on the type of users [reader/writter/expert/editor]. The member should be provided with the updated information about the daily journals. Provisions for the members to write or post any journals they want. The member is given a provision to check his account information and change the account information any time in the given valid period. The members are provided with username & password to read or post journals. The expert/administrater can get the information about the members who writes & reads writtings.

Software Requirements Specification for E-journal sytem

Page 5

The expert is provided with interfaces to accept/reject the writtings posted to his account and keep the rejected one for future analysis. The editor arrange the accepted writings to be publish in the next shift.

2.3

USER CLASSES AND CHARACTERISTICS End users : There are two type of end user, one is writers & the other is readers. They can only read and post the journals. Publishing users: there are many user , they are expert, editors, reviewer, administrater. They manages journals, users & publishing process. OPERATING ENVIRONMENT Operating System -: Window XP,7, vista Browser -: internet explorer above 6.0, Mozilla firefox & opera above 7.0 Database -: SQL server Language -: HTML, Web Server -: Apache The only requirement to use this online product would be the internet connection.

2.4

Software Requirements Specification for E-journal sytem

Page 6

2.5 DESIGN AND IMPLEMENTATION CONSTRAINTS The user/writers/readers must be compatible with the Internet applications. The E-Journal System is connected to the internet server and is running all 24 hours a day. The users access the E-journal System from any computer that has Internet browsing capabilities and an Internet connection. The users must have their correct usernames and passwords to enter into the E-Journal System website.

The writer & readers must know the use of computer, internet & how to post ?. 2.5 USER DOCUMENTATION Online help is provided for each of the feature available with the E-Journal. All the applications provide an on-line help system to assist the user. The nature of these systems is unique to application development as they combine aspects of programming (hyperlinks, etc) with aspects of technical writing (organization, presentation). Online help is provided for each and every feature provided by the system. The User Manual describes the use of the system to users and admins. It describes the use of the system on mobile systems. Also, a Read Me file is typically included as a standard component. The Read Me includes a Whats New With This Release section, and a discussion of compatibility issues with earlier releases. Since the installation of E-Journal is a complex process, our experts will do it. So an installation Guide will not be provided to the user. 2.6 ASSUMPTIONS AND DEPENDENCIES The users have sufficient knowledge of computers. The users computer should have Internet connection and Internet server capabilities. The users know the English language, as the user interface will be provided in English. The user should have registered in the E-jounal website

Software Requirements Specification for E-journal sytem

Page 7

3.

SYSTEM FEATURES

3.1

DESCRIPTION AND PRIORITY


1. First priority goes to the welcome form. when user will login the system

2.

3.

4.

5. 6.

there will be welcome screen which will assure to the use either he wants to register or login. After the welcome form there will be registration form & login form. New user can register by giving their data in the registration form & registered user can login by giving authenticated username & password on the login form. Second priority goes to the menu form where the contents, manuals, and some others functions of the system. From the menu form the user can go to any form of the system. In the menu form there will be a facility to select their choice for working like if the user just only wants to search the journals then he will only select the search field and go to the searching. Similarly if the user wants to post some document then he will go to the posting section and present the journal in the desired format(html). the priority given through user basic.

3.2

FUNCTIONAL REQUIREMENTS In this system there are lots of functioning. The user can Search journals, post his journals and see his/her account information. He will be able to post in any journals in only desired format. There will also be a reminder of new journals published Expert can able to check, accept & reject all journals posted by all users. Editor can able to arrange the journals according to his knowledge. Admin can add/delete users and saw all record of published journals as well as online publishing house.

Software Requirements Specification for E-journal sytem

Page 8

I.

register: Input name, d.o.b, address, E-mail id, phone no., voter id no, pan no. to register Processing: new record will be created temporarily till all document is verified login: user input username & password to login. Msg : username & password is incorrect. Search: User can search old & new journals by typing the date. Msg : incorrect date format, no journals found Posting: User post their journals in html,doc & pdf format. Msg : wrong format

II.

III.

IV.

V.

VI.

Expert module: Expert login using his own username & password, then he checks all journals posted by the users. He accepts some journals & rejected journals are remained there for future use. Msg: incorrect username & password, Journals accepted, Rejected journals sent to trash Editorial module: Editor user his authentication process to log in, then he is able to see the expert accepted journals, which is arranged by him which is to be published. Msg: incorrect username & password Journal published

Software Requirements Specification for E-journal sytem

Page 9

4.
4.1

EXTERNAL INTERFACE REQUIREMENTS


USER INTERFACES: The design of every page will be very clear and very interactive to the user. When the user open the website the welcome page will appear. In the login page the user can easily entered the desired password and login name. Then it will give the successfully login message. In every page there is help and support option is present for the ease of user. There will be a efficient server to provide a good service. In the screen layout the background color is very light and the graphics and font style will be in proper manner and well organized. If the user will print any error statement then it will give the proper error message display. The user will be able to search any issues from the record by using proper guideline shown in the website This will provide the better security data because the menu page will be displaying according to the login (admin or normal user). User can easily save its data in to the database and keep track of the records of posting and reading This website will be easily understandable and operable by the user.

4.2

HARDWARE INTERFACES

Server Side: Operating System: Windows 9x/xp ,Windows ME Processor: Pentium 3.0 GHz or higher RAM: 256 Mb or more Hard Drive: 10 GB or more Client side:

Software Requirements Specification for E-journal sytem

Page 10

Operating System: Windows 9x or above, MAC or UNIX. Processor: Pentium III or 2.0 GHz or higher. RAM: 256 Mb or more

4.3

SOFTWARE INTERFACES

<Describe the connections between this product and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint.>

4.4

COMMUNICATIONS INTERFACES

The Customer must connect to the Internet to access the Website: Dialup Modem of 52 kbps Broadband Internet Dialup or Broadband Connection with a Internet Provider.

5.
5.1

OTHER NONFUNCTIONAL REQUIREMENTS


PERFORMANCE REQUIREMENTS

The proposed system that we are going to develop will be used as the Chief performance system in the open journal organization which interact with the users from all over the world.

Software Requirements Specification for E-journal sytem

Page 11

Therefore, it is expected that the database & the server would perform functionally all the requirements that are specified by the organisation . For login to the software password and user name will be matched to the password and name saved in the database and thus only authenticated users are allowed to the login.

5.2

SAFETY REQUIREMENTS The external security can be provided by given the login authentication. There is also required a user authentication. The database may get crashed at any certain time due to virus or operating system failure. Therefore, it is required to take the database backup There is also the facility that the admin can lock his private data that will not be accessed by anyone

5.3

SECURITY REQUIREMENTS

<Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.>

5.4

SOFTWARE QUALITY ATTRIBUTES

<Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.>

6.

OTHER REQUIREMENTS

<Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.>

Software Requirements Specification for E-journal sytem

Page 12

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.>

Appendix B: Analysis Models


<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, statetransition diagrams, or entity-relationship diagrams.>

Appendix C: Issues List


< This is a dynamic list of the open requirements issues that remain to be resolved, including TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>