Shabnum Asim - Money Monitor System

Money Monitor System
APRIL 4, 2018
MONEY MONITOR SYSTEM

SOFTWARE DESIGN DOCUMENT
VERSION: 1.0
ROLL NO 162107 SHABNUM ASIM

SESSION: 2016-2018
Department of Computer Science/Khawaja Farid Govt P/G College Rahim Yar Khan
Revision History
Date Description Author Comments
04/04/2018 <Version 1.0> ShabnumAsim First submission on turn it
Document Approval
The following Software Requirements Specification has been accepted and approved by the following:
Signature Printed Name Title Date

Sir UsmanGhani Supervisor, CSIT 21306 04/04/2018
i
Table of Contents
1. INTRODUCTION ..................................................................................................................................................... 1
1.1 Purpose ...................................................................................................................................................................1
1.2 Scope ......................................................................................................................................................................1
1.3 Overview ................................................................................................................................................................ 1
1.4 Reference Material ................................................................................................................................................. 1
1.5 Definitions and Acronyms ......................................................................................................................................1
2. SYSTEM OVERVIEW .............................................................................................................................................1
2.1 General constraints………………………………………………………………………………………………2
2.2 System environment…………………………………………………………………………………………………………..…………2
2.3 Technology used…….………………………………………………………………………………………………………..…………….2
2.4 Design languages………….………………………………………………………………………………………………………………..2

3. SYSTEM ARCHITECTURE .................................................................................................................................... 2
3.1 Architectural Design ............................................................................................................................................... 2
3.1.1 Web Architecture..……………………………………………………………………………………………………………………….3
3.1.2 Block diagram……………………………………………………………………………………………………………………………….4

3.2 Decomposition Description ....................................................................................................................................5
3.2.1 Class Diagram…………………………………………………………………………………………………………………………………5
3.2.1.1 Class Diagram for Account……………………………………………………………………………………………………………5
3.2.1.2 Class Diagram for Transaction………………………………………………………………………………………………………6
3.2.1.3 Class Diagram for Summery…………………………………………………………………………………………………………7
3.2.1.4 Class Diagram for Ledger……………………………………………………………………………………………………………..8
3.2.1.5 Over all class Diagram………………………………………………………………………………………………………………….9
3.2.2 Use case Diagram………………………………………………………………………………………………………………………….10
3.2.2.1 Create Account…………………………………………………………………………………………………………………………..11
3.2.2.2 Delete Account………………………………………………………………………………………………………………………….12
3.2.2.3 Modify Account…………………………………………………………………………………………………………………………13
3.2.2.4 Create category………………………………………………………………………………………………………………………..14
3.2.2.5 Delete Category………………………………………………………………………………………………………………………..15
3.2.2.6 Modify Category……………………………………………………………………………………………………………………….16
ii
3.2.2.7 Add expense Transaction………………………………………………………………………………………………………….17
3.2.2.8 Add income Transaction……………………………………………………………………………………………………………18
3.2.2.9 Transfer Transaction………………………………………………………………………………………………………………….19
3.2.2.10 Modify Transaction………………………………………………………………………………………………………………….20
3.2.2.11 Delete Transaction………………………………………………………………………………………………………………….21
3.2.2.12 Transaction Summery……………………………………………………………………………………………………………..22
3.2.2.13 Show Ledger…………………………………………………………………………………………………………………………..23
3.2.2.14 Save Date to Cloud…………………………………………………………………………………………………………………24
3.2.3 Sequence Diagram………………………………………………………………………………………………………………………25
3.2.3.1 Sequence diagram for Login……………………………………………………………………………………………………..25
3.2.3.2 Sequence Diagram for Category………………………………………………………………………………………………26
3.2.3.3 Sequence Diagram for Summery……………………………………………………………………………………………..27
3.2.3.4 Sequence Diagram for Transaction………………………………………………………………………………………….28
3.2.4 State-Transition Diagram…………………………………………………………………………………………………………….29
3.2.4.1 State-Transition Diagram for Account……………………………………………………………………………………….29
3.2.4.2 State-Transition Diagram for Transaction…………………………………………………………………………………30
3.2.5 Activity Diagram…………………………………………………………………………………………………………………………..31
3.2.5.1 Activity Diagram for Login………………………………………………………………………………………………………….31
3.2.5.2 Activity Diagram for Transaction………………………………………………………………………………………………..32
3.2.5.3 Activity Diagram for Summery……………………………………………………………………………………………………33

3.3 Design Rationale…………………………………………………………………………………………………33
4. DATA DESIGN……………………………………………………………………………………………………34
4.1 Data Description…………………………………………………………………………………………………34
4.2 Data Dictionary………………………………………………………………………………………………….36
4.3 Relational and complete Data Design…………………………………………………………………………………………….40
5. COMPONENT DESIGN…………………………………………………………………………………………..41
6. HUMAN INTERFACE DESIGN………………………………………………………………………………….47
6.1 Overview of User Interface………………………………………………………………………………………47
6.2 Screen Images……………………………………………………………………………………………………47
6.2.1 Login……………………………………………………………………………………………………………47
6.2.2 Account Creation……………………………………………………………………………………………….48
iii
6.2.3 Create Category…………………………………………………………………………………………………48

6.2.4 Transaction……………………………………………………………………………………………………..49
6.2.5 Reset Password…………………………………………………………………………………………………49
6.2.6 Show Summery…………………………………………………………………………………………………50
6.2.7 Ledger Screen…………………………………………………………………………………………………..50
6.2.8 Current Balance…………………………………………………………………………………………………51
6.2.9 Save Date……………………………………………………………………………………………………….51
7. REQUIREMENTS MATRIX……………………………………………………………………………………..52
iv
1. INTRODUCTION
1.1 Purpose
The basic purpose of this Software Design Document (SDD) is to design all main components and
its sub components ofMoney Monitor System (MMS). That is a personal finance management
application.It also explains the personal features of the application with interface details and
design constraints. This SDD describes the design of Money MonitorSystem (MMS) along with
interface details, design constraints and related considerations such as performance characteristics. The
intended users of this Software Design Document are software developer, software designer and
the end users.
1.2 Scope
This Money Monitor System (MMS) maintains the personal accounts. It can also be track and
organize over all accounts, cash flow, transactions, general flow, cleared and un-cleared
transaction in an easy way. It also provides a way for money comes and goes by controlling all
the expenses and income of the users. .
1.3 Overview
First section contain introduction of the project, second section of SDD contain system overview, in
this section describe overall system in high level definition. Third section contains system
architecture of the project; main components and its sub components are define in section three. Four
sections contain data design in this section design the system using Entity Relationship Diagram and
Data Flow Diagram etc. Section five contains component design, in which different comments are
design. Section six of the SDD contains Human Interface Design and Last section contains the
Requirements Matrix.
1.4 Reference Material

[1] ANSI/IEEESTD 100-1977, IEEE Standard Dictionary of Electrical and Electronics Terms.
[2] ANSI/IEEE STD 730-1981, IEEE Standard for Software Quality Assurance Plans.
1.5 Definitions and Acronyms

SDD Software Design Document
MMS Money Monitor System
DB Data Base
ET Expense Transaction
CT Create Transaction
EU End Users
ER Entity Relationship
SDD Document 1.0 Page 1 04/09/18 f

2. SYSTEM OVERVIEW
The Money Monitor System (MMS) provides many facilities to their users. It is an easier way to
perform many operations for the required functionality. It takes less time and provide an
environment in which user perform required operations with satisfaction.
2.1 General constraints

There are basically three important general constraints: First is, the system must be delivered on
the specific period of time. Second is, the system must be user friendly. And the third is, the end
users should have at least android 4.0 (kit Kat) or any other higher.
2.2 System environment
The Software Design Document (SDD) is designed to work on all operating systems that can
support a current media enabled web browser.
2.3 Technologies Used
Different technologies are used in Money Monitor System (MMS), like HTML, CSS, PHP, MYSQL
are used. HTML and CSS are used to make the front-end of the site and MYSQL database and PHP
are used for back-end. My SQL database is used to save the records of users, accounts and all
transactions. PHP is used for communication between user and system.
2.4 Design Languages
Unified Modeling Language (UML) 5.02 is used for graphical representations of viewpoints in
MOBCOLL Project in 3.System Architecture, 4.Data Design and 5.Component Design parts. The
MOBCOLL Android Application will be developed as a single Android Client.
3. SYSTEM ARCHITECTURE
3.1 Architectural Design
Money Monitor System (MMS) contains different modules. These modules are combined to
provide services to user. MMS includes various modules such as Account, Category,
Transaction, ledger and Summery. Account module holds user money and provides facilities
such as create, delete and modify account. Category module describe purpose for which
expense/income occurs and provide many facilities to their user such as create, delete and
modify category.Transaction module allowed their to perform transaction in various form sch as
add expense and income transaction, transfer,modify and delete transaction. Ledger module
provide collection of entire group of an account or category. Summery module show the
summary of all transaction, occurred during a specified time period. All these modules are
combined to achieve entire functionality of MMS.

3.1.1 Web Architecture

Internet, Web Application, Web Server and Database are used in Money Monitor System’s
website. Desktop computer or Laptop is connected with internet using TCP/IP. Using Web
Application communication with Web Server, Web Server further communicate with Database
to save data into database or get data from database.
Internet
Web Application
Web Server
Database

3.1.2Block Diagram
User User User User User
Registration Login Account Category Transaction
Summery Money Monitor System Ledger
Web Server
MySQL

3.2 Decomposition Description

3.2.1 Class Diagram
3.2.1.1Class Diagram for Account
User Account
-U-Name:string -name:string
-User-Type:char -phoneNumber:int
-U-Address:string -address:string
+registration():bool()() +setName(str:string)()
+logIn():bool()() +getName()string()
+view Account()() +setNumber(uum:int)()
+view Report()() +getNumber()int()
+setAddress(str:string)()
+getAddress()string()
Category
-categoryName;string
-accountNumber:int
-passward:string
+setcategoryName(str:string)()
+getcaregoryName()string()
+setaccountNumber(num:int)()
+getaccountNumber()int()
+setPassward(str:string)()
+getPassward()string()

3.2.1.2 Class Diagram for Transaction
User
-U-Name:string
-User-Type:char
-U-Address:string
+registration():bool()()
+logIn():bool()()
+view Account()()
+view Report()() Transaction
-categoryName:string
-accountNumber:int
-password:string
+getcategoryName()string()
+setPassword(str:string)()
+getPassword()string()
LogIn
-emailId:string
-password:string
+setEmailId(email:string)()
+getEmailId()
+setPassword(PSW:string)()
+getPassword()()

3.2.1.3 Class Diagram for Summery
User
-U-Name:string LogIn
-User-Type:char
-emailId:string
-U-Address:string
-password:string
+registration():bool()()
+logIn():bool()()
+getEmailId()
+view Account()()
+setPassword(PSW:string)()
+view Report()()
+getPassword()()
Summery
Transaction
-accountNumber:int
-password:string -categoryName:string
-categoryName:string -accountNumber:int
-address:string -password:string
+setaccountNumber(num:int)() +setcategoryName(str:string)()
+getaccountNumber()int() +getcategoryName()string()
+setPassword(str:string)() +setaccountNumber(num:int)()
+getPassword()string() +getaccountNumber()int()
+setcatagoryName(str:string)() +setPassword(str:string)()
+getcategoryName()string() +getPassword()string()
+setAddress(str:string0()

3.2.1.4 Class Diagram for Ledger
User LogIn
-U-Name:string -emailId:string
-User-Type:char -password:string
-U-Address:string
+registration():bool()() +getEmailId()
+logIn():bool()() +setPassword(PSW:string)()
+view Account()() +getPassword()()
+view Report()()
Ledger
Account
-categoryName:stringe
-accountNumber:int -name:string
-password:string -phoneNumber:int
-address:string
+setcatagoryName(str:string)()()
+getcategoryName()string()() +setName(str:string)()
+setaccountNumber(num:int)()() +getName()string()
+getaccountNumber()int()() +setNumber(uum:int)()
+setPassword(str:string)()() +getNumber()int()
+getPassword()string()() +setAddress(str:string)()

3.2.1.5 over all Class Diagram
User LogIn
-U-Name:string -emailId:string
-User-Type:char -password:string
-U-Address:string +setEmailId(email:string)()
+registration():bool()() +getEmailId()
+logIn():bool()() +setPassword(PSW:string)()
+view Account()() +getPassword()()
+view Report()()
Summery
Ledger Account
-accountNumber:int
-password:string -name:string
-categoryName:stringe
-categoryName:string -phoneNumber:int
-accountNumber:int
-address:string -address:string
-password:string
+setaccountNumber(num:int)() +setName(str:string)()
+setcatagoryName(str:string)()()
+getaccountNumber()int() +getName()string()
+getcategoryName()string()()
+setPassword(str:string)() +setNumber(uum:int)()
+setaccountNumber(num:int)()()
+getPassword()string() +getNumber()int()
+getaccountNumber()int()()
+setcatagoryName(str:string)() +setAddress(str:string)()
+setPassword(str:string)()()
+getcategoryName()string() +getAddress()string()
+getPassword()string()()
+setAddress(str:string0()
1 Category
-categoryName;string
-accountNumber:int
-passward:string
+getcaregoryName()string()
Transaction 1 +getaccountNumber()int()
+setPassward(str:string)()
-categoryName:string +getPassward()string()
-accountNumber:int
-password:string
+getcategoryName()string()
+setPassword(str:string)()
+getPassword()string()

3.2.2 Use Case Diagram
Use case list

1. Create Account
2. Delete Account
3. Modify Account
4. Create Category
5. Delete Category
6. Modify Category
7. Add Expense Transaction
8. Add Income Transaction
9. Add Transfer Transaction
10. Modify Transaction
11. Delete Transaction
12. Transaction Summery
13. Show Ledger
14. Save Date to cloud

3.2.2.1: Create account
Sy ste m
A ccount
User User
Cre a te a ccount
Actor User
Pre-condition Money Monitor System site should be open.
Post-condition User wants to create account.
Description User enters her/his detail.
User action 1: User open MMS application site.

3: User select create account option.
5: User fill up user name, contact number, address, set password
and submit form.
System response 2: Display home page of site.

4: Display creates account form.
6: Display message that you are successfully create account
otherwise display an error message.

3.2.2.2: Delete account
Sy stem
A ccount
User User
D e le t e a c c o u n t
Actor User
Pre-condition Money Monitor application site should be open.
Post- condition User wants to delete an account.
Description User enters her/his detail for delete account.
Actor action 1: User open MM application site.

3: User select delete account option.
5: User fill up user name, contact number, address, set
password and submit form.

4: Display deletes account form.
6: Display message that your account successfully deleted or
display an error message.

3.2.2..3: Modify account
Sy ste m
A ccount
User User
M o d if y a c c o u n t s
Actor User
Post- condition User wants to modify an account.
Description User enters details for sign up.
Actor action 1: User open MM application site.

3: User select modify account option.
System response 2: Display home page of sits.

4: Display modifies account form.
6: display message that your account successfully modified

3.2.2.4: Create category
Sy stem
Ca te g o ry
User
Use r
Cre a te ca te g o ry
Actor User
Post-condition User wants to create category.
Description User enter her/his detail for create category.
User action 1: User open MM application site.

3: User select create category option.

4: Display creates category form.
6: Display message that you are successfully create category

3.2.2.5: Delete category
Sy s t e m
Ca t e g o r y
User
User
D e le t e c a t e g o r y
Actor User
Post-condition User wants to delete category.
Description User enters her/his detail for delete category.

3: User select delete category option.

4: Display deletes category form.
6: Display message that you are successfully delete category

3.2.2.6: Modify category
System
Category
User User
Modify category
Actor User
Post-condition User wants to modify category.
Description User enters her/his detail for modify category.

3: User select modify category option.

4: Display modifies category form.
6: Display message that you are successfully modify category

3.2.2.7: Add expense transaction
System
Transaction
User User
Add expense transaction
Actor User
Post-condition User wants to add expense transaction.
Description User enters her/his detail for add expense transaction.

3: User select add expense transaction option.

4: Display adds expense transaction form.
6: Display message that you are successfully add expense
transaction otherwise display an error message.

3.2.2.8: Add income transaction
System
Transaction
User User
Add income transacton
Actor User
Post-condition User wants to add income transaction.
Description User enters her/his detail for add income transaction.

3: User select add income transaction option.

4: Display adds income transaction form.
6: Display message that you are successfully add income

3.2.2.9: Transfer transaction
Sy ste m
T r a n s a c t io n
User
User
T r a n s fa r t r a n s a c t io n
Actor User
Post-condition User wants to transfer transaction.
Description User enters her/his detail for transfer transaction.

3: User select transfer transaction option.

4: Display transfer transaction form.
6: Display message that you are successfully transfer

3.2.2.10: Modify transaction
Sy ste m
T r a n s a c t io n
Use r
User
M o d ify t r a s a c t io n
Actor User
Post-condition User wants to modify transaction.
Description User enters her/his detail for modify transaction.

3: User select modify transaction option.

4: Display modifies transaction form.
6: Display message that you are successfully modify transaction

3.2.2.11: Delete transaction
System
Transaction
User User
Delete transaction
Actor User
Post-condition User wants to delete transaction.
Description User enters her/his detail for delete transaction.

3: User select delete transaction option.

4: Display deletes transaction form.
6: Display message that you are successfully delete transaction

3.2.2.12: Transaction summary
System
Transaction
User
User
Transaction summary
Actor User
Post-condition User wants to saw all transaction summaries.
Description User enters her/his detail for saw transaction summary.

3: User select saw transaction summary option.

4: Display saw transaction summary form.
6: Display transaction summary of all accounts, otherwise
display an error message.

3.2.2.13: Show ledger
System
Show ledger
User User
Actor User
Post-condition User wants to saw the ledger report of selected account.
Description User enters her/his detail for saw the ledger report.

3: User select saw ledger report of account option.

4: Display saw ledger report of account form.
6: Display ledger report of account, otherwise display an error
message.

3.2.2.14: Save data to cloud
System
save data to cloude
User
User
Actor User
Post-condition User wants to save data of account.
Description User enters her/his detail for save data.

3: User select save data of account option.

4: Display saves data of account form.
6: Display save data of account, otherwise display an error
message.

3.2.3: Sequence Diagram
3.2.3.1: Sequence diagram for Login
User Login credentional
2 : Login()
4 : Verify for login details()
7 : enter correct details()
11 : successfully login()

3.2.3.2: Sequence diagram for category
Acc0unt Category
1 : Create category()
2 : get account details()
3 : Valid account details()
4 : Successfully create category()

3.2.3.3: Sequence diagram for Summery
User Summery
1 : wants to see transaction summery()
2 : verify transaction details()
3 : provide valid transaction details()
4 : show all transaction summery()

3.2.3.4: Sequence diagram for Transaction
User Transaction
1 : Wants money transfar()
2 : Verify user details()
3 : Please inter valid details()
4 : Show successfully transaction()

3.2.4 State – Transition Diagram
3.2.4.1 State – Transition Diagram for Account
Make Account Creation

do/Reationquest for Account creation Valid
entry/Create Account
do/Check user details
exit/Valid or Invalid details
Wants to leave
Account functions
Verifaction
do/Modify Account
do/Check user details exit/Modifaction
exit/All actions done

3.2.4.2 State – Transition Diagram for Transaction
Make Transaction
Show valid details System
do/Transaction
do/Verify Account details entry/Show Transaction
exit/Valid/invalid details
User wants to leave
Transaction functions
Verifaction
do/Expense Transaction
do/Check Account/Category details do/Income Transaction
exit/All functions complete do/Cleared/Uncleared Transaction
exit/Show all functionality

3.2.5 Activity Diagram

3.2.5.1 Activity diagram for Login
Enter Login Detail
Verification
No Invalid information
Yes
Successfully Login
Display desired information

3.2.5.2 Activity diagram for Transaction
Enter Account information
Verification
No Incorrect information
Yes
Enter ammount
Perform Transaction

3.2.5.3 Activity diagram for Summery
Enter all Transaction information
Verification
No Incorrect information
Show Transaction Summery
3.3 Design Rationale

We use MySQL Database in Money Monitor System because it will give accurate and fast result and its
open ended software. For server site language we use PHP because it is easy and also open ended.

4. DATA DESIGN
4.1 Data Description
MySQL is used to all the information of money Monitor System (MMS).PHP is used to manipulate the
information such as get information from the Database and also put information into Database. Local
web Server also used with PHP script.
Data Objects
User:
Id: To uniquely identify each user in database. It is unique for each user.
Name: Indicate the name of user.
Age: Indicate the age of user.
Address: Show the present address of user.
E-mail: E-mail of user used to interact with system.
Phone Number: Phone number is used for communication with user.
CNIC: Indicate the national identification number of user.
Admin:
Id: id of the Admin to uniquely identify any user of the site.
Name: Name of Admin.
Password: Password of Admin used for Login.
Age: Indicate the age of Admin.

Address: Show the present address of Admin.
CNIC: Indicate the national identification number of Admin.
User Name: user name of admin for log in.
Transaction:
Name: Indicate the name of user.
Age: Indicate the age of user.
Address: Show the present address of user.
E-mail: E-mail of user used for transaction.

CNIC: Indicate the national identification number of user.
Account:
Number: Indicate the number of Account.
Name: Indicate the name of category for Account.
Password: Password of Account used for transaction.
Document:
Name:Name of Document.
Type:Type of Document like word files, PDF files etc.
Size: Size of Document.
Category:
Name: Indicate the name of category for which transaction is performed.
Date: Specify the date for transaction.
Number: Indicate the number of category.
Comments:
Id: Id of user.
Username:User name of user for Login.
Document:Name of Document.

4.2 Data Dictionary
User: Parameter types:

Id: Int
Name: String
Address: String
E-mail: String
Phone Number: Int
CNIC: String
Admin: Parameter types:

Id: Int
Name: String
Address: String
CNIC: String
Password: Char
Age: Int
User Name String

Transaction: Parameter types:

Name: String
Address: String
CNIC: String
Age: Int
E-mail String
Account: Parameter types:

Number: Int
Name: String
Password: Char

Document: Parameter types:

Name: String
Type: Word or PDF or power point
Size: Bytes
Category: Parameter types:

Name: String
Date: Int
Number: Int

Comments: Parameter types:

Id: Int
User Name: String
Document: Word or PDF or power point

4.3 Relational and complete data model
Password
Name Address
Administrator
Password
Enters
Account NO
Account
Ads Name
Contact NO
Addres Handles Category NO
s
User Category
Email
Category Name
Maintains
Has Income
Transfer
Transaction
Section Expense
name
Sections
ReportM
Manages
Section NO onthly
Annual
Report report

5. COMPONENT DESIGN
Account
Class Name Account
Brief Description Account holds the user money. It also performs different
operations like creation, deletion and modification of
account.
Attributes(fields) Attributes Description
Name This attribute is used to store the name of user for account.
Phone Number This attribute is used to store the phone number of user for
account.
Address This attribute is used to store the address of the user.
Methods(operations) Methods Description
registration() A method which is used to perform registration when user
wants to register with the site.
Pseudo Code
1: Display registration form
2:when user fill this from check all the fields are filled or
not
3:Store user information in database
4: Display message to the user “Successfully Register”.
login() A method used to perform login when user wants to login

with the site.
Pseudo Code
1: Display login form.

2: Check Username and password are filled or not.
3: Match information with the password and user name
4: Display message” Login” or “Not Login”.

Account Creation() Pseudo Code
Add user details(name, address, phone no)

{
Stringname;
String address;
Int phone no;
}
1. Validation is performed.
2. Database connection is created.
3. Display Account is created successfully or not.
Transaction
Class Name Transaction
Brief Description Transaction transfers the user money from their account. It also
adds the expense and income transaction and also performs
transfer, modify and delete transaction.
Attributes(fields) Attributes Description
Name This attribute is used to store the name of Category for Transaction.
Number This attribute is used to store the Number of Account for

Transaction.
Password This attribute is used to store the password of user for transaction.
Methods(operations) Methods Description

A method that is used to perform registration when user wants to

registration() register with the site.
Pseudo Code

2:when user fill this from check all the fields are filled or not
login() A method used to perform login when user wants to login with the
site.
Pseudo Code

Money Transfer() Pseudo Code
Add transaction details(name, number, password)

{
Stringname;
String password;
Int number;
}
3. Display transaction is performed successfully or not.

Summery
Class Name Summery
Brief Description Summery provide the all information about accounts and transactions.
It also provides the information about the category of account.
Attributes (fields) Attributes Description
Number This attribute is used to store the number of Account for Summery.
Password This attribute is used to store the password of user for Summery.
Name This attribute is used to store the name of Category for Summery.
Address This attribute is used to store the address of the user.
Methods (operations) Methods Description
Registration () A method which is used to perform registration when user wants to

register with the site.
Pseudo Code

Login () A method used to perform login when user wants to login with the
site.
Pseudo Code



Pseudo Code
Show Summery ()
Add user details(name, address, number, password)
{
Stringname;
String password;
Int number;
Char password;
}
1. Verification is performed.
3. Display the Summery of all accountsor not.

Class Name User
Brief Description Identify any user who wants to interact with the MMS for account
creation, transaction, modification and many other activities.
Attributes (fields) Attributes Description
Name This attribute identify the Name of user.
Id This attribute identify the user Id.
Address This attribute identify the Address of the user.
Methods (operations) Methods Description

A method which is used to perform registration when user wants to
Registration () register with the site.
Pseudo Code

A method used to perform login when user wants to login with the
Login () site.
Pseudo Code

Pseudo Code
Registration ()
Add User details(name, id , address)
{
String name;
Int id;
String address;
}
3. Insert record in registration table.
6. HUMAN INTERFACE DESIGN
6.1 Overview of User Interface
Difference interfaces are provider for different users, admin has difference user interface that is a
simple user of the site. First of all, user creates his/her account by simply fill the
registration form after registration user log in to access his/her account. If user log in
successfully, then he/she perform different operation like create account, perform
transaction, create category and show the summery.
6.2 Screen Images
6.2.1 Login
It will be the first page when user opens the site.
User ID:
Password:
Login Try again

6.2.2 Account creation

It is the Account creation form.
First Name:
Last Name:
Phone Number:
Address:
Successfully
Cancel
Creation
6.2.3 Create Category

It is the form of category creation.
Account Number:
Category Name:
Password:
Add Cancel

6.2.4 Transaction
It will be the money transfer form.
Category Name:
Account Number:
Password:
Transfer Money Cancel
6.2.5 Reset password
It will be the form for Reset the password.
Old password:
New password:
Confirm new password:
Reset password Cancel

6.2.6 Show Summery

This screen form shows the Summery of all accounts.
Account Number: Password:
Category Name: Address:
Show Cancel
6.2.7 Ledger Screen
Ledger screen form provides the collection of entire group of an account or category.
Account Number:
Show
Category Name:
Cancel
Password:

6.2.8 Current Balance

This screen form shows the current balance of all accounts.
Account Number:
Balance:
Display Cancel
6.2.9 Save Date
Save date screen form save the date of transaction.
User Id: Save
Cancel
Date:

7. REQUIREMENTS MATRIX
Co Cr De M Cr Del Mo Exp Inco Tra Mo Dele Tra Sh S

mp eat let od eat ete dif ense me nsfe dify te nsac o a
one e e ify e y Tra Tra r tra Tra tion w v
Ca
nt Ac Ca nsac nsac Tra nsa nsac Su Le e
Ac Ac Ca teg
co teg tion tion nsac ctio tion mm dg D
(Us co co teg ory
un ory tion n ery er a
e un un ory
t t
case t t
e
)
3.2. X
2.1
3.2. X
2.2
3.2. X
2.3
3.2. X
2.4
3.2. X
2.5
3.2. X
2.6
3.2. X
2.7
3.2. X
2.8
3.2. X
2.9

3.2. X
2.10
3.2. X
2.11
3.2. X
2.12
3.2. X
2.13
3.2. X
2.14

Shabnum Asim - Money Monitor System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Shabnum Asim - Money Monitor System

Uploaded by

Copyright:

Available Formats

Money Monitor System

MONEY MONITOR SYSTEM

ROLL NO 162107 SHABNUM ASIM

Signature Printed Name Title Date

2.3 Technology used…….………………………………………………………………………………………………………..…………….2

2.4 Design languages………….………………………………………………………………………………………………………………..2

3.1.2 Block diagram……………………………………………………………………………………………………………………………….4

3.2.1.1 Class Diagram for Account……………………………………………………………………………………………………………5

3.2.1.2 Class Diagram for Transaction………………………………………………………………………………………………………6

3.2.1.3 Class Diagram for Summery…………………………………………………………………………………………………………7

3.2.1.4 Class Diagram for Ledger……………………………………………………………………………………………………………..8

3.2.1.5 Over all class Diagram………………………………………………………………………………………………………………….9

3.2.2 Use case Diagram………………………………………………………………………………………………………………………….10

3.2.2.1 Create Account…………………………………………………………………………………………………………………………..11

3.2.2.2 Delete Account………………………………………………………………………………………………………………………….12

3.2.2.3 Modify Account…………………………………………………………………………………………………………………………13

3.2.2.4 Create category………………………………………………………………………………………………………………………..14

3.2.2.5 Delete Category………………………………………………………………………………………………………………………..15

3.2.2.6 Modify Category……………………………………………………………………………………………………………………….16

3.2.2.7 Add expense Transaction………………………………………………………………………………………………………….17

3.2.2.8 Add income Transaction……………………………………………………………………………………………………………18

3.2.2.9 Transfer Transaction………………………………………………………………………………………………………………….19

3.2.2.10 Modify Transaction………………………………………………………………………………………………………………….20

3.2.2.11 Delete Transaction………………………………………………………………………………………………………………….21

3.2.2.12 Transaction Summery……………………………………………………………………………………………………………..22

3.2.2.13 Show Ledger…………………………………………………………………………………………………………………………..23

3.2.2.14 Save Date to Cloud…………………………………………………………………………………………………………………24

3.2.3 Sequence Diagram………………………………………………………………………………………………………………………25

3.2.3.1 Sequence diagram for Login……………………………………………………………………………………………………..25

3.2.3.2 Sequence Diagram for Category………………………………………………………………………………………………26

3.2.3.3 Sequence Diagram for Summery……………………………………………………………………………………………..27

3.2.3.4 Sequence Diagram for Transaction………………………………………………………………………………………….28

3.2.4 State-Transition Diagram…………………………………………………………………………………………………………….29

3.2.4.1 State-Transition Diagram for Account……………………………………………………………………………………….29

3.2.4.2 State-Transition Diagram for Transaction…………………………………………………………………………………30

3.2.5 Activity Diagram…………………………………………………………………………………………………………………………..31

3.2.5.1 Activity Diagram for Login………………………………………………………………………………………………………….31

3.2.5.2 Activity Diagram for Transaction………………………………………………………………………………………………..32

3.2.5.3 Activity Diagram for Summery……………………………………………………………………………………………………33

6.2.3 Create Category…………………………………………………………………………………………………48

1.4 Reference Material

1.5 Definitions and Acronyms

SDD Document 1.0 Page 1 04/09/18 f

2.1 General constraints

2.2 System environment

2.3 Technologies Used

2.4 Design Languages

SDD Document 1.0 Page 2 04/09/18 f

3.1.1 Web Architecture

SDD Document 1.0 Page 3 04/09/18 f

User User User User User

Registration Login Account Category Transaction

Summery Money Monitor System Ledger

SDD Document 1.0 Page 4 04/09/18 f

3.2 Decomposition Description

SDD Document 1.0 Page 5 04/09/18 f

3.2.1.2 Class Diagram for Transaction

SDD Document 1.0 Page 6 04/09/18 f

3.2.1.3 Class Diagram for Summery

SDD Document 1.0 Page 7 04/09/18 f

3.2.1.4 Class Diagram for Ledger

SDD Document 1.0 Page 8 04/09/18 f

3.2.1.5 over all Class Diagram