Addis Ababa Institute of Technology

Center of Information Technology and Scientific

Computing School.
                           Expense Tracker
Software Design Specification
Team Members: 
1. Mekides Bishaw
2. Abenezer Fikadu
3. Biruk Ayalew
4. Tolosa Mitiku 

Advisors: Mrs. Belete

                                                                        Date

1|Page
Table of Contents
List of Tables ii

List of figures iii

Definitions, Acronyms, Abbreviations iv

1. Introduction 1

1.1 Purpose 1

1.2 General Overview1

1.3 Development Methods & Contingencies 1

2. System design model 1

2.1 Subsystem decomposition 1

2.2 Hardware/software mapping 1

2.3 Access control 1

3.  Object Model 2

3.1 Class Diagram 2

3.2 Sequence Diagram 2

3.2 State chart Diagram 2

4. Detailed Design 2

References 3

2|Page
List of Tables

3|Page
List of figures 

4|Page
Definitions, Acronyms, Abbreviations

UI User Interface

OS Operating System

PC Personal Computer

HTML Hyper Text Markup Language

CSS Cascading Style sheet

5|Page
1. Introduction
1.1 Purpose 
This document will outline the software design and specification of our workflow task
management system in addition to system architecture, system components, and software
requirements as agreed upon by the project team.

1.2 General Overview

This document will contain specifics about the design of our software. It is a high level
explanation of how the project will function, and which components will be developed to help it
do so. This document will also serve to explain the technologies used to develop the website, as
well as the user's interaction with various features.

The model that we use to make our Expense Tracker system more resembles to be a Water fall
due to the following reasons

 Simple and easy to understand and use.

 There were no ambiguous requirements.
 Easy to manage due to the rigidity of the model. Each phase has specific deliverables and
a review process.
 Clearly defined stages.
 Well understood milestones. Easy to arrange tasks

1.3 Development Methods & Contingencies

Prior to building any system from scratch, it is important to plan the design flow of the system.
The UI design is pretty essential to know how the system is intended to work. Planning a system
definitely involves some specific strategies. Many strategic questions come to the mind while
designing and planning a system like there might be other system similar to our idea, what the
need of such system in the market is, what features make our system unique , what make the
people use our system, how much time the system will take to develop, what user requirements
either small or big should be considered etc.
 Fronted Html: Hypertext Markup Language (HTML) is the standard
markup language for documents designed to be displayed in a web

6|Page
 browser. It can be assisted by technologies such as Cascading Style
Sheets (CSS) and scripting languages such as JavaScript. Web browsers
receive HTML documents from a web server or from local storage and
render the documents into multimedia web pages. HTML describes the
structure of a web page semantically and originally included cues for the
appearance of the document.
 Database: It is a collection of table with related data. provides the
management of saving objects to and retrieving them from storage.
 Expense/Income page: contain list of expense/income made for a
particular date. The user can either enter an expense or an income
depending on what he chooses.
 When Expense/Income category is pressed, it brings to another page with
some pre-filled entries in the database. The user can press the edit button
to delete the existing categories or add new categories to the existing list.
If all the rows are entered, the user has the flexibility to see the result
(expenses) in the report page based on category.

2. System Architecture  
2.1 Subsystem decomposition 

2.2 Hardware/software mapping 

UML Deployment diagram 

7|Page
3.  Object Model  
3.1 Class Diagram 

3.2 Sequence Diagram

8|Page
9|Page
3.2 State chart Diagram (optional element)
UML State chart diagram (If you have an object that can be in many states only)

10 | P a g e
4. Detailed Design
Here show the identified class in detail for example: -Assume a system has a Mobile Client Class
then describe about the class in the following manner.
The classes represented here are the ones identified on your class diagram. But you must add the
methods and classes identified in sequence and state chart diagram.
Table: x Mobile Client class 

Mobile Client
+Name:String
+ PhoneNumber:Integer
+Address:String
-Email:String
-ID:String
s+fillPersonal ()
+Beggar’sInfo ()
+SubmitInfo ()

Table: x Attributes description for Mobile Client class 

Attribute Type  Visibilit Invariant

y
Name: String Public Name <> NULL and must contain first, middle and last
name and shouldn’t contain special characters and integers.

PhoneNumber Intege Public PhoneNumber <> NULL must be 10 digits and must start
r by +251/09

Address String Public Address <>NULL and it must be between 12 to 20

characters

Email String Private Email <> NULL 

 Must contain @
 Must contain. (dot)
 Position of @ >1
 Position of (dot)>position of @ + 2
 Position of (dot)+3<= total length of email address
and the total character of the Email is at least 5
characters

Table: 7 Operation description for Mobile Client class 

Operation Visibil Retu Argum Pre-Condition Post Condition

ity rn ent
type
RegisterPersona Public void . The clients personal The clients personal

11 | P a g e
 lInfo information  shouldn’t information  should
exist exist
RegisterBeggar’ Public void . The Beggar’s  The Beggar’s 
sInfo information  shouldn’t information should
exist exist
SubmitInfo  Public void - Both the client’s and Both the client’s and
Beggar’s  information  Beggar’s  information 
shouldn’t exist should exist

12 | P a g e
References

Bibliography
(list of book used for referance)
Web resource
(list of web pages you used as reference//address + access date )
http://www.tutorialspoint.com/uml/index.htm at May 5,2016(use this link for uml diagrams)

13 | P a g e