U mobile
- 1. U-MOBILE AIM: To implement a software for U-MOBILE. (I)PROBLEM STATEMENT: Now a days people are busy with their works.As the population increases the number of banks in each city is less ,so people are wasting their time by spending in bank. even though they are spending time in banks, sometimes the work of the user is not completing due to more people in banks.There is no time to go banks for money transfer and for other works.So people are interested to move online money transactions apps which are provided by banks. By these online source we can transfer money, recharge our mobiles and we can do any works related to bank without going to banks. (II) SOFTWARE REQUIREMENT SPECIFICATION: 1.0 INTRODUCTION U-MOBILE is an application which can transfer money and mobile recharge. Through this app we can utilize above functionalities provided the mobile is connected to internet and this application is installed in it. We can know about their bank details. And also we can get our previous transactions and also get an E-Statement etc. 1.1 PURPOSE To transfer the money,mobile recharge and other bank activities that are taking place in our location. To make the life easy and reduce the time for bank applications which are money transactions and other activities. More options for transfer money to other bank users and more offers for mobile recharge.
- 2. 1.2 SCOPE U-Mobile source gives information for transfer money and for mobile recharges. customer can transfer their money to other bank customer and mobile recharge in anytime. It reduces the time for going to banks. To give correct and accurate information for the customers. 1.3 DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS • User- One who uses the application • Admin- One who develop the application 1.4 System- Where all the changes stored.REFERENCES IEEE Software Requirement Specification format. 1.5 TECHNOLOGIES TO BE USED • HTML • JSP • Javascript • Java 1.6 TOOLS TO BE USED • Eclipse IDE (Integrated Development Environment) • Rational Rose tool (for developing UML Patterns) 1.7 OVERVIEW SRS includes two sections overall description and specific requirements – Overall Description will describe major role of the system components and inter- connections. Specific Requirements will describe roles & functions of the actors.
- 3. 2.0 OVERALL DESCRIPTION 2.1 PRODUCT PERSPECTIVE The U-Mobile application helps user to transfer money and recharge mobile and get to know bank details. THE SOFTWARE INTERFACE Front End Client - The exporter online interface is built using JSP and HTML. Web Server – Apache Tomcat Server (Oracle Corporation) Back End - Oracle 11g database 2.2 HARDWARE INTERFACE The BPO system’s server is directly connected to the client systems via ftp. The client systems have access to the database in the server. 2.3 SYSTEM FUNCTIONS In this application the customer can login. It can transfer the money that are taking place with every bank and recharge their mobiles. .User can order the food and beverages at the time of booking ticket Comprehensive reports have been developed to track the status of the documents at any given point of time.The customer can cancel the transaction before the money will debited to other account. This online source provides so many options for money transactions. 2.4 USER CHARACTERISTICS • Customer- The customer can transfer the money and recharge their mobiles,cancel the transactions and recharges.The payment was in various options. • Admin - He has the certain activities such as add,delete,update the information
- 4. about the transaction and bank activities 2.5 CONSTRAINTS • This application need internet to use. • The refund money will be credited into customers account after 3 to 4 working days. 2.6 ASSUMPTIONS AND DEPENDENCIES • To transfer the money and for the mobile recharge the bank account for the customer is needed. ( III )USECASE DIAGRAM: The u-mobile use cases are: 1. login 2. Transactions 3. Mobile recharge 4. Update information 5. logout ACTORS: Actors are as follows: 1. User 2. Admin 3. System ACTORS DOCUMENTATION: 1. User: login transaction Mobile recharge logout 2. Admin: Update information
- 5. 3. System: Transaction Mobile recharge Update information USE-CASE NAME: cancel mobile recharge The customer can recharge their mobile with better and special offers which are given to their phone number. Recharge cancellation can be done by the customer.after then update information will be stored in the system. USE-CASE NAME: transaction The customer can transfer the money in various account types which are saving account and current account.if the transaction is cancel the money will not be debited.if the transaction is cancel by any technical issue the money will credited in our accounts in 3 to 4 working days.after then update information will be stored in the system. USE-CASE NAME: update information The admin will update the information in the application which was useful to customers whenever the update the online source version,add accounts,delete accounts and the updated information will stored in the system. USE-CASE NAME: Transaction Use case diagrams are usually referred to as behavior diagrams used to describe a set of actions (use cases) that some system or systems (subject) should or can perform in collaboration with one or more external users of the system (actors). Each use case should provide some observable and valuable result to the actors or other stakeholders of the system.
- 6. ACTIVITY DIAGRAM: Activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams can be used to describe the business and operational step-by- step workflows of components in a system. An activity diagram shows the overall flow of control. An activity is shown as an rounded box containing the name of the operation.This activity diagram describes the behavior of the system. Activity of User for Transaction:
- 8. Activity Diagram of mobile recharge:
- 9. Activity Diagram of Admin:
- 10. UML CLASS DIAGRAM: The UML class diagram is to illustrate class interfaces and their actions. They are used for static object modeling, we have already introduced and used their UML diagram while domain modeling.
- 11. UML SEQUENCE DIAGRAM: A sequence diagram illustrates a kind of format in which each object interacts via message. It is generalize between two or more specialized diagram. Sequence Diagram of user for transactions:
- 12. Sequence Diagram of user for mobile recharge: Sequence Diagram of user for admin:
- 13. Communication Diagram: Communication diagram illustrate that object interact on a graph or network format in which object can be placed where on the diagram. In collaboration diagram the object can be placed in anywhere on the diagram. The collaboration comes from sequence diagram. Collaboration Diagram of user for transactions: Collaboration Diagram of user for mobile recharge:
- 14. Collaboration Diagram of user for admin: STATE DIAGRAM: State chart diagram is one of the five UML diagrams used to model the dynamic nature of a system. They define different states of an object during its lifetime and these states are changed by events. State chart diagrams are useful to model the reactive systems. Reactive systems can be defined as a system that responds to external or internal events.
- 15. COMPONENT DIAGRAM: Component diagram is a special kind of diagram in UML. It does not describe the functionality of the system but it describes the components used to make those functionalities. component diagrams are used to visualize the physical components in a system, and also be described as a static implementation view of a system. Static implementation represents the organization of the components at a particular moment.
- 16. DEPLOYMENT DIAGRAM: Deployment diagrams are used to visualize the topology of the physical components of a system where the software components are deployed. .