budget manager application in android.

1. ANDROID PROJECT
(Expense Manager)
By:
• Nalini Mehta

2. Android is an operating system based on Linux with a Java programming
interface.

3. Android user interface
components
1.) Activity
• Represents the visual representation of an Android application.
• An Android application can have several activities.
2.) Views and layout manager
• Views are user interface widgets, e.g. buttons or text fields.
3.) Intents
• Intents are asynchronous messages that allow an Android application to
start and to interact with components from other Android applications.
4.) Services
• Services perform tasks without providing a user interface. These are
sometimes also called background services. Examples of some services are
Alarm services, battery manager, booting services, etc.
5.) Content Provider
• With a content provider one application can share data with other
applications. Android contains a SQLite database which is frequently used to
store the data in Android, which would be accessed via the content provide

4. WATERFALL
MODEL
 simple to understand
and use.
 easy to manage .
 phases are processed
and completed one at a
time.
 it works well for smaller
projects where
requirements are very
well understood.

5. PLANNING STAGE

6.  Inputs to the planning
stage
1.) Application goals
which helps in :-
• Understanding the
problem
• Preparing solution
strategy for the problem.
• And to Determine
system-level goals and
requirements for the
development process.
2.) Life cycle model which
is used to describe
different stages of the
project.

7.  PROCESS
• Develop several
solution strategies,
without regard for
constraints.
• Develop a list of
priorities for product
characteristics.

8.  OUTPUT OF PLANNING
STAGE
• Establishing a cost
estimate for project.
• Establishing the
development schedule.
• Establishing s/w quality
assurance and security
• Identifying sources of
information and follow
them throught the
project plan.

9. Requirement Definition:-
Definition:-
“A raw need which
requires external
inputs or efforts to
deliver a final
product”.

10. SRS
• SYSTEM CONFIGURATION:
• For the developers:
• Hardware requirement:
• Dual core processor or 1 GHz processor (at least).
• Ram: 512 MB.
• SD Card: 50MB.
• Device type: touch screen with LED screen.
•
• Software required:
• Frontend:
• Operating system: Android
• Version: Gingerbread (2.3) or later.
•
• Backend:
• SQLite database manager.

11. SRS
For the client:
• Android Based
mobile with version
Gingerbread (2.3)
or later.

12. Suggested Modules for our application are:
Add Money/Money Management
Transaction Management
Category Management
Reminder Management
History Management
Feasibility Study includes:
Time Feasibility
Resource Feasibility
Technical Feasibility
EconomicalFeasibility
Behavioural Feasibility
Future Flexibility

13. ANALYSIS & DESIGN STAGE
• DFD
• Screen Layouts
• ER Diagrams
• UML Diagrams

14. Data flow diagram:
Graphical representation of the "flow" of data through an information
system, modeling its process aspects.

15.  Context level DFD (0 level
DFD):
The context diagram
shows the entire system
as a single process, and
gives no clues as to its
internal organization.

16.  Level 1 DFD:
The Level 1 DFD shows
how the system is
divided into sub-systems
(processes)
like the money
management,
transaction
management, etc. ,
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
system as a whole.

17.  Child Diagrams (level 2 DFD):
1.) Money
Management

18. 2.) Transaction Management:

19. 3.) Category Management:

20. 4.) Reminder Management

21. 5.) History management

22. Screen Layouts
Give a pictorial
view of how our
application looks
like.

23. First Screen

25. Transaction Screen

26. Reminder Screen

28. History Screen

31. Settings Screen

33. Quick Add Screen

34. Entity Relationship Diagram
An Entity Relationship
Diagram (ERD) is a visual
representation of different
data using conventions
that describe how these
data are related to each
other.

35. The ERD for our application looks
like this:

36. Unified modeling language
Unified Modeling Language (UML) combines techniques
from data modeling (entity relationship diagrams), business
modeling (work flows), object modeling, and component
modeling.
Includes elements such as:
• Activities
• Actors
• business processes
• database schemas
• (logical) components
• programming language statements
• Reusable software components.

37. Use case Diagram
• It is a technique for
capturing the functional
requirements of a
system.
• It describes the
interaction between the
user and the system.
• It helps to communicate
the scope of a
development project.
• Emphasis is given on
what a system does
rather than how.

38. UML Class Diagrams
• It is visual specification of
types of objects that exist in a
system and the relationships
that exist among them.
• A UML class describes a set
of objects that share the same
attributes, operations,
relationships, and semantics.
• Class diagrams may specify
both the conceptual [what]
and implementation [how]
details of the system.
• Class diagrams represent
structural and not
behavioral relationships
that exist among system
entities.

40. Development
XML

41. Activity

42. Integration and Testing

43. Installation and Acceptance

44. Conclusion
• After making this application we assure that
this application will help its users to manage
the cost of their daily expenditure. It will prove
to be helpful for the people who are frustrated
with their daily budget management, irritated
because of high amount of expenses and
wishes to manage money and to preserve the
record of their daily costs which may be useful
to change their way of spending money.
• In short this application will help its users to
overcome the wastage of money.

45. Future Scope