Chenne mane game SRS: Chennemane is a popular folk game called Dakshina Kannada. In this project, we will be introducing the game and maintaining the traditionalism of our Tulunadu. It concerns playing a game on a PC and receiving SMS updates about ratings, achievements generated by the respective player. The performance of the specifications specification is the “Software Requirement Specification” (SRS).

The SRS is a text that fully explains the exterior actions of the program. It is the first and foremost task of the software developer to research the framework to be built and to determine the specifications of the customer before continuing with the design component.

Chenne mane game SRS

Purpose

The goal of the project is to spread the folk game around the world and to popularize the “Chennemane Game” among the people of the current and future generations. As there is no current structure to play the game, our key purpose is to provide a forum for this diminishing folk-game.

The introduction of the Chennemane game is the solution to popularize this game among young people.

• Implementation of Chennemane is helpful for learners to learn the game by using “Training mode” (Demo).
• When the player registers, his account will be produced and his results registered.
• If the new record (maximum score) is broken, the SMS alert will be sent to the previous record holder and prompts him to restore his old record.

Scope

The proposed project would introduce the Chennemane game on the PC and help to play the game without using the conventional board and coins (a seed named “Manjutti”).

The project is going to:

• Provide the user (players) with ‘username’ and ‘password’ to protect his account.
• Store, update and show the score of each player in the course of the game.
• Compare the score of the last match and send an SMS warning to the previous record-holder if a new record is set.

Constraints

 General Constraints

The score of each player is registered only after every game has been completed.

Definition, acronyms, abbreviation

The score of each player is registered only after every game has been completed.

• Login: Before you play the game, users must choose a special username and password that guarantees their account and maintains their database regularly.
• Player: It’s the consumer who plays the role.
• Game Selection: The game mode must be chosen after the user has logged in. There are two types:

            a. Single-end mode: Demo game which helps the new players to learn this game.

            b. LAN game mode: In this mode, an actor has to play on his own, with the player on another system that is connected through the Local Area Network.

Score:

Points are taken by the player in the game.

Result: The result of the match, which includes the winner of the match, the cumulative score of the teams, and the time taken to defeat the opponent.

2.3 Overview

Project execution starts when the user logs in to the game. The user has to pick the game mode. If he’s new to the game, in training mode, he can learn the art of Chennemane. He will play the match in Real mode when he’s well into it. After matching, the result will be presented and saved in your database. When a player tops the new top score, an SMS alert will be sent to the previous record holder and encourages him to regain his old record.

References:

The specifications for this project are drawn from the Software Company: A1 Logics, Mangalore.

2.4 Product Perspective: The Chennemane game project would have a new layer in the world of video games. This will help urban people learn to play folk games without the help of the traditional board and coins. When a user plays the game, his score will be saved in the database and the scores of existing players will be shown throughout the game.

 Product Function: The proposed project would implement the Chennemane game on your PC and allow you to play the game without using the conventional board and coins.

2.5 System Interface

External Interface Requirements

•  User interface: The user Interface is designed in a user-friendly way. And the user has to shift coins that require the keyboard and the mouse for the GUI.
• Hardware Interface: Modem.
• Software Interface: The front-end application is ASP.NET, C# for users for getting information about items and placing orders. In the Back End, to manage data in the Microsoft SQL Server 2005 database as the back end
• Communication Interface: TCP/IP

Functional Requirements

Module: We have 2 levels of user:

• Admin
• Player

Login Module: In this module, if a new player wishes to play the game, he may register.

Reports: This is the outcome that is stored in the database after the match has been concluded.

Alerts: Alerts are messages sent to a player whose record is being beaten by another player.

2.6 User Characteristics

We are having two levels of users:

Admin:

• The user account can be accessed

• You can delete a user account.

Player:

• He can play the game only after he creates an account by logging in.

• He can only see his own score and the ‘highest score.’

Assumptions and dependences

Both data entered would be reliable and up-to-date. The Browser and the operating system will support the work of the system and the DOTNET framework.

Performance Requirements:

There are no other requirements for performance.

System Attributes: The software requires a minimum configuration of 20 GB of HDD, Dual Speakers or headphones, a 2.6 GHz processor, and a minimum of 512 MB of RAM at the end of the client.

Other Requirements:

There are no other requirements.