05-09-2016, 10:29 AM
1452673866-RakeshmeenaSrS.pptx (Size: 336.48 KB / Downloads: 4)
Introduction
Background Study:-
There are many projects for sanding massage one client to other. But each project has some disadvantage. Like that way2sms have typing limitation like we can’t type more than 130 words in one message. And in which also we can’t sand video message & download video. This type problem removes by my project
Project Scope:-
The SRS is intended to produce a sending sms to be called WebSMS. It will have many features that will help users to interact between themselves. Some of the intended features which this platform will provide are.
1. Communication (Sms)
2. Sending message & Photo & video
3. Discovery of old contacts
4. Making new contacts Overall Description
5. Download song
2. Overall Description
2.1 Product Perspective:-
This product is a web based application with a network of users using the service to communicate and stay in touch with each other. It requires a web browser with an internet connection and a server supporting PHP and a MySQL database.
2.2 Product Features:-
This web service performs the following functions:
It allows user to create his profile.. It allows a user to add another user to his list of friends. Search for users with common interests from the friend list · Post messages, pictures & also video etc Join group And Download video
2.3 User Classes and Characteristics:-
User Characteristics:-
This software is going to be used by people and which have registered at WebSMS. There are going to be three types of users. They are Administrator, Basic user, Login users.
The various functions that can be performed by these uses are indicated in section 3, functional requirements
These users have the following hierarchy of permissions
Administrator
|
Login Users
|
Basic Users
Each of the users will have access to the system only by User- id and password mechanism
2.5 Design and Implementation Constraints:-
We can use database for store data of user. And also using TCP/IP protocol for Communication of message from one side to another side.
2.6 Assumptions and Dependencies:-
Each User has a unique ID & password. User can logging on WebSMS then sends message (text & video) by user-id & password .We can also download video & send video & message. User can’t log on web without user-id & password & also which user doesn’t have account. He can’t log on WebSMS
3 External Interface Requirements:-
There are many types of interfaces as such supported by the WebSMS software system namely. The protocol used shall be HTTP. The Port number used will be 80. There shall be logical address of the system in IPv4 format.
User Interface
Software Interface
Hardware Interface.
3.1 User Interfaces:-
The user interface for the software .That should be compatible to any browser such as Internet Explorer, Mozilla by which user can access to the system. User login help of ID & Password on browser.
3.2 Hardware Interfaces
WebSMS is should work on any type of hardware that can support a browser. Since the application must run over the internet. All the hardware shall require to connect internet will be hardware interface for the system.
3.3 Software Interfaces
WebSMS shall work with browsers. It need connect with HTTP protocol for communication.
3.4 Communications Interfaces
The WebSMS system shall use the HTTP protocol for communication over the internet and for the intranet communication will be through TCP/IP protocol suite
4.1 Performance Requirements:-
The product shall be based on web and has to be run from a web server. The product shall take initial load time depending on internet connection strength which also depends on the media from which the product is run. The performance shall depend upon hardware components of the client/customer.
4.2 Safety Requirements
You must not send messages like abuse. We classify as Restricted Messages and do not permit on the Site. If a Registered User is found to send Restricted Messages, his account will be completely blocked.
4.3 Security Requirements
Safety is very important issues. If your project isn’t provide safety for user. So In this project user first create an account on WebSMS. After that Each User has a unique ID & password. So user can logging on WebSMS. But without id &password can’t log
4.4 Software Quality Attributes:-
The graphical user interface of WebSMS is to be designed with usability as the first priority
And design send message. There will be feedbacks such as notifications to inform users of updates provide users with instructions. User can easily work with WebSMS web. We can create friend list. And also create group of friend. The group leader also has the option to add members
Assumptions
We made plan for group member’s working. Then we divided work into part. One member work on coding part and another member work on testing &
Implementation & analysis part.
5.2 Design Methodology:-
Planning
Design coding.
Analysis of design coding.
Remove Problem
Testing project
Run on server
5.3 Risk and Volatile areas:-
This project is very good but it have only one disadvantage it’s only work online. We can’t work offline. If you forget about your username. You again create account. If a Registered User is found to send Restricted Messages, his account will be completely blocked. Advertisement messages. Such commercial messages are Restricted Messages. The customer agrees that, by definition, access to the Internet, the GSM and CDMA networks and other communication media is associated with risks