Your SlideShare is downloading. ×
Srs(Modified)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Srs(Modified)

476
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
476
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Software Requirements Specification for New Service Boosters to control outward churn Version 1.0 approved Prepared by S.M.Jagadish R.Jothiswaran K.Govindaraj
  • 2. Ericsson India Pvt .Ltd 22.12.2009 Table of Contents Introduction..........................................................................................................................................3 Purpose .......................................................................................................................................................3 Document Conventions................................................................................................................................3 Intended Audience and Reading Suggestions...............................................................................................3 Product Scope..............................................................................................................................................3 References...................................................................................................................................................3 Overall Description..............................................................................................................................3 Product Perspective......................................................................................................................................3 Product Functions........................................................................................................................................4 User Classes and Characteristics..................................................................................................................5 Operating Environment................................................................................................................................5 Design and Implementation Constraints......................................................................................................5 User Documentation....................................................................................................................................5 Assumptions and Dependencies...................................................................................................................5 External Interface Requirements.......................................................................................................5 User Interfaces.............................................................................................................................................5 Hardware Interfaces.....................................................................................................................................6 Software Interfaces......................................................................................................................................6 Communications Interfaces.........................................................................................................................6 System Features....................................................................................................................................6 Group Creation:...................................................................................................................................6 Reusing a service:.................................................................................................................................7 Terminating the group membership:.................................................................................................7 Other Nonfunctional Requirements...................................................................................................8 Performance Requirements..........................................................................................................................8 Safety Requirements....................................................................................................................................8 Security Requirements.................................................................................................................................8 Software Quality Attributes.........................................................................................................................8 Business Rules.............................................................................................................................................8 Other Requirements............................................................................................................................8
  • 3. Introduction Purpose  This SRS explains the features of the new service boosters that we plan to introduce for value added services. These new service boosters are an extension to the currently existing methodology for value-added services. Document Conventions The tables to be used in this project are specified in an italicized format. Every requirement stated in this SRS has its own priority. Intended Audience and Reading Suggestions This SRS is intended for usage by telecom operators for bringing about some improvements in the way value added services are offered. The rest of the SRS gives some valuable info about the softwares needed for implementation. Product Scope This software introduces the concept of groups for value added services. This is mainly to encourages the usage of value added services. It also establishes links between otherwise unrelated nodes(customers). It not only results in an increase of revenue for the operator but also helps to control churn by offering a win-win strategy for both the parties involved(operator and user). References http://telecomandinternet.com/innovation-of-value-added-service-vas/ ACM International Conference Proceeding Series; Vol. 261 archive Proceedings of the 11th international conference on Extending database technology:  Advances in database technology.  Nantes, France  Year of Publication:2008  Overall Description Product Perspective The origin for this software lies in the groups concept thats used in most of the web-
  • 4. sites. While this concept has been applied for voice( calls), its not been tested for value added services. We thus introduce a brand-new software that can be used by the operators for offering value-added services. This software needs to be integrated with the telecom infrastructure before being used. OWNER GROUP ID VAS1,VAS2,V AS3… MEMBER6 MEMBER1 MEMBER5 MEMBER2 MEMBER3 MEMBER4 Product Functions  It enables users to create groups or repositories for value added services  It enables users to join an existing group  It allows users to reuse a value added service thats present in the group(added by another user)  It also allows an operator to broadcast any new service directly to the group for a better response.  Indirectly,it results in the creation of social networks which is of immense value to the operator
  • 5. User Classes and Characteristics The users classes may be viewed from two perspectives . The first is from the perspective of “group”. Users may be either an owner or a member. Members can just add a service or reuse an existing service. It is the owner who actually creates a group. In addition to the privileges enjoyed by the member,he has the privilege to broadcast a message to all the members is the group. The second is from the perspective of services present in the group. In this case users are either a parent or child. Parent is the one who adds the service, while the child is the one who is going to reuse this service. Operating Environment Since we are dealing with a potentially large volume of data, a high speed server like the sun blade server is necessary. There is constraint on the operating system that is needed. An important point to note is that it must be easily integrated with the underlying telecom infrastructure. Design and Implementation Constraints This software for its efficient execution needs a high-speed hardware configuration. It also demands a huge secondary memory because of the large volume of the data involved. Moreover it needs access to the call detail records(CDR) for its implementation. It also needs constant maintenance and support by the vendor. User Documentation A user manual with detailed explanation about the conventions for creating a group, adding a service,re-using an existing service etc. an online help facility will also be provided. Assumptions and Dependencies It is assumed that this software is proposed for the alpha users or the most influential users. In the absence of the required hardware and software configurations , only a simulation is possible. The process of finding the alpha users can be borrowed from the techniques already existing. External Interface Requirements User Interfaces The user interface is basically going to be in the form of a mobile phone. This can be easily simulated using an open wave simulator or other tools. We show a sequence of such mobile phones. When a command is passed to this mobile phone interface it causes the functional requirements to be executed , thereby producing a text output in
  • 6. another mobile phone . the database is also subsequently updated. Hardware Interfaces The data needed by the software is fetched from a relational database. The interaction between the hardware and the software is in the form of text messages that are typed using a keyboard. While the output is also a text data displayed on the monitor or any other display device using an appropriate simulator tool Software Interfaces The software has a strong physical connection to the module that is going to find the alpha users. There are 3 main types of messages(the input) coming into the system. The first is a “ create group “ message which enables a person to create a group. The next is a “ reuse service” message which allows a child to use the service submitted by a parent. The last is a “broadcast “ message which can be used only by the owner of the group . In addition messages are also defined for quitting from a group. All these input data is in the form of a simple text that is sent to the system which then retrieves the needed data. Communications Interfaces Any simple client-server protocol can be used. In this case the front end is going to be a mobile interface while the back end is the database containing the call detail records. System Features Group Creation: 4.1.1 Description and Priority This feature serves as a start-up for our software. As the name indicates it involves an alpha user, creating a group by a simple text message mechanism. This feature has a very high priority for the simple reason that the remaining services are based on this. 4.1.2 Stimulus/Response Sequences The alpha user sends a text message requesting for a group creation . The system creates a repository and then immediately responds with a notification that the group has been created, also informing the user of the group-id. Also the services currently subscribed by the user will be automatically added to the repository 4.1.3 Functional Requirements REQ-1: The user has to have a certain minimal balance thats needed for the group creation. Else the system responds with a “ balance insufficient” message.
  • 7. REQ-2: Also he must use the appropriate format as mentioned in the documentation. Else the system responds with a “creation failed” message. Reusing a service: 4.1.1 Description and Priority This feature allows members to reuse the services which are present in the group( having been already added by another member) at a reduced cost. This feature has a comparitively lesser priority when compared to the group creation. 4.1.2 Stimulus/Response Sequences The member wishes to subscribe for a service. If that service is already present in a group that he belongs to, the system responds with a message indicating him to reuse this service. The member then sends a confirmatory message to the system so as to reuse the service from the group. 4.1.3 Functional Requirements REQ-1: The user has to have a certain minimal balance thats needed for the service usage. Else the system responds with a “ balance insufficient” message. REQ-2: Also he must use the appropriate format as mentioned in the documentation. Else the system responds with a “usage failed” message. REQ-3: If the service is not present in the group the system responds with a “service not present” message . Terminating the group membership: 4.1.1 Description and Priority This feature allows an owner as well as a member to quit from the group. In the event of the owner quitting from the group, the first member to have joined the group after the owner becomes the new owner. 4.1.2 Stimulus/Response Sequences The user must send a text message indicating that he needs to quit from the group. The system then responds with a confirmatory message. 4.1.3 Functional Requirements REQ-1: The user has to be a member of the group before using this service REQ-2: Also he must use the appropriate format as mentioned in the documentation. Else the system responds with a “termination failed”
  • 8. message. Other Nonfunctional Requirements Performance Requirements With respect to the “reusing service” functionality , the availability of a high speed system configuration is necessary for searching the large database. Safety Requirements Database updates must occur synchronously with the user access, for the enhanced reliability of the system. Security Requirements The database design must be such that the identity of one user is not revealed to any other user in the same group. This is the case even during service reuse. Software Quality Attributes The software has a high degree of reliability and is also portable. However its usability demands a considerable level of user expertise. The software is also highly flexible as it changes dynamically with the changing trends in the network. Business Rules Only the owner can implement the broadcast message service. Other Requirements The service provider who introduces this software in the market may opt for a patent to prevent copyright infringement . Appendix A: Glossary cdr-Call data records-details about the users behavior in a particular region vas-value added services- add-on services like dialer tunes,stock exchange updates.
  • 9. Appendix B: Analysis Models creating a group group DB owner joining the group <<includes>> adding a service service DB reusing a service member termination from group operator charging