Mobile Service Enqiry System UML Diagram

Posted By freeproject on March 22, 2018

Mobile Service Enqiry System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Mobile Service Enqiry System which shows the flows between the activity of Models, Warranty, Mobile, Customer, Problem. The main activity involved in this UML Activity Diagram of Mobile Service Enqiry System are as follows:

  • Models Activity
  • Warranty Activity
  • Mobile Activity
  • Customer Activity
  • Problem Activity

Features of the Activity UML diagram of Mobile Service Enqiry System

  • Admin User can search Models, view description of a selected Models, add Models, update Models and delete Models.
  • Its shows the activity flow of editing, adding and updating of Warranty
  • User will be able to search and generate report of Mobile, Customer, Problem
  • All objects such as ( Models, Warranty, Problem) are interlinked
  • Its shows the full description and flow of Models, Customer, Problem, Mobile, Warranty
Mobile Service Enqiry System Activity Diagram

Mobile Service Enquiry System Class Diagram

Posted By freeproject on August 2, 2017

Mobile Service Enqiry System Class Diagram describes the structure of a Mobile Service Enqiry System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Mobile Service Enqiry System are Mobile, Customer, Problems, Payments, Models, Service.

Classes of Mobile Service Enqiry System Class Diagram:

  • Mobile Class : Manage all the operations of Mobile
  • Customer Class : Manage all the operations of Customer
  • Problems Class : Manage all the operations of Problems
  • Payments Class : Manage all the operations of Payments
  • Models Class : Manage all the operations of Models
  • Service Class : Manage all the operations of Service

Classes and their attributes of Mobile Service Enqiry System Class Diagram:

  • Mobile Attributes : mobile_id, mobile_company_id, mobile_model_id, mobile_name, mobile_type, mobile_description
  • Customer Attributes : customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Problems Attributes : problem_id, problem_mobile_id, problem_name, problem_type, problem_description
  • Payments Attributes : payment_id, payment_customer_id, payment_date, payment_amount, payment_description
  • Models Attributes : model_id, model_name, model_number, model_year, model_type, model_description
  • Service Attributes : service_id, service_name, service_type, service_branch, service_description

Classes and their methods of Mobile Service Enqiry System Class Diagram:

  • Mobile Methods : addMobile(), editMobile(), deleteMobile(), updateMobile(), saveMobile(), searchMobile()
  • Customer Methods : addCustomer(), editCustomer(), deleteCustomer(), updateCustomer(), saveCustomer(), searchCustomer()
  • Problems Methods : addProblems(), editProblems(), deleteProblems(), updateProblems(), saveProblems(), searchProblems()
  • Payments Methods : addPayments(), editPayments(), deletePayments(), updatePayments(), savePayments(), searchPayments()
  • Models Methods : addModels(), editModels(), deleteModels(), updateModels(), saveModels(), searchModels()
  • Service Methods : addService(), editService(), deleteService(), updateService(), saveService(), searchService()

Class Diagram of Mobile Service Enqiry System :

Class Diagram Image: 
Mobile Service Enquiry System Class Diagram

Mobile Service Enqiry System Component Diagram

Posted By freeproject on February 8, 2018

This is a Component diagram of Mobile Service Enqiry System which shows components, provided and required interfaces, ports, and relationships between the Mobile, Customer, Warranty, Problem and Models. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Mobile Service Enqiry System UML component diagram, describes the organization and wiring of the physical components in a system.

Components of UML Component Diagram of Mobile Service Enqiry System:

  • Mobile Component
  • Customer Component
  • Warranty Component
  • Problem Component
  • Models Component

Featues of Mobile Service Enqiry System Component Diagram:

  • You can show the models the components of Mobile Service Enqiry System.
  • Model the database schema of Mobile Service Enqiry System
  • Model the executables of an application of Mobile Service Enqiry System
  • Model the system's source code of Mobile Service Enqiry System
Component Diagram: 

Mobile Phone Billing System Dataflow Diagram

Posted By namita on July 7, 2017

Mobile Phone Billing System Data flow diagram is often used as a preliminary step to create an overview of the Mobile without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Mobile process. It contains all of the userflow and their entities such all the flow of Bills, Customers, Connections, Tarrifs, Connection Types, Payments, Login. All of the below diagrams has been used for the visualization of data processing and structured design of the Mobile process and working flow.


Zero Level Data flow Diagram(0 Level DFD) of Mobile Phone Billing System :

This is the Zero Level DFD of Mobile Phone Billing System, where we have eloborated the high level process of Mobile. It’s a basic overview of the whole Mobile Phone Billing System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Connection Types,Payments and Login showing the system as a single high-level process, with its relationship to external entities of Bills,Customers and Connections. It should be easily understood by a wide audience, including Bills,Connections and Connection Types In zero leve DFD of Mobile Phone Billing System, we have described the high level flow of the Mobile system.

High Level Entities and proccess flow of Mobile Phone Billing System:

  • Managing all the Bills
  • Managing all the Customers
  • Managing all the Connections
  • Managing all the Tarrifs
  • Managing all the Connection Types
  • Managing all the Payments
  • Managing all the Login
Zero Level Data flow Diagram(0 Level DFD) of Mobile Phone Billing System

First Level Data flow Diagram(1st Level DFD) of Mobile Phone Billing System :

First Level DFD (1st Level) of Mobile Phone Billing System shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the Mobile Phone Billing System system as a whole. It also identifies internal data stores of Login, Payments, Connection Types, Tarrifs, Connections that must be present in order for the Mobile system to do its job, and shows the flow of data between the various parts of Bills, Connections, Payments, Login, Connection Types of the system. DFD Level 1 provides a more detailed breakout of pieces of the 1st level DFD. You will highlight the main functionalities of Mobile.

Main entities and output of First Level DFD (1st Level DFD):

  • Processing Bills records and generate report of all Bills
  • Processing Customers records and generate report of all Customers
  • Processing Connections records and generate report of all Connections
  • Processing Tarrifs records and generate report of all Tarrifs
  • Processing Connection Types records and generate report of all Connection Types
  • Processing Payments records and generate report of all Payments
  • Processing Login records and generate report of all Login
First Level Data flow Diagram(1st Level DFD) of Mobile Phone Billing System

Second Level Data flow Diagram(2nd Level DFD) of Mobile Phone Billing System :

DFD Level 2 then goes one step deeper into parts of Level 1 of Mobile. It may require more functionalities of Mobile to reach the necessary level of detail about the Mobile functioning. First Level DFD (1st Level) of Mobile Phone Billing System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Login, Payments, Connection Types, Tarrifs, Connections, Customers, Bills.

Low level functionalities of Mobile Phone Billing System

  • Admin logins to the system and manage all the functionalities of Mobile Phone Billing System
  • Admin can add, edit, delete and view the records of Bills, Connections, Connection Types, Login
  • Admin can manage all the details of Customers, Tarrifs, Payments
  • Admin can also generate reports of Bills, Customers, Connections, Tarrifs, Connection Types, Payments
  • Admin can search the details of Customers, Connection Types, Payments
  • Admin can apply different level of filters on report of Bills, Tarrifs, Connection Types
  • Admin can tracks the detailed information of Customers, Connections, Tarrifs, , Connection Types
Second Level Data flow Diagram(2nd Level DFD) of Mobile Phone Billing System

Mobile Phone Billing System ER Diagram

Posted By freeproject on July 17, 2017

This ER (Entity Relationship) Diagram represents the model of Mobile Phone Billing System Entity. The entity-relationship diagram of Mobile Phone Billing System shows all the visual instrument of database tables and the relations between Customers, Tarrifs, Bills, Payments etc. It used structure data and to define the relationships between structured data groups of Mobile Phone Billing System functionalities. The main entities of the Mobile Phone Billing System are Bills, Customers, Connections, Tarrifs, Connection Types and Payments.

Mobile Phone Billing System entities and their attributes :

  • Bills Entity : Attributes of Bills are bill_id, bill_customer_id, bill_number, bill_type, bill_receipt, bill_description
  • Customers Entity : Attributes of Customers are customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Connections Entity : Attributes of Connections are connection_id, onnection_customer_id, onnection_name, onnection_type, onnection_description
  • Tarrifs Entity : Attributes of Tarrifs are tarrif_id, tarrif_name, tarrif_type, tarrif_description
  • Connection Types Entity : Attributes of Connection Types are cnnectio_type_id, cnnectio_type_name, cnnectio_type_description
  • Payments Entity : Attributes of Payments are payment_id, payment_customer_id, payment_date, payment_amount, payment_description

Description of Mobile Phone Billing System Database :

  • The details of Bills is store into the Bills tables respective with all tables
  • Each entity (Payments, Connections, Connection Types, Customers, Bills) contains primary key and unique keys.
  • The entity Connections, Connection Types has binded with Bills, Customers entities with foreign key
  • There is one-to-one and one-to-many relationships available between Connection Types, Tarrifs, Payments, Bills
  • All the entities Bills, Connection Types, Connections, Payments are normalized and reduce duplicacy of records
  • We have implemented indexing on each tables of Mobile Phone Billing System tables for fast query execution.
Mobile Phone Billing System ER Diagram

Mobile Phone Billing System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Mobile Phone Billing System which shows the interaction between the objects of Connection, Payments, Bill, Tarrif, Customer. The instance of class objects involved in this UML Sequence Diagram of Mobile Phone Billing System are as follows:

  • Connection Object
  • Payments Object
  • Bill Object
  • Tarrif Object
  • Customer Object

This is the UML sequence diagram of Mobile Phone Billing System which shows the interaction between the objects of Connection, Payments, Bill, Tarrif, Customer. The instance of class objects involved in this UML Sequence Diagram of Mobile Phone Billing System are as follows:

  • Connection Object
  • Payments Object
  • Bill Object
  • Tarrif Object
  • Customer Object

Mobile Phone Billing System Use Case Diagram

Posted By freeproject on July 24, 2017

This Use Case Diagram is a graphic depiction of the interactions among the elements of Mobile Phone Billing System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Mobile Phone Billing System. The main actors of Mobile Phone Billing System in this Use Case Diagram are: Super Admin, System User, Shopkeeper, Customers, who perform the different type of use cases such as Manage Bills, Manage Customers, Manage Connections, Manage Tarrifs, Manage Connection Types, Manage Payments, Manage Users and Full Mobile Phone Billing System Operations. Major elements of the UML use case diagram of Mobile Phone Billing System are shown on the picture below.

The relationships between and among the actors and the use cases of Mobile Phone Billing System:

  • Super Admin Entity : Use cases of Super Admin are Manage Bills, Manage Customers, Manage Connections, Manage Tarrifs, Manage Connection Types, Manage Payments, Manage Users and Full Mobile Phone Billing System Operations
  • System User Entity : Use cases of System User are Manage Bills, Manage Customers, Manage Connections, Manage Tarrifs, Manage Connection Types, Manage Payments
  • Shopkeeper Entity : Use cases of Shopkeeper are Create Invoice, Manage Mobiles, Manage Customers, Create Bills, Collect Payments
  • Customers Entity : Use cases of Customers are Search Mobile, Add to Cart, Make Payment, View Mobile Features

Use Case Diagram of Mobile Phone Billing System :

Mobile Phone Billing System Use Case Diagram

Project Category