02/02/2023 Ambo University 1

02/02/2023 Ambo University 1
ENTA TION
OU R PRES
OM E TO
C
WELL
E O NE
C T PHAS
RO J E
IA L P
U ST R M A RT
R IN D ED S
Y EA BA S
L I D
FINA :-ANDRO EMINDER
IT L E NTR
T T M E
I N
APPO
GROUP MEMBER ID
ABEBA SHASHO R/1808/03
EZRA KIROS R/1824/03
HIWOT TESFA R/1832/03
MEBRAHTU CHAKLU R/1842/03
Advisor: Mr.Wondmagegn Desta

Co-Advisor: Mr. Tilahun Ayalew
Submitted to Department of Computer Science, Institute of Technology,
Ambo University, in Partial fulfillment for the requirement of the Degree in
Bachelor Science in (Computer Science)
Ambo, Ethiopia
[15 February
2014]

Chap
ter on
Introd e
uction
4
Overview :-
Introduction
Background Information
Statement of the problem
Scope and Limitation
Software used
Feasibility Study
Project Management Plan
Project Organization

ANDROID BASED SMART APPOINTMENT
REMINDER
1. Introduction
 Mobile computing has so many distinguished
characteristics
such as:-
 wireless connectivity
small screen size
 battery power usage, and its functionality suited to
the mobile user.
 Because of this nature, developing mobile applications are
inherently different from desktop or web based applications .

Introduction Continued …
these days the numbers of mobile users are increasing and a lot of
applications, and services generate a lot of data, and information to
mobile users.
in general everyone is becoming a mobile service user.
building an appointment reminder application will solve some of

the problem face by many people such as forgetting.
forgetting is a common complaint or factor that everyone shares.

Introduction Continued …
for this reason, Android Based Smart Appointment Reminder

application helps you to remember your important meeting dates
and place.
 these users are using different applications; among the many

applications used by many users are :-
 Our team member will build a productivity application

named android based smart appointment reminder

1.1Background Information
 forthe past few years, android based mobile
applications were almost not applicable.
 according to the information from the Android website,

android based mobile devices are increasing by 53%
every year and becoming an open standard for mobile
devices
 considering them as a key lever to development of

android based application

1.1Background Information Continued….
know day’s any appointment agreements based on current location

and transport mood are manually or mind work.
but this system is not well. For better appointment management

and time usage, an efficient smart appointment reminder application
is a key.
it helps to monitor appointment place and time.

1.2 Statement of the problem
Now a day, mobile applications play an important role in the
development of the country in respects of many ways
accordingly users need to get enough information about each

and every smart service using mobile applications.
from these mobile application the user need will be to get

service like appointment reminder mobile application.
appointment handling, as most of us know, are composed

time and place.
sometimes it is necessary to be notified about the

appointment on time.
1.2 Statement of the problem continued ….
considering growth of usage of android powered mobile devices,
create an Android based smart appointment reminder which notifies
the appointee his/her appointment based on his/her current location
and mood transportation to appointment place is a solution for the
specified problem.
however, within the current android based mobile application it is

not possible to be notified about the appointment based on current
location and mood of transport.

1.3 Objective of the project
1.3.1 General Objective

is to design and develop android based mobile application
appointment reminder
 and for partial fulfillment of bachelor degree of computer

science.
1.3.2 Specific Objective

developed to help users by reminding appointment using mobile
simply by detecting current location
 and retrieving the appointment position .

Specific Objective Continued…
the specific objectives of this project are listed as follow:
avoiding paper based appointment setting by providing

automated based appointment reminder
 avoid an appointment time lost and notifies appointment

based on transportation mood.
avoid forgetting an appointment
it prevents to the user from stress and confusion.
notifies users the type of problem facing

1.4 Scope and limitation of the project
1.4.1 Scope of the system
The project will include android development environment setup,

user interface design, database design, coding, testing.
in other words, it is a complete life cycle of a full mobile application

development.
1.4.2 Limitations of the system
Due to lack of time, budget, access and different academic loads on

the project developer group the project cannot encompasses the
following activates:-

Limitations of the system Continued…
works in android operating system only.
 it need high accuracy GPS and it is not work without the

internet connection
restricted in areas.
other mobile operating system may be considered after the

completion of this project as a second phase or future
development.

1.5 Methodology and Software used
1.5.1 Systems analysis and design methodology
A.In Analysis and Design:- Object Oriented System Analysis

and Design (OOSAD) using Unified Modeling Language (UML)
and Visio Software. Because
allows full exploitation of the power of object-based and object-
oriented programming languages

Systems analysis and design methodology Continued…
B. In Implementation
· Graphics design tools (like Photoshop, paint),Database (like
Sqlite),Programming language (Java),Development tools
(Eclipse, ADT)
The model that we will use in our system development life cycle is
the waterfall model
1.5.2 Data Collection Methodology
The project team has used the following techniques mainly for
gathering requirements and for describing the proposed application.
· review related works
· by Observing the existing problem
· by discussing and analyzing the problems with project team.

1.5.3 Development environment, programming tools
and resource required
In this project, we will use following resources to achieve the
project objectives.
Data and information

Internet(Email and website(www.javatpoint.com))
Books (2008_Ed_Burnette_Hello_Android, mobile computing
principles text book and From_OO-SAD lecture note)
Computer Software like

MS-office, MS-project, paint, Visio, Java, Sqlite database
server, Eclipse, ADT and Android SDK,

Development environment, programming tools and
resource required Continued…
Computer Hardware like

Server, Personal computers, Switch, Printers, Different wires
and related equipment’s
External storage devise:-

Flash disc 1-16 GB and Compactable CD-ROM 700 MB
Based on requirements, the analysis, design and implementation

of the system will be performed using the above computer hardware
and software, and object oriented analysis and design (using UML).

1.6 Feasibility study
the feasibility analysis of our project involves the following:-
1.6.1Economic Feasibility
identifying the costs and benefits related with developing the
project.
that is why it is sometimes called Cost-Benefit Analysis.
 here, in determining benefits, there are two cases for benefit

analysis such as
 Intangible and Tangible
in determining cost analysis

 One time(initial) cost and recurring costs.

Economic Feasibility Continue…
the following are the tangible and intangible benefits:-
A.Tangible benefit: - are those our project benefit that

can convert into monetary values.
e.g. reduced stationary cost
B.Intangible benefits: are those our project benefit that
cannot convert into monetary values.
e.g. knowledge gain by project developer, increasing

the competitiveness of the individual ,more timely,
updated, and accurate information, better appointment
management

C. One time(initial)cost:- are costs incurred at the time
of developing our project. For this project, we have come
up with the following tangible costs and intangible cost.
Tangible cost
 include the cost of equipment’s such as computers,
server, terminals and the costs of other resources
which can be covered by the departments and others
which can be covered by the team members are:-

Intangible Costs
are costs that will be incurred during the project but are difficult to
be
represented in monetary terms.
the intangible costs involved in this project are:-
Time and effort of the development team.
D.Recurring costs:-are costs those incurred to use and maintain our

project once developed.
So, generally the benefit analysis of our project greater than from the
cost analysis of our project. Therefore our team decided the proposed
project is economically feasible.
1.6.2Technical Feasibility
assessing the ability of our team to construct the proposed
application.
Generally our team members are new to the developing

environment of mobile application.
 But we will try to understand the scope, objectives including
specific objectives and limitations of the proposed application well.
As a result we will try to develop the ASAR mobile application
successfully within proposed time and required functionality.
So that, the project is technically feasible.

1.6.3Operational Feasibility
deals with the degree to which the proposed application solves
business problems.
 the proposed application will solve the problems in the

following ways.
· by providing a new and reliable means to handling
appointment
· by providing up to date and accurate alert to the appointment
· better management of time
so ,the entire team member expects the application to be

operationally feasible.

1.6.4Schedule Feasibility
 concerned with analyzing the expected completion date of the
project and the constraints that may bring change to this date.
we have so many fixed schedule to work together the project with
all group within each day and for the simplicity and fast developing
purpose we also follow work break down structure on the team
member.
so, the project team members think that the project will be finished
within the specified time.
in general, the project is less risky as a result of the reasons

specified in each of the feasibility analysis studies.

1.7 Beneficiaries Of The Project
User:-after developing the ASAR any person can beneficiary. By
the following ways:-
remained their appointment time early
can get necessary information about the appointment

remained their appointment place
The developers or team members
obtain knowledge and experience from it.
use it for partial fulfillment of degree program.

gain income if it is complete

1.8Project Management Plan
 is a process of devising and maintaining a workable scheme to
accomplish the business need that the project was undertaken to
address.
1.8.1Scope Management Plan
Statement of work
 is a document prepared for our user to describe what the
project will deliver and outlines all work required to complete
the project .
we prepare it to assure that both of us gain a common
understanding of the project as below table.

Scope Management Plan Continued…

Work Breakdown Structure (WBS)
Fig WBS

1.8.2Time Management Plan
 deals with the timely completion of the project considering
the time required for each activity in the work break down
structure (WBS).see as below:-
Fig Gantt Chart

1.8.3Cost Management Plan
provides a rough idea of what a project will cost until it is
completed.
Table Cost Management Plan

1.8.4Quality Management Plan
is needed to ensure that the project will satisfy the needs and
requirements for which it was undertaken.
is viewed from different perspectives; some of these perspectives

are the following:
1. Functionality
2. System Output
3. Performance

1.8.5 Communication Management Plan
the following table shows a list of communication plans of the project.
Table Communication Management Plan

1.8.6 Assessing risk
the team member has adopted different system of advising as well
as checking its successful accomplishment to protect the system
from failure.
some of the problems that we might face while doing this project
would include:-
damage on the computer that we work on
 lack of references and internet connection. Etc
so that the above problems might require some kind of
management and we had put some methods down:-
we would have backup CD and flash so that, the data could not
be loss.
we would use lecture note as a reference etc.

1.9 Project Organization
 our project organized in two main phases.
 the first phase of our project include chapter one of project up to

chapter four which includes :-
 introduction
 prior related work system information
 proposed system information System
 and Modeling using OO(Object Oriented)Paradigm for
phase one
 design OO (Object Oriented paradigm) and system
implementation for second phases.

1.9.1 Team organization
in our team every task must be done by every person of the group.
as we know there is three type of Team organization;

 centralized-control team
 decentralized-control team
and Mixed-control team organization.
we select Decentralized-control Team organization because it has
Some any advantage like
e.g. all team member can get equal knowledge and moral

Overview :-
• Prior Related work description
• Drawback of Related works
• Practice to be reserved
• Business Rule
• Players in the Prior Related work

2.1Android Fundamentals
2.1.1 Android - History
 android is an operating system based on the Linux kernel and
designed primarily for touch screen mobile devices such as smart
phones and tablet computer.
introduction of Android in 2007, Google’s flagship open-source OS

for mobiles, the dynamics of the mobile phone industry have
changed completely
for this reason we need to develop ASAR application and let as

describe some basic android terms that we will use in the
development of ASAR

Android Framework Components
android application is a package which consists of loosely coupled
components which are connected to each other at runtime.
the components are the basic building components of any Android

application.
 all these components work together in collaboration by responding
to events or Intents or Android system
AndroidManifest.xml file
 every Android application has a "manifest" file which contains a
list of
 all activities
 intents
and permissions which the application includes.
the AndroidManifest.xml file is the starting point of any
application. It mentions the permissions that are installed as part of
the application.
Activities
 is basically a single screen that the user views with a user
interface. An application can consist of multiple activities.
SQLite Database
is an open source database which is embedded into Android.

the major advantage of SQLite is that it requires approximately
only 250 Kbytes of memory at runtime.
SQLite is available on every Android running device and does not

require any additional setup
Content Providers
are the application components that are used to store and retrieve
data and make it accessible to the other applications.

2.2 Prior Related Work (Current Related
Application Description)
as we know now days there are so many ways to remember any
appointment to the user.
among these applications we will try to describe some of

application they are related to ASAR.
these applications are related to ASAR in deferent angles and all

have their own drawbacks and advantages.
these applications are lists below:

2.2.1 Location Reminder
is an efficient and accurate location based reminder application.
 it is the perfect travel reminder Application that reminds you of your
place or area as you go.
the Application is a completely free location reminder, full-featured

alarm that notifies when you arrive in the surrounding area of a
location.
Functional Requirement
• sense the location of the user
• Notifies sms to the user
Non Functional Requirement
• give accurate information to the user about he/she exists
• prevent the user from stress
• hardware consideration
• minimal space

2.2.2 Alarm reminder
is used to the mobile application user to remind appointment time
based on which can be set.
 it reminds or notifies to the use only the appointment time.
• set alarm
• delete alarm
• update alarm
• view alarm
• notifies alarm
• reliability
• usability
• accuracy
• error handling

2.2.3 GPS Tracker
is an application that enables you to record any track you passed using
the GPS device on your Android powered phone .
GPS Tracker uses the Google Maps interface for displaying recorded
tracks.
 GPS receiver estimates position by measuring satellite signal’s
time difference of arrival
• track the location of the user
• guides and control the user
• shows user location
• prevent the user from stress
2.2.4 Calendar
simply reminds to the user year, month, date and time.

2.3 Prior Work Defiance’s
drawbacks such they remind at the exact time of appointment.
as the result if we are in other place we will not reach on time.
 these drawbacks when combined with living under stress make people
more depressed.
let as see the drawbacks one by one on each applications:-
Location Reminder: - this reminder notifies to the user only the

current location or place of the user available.
But it is not notifies the appointment place, appointment type ,based

on the transportation mood and the appointment time

Alarm reminder:-it notifies or reminds only the appointment time
But it is not notifies the appointment place, appointment type , based on

the transportation mood and the appointment time also notifies on the
exact time.
Generally we will image that the drawbacks of all application solves
ASAR application.
2.4 Practice to preserved from the related work
 all applications have their own advantageous side.
so ASAR preserves the advantageous service such as reminding time,

place and can take some of the required functional requirement and non
functional requirement from the prior related work listed above, then
combing them to form ASAR application.

2.5 Business Rules
 is a principle or policy in which the system operates accordingly .
It deals with access control issues, reliability issues, and policies of the
organization.
The following are the business rules found in the system:
BR 01 Only users of the mobile with required version of android
operating system are allowed to set appointment and remind.
BR02 Only intended user of mobile should delete, view and update
appointment.
BR03 The system must delete automatically the setted appointment after
reminding.
2.6 Players in the existing system (on related works)
The existing system will have an actor that interacts with the application
which is called user and GPS sensor.

r e e
T h
t er t h e
h a p o f on
C iew icati
e rv pp l
v
O sed A
o po
Pr
50
Overview :-
• Overview of the proposed system
• Functional Requirement
 Essential use case modeling
Essential User Interface prototyping
Essential User Interface flow diagram
• Domain Modeling
• Non- Functional Requirement

3.1 Over view of the Proposed Application
after careful observing and analyzing the problem the prior related
mobile application our team decide to design and develop the android
based smart appointment reminder as a solution.
the new mobile application is designed to make your appointment

application better and also user may view the contents of any
appointment at any time and place as they needed.
it will use the major functionality of the prior related work application
to advance the prior related work .
this means that ASAR provides information to the user about the
appointment time and appointment place based on transportation mood.

3.2 Functional Requirements
is requirement that deal with the function processes of the application.
i.e. The main or the basic tasks that the application must do.
the application to be developed should be able to support the following:

• update existing appointment details.
• cancel appointment details
• reminds your day of appointment through sending SMS or vibrating a

sound.
• user set unlimited number of appointment details.
• select date of appointment, transportation mood and appointment
place.
• detect or sense/Track current location.
• user view appointment detail.
3.2.1Essential Use Case Modeling
 is one of the Unified Modeling Language artifacts which is intended to
capture the essence of problems through technology-free, idealized and
abstract descriptions.
It also highlights what its users are trying to accomplish.
Android Based Smart Appointment Reminder
Select appointment
detail
Sense current
location
Set appointment
Update appointment
User
GPS Sensor
Cancel appointmen
View appointment Remind appointment
Fig3.1 Essential Use Case Model

3.2.2 Essential User Interface Prototyping
is a model or a prototype of the user interface (UI) for a system.
it represents the main ideas behind the UI but not the exact details.
it demonstrate UI requirements in a technology independent manner.
let as see our proposed application Essential User Interface prototyping

shown below:-

Fig3.2 Essential User Interface Prototyping

3.2.3 Essential User Interface Flow Diagram
shows the relationships among the major user interfaces like reports
and forms that compose the application.
Home
page
Lock page Press key
Unlock
page
Activity ASAR application

page page
Set appointment page

Remind appointment
page
Update appointment page
Notifies appointment
page
Fig.3.3 Essential User Interface Flow
Diagram View appointment page
Delete appointment page

Table User Interface Description

3.2.4Domain Modeling

is the task of discovering the classes that represent the things and
concepts contained in the ASAR.
in this modeling, we use Class Responsibility Collaborators (CRCs),

since they are well suited for domain modeling during requirements
gathering. CRCs have three sections which are:-
• Class name: - It is the name of a group of similar objects in ASAR.
• Responsibility:-is anything that a class knows or does in ASAR

application.
• Collaborators: - are lists of classes that interact with the class for
information that is used to full fill a responsibility.
Generally our proposed application domain modeling looks like below.

Gps Activity
Appointment
Knows longitude Location Manager Knows Type Location Manager
Knows latitude Knows time Transportation mood
Knows current location knows date
knows place
Location manager Activity

Knows Request location update Appointment
Knows on create Appointment
Knows on start
Knows on pause
Knows on resume
Transportation mood
Knows Vehicle name Map activity Map Activity
Knows Vehicle identity Gps activity
Knows Starting place Appointment
Knows Destination place Knows zoom in Location manager
Knows Circulation place Knows zoom out
List of CRC

3.3 Non-Functional Requirement
are those requirements that have nothing to do with the functionality of
the system but they determine the performance of the whole application.
some of the none functional requirements are: -

• the application can be quickly performed the work.
• the application must be reliable.
• the application must be low-cost.
• the application must have reusable components and code.
• the application will be use minimal space.
• the application must be support new technology etc.

in this chapter, we are used different system diagram modeling to
model the new proposed application, such as :-
 use case diagram model

 activity diagram model,
and sequence diagram model using object oriented paradigm

App C h apte
l ic at r Fou
ion M r
odel
ing
64
Overview :-
 Use Case Modeling
Sequence Diagram
Activity Diagram

4.1 Use Case Diagram For New System
is a high level requirements overview that shows one path of activity
from start to finish.
so, the use case diagram for android based appointment remainder
mobile user application used to retrieve current detail information without
describing how the interaction works in a detailed manner
an actor typically initiates a use case and derives some benefit from its
use
an actor may be an actual person, another system, or even a hardware

device, but it always represents a set of roles that will be interacting with
the system from the out said . So the use case diagram the proposed
application is shown below:-

Fig 4.1 Refined Use Case Diagram Modeling For New Application
Use Case Description Continued…
Use case name: Set appointment
Identifier UCI:-2
Description: Allows user to set appointment detail such as appointment time, place , transportation mood and
appointment type.
Actor User
Pre-condition: Appointment not setted.
1. User presses the appointment reminder application from the mobile application list.
Basic course of action:
2. The application displays list of appointment reminder application icons.
3. The users select the set appointment icon and then press the icon.
4. The application displays the set appointment page.
5. The user enters the appointment details.[A1][A2]
6. The users press the ok button.
7. The application send acknowledgement message to the user such as the appointment is sated.
8. The appointment is sated.
Extends: --
Includes: Unlock key pad
Post condition: the appointment reminder is setted
Alternate course of action: A1
1. The application displays wrong data entry.
2. The application resumes at step 4.
A2:
1. The application displays required field missing message.
2. The application resumes to step 4.
Table Set appointment detail Use Case Description

Use case name: Cancel appointment
Identifier UCI:-4
Description: Allows users to cancel or delete appointment which can be sated before.
Actor User
Pre-condition: The appointment must be setted before.
1. The user press or initiates the appointment reminder application from the
mobile application lists
2. The system displays list of application icons.
3. The user chooses the sated appointment and then presses cancel or delete
appointment icons.
4. The system sends acknowledgement message to the user such as the
appointment deleted.
5. The system deletes the setted appointment.
Extends: --
Post condition: the appointment is deleted or canceled
Table Cancel appointment detail Use Case Description

Use case name: View appointment
Identifier UCI:-5
Description: The user views or sees the appointment detail which can be remind by the
appointment reminder application.
Actor User
Pre-condition: Appointment must setted and the appointment reminder application must send or
remind to the user.
1. Reminder remind to the user through sending sms or vibrating tone.
2. The user presses the view appointment icons.
3. The system displays the appointment detail which can receive from the
reminder.
4. The user sees the appointment detail.
5. The users remind and go to the appointment.
Extends:
Post condition: Appointment viewed and remind by the user.
Table View appointment detail Use Case Description

Use case name: Remind appointment
Identifier UCI:-7
Description: The GPS sensor remind the appointment to the user by sending sms or vibrating
tons with the consideration of current location of the user and the appointment
place through detecting latitude and longitude.
Actor GPS sensor

Pre-condition: Appointment detail must be setted before and not remind.
1. The GPS initiate to sense current location of the user.
2. The GPS calculates longitude and altitude of the current position of the
user.
3. The GPS considers the appointment place, time and transportation mood.
4. The applications remind the appointment detail to the user before.
Extends: View appointment

Includes: -------
Post condition: The appointment will remembered to the user.
Table Remind Appointment Use Case Description

4.2 Sequence Diagram
 the Sequence diagrams our proposed application show a succession
of interactions between classes or object instances over time.
:Appointment reminder :Set appointment page

:List of appointment :Set appointment page control
application :Set appointment table
:User application icon
:user
Press()
Display()
Select()
Press()
Display()
Fill()
press()
Validtion()
Validation ok()
Set Appointment()
Save Appointment()
Send ACK()
Send ACK message success fuly set apppointment()
Fig 4.2 Sequence Diagram For Set Appointment

:list of Appointment
:User :Apointment reminder remainder application :Delet Appointment Table
appliction icons
press()
Disply()
Select()
Press()
Delet()
Delet sated Appointment()

ACK()
Send ACK message appointment deleted()
Fig 4.4 Sequence diagram for delete appointment use case

:User :View appointment page :View appointment table
clicks()
intiats()
sends reminded appointment()

displays appointment detail()
see appointment details()
remember appointment()
Fig 4.5 Sequence diagram for view appointment use case

Fig 4.5Sequence diagram for sense current location use case
4.3 Activity diagram
 the purpose of the activity diagram is to model the procedural flow
of actions that are part of a larger activity
User GPS sensor
Sense current location
Unlock key pad
Set appointment Check setted appointment
-[Invalied] -[Valid]
Reset appointment
Calculate appointment detail
View appointment Appointment time reach Appointment time not reach
Remind appointment
Notifies appointment Waite
02/02/2023 Fig 4.7Activity Diagram 76

??

02/02/2023 Ambo University 1

Uploaded by

Copyright:

Available Formats

02/02/2023 Ambo University 1

Uploaded by

Document Information

Original Description:

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

02/02/2023 Ambo University 1

Uploaded by

Copyright:

Available Formats

02/02/2023 Ambo University 1

Advisor: Mr.Wondmagegn Desta

02/02/2023 Ambo University 3

02/02/2023 Ambo University 5

02/02/2023 Ambo University 6

in general everyone is becoming a mobile service user.

building an appointment reminder application will solve some of

forgetting is a common complaint or factor that everyone shares.

02/02/2023 Ambo University 7

for this reason, Android Based Smart Appointment Reminder

 these users are using different applications; among the many

 Our team member will build a productivity application

02/02/2023 Ambo University 8

 according to the information from the Android website,

 considering them as a key lever to development of

02/02/2023 Ambo University 9

know day’s any appointment agreements based on current location

but this system is not well. For better appointment management

it helps to monitor appointment place and time.

02/02/2023 Ambo University 10

accordingly users need to get enough information about each

from these mobile application the user need will be to get

appointment handling, as most of us know, are composed

sometimes it is necessary to be notified about the

however, within the current android based mobile application it is

02/02/2023 Ambo University 12

1.3.1 General Objective

 and for partial fulfillment of bachelor degree of computer

1.3.2 Specific Objective

 and retrieving the appointment position .

02/02/2023 Ambo University 13

the specific objectives of this project are listed as follow:

avoiding paper based appointment setting by providing

 avoid an appointment time lost and notifies appointment

avoid forgetting an appointment

it prevents to the user from stress and confusion.

notifies users the type of problem facing

02/02/2023 Ambo University 14

The project will include android development environment setup,

in other words, it is a complete life cycle of a full mobile application

Due to lack of time, budget, access and different academic loads on

02/02/2023 Ambo University 15

works in android operating system only.

 it need high accuracy GPS and it is not work without the

other mobile operating system may be considered after the

02/02/2023 Ambo University 16

A.In Analysis and Design:- Object Oriented System Analysis

02/02/2023 Ambo University 17

02/02/2023 Ambo University 18

Data and information

Computer Software like

02/02/2023 Ambo University 19

Computer Hardware like

External storage devise:-

Based on requirements, the analysis, design and implementation

02/02/2023 Ambo University 20

that is why it is sometimes called Cost-Benefit Analysis.

 here, in determining benefits, there are two cases for benefit