Index and Tables
1) Introduction:
1.01) Purpose……………………………………………………..
1.02)Scope………………………………………………………...
1.03)Abbreviations………………………………………………..
1.04)Reference……………………………………………………
1.05)Technologies………………………………………………...
2) Overall Description:
2.01) Product Perspective .....................................................
2.02) Software Interface ........................................................
2.03) Hardware Interface .......................................................
2.04) Communication Interface ..............................................
2.05) Product Function ...........................................................
2.06) User Characteristics ......................................................
2.07) Constraints ....................................................................
2.08) Use-Case Model Survey ...............................................
2.09) Database design ...........................................................
2.11) Assumptions and Dependencies ..................................
3) Specific Requirements:
3.01) Use-Case Reports .........................................................
3.02) Supplementary Requirements .......................................
1) Introduction:
1.1) Purpose:
1.2) Scope:
//Add more then 8 points
1.3) Abbreviations:
HTML: Hypertext Markup Language is a markup language used to design
static web pages.
J2EE: Java 2 Enterprise Edition is a programming platform— part of the
Java Platform— for developing and running distributed multitier
architecture Java applications, based largely on modular software
components running on an application server.
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 (secure
socket layer).
RTP
RTSP
//add more points
1.4) References:
1.5) Technologies:
J2EE: Application Architecture
My sql
Tomcat
//add more points
Rational: Design Tool
2) Overall Description:
Describe the general factors that affect the product and its requirements.
2.01) Product Perspective:
2.02) Software Interface:
Client on Internet: Web Browser, Operating System (any)
Client on Intranet: Client Software, Web Browser, Operating System (any)
Web Server: Tomcat, Operating System (any)
Data Base Server: My SQL, Operating System (any)
Development End: Netbeens (J2EE, J2ME,Java, Java Bean, Servlets, HTML),
My SQL, OS (Windows), Tomcat.
2.03) Hardware Interface:
2.04) Communication Interface:
Client on Internet will be using HTTP/HTTPS protocol.
The application will be using RTP protocol for Video Streaming
2.05) Product Function:
2.06) User Characteristics: Every user should be comfortable of working with
computer and net
browsing. He must have basic knowledge of English too.
2.07) Constraints:
GUI is only in English.
Login and password is used for identification of user and there is no facility
for guest.
There is no maintainability of back up so availability will get effected.
Limited to HTTP/HTTPS.
2.08) Use-Case Model Survey:
USE CASE DIAGRAM
//Add use case diagram
//explain each and every user usecases
2.09)Database design:
//add diagram
3) Specific Requirements:
3.1) Use-Case Reports:
//give usecase scenario and activity diagram for every usecase
3.2) Supplementary Requirements:
Have hours of operation that are 24 x 7 –Because system can be an
automated process, so it can stay open for 24 hours a day. If the base is now
the entire world, staying open 24 hours a day becomes critical. System is
required to be available 24X7 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.
Make the existing Web site more dynamic in nature - 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.
Tie the existing Web site into 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.
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.
