IS 2900 – Project on IT Applications

IS 2900 – Project on IT Applications

Interim Report

Easy Way Android App

Sharks

Index No Name

175079D SRISHAN O.P.D.

KUMARATHUNGA
175044R U.K.K.G
175015F DE SILVA B.H.Y.L.
175012T CHANDRANI K.G.A.
175011N BOMBUWALA C.P.

Supervised by:

Dr.Champika Epa Ranasinghe Uduwaagoda

Dr. TC Sandanayake

Client:
Orange IT Solutions,
Navinna,
Maharagama.

Faculty of Information Technology

University of Moratuwa
2019

i
 IS 2900 – Project on IT Applications

Declaration

We declare that this report is our own work and has not been submitted in any form for another
degree or diploma at any university or other institution of tertiary education. Information
derived from the published or unpublished work of others has been acknowledged in the text
and a list of references is given.

Names of Students Signatures of Students

Date:

Supervised by:

Names of Supervisors Signatures of Supervisors

Mrs.Champika Epa Ranasinghe Uduwaagoda

Date:

Mrs. TC Sandanayake

Date:

ii
 IS 2900 – Project on IT Applications

Abstract

iii
 IS 2900 – Project on IT Applications

Table of Contents
Chapter 1 Introduction ............................................................................................................... 1

1.1 Introduction ...................................................................................................................... 1

1.2 Problem in Brief ............................................................................................................... 2

1.3 Aim and Objectives .......................................................................................................... 2

1.3.1. Aim ........................................................................................................................... 2

1.3.2. Objectives ................................................................................................................. 2

1.4 Proposed Solution ............................................................................................................ 3

1.5 Structure of the Report ..................................................................................................... 4

1.6 Summary .......................................................................................................................... 4

Chapter 2 Literature Review ...................................................................................................... 5

2.1 Introduction ...................................................................................................................... 5

2.2 Analysis of needs ........................................................... Error! Bookmark not defined.

2.3 System Analysis and Design Systems ............................ Error! Bookmark not defined.

2.4 Summary ........................................................................ Error! Bookmark not defined.

Chapter 3 Easy Way Project Management System .................. Error! Bookmark not defined.

3.1 Introduction .................................................................................................................... 11

Chapter 4 Analysis and Design ................................................................................................ 12

4.1 Introduction .................................................................... Error! Bookmark not defined.

Chapter 5 Implementation ........................................................................................................ 16

5.1 Introduction .................................................................................................................... 19

References ................................................................................................................................ 23

Appendix A Individual Contribution to the Project ................................................................. 24

iv
 IS 2900 – Project on IT Applications

List of Figures/Tables

v
 IS 2900 – Project on IT Applications

Chapter 1 Introduction

1.1 Introduction

The purpose of this project is to gain an understanding of project management and to obtain a
brief overview of the methodology that underpins most formally run projects. Many
organizations do not employ full time Project Managers and it is common to pull together a
project team to address a specific need. While most people are not formally skilled in project
methodology, taking a role in a project team can be an excellent learning opportunity and can
enhance a person's career profile.
A project is a temporary and one-time exercise which varies in duration. It is undertaken to
address a specific need in an organization, which may be to create a product or service or to
change a business process. This is in direct contrast to how an organization generally works on
a permanent basis to produce their goods or services. For example, the work of an organization
may be to manufacture trucks on a continual basis, therefore the work is considered functional
as the organization creates the same products or services over-and-over again and people hold
their roles on a semi-permanent basis.

As an IT Company Orange IT Solution want to create their own project management system to
their system because they do not like to use others system to their company. As well as most
project management systems are high costly. That is another reason to they develop a project
management system newly. Apart from that they want to create this project management system
to only their use. They do not like to use a project management system what others use.

A project is generally initiated by a perceived need in an organization. Being a one-off

undertaking, it will have a start and an end, constraints of budgets, time and resources and
involves a purpose-built team. Project teams are made up of many different team members, for
example, end users/customers (of a product or service), representatives from Information
Technology (IT), a project leader, business analysts, trainers, the project sponsor and other
stakeholders.

Project management is the discipline of managing all the different resources and aspects of the
project in such a way that the resources will deliver all the output that is required to complete
the project within the defined scope, time, and cost constraints. These are agreed upon in the
project initiation stage and by the time the project begins all stakeholders and team members

1
 IS 2900 – Project on IT Applications

will have a clear understanding and acceptance of the process, methodology and expected
outcomes. A good project management software utilizes a formal process that can be audited
and used as a blue print for the project, and this is achieved by employing a project management
methodology. The technologies and methodologies that we are using here are JAVA, Android,
IOS, Waterfall method, Critical Path Method (CPM) so on.

1.2 Problem in Brief

Orange IT Solution has a huge problem about their project management because they use a
manual system to manage their projects. As well as they have a problem about the parts of the
projects. Some parts of their projects will be remain until their deadlines. At that time they must
be extend their deadlines. Not only that, management don’t know who is the person in charge of
the task in the project. As this, management must talk with each member to know about the
project.
Apart from that each project have sub parts and that sub parts can divide as task to easy their
works. At that time user and the management, both of them must know about the task. Not only
that, they happen to maintain a board to display their task. When they divide their task as to do,
doing and done. At that time, when they start to doing that task they must change their display as
doing but all the members not going to do that thing. Sometime they will forget that work.
As an IT Company that method not suitable for them. As this they hope to create a project
management software. From that software they can decrease their mistakes and all of the members
can give an idea about the project

1.3 Aim and Objectives

1.3.1. Aim
The aim of this project is To develop a Project Management Software for direct and indirect users
to know about the unique contribution of the project, current situation of the project, daily
maintenance and timeline of the whole project.

1.3.2. Objectives
To achieve the above aim, the following objectives will be achieved.
• To give the main idea for top management about the current situation of the project
• User can handle their unique contribution easily.
• Increase collaboration between top management and low management in the project.
• Everyone can finish their contribution with in the correct timeline.
• As a big company they can handle their projects in easy manner.

2
 IS 2900 – Project on IT Applications

1.4 Proposed Solution

Our System is proposed to develop a System call “Easy Way” an Android app based application
system that can be applied as users of the software projects. This can be very helpful to software
team of the organization to manage the software projects managements. This system is used by
direct labors, indirect labors of the software team and software management. We suggest build
two android apps and one IOS app for the solving company above problems. From these apps,
one android app suggest for the direct and indirect labors of the software project and another
android app and IOS app suggest for the software management. This can be very useful to users
to manage their operations as well. Therefor with the help of the “Easy Way” system, decrease
their mistakes and all of the members can get an idea about the project.
Through this system user can first register in the “Easy Way” system by using their company
Employee ID. Then they can log to the system by using their EID. After that they can see what
the projects they involved. After that they can select project from the project list. As well as
user can identify who are the other members working in this project with him/her?
Furthermore, projects divided to subparts and each sub part has tasks. Users can see what are
the sub parts of the projects and who do each sub parts. At that time users and management,
both of them know about the parts of that projects and users of the projects.
Not only that, they happen to maintain a display board to maintain the tasks. Display board
divided to four parts such as To Do, Doing, Done, Revive. When user has project to start, user
should able to keep his task on the ‘To Do’ part of the display board. When they doing the task,
they must
• To give the main idea for top management about the current situation of the project • User can
handle their unique contribution easily. • Increase collaboration between top management and
low management in the project. • Everyone can finish their contribution with in the correct
timeline. • As a big company they can handle their projects in easy manner.
IS 2900-Project on IT Application
change their display board to ‘Doing’ part of the display board. As well as when task is finished
user must drag and drop their part/task to ‘Done’ part of the display board.
As well as ‘Easy Way’ system manage the deadlines of the each project. And management can
connect with each member of the project. Therefore management also can login to the system
and can see who do the each part, where now they work, on time working situation, etc.

3
 IS 2900 – Project on IT Applications

So, our system will be useful to make the software management system and help busy users to
do their parts and to manage the time for users work and increasing efficiency.
By applying necessary technological applications we intend to find the proper solution to the
above mentioned scenario. As the technologies to implement this “Easy Way” system we have
to suppose java, Android, IOS, DBMS, waterfall method, agile method so on.

1.5 Structure of the Report

The report is consisted of six chapters. The first one contains introduction, Problem in brief, Aim
and Objectives, Proposed solution. In above part we show this details. The second chapter is also
contained of Literature review. Chapter three for presented with reference to users, inputs, outputs,
process, technology that implements the solution. In chapter four for Analysis and Design parts.
Using ER diagrams, User case diagram , Activity diagram and other diagram shows analysis and
design parts. Chapter five we will include software hardware, flowcharts, algorithms we used for
our project. Final chapter we will be able to discusses and conclusion of project.

1.6 Summary
In this chapter we give details about our project proposal. Our main target is introduce a project
management system to Orange IT Solution. Because they do not like to use external system. Not
only they waste lot of time and money of their poor project management skills. Above section we
try to give ideas for it. We shows one by one their problems & and what can we do for that
problems. The system helps to their employee to do their work properly & do their work on time.

4
 IS 2900 – Project on IT Applications

Chapter 2 Literature Review

2.1 Introduction
Software development projects are a collection of large programs with many interoperability
and functionality. It is similar to other development projects, but it is a product that has never
before been created. As a result, there is a bad record of convergence and scheduling of software
development projects, and quality and workaround problems. Furthermore, the scope of the
project varies from market to market, making it very difficult to forecast the success of the
project. Therefore, it is necessary to cancel resources and to replace resources to overcome the
costs. Many software projects include companies, companies, departments, etc. Often, the lack
of disconnection between software developers and their management is not likely to be
associated with others in reality. According to Doherty and King and Working ton, the
organizational risk arising from organizational culture, structure, and business processes has a
bearing on technical software development problems and creates a number of potential split
points. A study found that 65% of the project's problems were due to management problems
Apparently, implementing software projects can be extremely risky. Therefore, risk
management is basically important in the development of software projects in large scale
software projects. If the risk of the project is not controlled at the earliest, the cost of the project
will increase rapidly.

5
 IS 2900 – Project on IT Applications

Figure 2.1
A number of noteworthy frameworks to illustrate the various types of software development
risks and costs / returns, various software development risks, risk management strategies,
preferred organizational climate, and various project performance features. This chapter aims
to investigate and critically investigate the risks of software, organizational conditions, and
studies on software projects.
A key part of the software project is the customer, which will use the system provided by its
business activities, which will benefit the system in the value of its business. The second
important part of the software project is that the party that builds the system is used. The success
or failure of the software project is scaled as given in Figure 2.2.
 Cost - Anything related to supplies, supplies or outsourcing contracts is involved.
 Time - Each part of the project schedule is linked to each task, including periods,
milestones and periods.
 Product Performance - A specification, quality, scope or standards that are designed to
achieve a part or all of the project

6
 IS 2900 – Project on IT Applications

Figure 2.1.2
However, this project cannot be successful or successful. When looking at these parameters,
based on these three parameters, it is not possible to see it. The outcome of the project can mean
different things to different people. The management of a successful project is different from
the project manager, and the developer and users may vary on success. Optical potential of the
vision is due to different expectations, motivation and responsibilities. Lynggger discovered
that software developers were regarded as a successful project, but it was canceled before they
were successful. Baker & Al defines the following project successes: Success of the project is
taken into account in the technical performance specification and / or fulfillment of the mission.
If there is a high level of satisfaction with the results of the main project, the head of the project
team and the head of the project team or head of the project team. Two criteria criteria for
defining project succession were evaluated in two criteria criteria for project management
criteria and product success. The success of project management involves meeting time, cost
and quality objectives, project success, achieving strategic goals of the project owner, meeting
customer satisfaction and satisfying user needs, and working with the ability to produce
productive productivity. They are the product for the stakeholders' needs. It has been repeatedly
emphasized in other studies.
However, based on the above definitions, the success of software projects can be seen on two
different perspectives: one of the consumer perspectives and one of the developer's views. The
success of our customers' software projects is:

7
 IS 2900 – Project on IT Applications

 Keeping expenses within the budget,

 Meeting the schedule,
 Acquiring the product of acceptable functionality & quality.
The developer ‘s success criteria of the software project are:
 Reaching customer satisfaction confirmed with timely payments,
 Matching the time to market demands
 , c) Building the product of high maintainability and reusability.
 Substantial learning that can be applied to the future projects.

2.2 Analysis of needs

The feasibility study of the Software Requirements obtained in the first step of this step is
considered. At this stage, the development team should communicate with consumers analyze
their needs and systems. A detailed record of this project, such as the design of the project or a
project, has been developed implementation of the system, target dates and implementation of
each phase for the development of the system. This phase is the basis of the software
development process due to another step in the development process of the software the
developmental life cycle will be based on the analysis carried out at this stage.

2.3 System Analysis and Design Systems

This is an important stage in software development. An analysis of the design of the system to
be developed is carried out. In other words, database design, efficient specification, low-level
design documents, high-end design documents, and so on. To prepare these writing documents,
you need to take care of the preparation of these worksheets based on the development stage-
the next step. A well-structured and analyzed plan
Document preparation, which will reduce the time needed for software development in the
development of the life cycle and testing phases.

8
 IS 2900 – Project on IT Applications

2.4 Code Generation

This is the phase where actual development of the software takes place. That is based on the
design documents prepared in the earlier phase. Code is written in the programming technology
chosen. Here, the code is converted into executables in this phase after code generation
2.5 Testing

It is important to ensure that the software provided to ensure the quality of the software is not
faulty. This can be confirmed by checking developed codes. Different tools and
Techniques, immunoassay for testing at different levels, performance tests, stress test, etc.
Depending on the requirement, the selection of test methods and reporting will be faulty. After
this process, check again and restart the system to restart the system. This process keeps track
of the system failure.
2.6 Deployment

This is one of the final stages in the software development cycle. Software is designed to
document internal epigraphs for the maintenance and improvement of this phase.

2.7 Support, maintenance and improvement

The last stage of the software development lifecycle is to provide support and maintenance for
the delivered software. This is a continuous process. New issues have been found with a
changing environment, new dimensions are identified, and new needs identified
You must add to the current software. All this is covered in the software development cycle of
the support phase.
The entire software development cycle is constantly exposed to internal and external risks. At
every stage of the SDLC there are risks and the project manager is responsible for removing or
reducing its impact.

9
 IS 2900 – Project on IT Applications

2.8 Summary

According to the literature above, this research is led to understand the dynamics of
organizational management factors in software projects in investment. The purpose of this
program is to measure the understanding of management and development factors based on
various groups of software and professionals and based on demographic and project
characteristics.

10
 IS 2900 – Project on IT Applications

Chapter 3 Easy Way Project Management System

3.1 Introduction

As we mentioned “Easy Way” Project Management System, We use number of technologies

for our Front End, Back End & Database. We use Angular 7 for Front End. There are lot of
technologies we can use for Front End. But our client request us to use Angular 7 for project.
They told us normally they use to there projects to Angular 7 so they want it.
Angular is a platform that makes it easy to build applications with the web. Angular combines
declarative templates, dependency injection, end to end tooling, and integrated best practices to
solve development challenges. Angular empowers developers to build applications that live on
the web, mobile, or the desktop.
We use for back end part to Spring boot. Client request for use Spring boot for the Back End.
Spring Boot is a project built on the top of the Spring framework. It provides a simpler and
faster way to set up, configure, and run both simple and web-based applications.
For our Data Base part we use MongoDB. It is common one and lot of Company use it for their
Databases. Because it is free available. Client told us we can also use to heruko, My Sql or
MongoDB. Then we decide to use MongoDB. These are the technologies use to design web
application in our project.
Client need to create Mobile Application for this project. Therefore we decide to create Android
App for this Project. Android Studio use for this app development.

11
 IS 2900 – Project on IT Applications

Chapter 4 Analysis and Design

12
 IS 2900 – Project on IT Applications

13
 IS 2900 – Project on IT Applications

14
 IS 2900 – Project on IT Applications

15
 IS 2900 – Project on IT Applications

16
 IS 2900 – Project on IT Applications

17
 IS 2900 – Project on IT Applications

18
 IS 2900 – Project on IT Applications

Implementation
5.1 Introduction
Up to the time of Interim we have implemented the following activities
Android application
For each module we have used software Android Studio and Mongo database
5.1.1Creating account, Authentication and save the data in Database
For authentication we have specially used apilayer.com.
Code

19
 IS 2900 – Project on IT Applications

Figure 5.1.1: Creating account

Login
Code:

20
 IS 2900 – Project on IT Applications

Figure 5.1.2: Login code Segment

5.1.3 Adding user details to the system and save in Database

Code:

21
 IS 2900 – Project on IT Applications

Figure 5.1.3: Adding user details to the system and save in Database

22
 IS 2900 – Project on IT Applications

References

blog.inzpire.lk – NB IOT references

https://developer.android.com/guide/ - Android Development references
https://firebase.google.com/docs/?hl=ru – Firebase database development
http://jsonapi.org/ - JSON development
https://www.arduino.cc/en/Tutorial/UDPSendReceiveString - Send receive string from UDP
http://devdocs.io/node/ - API development using Node.js

23
 IS 2900 – Project on IT Applications

Appendix AND Individual Contribution to the Project

<Appendix A must include a short description by each student about his or her contribution.
You may have several other appendices to refer to further details related to chapters like
Analysis and Design, and Implementation.>

24