Beruflich Dokumente
Kultur Dokumente
Ver<1.0> 23/1/2011
Team Guide:
K SUSHMA
TEAM MEMBERS:
ELITE PROFESSIONALS ACE ENGINEERING COLLEGE GHATKESAR ANUSHKAPUR Andhra Pradesh. COMPUTER SCIENCE
Page 1
Ver<1.0> 23/1/2011
Date 23/01/2012
Version 1.0
ELITE PROFESSIONALS
Page 2
Ver<1.0> 23/1/2011
Table of contents
1.0 Introduction
PAGE NO
6 6 8 9 9 10
1.1. Purpose 1.2. Scope 1.3. Abbreviations 1.4. Reference 1.5. Technologies 1.6. Overview
Page 3
Ver<1.0> 23/1/2011
2.1. Product Perspective 2.2. Software Interface 2.3. Hardware Interface 2.4. Communication Interface 2.5. Product Functionalities 2.6. User Characteristics 2.7. Constraints 2.8. Use-Case Model Survey 2.9. Architecture diagram 2.10. Database design
ELITE PROFESSIONALS
10 12 12 12 13 14 14 15 16 18
Page 4
Ver<1.0> 23/1/2011
2.11. Schema Diagrams 2.12. Class Diagrams 2.13. Assumptions and Dependencies
19 20 20
3. Specific Requirements
3.1. Use-Case Reports 3.2. Supplementary Requirements 20 24
25
ELITE PROFESSIONALS
Page 5
Ver<1.0> 23/1/2011
1.1 Purpose:
The purpose of the SRS is to specify why the system needed and the requirements are that need to be fulfilled by the system. Along with the full functionality, the actors and their purposes will also be expanded. This srs provide us basic idea of our system. The motto of the software is: AN ENIVORNMENT TO SHARE IDEAS Factors behind the motivation of this system are to provide user friendly environment for interaction between students and teachers. Also to nurture the creativity from student
1.2 Scope:
In this SRS, we shall be detailing the overall functioning of the system rather than in depth look in to each and every operation performed by the various actors involved. This SRS shall directly affect our final project report. As this is the first version, as and when the system is reviewed alterations and improvisations will be done in the upcoming versions. The system will be prepared keeping in mind the Diagrams attached. Basic features: Create different system users and assign different roles with related permissions.
ELITE PROFESSIONALS
Page 6
Ver<1.0> 23/1/2011
MANAGING
i. Search Engine for all the articles posted till date. Accessible by anybody. ii. Essential steps to be taken to prevent authenticity infringement. iii. Articles to be distributed in categories. Can overlap 2 or more categories. Articles to be associated with suitable tags by the registered users at the time of posting, so that they are searchable. iv. The home page to consist of attractive essential features like: most read articles, editors pick, recently posted articles, highest rated articles, article of the month, college news, etc. v. Archives to be maintained. vi. Interactive feedback to be supported to enhance the user experience. vii. Guests can read articles, rate them and comment on them. They can also access other optional features (amenities like Word of the day, etc.) but cant post articles unless they sign in as registered users. viii. Automatic commenting on articles by spammers/automatic bots to be defied. ix. Prevent standard automated software from filling out a form. x. College Students/Faculties can only register as members (through unique IDs). xi. Alumni registration to be supported. xii. Registered members, Moderators and Administrators are allowed to post articles. xiii. Articles can be downloaded in various formats. xiv. Registered users, Moderators, and Admins will have their own profile, where they can edit info for the world to see. Useful updated info related to their activities to be available at their profiles. xv. Regex to be extensively used for prohibiting obscene and unacceptable comments.
ELITE PROFESSIONALS Page 7
Ver<1.0> 23/1/2011
Moderators will have associated categories, according to which to-be-validated-articles will be posted to them on their profiles. On rejection, he will have to provide a reason for the same, which will be forwarded to the concerned user.
Additional features:
1) Database connectivity to store user details 2) Secure Socket Layer (SSL) connectivity to ensure security. 3) Optimized AJAX usage for better user interaction. 4) Usage of Jquery for Pluggable look and feel. 5) Login and Password modification is made easy using JDBC connectivity
ELITE PROFESSIONALS
Page 8
Ver<1.0> 23/1/2011
Standards. RAD: Rational application developer is a toolkit which is designed for The creation of more complex projects, providing fully dynamic web Application utilizing EJBs. This consist of EJB tools, CMP, data mapping Tools & a universal test client that is designed to aid testing of EJBs. HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server. HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. TCP/IP Uses several protocols, the two main ones being TCP and IP.
1.4 References
SRS (IEEE SRS Format and Format provided by TGMC)
Page 9
Ver<1.0> 23/1/2011
1.6 Overview:
SRS includes two sections overall description and specific requirements Overall description will describe major role of the system components and interconnections. Specific requirements will describe roles & functions of the actors.
CLIENT SIDE INTERFACE for adding interactivity we will use javascript jquery and ajax
ELITE PROFESSIONALS Page 10
Ver<1.0> 23/1/2011
OVER ALL MODEL Client interacts with interface enter the details It connects to the database or servlet using server HTML(clientside)+ client side interactivity(javascript and jquery) JSP+Servlet+bean(server side interactivity at server)websphere +database(db2)
ELITE PROFESSIONALS Page 11
Ver<1.0> 23/1/2011
64 MB
1 GB
Server Side
Web sphere application serve V5.0
ELITE PROFESSIONALS Page 12
Ver<1.0> 23/1/2011
Pentium III at
DB2 V8.1
1 GHz
2.5 Product Functionalities: 1)Separate login page for administrator and user 2)CATEGORISED NEWS POST 3)COMMENTS AND POSTS ARE ALLOWED FOR REGISTERED STUDENTS ,MODERATORS AND ADMIN 4)REMOVAL OF NEWS OR POSTFEED CAN ONLY ALLOWED FOR ADMIN 5)FEEDBACK SYSTEM AND RATING FOR EVERY NEWS FEED 6)SECURITY MEASURES A)USE OF CAPTACHA TO PREVENT FOR AUTOMATIC FORM FILLING B)SECURE AUTHENTICATED LOGIN
ELITE PROFESSIONALS Page 13
Ver<1.0> 23/1/2011
ELITE PROFESSIONALS
Page 14
Ver<1.0> 23/1/2011
ELITE PROFESSIONALS
Page 15
Ver<1.0> 23/1/2011
ELITE PROFESSIONALS
Page 16
Ver<1.0> 23/1/2011
ELITE PROFESSIONALS
Page 17
Ver<1.0> 23/1/2011
ELITE PROFESSIONALS
Page 18
Ver<1.0> 23/1/2011
ELITE PROFESSIONALS
Page 19
Ver<1.0> 23/1/2011
2.13 Assumptions and Dependencies The end user should have a basic knowledge of English and computer usage. Administrator is created in the system already. Roles and tasks are predefined 3. Specific Requirements: 3.1 Use-Case Reports: Actors: The system caters to following types of user.
ELITE PROFESSIONALS
1)ADMINSTRATOR
Page 20
Ver<1.0> 23/1/2011
Login: In order to access other specific functionalities a user must login to the system. All Users can login to the system using their user name and password. Name of use case: login Description: client enters user name and password and the system authenticates The user Preconditions: The user account is existing in the database and has not yet logged In Normal flow of events: 1)The client enters user name and password. 2)JavaScript validates the provided information using regular expression. 3) the Jsp page passes the request to Servlet. 4) the Servlet checks against database and returns TRUE. 5)A bean instance is created and property is set by JavaScript. 6) User is asked for the option of continuing with previous session by java script. 7)Based on user input the session detail is got from Servlet and DOM is updated Alternative flow of events: 1) The client enters user name and password. 2) JavaScript validates the provided information using regular expression. 3)the Jsp page passes the request to Servlet. 4)the Servlet checks against database and returns FALSE.
ELITE PROFESSIONALS
Page 21
Ver<1.0> 23/1/2011
Name of use case: LOGGED IN Description: The client can post delete or comment or validate article Precondition: user must successfully logged in NORMAL FLOW OF EVENTS 1) Client enters the article and posts it or client rates or comment the article 2) JavaScript validates the entered article or comment checks if authentic 3)jsp passes the article to servlet 4) Checks the date and stores it in the database 5) User display gets updated
ELITE PROFESSIONALS
Page 22
Ver<1.0> 23/1/2011
. Logout: After completion all his/her activities an user may logout of the system. Change password: A user of the system would be provided a default password at the beginning. To Maintain privacy he/she can change his/her password. Name of use case: Change Password Description: client enters the new password in order to replace his existing Password. Preconditions: The user account is exists in the database and user has logged in. Normal flow of events: 1) The client clicks the button. 2) Jsp page asynchronously requests the servlet. 3) Servlet forwards the request to EJB. 4) The Servlet checks against database and returns true. 5) EJB makes changes to the database. 6) EJB reports the change to servlet. 7) Servlet similarly reports back to the JSP which updates the DOM . View help: A 24x7 help feature would be provided. The help is available both online and Offline. The user may access help feature that is convenient to him. Customize profile:
ELITE PROFESSIONALS
Page 23
Ver<1.0> 23/1/2011
To give user a better look and feel, the system boasts several kinds of skins and Theme. The user can customize his profile by selecting one from the available. Name of use case: Customize profile Description: client customizes his/her profile by choosing from predefined skins. Preconditions: The user account is exists in the database and user has logged in. Normal flow of events: 1) The client chooses the skin. 2) The client clicks the button. 3) Jsp page asynchronously requests the servlet. 4) Servlet forwards the request to EJB. 5) EJB makes changes to the database. 6) EJB reports the change to servlet. 7) Servlet similarly reports back to the JSP 8) JSP updates the DOM. User Specific Functionalities: 3.2 Supplementary Requirements 24 x 7 Availability If the base is now the entire world, staying open 24 Hours a day becomes critical. Because system can be an automated Process, so It can stay open for 24 hours a day. So UPS support must be on server site for At least 8 hours in case of power failure. System will remain inaccessible to Users at 2:00 to 4:00 am for backup and maintenance purpose. Dynamic Website - Many early Web implementations consisted of static HTML pages. This becomes very difficult to manage if the number of pages gets too large. An effective system should be largely dynamic taking advantage Of technology that automates this process rather than relying on manual Processes. Application should serve dynamic user based customized web Pages to its clients from server. Integration with existing enterprise systems Any existing Web site that Relies on the manual duplication of data from another system is one that can Be improved. Most of the business data in the world today exists in enterprise Servers that can be connected to the Web servers to make this process far More effective.
ELITE PROFESSIONALS
Page 24
Ver<1.0> 23/1/2011
Provide good performance and the ability to scale the server The Web Application Server should provide good performance and the ability to Manage performance with techniques, such as support for caching, clustering, And load balancing. Providing session management capability - Web application developers Should not spend valuable time worrying about how to maintain sessions Within the application. The Web Application Server should provide these services.
ELITE PROFESSIONALS
Page 25