final project presentation

1. ABNNS

2. System Design

3. In this section the application is described by
defining the design goals of the project, by
decomposing the system into smaller subsystems
that can be easily realized (proposed application
architecture) and by selecting strategies for
building the application, such as the
hardware/software platform on which the
application will run, the persistent data
management strategy and the handling of
boundary conditions. The result of system design
is a clear description of each of these strategies,
subsystem decomposition, and a deployment
diagram representing the hardware/software
mapping of the system.

4. This class diagrams explain about classes within
model. Classes have attributes like (member
variables), operations (member functions) and
relationships with other classes in object oriented
application. The top, middle and bottom are the
parts we see in the class icon. The top part will
contain the name of the class. The middle class
contain list of attributes (member variables) and
bottom part contain list of operations (member
function).This diagram can be derived from the
phase one part of our Domain Modeling which is
called Class Responsibility Collaborators (CRCs).

5. +onCreat() : void
+onPause() : void
+onStop() : void
+onDestroy() : void
Activity
+Add() : void
+Delete() : void
+Notify() : void
+LogOut() : void
-Start Time : int
-RoomNo : int
-Date : int
-Year : int
-Course Title : string
-IDRange : string(idl)
-Supervisor : string
Exame Schedule
+Create Account() : void
+Log in() : void
-Username : string
-Password : string
LogIn
+Add() : void
+Delete() : void
+Notify() : void
+LogOut() : void
-Note : string
Note Class
+add() : object
+LogOut() : object
+delete() : object
+Notify() : object
-Dept : string
-Year : int
-Semester : int
-Section : int
-Instructor : string
-Course Title : string
-WeekDay : string
-Time : int
Class scheduling
-Enter *
1
-Notify * 0..*
-Notify
*
0..*
-provide *
1

6. The software going to be developed is allowed by
UML model. UML deployment diagram show
physical view of system, taking software into real
world by showing how software gets assigned to
hardware and how communicates. The
deployment diagram shows how the software
components, processes, and objects are deployed
into the physical architecture of the system. It
shows the configuration of the hardware units and
how the software components are distributed
across the units.

7. Mobile Phone
ABNNS Application Layout
Log in
Notify
Notification database
Local Sqlite database
Add information
-Xml
Application Server
Notify sqlite
-java JDBC
Info service

8. UML state chart diagrams depict the various states
that an object may be in the transition between
those states. In other word it has initial and final
states in addition to transition that is a progression
from one state to another. States are represented as
a rounded rectangle with the name of the state
shown in the system. Connecting states together
are transitions. These represent the events that
cause the object to change from one state to
another. The guard clause of the label is again
mutually exclusive and must resolve itself to be
either true or false. Actions represent tasks that
run causing the transitions.

9. Fig5.3 state chart diagram for add
information
ABNNSActivity
/ click
Layout
/ Enter
/ validate input
/ incorect
Error Message
/ correct
Add
Display tost message
/ ACK
/ check app
/ reach app
Notify Info
/ not reach
Waite untill
time is up
View Info
Required field

10. User interface design is the specification of
communication/interaction mechanism between
the application users and a mobile. The process
involves input mechanism design, output
mechanism design, and navigation mechanism

14. System
Implementation

15. The focus of our test strategy was simply
waterfall testing on our application due to the
limited development time frame, freshness of
the platform and the sheer variety and number
of components involved. The Android SDK
provides a set of integrated development
and testing tools that include a built in
emulator, debugger, logger, and device
drivers that allow running applications on an
Android phone. The emulator was used
extensively in the initial development and
testing of ABNNS

16. 6.2 .1 Unit Testing
The app's various functions were tested
independent of the system. The following types
of unit test were conducted:
 The navigation from one view to another
 Synchronization of data between Google Cloud
messaging and the application
 Removal of deleted and expired events
 Finally firing of notifications

17. 6.2 .2 Functional Testing
Functional testing was tests all the
modules of the application will work
correctly the functionality this was
done to test the functionality of all
the modules were combined.

18. Constraint
 The first problem encountered when starting the
Android application was how to access the Google Cloud
Messaging and keep it updated and synchronized. As at
that time, Android had not released support for Android
Google Cloud Messaging
 The course wireless communication and mobile
computing is given at the 4th year. So we are not familiar
with android very well at the time of starting this project
and anxiety on the team member can be encountered.
 Another problem faced was debugging, since the
Android emulator provided by Google does not have
Google Cloud Messaging built in. Building the app had
to be done entirely directly on the phone. The traditional
method of putting break points and debugging code
could not be done, as it was not supported. This was
overcome by using the "Logcat" tool .

19. 6.4 .1 Conclusion
In this Topic we summarize the result of the
study that has been found in the analysis.
Based on the result rational suggestions and
recommendations have been forwarded. The
project is partitioned into two phase and each
phase has a specific deliverable which is
essential and base for the next phase.

20. 6.4.2 Recommendation
As we try to describe on phase one android based mobile
device are increasing by 53% every year in the world
and almost more users are available in our campus. It
can be an open standard for mobile devices,
considering them we will recommend to the next
generation student to develop their project on android
based application. To do so ambo university at least
satisfy the following things:
1. Wireless communication and mobile computing course
must give at 3rd year.
2. Give to their student orientation before about android
project development.
3. If it is possible prepare Mac for development