A Complete Android Application for

Student Portal System

This project is submitted to the Department of Computer Science & Engineering,
Dhaka International University, in partial fulfillment to the requirements of
Bachelor of Science (B.Sc.) in Computer Science & Engineering (CSE).

Submitted By
Name Reg. No. Roll No.
Md. Abir Ahmed Akash CS-E-53-16-103029 20
Mahmudul Hasan Murad CS-E-53-16-103108 27
Md. Rabbi CS-E-53-16-103116 29
S.M. Fazla Rabbi CS-E-53-16-103142 37
Md. Taraquzzaman Sharif CS-E-53-16-103146 39

Batch: 53rd (2nd Shift), Session: 2016-17

Supervised By
Md. Tahzib-Ul-Islam
Assistant Professor

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

FACULTY OF SCIENCE & ENGINEERING
DHAKA INTERNATIONAL UNIVERSITY
DHAKA, BANGLADESH
JULY-2020
 SUPERVISOR’S STATEMENT
This is to certify that the project paper entitled as “A Complete Android
Application for Student Portal System” submitted Md. Abir Ahmed Akash, Roll
No:- 20; Mahmudul Hasan Murad, Roll No:- 27; Md. Rabbi, Roll No:- 29; S.M.
Fazla Rabbi, Roll No:- 37; Md. Taraquzzaman Sharif, Roll No:-39; from 53rd
batch, 2nd shift has been carried out under my supervision. This project has been
prepared in partial fulfillment of the requirement for the degree of Bachelor of
Science (B.Sc.) in Computer Science & Engineering, Department of Computer
Science & Engineering, Dhaka International University, Dhaka, Bangladesh.

Date: ..... /..... /............. ........................................

(Supervisor’s Signature)
Md. Tahzib-Ul-Islam
Assistant Professor
Dept. of Computer Science & Engineering
Dhaka International University
 APPROVAL
The project report as “A Complete Android Application for Student Portal System”
submitted by Md. Abir Ahmed Akash, Mahmudul Hasan Murad, Md. Rabbi, S.M.
Fazla Rabbi, Md. Taraquzzaman Sharif to the Department of Computer Science &
Engineering, Dhaka International University, has been accepted as satisfactory for the
partial fulfillment of the requirements for the degree of Bachelor of Science (B.Sc.) in
Computer Science and Engineering and approved as to its style and contents.

Board of Honorable Examiners

1. Chairman
......................................................................
Prof. Dr. A. T. M. Mahbubur Rahman
Dean,
Faculty of Science & Engineering,
Chairman,
Dept. of Computer Science & Engineering,
Dhaka International University

2. Internal Member ......................................................................

Associate Prof. Md. Abdul Based
Chairman,
Dept. of Electrical, Electronics &
Telecommunication Engineering,
Dhaka International University
3. Internal Member
......................................................................
Mst. Jahanara Akhtar
Associate Professor,
Dept. of Computer Science & Engineering,
Dhaka International University

3. Supervisor and Member .....................................................................

Md. Tahzib-Ul-Islam
Assistant professor,
Dept. of Computer Science & Engineering,
Dhaka International University

4. External Member .....................................................................

Prof. Dr. Hafiz Md. Hasan Babu
Pro-Vice-Chancellor,
National University of Bangladesh
Ex-Chairman,
Dept. of Computer Science & Engineering,
University of Dhaka
 DECLARATION
We hereby declare that, this project has been carried out by us and it has been
submitted for the award of the Bachelor of Science (B.Sc.) degree. We also certify
that this project was prepared by us for the purpose of fulfillment of the
requirements for the Bachelor of Science (B.Sc.) in Computer Science &
Engineering.

Authors Signature

....................................... .......................................
Md. Abir Ahmed Akash Mahmudul Hasan Murad
B.Sc. In CSE, Roll No: 20 B.Sc. In CSE, Roll No: 27
Reg. No: CS-E-53-16-103029 Reg. No: C-E-53-16-103108
Batch: E-53, Session: 2016-17 Batch: E-53, Session: 2016-17
Dhaka International University Dhaka International University

....................................... ....................................... .......................................

Md. Rabbi
B.Sc. In CSE, Roll No: 29
Reg. No: CS-E-53-16-103116
Batch: E-53, Session: 2016-17
Dhaka International University
S.M. Fazla Rabbi
B.Sc. In CSE, Roll No: 37
Reg. No: CS-E-53-16-103142
Batch: E-53, Session: 2016-17
Dhaka International University
Md. Taraquzzaman Sharif
B.Sc. In CSE, Roll No: 39
Reg. No: CS-E-53-16-103146
Batch: E-53, Session: 2016-17
Dhaka International University

Supervisor’s Signature

Date: ....................................... .......................................

Md. Tahzib-Ul-Islam
Assistant professor
Dept. of Computer Science and Engineering
Dhaka International University
 ABSTRACT

The aim of this project is to develop a mobile based student portal system
application for the standardization of institutional service of educational institute.
The system is an android application that can be accessed throughout the
organization website and outside as well with proper login provided. This system
can be used as an online student service solution of the institute to manage the
student information with regards to placement. Students logging should be able
to upload their information. Admin logging in may also access/search any
information put up by Students. The project has been planned to be having the
view of distributed architecture, with centralized storage of the web database that
exists. The application for the storage of the data has been planned. Using the
web API and retrofit & glide library, the interfaces have been designed. The
database connectivity is planned using the ―api fetch Connection methodology.
The standards of security and data protective mechanism have been given a big
choice for proper usage. The application takes care of different modules and their
associated reports, which are produced as per the applicable strategies and
standards that are put forwarded by the administrative staff.

i|Page
 ACKNOWLEDGEMENTS
We would like to pay our gratitude to the almighty Allah who created us with not
only the ability to design and program this system but also the power of practice.

We would also like to express our sincere thanks to our respected supervisor Md.
Tahzib-Ul-Islam, Assistant Professor, Department of CSE, Dhaka International
University for his continuous encouragement, motivation and professional
guidance during the work of this project. Without his valuable support, this
project could not elevate up this level of development from our point of view.

We would like to thank all the faculty members for their valuable time spent on
requirements analysis and evaluation of the project work. We would like to
express our sincere and cordial gratitude to the people those who have supported
us directly, provided mental encouragement. Evaluated and criticized our work
in several phases during the development of this project and for preparing this
dissertation indirectly. We are also thankful to our family and friends who have
contributed directly or indirectly the development word and its associated
activities.

We warmly thank Prof. Dr. A. T. M. Mahbubur Rahman, Dean, Faculty of

Science and Engineering & Chairman, Department of CSE, Dhaka International
University for their valuable advice and moral support. Their extensive discussion
around work and interesting exploration in operations has been very helpful for
this study.

Finally, we would like to dedicate this project to our teachers for their love,
encouragement and professional guidance throughout the project.

ii | P a g e
 DEDICATION

Dedicated to-

Our Parents
&
Teachers

iii | P a g e
 TABLE OF CONTENTS
ABSTRACT i
ACKNOWLEDGEMENTS ii
DEDICATION iii
TABLE OF CONTENTS iv-vi
LIST OF FIGURES vii

Chapter 1: Introduction Page: 1-5

1.1 Definition of Project 2
1.2 Overview 2
1.3 Taxonomy of Student Portal 3
1.4 Purpose, Scope and Objectives 3
1.5 Project Description 3-4
1.6 Expected Outcome 4
1.7 Advantages 4
1.8 Disadvantages 4
1.9 Accuracy 4
1.10 Motivation 5
1.11 Book Outline 5
Summary 5

Chapter 2: Background Study Page: 6-13

2.1 Feedback from General Student 7
2.2 Feedback from Authority 7
2.3 Conceptual Framework 7-8
2.3.1 Requirement gathering and analysis 8
2.3.2 Design 8
2.3.3 Development/coding 9
2.3.4 Testing and Integration 9
2.3.5 Implementation 9
2.3.6 Maintenance 9
2.4 Android Application Lifecycle Management 9-10
2.5 Back-End Tools 10
2.5.1 Java 10
2.5.2 API 11
2.6 User Interface Tools 11
2.6.1 XML 11
2.6.2 Android Studio 12

iv | P a g e
 2.7 Related Works 12
2.8 Comparative Studies 12
2.9 Application Sector of this Project 12-13
2.10 Challenges 13
Summary 13

Chapter 3: Planning & Requirement Analysis Page: 14-20

3.1 Process Model Planning 15
3.2 Requirement Collection and Analysis 15-16
3.3 Use Case Modeling 16
3.4 Data Flow Diagram 16-17
3.5 ER Diagram 17
3.6 Logical Data Model 18
3.7 External Interface Requirements 18
3.7.1 User Application Interface 18-20
3.7.2 Hardware Interface 20
3.7.3 Software Interface 20
3.8 Functional Requirements 20
Summary 20

Chapter 4: Project Design Page: 21-28

4.1 Access application 22
4.1.1 Login page 22
4.1.2 Register page 22
4.1.3 Profile page 23
4.1.4 Navigation Drawer page 23
4.2 Dashboard 24
4.2.1 Home page 24
4.2.2 Academic Result page 24
4.2.3 Account Details page 25
4.2.4 Notice Board page 25
4.3 Academics 26
4.3.1 Administration page 26
4.3.2 Departments page 27
4.3.3 Students Community page 27
4.4 Info 28
4.4.1 Admission page 28
4.4.2 Contact page 28
Summary 29

v|Page
 Chapter 5: Workflow & Methodology Page: 30-36
5.1 Work flow and Methodology 31
5.2 Activity Lifecycle 31-32
5.3 Application Process Model 32
5.4 Reason of Choosing The Model 33
5.5 Technical Skills Acquired 33
5.6 MVC Design Pattern 33
5.7 Rapid Development 34
5.7.1 Easier Maintenance 34
5.7.2 Stronger Teamwork 34
5.7.3 The Community is there for you 34
5.8 Some Design and Development Tools 34
5.8.1 Common Android Tag 34-35
5.8.2 API use in application 35-36
5.8.3 Navigation Drawer 36
Summary 36

Chapter 6: Conclusion & Future Scope Page: 37-39

6.1 Conclusion and Discussion 38
6.2 Limitations 38
6.3 Future Scope 39
6.4 Security Risks 39
6.5 Scopes for Future Development 39

REFERENCES Page: 40

vi | P a g e
 LIST OF FIGURES
Figure No. Figure Name Page No.

Figure 2.1 Software Development Life Cycle 08

Figure 2.2 Android App Lifecycle Management 10
Figure 3.1 Process Model 15
Figure 3.2 Use Case Model 16
Figure 3.3 Dataflow Diagram 17
Figure 3.4 Entity Relationship Diagram 17
Figure 3.5 Logical Data Model 18
Figure 4.1 App Icon 22
Figure 4.2 login Page 22
Figure 4.3 Register Page 22
Figure 4.4 Profile Page 23
Figure 4.5 Navigation Drawer Page 23
Figure 4.6 Home Page 24
Figure 4.7 Academic Result Page 24
Figure 4.8 Account Details Page 25
Figure 4.9 Statement Page 25
Figure 4.10 Notices (list) Page 25
Figure 4.11 Notices (view) Page 25
Figure 4.12 Administration Page 26
Figure 4.13 Academic council 26
Figure 4.14 Board of Trustees Page 26
Figure 4.15 Syndicate Page 26
Figure 4.16 vice chancellor Page 26
Figure 4.17 Department (list) Page 27
Figure 4.18 Department Information (view) page 27
Figure 4.19 Club & Community Page 27
Figure 4.20 Club’s information (view) Page 27
Figure 4.21 Admission Page 28
Figure 4.22 Contact Page 28
Figure 5.1 Activity Lifecycle 31
Figure 5.2 MVC Design Pattern 33
Figure 5.3 Navigation Drawer 36

[N.B. 2.1 means First Figure of Chapter 2. Similarly, 4.7 means seventh figure of chapter 4.]

vii | P a g e
 CHAPTER

INTRODUCTION
1.1 Definition of Project

1.2 Overview

1.3 Taxonomy of Student Portal

1.4 Purpose, Scope and Objectives

1.5 Project Description

1.6 Expected Outcome

1.7 Advantages

1.8 Disadvantages

1.9 Accuracy

1.10 Motivation

1.11 Book Outline

Summary

1|Page
INTRODUCTION
This document will propose all features and procedures to develop the system. This document
specially containing details about objectives, scope limitation, process model, primary
requirements, team development, possible project risks, project schedule, and finally monitoring
and reporting mechanisms.

In our day to day life we want faster technologies to make our life simple. Without the way of
good communication system in faster technologies via networking part nothing can be able to do
happen. In our daily life we want faster education care system to get more opportunities in our life.
Instead of mobile apps are trending. It is the Era of technology and when it comes to education
care, the computer professionals are required to take prompt decisions and implement them timely
in order to save time and increase efficiency. The use of mobile devices by students has
transformed many aspects of institutional practice. Mobile devices have become common place in
education care settings, leading to rapid growth in the development of student portal applications
for these platforms.

Our application “Student Portal” is a mobile application for educational institute help. This is an
Android based mobile application. Students can easily use the application in their Android mobile
device. All services of educational help student gets in our application. They get services of
account details, academic calendar, notice notification, academic supports and a lot of information.

1.1 Definition of Project

Student Portal is an application of educational help which help student to get all institutional
services easily and educational material as well. The main objective of Student Portal is to provide
institutional services with a word “Log in once, To Stay connected with Institute”. Our project
contain one application Student Portal (user application).

1.2 Overview
“Student Portal: An Android Application for institutional Services” the platform is conceived
as an online based institutional help Android base mobile application. By using our application
people get all services of an educational institute such as looking account details in app and get
details of transactions to recognize and get other information like academic result, routine,
education material in app and notify by authority. Student also can request to any need on directly
massage to authority by using our application and also see current, previous or pending
notifications.

2|Page
1.3 Taxonomy of Student Portal
Users of Student Portal are classified into two categories: Admin, Users. Admin are responsible
for register an information and provide updates. Admin also can check the data list from database.
Users login to Student Portal application with their user name and password provide by authority
or admin and check notifications & information visualized by authority and also edit own profile.

1.4 Purpose, Scopes and Objectives

Student Portal is an innovative institutional help and digital education care platform with a mission
to provide quality institutional services to students when they need it in the most cost-effective
way leveraging technology. Expert IT specialists and caring institutional staff provide you with
exceptional student care.
Objectives:
 To make an easy platform for a students to get any institutional help.
 To notify students from anywhere any time, so it will reduce their valuable time.
 To allow each student for quality institutional and educational service.
 To allow a student to create their profile and keep institutional history.
 To maintain quality of institutional management.

1.5 Project Description

Online student’s service is an all-new way to provide consultations by IT experts. We are
describing an environment of our Student Portal System application. It is a modern solution
educational institution. Connecting everyone and everything in a one platform in our hand while
integrating the system that we already in use at website. Whether, we are a prospect of students,
alumni, stuff, campus provides a personalized experience. Intelligently connecting us with the
most important to university services. Like notice, results, academic information, accounts details,
which keeps track of everything that we need do in one place very easily. Helping a part of institute
management to do things organized and get things done on time. Notices push us relevant
announcements and alerts from campus closures to safety warnings. Helping ensure everyone gets
the massage.

3|Page
Connect students with the systems, people, and updates most important to their success. Bring
together systems, resources, and information in app. It improve student’s engagement, satisfaction,
and retention. This student portal mobile application provide a connected, personalized experience
spanning the lifecycle to impact the things institutions care about most.

1.6 Expected Outcome

 Quality full Institutional help platform.
 Collaboration with Institute, authority and students.
 A rich user list.
 Large database of user and users needed information.

1.7 Advantage
 Hassle-free login and creating an account.
 Student Portal retrieves all of the academic records for students.
 Students can personalize their profile.
 Students can find their information according to their interests.
 It frees from the conventional trends to visit institute website.
 It caches the regular info and refreshes the data in each and every time of use of app.

1.8 Disadvantages
 Users mobile must meet specific technical requirements to be able to take part in Student
Portal.
 The model is more expensive for maintain and hard to customize.

 Student Portal does not work without internet connection.

1.9 Accuracy
The system functionality should ensure that unauthorized cannot complete any function here. Here
need register first. Only admin can approve register.

4|Page
1.10 Motivation
Nowadays internet is available everywhere and day by day it is becoming popular in Bangladesh.
So people are moving towards the online systems rather than conventional systems. Digital
technologies are becoming the essential part of our life. Life is becoming easier day by day. By
using this application students get institutional help. This application performance available
anywhere anytime and made students to gather information easily.

1.11 Book Outline

In this chapter, describes the aim and objectives of this project. Rest of the book organized as
follows:

In Chapter 2, it has been describing the background study of this project.

In Chapter 3, it has been describing about planning and system requirements.
In Chapter 4, it has been describing the overall design and implementation of the project.
In Chapter 5, it has been describing workflow & methodology of the project.
In Chapter 6, it has been describing about outcome and scopes for future enhancement.

Summary
In this chapter, explain the conceptual framework and total overview of the project. The main
objectives and how the full project is designed and how it will be helpful for students and institutes
all are described in this chapter. The rest of the description will explain in next chapter according
to the outline.

5|Page
 CHAPTER

BACKGROUND STUDY
2.1 Feedback from General Student

2.2 Feedback from Authority

2.3 Conceptual Framework

2.3.1 Requirement gathering and analysis
2.3.2 Design
2.3.3 Development/coding
2.3.4 Testing and Integration
2.3.5 Implementation
2.3.6 Maintenance

2.4 Android Application Lifecycle Management

2.5 Back-End Tools

2.5.1 Java
2.5.2 API

2.6 User Interface Tools

2.6.1 XML
2.6.2 Android Studio

2.7 Related Works

2.8 Comparative Studies

2.9 Application Sector of this Project

2.10 Challenges

Summary
6|Page
2.1 Feedback from General Student
Before starting the project, we have talked to general student about the situation and our
institutional process. Most of them told us that it would be very much easier if there exists a mobile
application for finding information about notice, rules & regulations, admission info and updated
with notifications, result and transaction statement.

2.2 Feedback from Authority

In this project, we need to talk with authority persons who willing to give services any time to the
student. For that, we discuss with stuff from the IT team, account section, exam controller. Most
of the teachers said that they could give services and also said that a student finds the information
very easy and can make step accordingly.

2.3 Conceptual Framework

Software Development Life Cycle (SDLC) is a framework that defines the involved in the
development of software at each phase. It covers the detailed plan for building, deploying and
maintaining the software. SDLC defines the complete cycle of development, all the tasks involved
in planning, creating, testing, and deploying a software product. SDLC is a process which defines
the various stages involved in the development of software for delivering a high-quality product.
SDLC stages cover the complete life cycle of a software i.e. from inception to retirement of the
product. Adhering to the SDLC process leads to the development of the software in a systematic
and disciplined manner. In order to design an application, the relational database must be designed
first. Conceptual design can be divided into two parts: The data model and the process model. The
data model focuses on what data should be stored in the database while the process model deals
with how the data is processed [02].

The six phases are-

1. Planning.
2. Analysis.
3. Design.
4. Development or Implementation
5. Testing & Integration.
6. Maintenance [03].

7|Page
In figure 2.1, following six phases in every software development life cycle model has shown.

Figure 2.1: Software Development Life Cycle

2.3.1 Requirement gathering and analysis

Business requirements are gathered in this phase. This phase is the main focus of the project
managers and stake holders. Meetings with managers, stake holders and users are held in order to
determine the requirements like; who is going to use the system? How will they use the system?
What data should be input into the system? What data should be output by the system? These are
gathering these requirements are analyzed for their validity and the possibility of incorporating the
requirements in the system to be development is also studied. Finally, a Requirement Specification
document is created which serves the purpose of guideline for the next phase of the model. The
testing team follows the software Testing Life Cycle and starts the Test Planning phase after the
requirements analysis is completed.

2.3.2 Design
In this phase the system and software design are prepared from the requirement specifications
which were studies in the first phase. System Design helps in specifying hardware and system

8|Page
requirements and also helps in defining overall system architecture. The system design
specifications serve as input for the next phase of the model, how to test.

2.3.3 Development/coding
On receiving system design documents, the work is divided in modules/units and actual coding is
started. Since, in this phase the code is produced so it is the main focus for the developer. This is
the longest phase of the software development life cycle.

2.3.4 Testing & Integration

After the code is developed it is tested against the requirements to make sure that the product is
actually solving the needs addressed and gathered during the requirements phase. During this
phase all types of functional testing like unit testing, integration testing, system testing, acceptance
testing are done as well as non-functional testing are also done.

2.3.5 Implementation
After successfully testing, the product is delivered to the user for their use. As soon as the product
is given to the users they will first do the beta testing. If any changes are required or if any bugs
are caught, then they will report it to the engineering team. Once those changes are made or the
bugs are fixed, then the final deployment will happen.

2.3.6 Maintenance
Once when the users start using the developed system then the actual problems come up and needs
to be solved from time to time. This process where the care is taken for the developed product is
known as maintenance.

2.4 Android Application Lifecycle Management

Android application life cycle management plan contains requirement analysis, scoping and
project and resource plan. In figure 2.2, it seems that android application lifecycle also contain
design, development and integrations, quality assurance, distribute and monitoring and continuous
optimization [04].

9|Page
 Figure 2.2: Android App Lifecycle Management

2.5 Back-End Tools

There are so many back-end tools, we use here Java, API and database. Here is all using tools of
back-end we have is given below:

2.5.1 Java

Java is a general-purpose programming language that is class-based, object-oriented, and designed

to have as few implementation dependencies as possible. It is intended to let application
developers write once, run anywhere (WORA), meaning that compiled Java code can run on all
platforms that support Java without the need for recompilation. Java applications are typically
compiled to bytecode that can run on any Java virtual machine (JVM) regardless of the
underlying computer architecture. The syntax of Java is similar to C and C++, but it has fewer low-
level facilities than either of them. As of 2019, Java was one of the most popular programming
languages in use according to GitHub, particularly for client-server web applications, with a
reported 9 million developers [05].

10 | P a g e
2.5.2 API

Application program interface (API) is a set of routines, protocols, and tools for building software
applications. An API specifies how software components should interact and APIs are used when
programming graphical user interface (GUI) components. An API is a type of program that
contains code for use in applications. This code normally allows to add certain functionalities to
your application. There is usually a documentation that comes along with that code and it explains,
how to actually use that code. Most times we'll have to follow a certain protocol before using the
API. The Android API refers to the collection of various software modules which make up the
complete Android SDK. In simpler words the Android API or Android SDK or just plain simple
Android basically refers to the same thing. Since the software you write yourself interacts with the
Android software to do various things, so the Android part is like an API [06].

2.6 User Interface Tools

There are so many user interface tools, we use here XML and Android Studio. Here is using tools
of back-end we have is given below:

2.6.1 XML

Extensible Markup Language (XML) is a markup language that defines a set of rules for
encoding documents in a format that is both human-readable and machine-readable. The World
Wide Web Consortium's XML 1.0 Specification of 1998 and several other related specifications
all of them free open standards define XML. The design goals of XML emphasize simplicity,
generality, and usability across the Internet. It is a textual data format with strong support
via Unicode for different human languages. Although the design of XML focuses on documents,
the language is widely used for the representation of arbitrary data structures such as those used
in web services. Several schema systems exist to aid in the definition of XML-based languages,
while programmers have developed many application programming interfaces (APIs) to aid the
processing of XML data [07].

11 | P a g e
2.6.2 Android Studio
The easiest way to get started with developing Android applications is to download the Android
Studio application suite. We can download a copy of Android Studio for a preferred platform
(Windows®, Mac OS X, or Linux) from the Android developer’s site.

Android Studio includes tools for managing multiple platform-specific features with the SDK
manager and the ability to test your application on either a real device or the emulator.

There are older generations of development tools, including Android Developer Tools (ADT),
which is the predecessor to Android Studio, and Eclipse with an Android Developer Tools plug-
in, which was the predecessor to ADT. In essence, Android Studio is the third generation of the
Android Integrated Developer Environment (IDE). There are also command-line tools and various
continuous integration tool chains that permit the building of Android applications [08].

2.7 Related Works

In our country and see other countries worldwide how they provide this kind of service through a
mobile application. We followed many apps like campusapp, rgnulerp.org etc. we collected
information from a various app, how they develop and maintain the institutional service, what do
they expects from this kind of system.

2.8 Comparative Studies

We have seen many websites and application that how they provide this service. We found a couple
of websites and application those who are providing this kind of service and we found some
drawback of them. Most of them provide paid service and most of them have some limited services.
But our application will have all the services and it will be flexible for that kind of purpose [09].

2.9 Application Sector of this Project

 Student Portal application is designed for all kind of educational institute and
in future, it will be available for anyone.
 The system handles all the operations and generates information as soon as in
the database, which includes required information for users.

12 | P a g e
  Allow students to see or display his/her all information after login.
 The service of Student Portal is fully online [01].

2.10 Challenges
Here are some challenges which are difficult to overcome. The main challenge is continuous
development of the application according to the global requirement of educational institute. On
the other hand, student of developing country like Bangladesh are not so concerned about internet
& application. Sometimes it is a matter of time consuming to engage them with new system.

Summary
Background the information identifies and describes the history and nature of a well-defined
research problem with reference to the existing literature. The background information should
write down the root of the problem being studied, proper context of the problem with theory,
research, and practice. Its scope, and the extent to which earlier studies have successfully
investigated the problem, noting, in particular, where gaps exist that our study attempts to discuss.

13 | P a g e
 CHAPTER

PLANNING & REQUIREMENT ANALYSIS

3.1 Process Model Planning

3.2 Requirement Collection and Analysis

3.3 Use Case Modeling and Description

3.4 Data Flow Diagram

3.5 ER Diagram

3.6 Logical Data Model

3.7 External Interface Requirements

3.7.1 User Interface

3.7.4 Hardware Interface

3.7.5 Software Interface

3.8 Functional Requirements

Summary

14 | P a g e
3.1 Process Model Planning
In our application admin allows to register the user and provide information about login and
maintain the system. By using these this information user login and take part in student portal
service application. The following figure 3.1 shows the process model planning [10].

3.2 Requirement Collection and Analysis

Project must be planned and executed to process data timely and create viable solutions that are
both relevant and realistic. To meet these goals, every project must begin with a fully vetted and
approved requirement specification. This project is a complex project requirements are typically

15 | P a g e
multifaceted, covering technical, financial and operational elements and are also perception, bias
and stakeholder interests. As such requirements collection process must incorporate and address
all these realistic to identify requirements at all levels and perceptions.

3.3 Use Case Modeling

The Use Case Model describes the proposed functionality of the new system. A Use Case
represents a discrete unit of interaction between a user and the system. The use case model is
necessary to give a top view of our proposed system and make me understand how the system will
be working. The following figure 3.2 shows the use case model of this application [11].

User register

Give
Permission

Manage
Database
User Admin

System
Login

Test

Figure 3.2: Use Case Model

3.4 Data Flow Diagram

A data-flow diagram (DFD) is a way of representing a flow of a data of a process or a system
(usually an information system). The DFD also provides information about the outputs and inputs

16 | P a g e
of each entity and the process itself. A data-flow diagram has no control flow, there are no decision
rules and no loops. The data-flow diagram (level-1) of this project is shown in figure 3.3 [12].

Register/Login User

Get information

Database

Register/Login Admin
approval

User
Requests

Figure 3.3: Dataflow Diagram

3.5 Entity Relationship Diagram

An entity relationship model, also called an entity-relationship (ER) diagram, is a graphical
representation of table and fields information. Entities and their relationships to each other,
typically used in computing in regard to the organization of data within database or information
systems. An entity is a piece of data-an object or concept about which data is stored. We represent
graphically the all database table using entity, Attribute and process which is shown in below in
figure-3.4 [13].

Figure 3.4: Entity Relationship Diagram

17 | P a g e
3.6 Logical Data Model
A logical data models represents the structure of a domain of information. They are diagrammatic
in nature and are most typically used in model processes that seek to capture think of importance
to an organization and how they relate to one another. Once validated and approved, the logical
data model become the basis of a physical data model and form the design of a database. Following
figure 3.5 shows logical data model of our system.

User
+ Name: Char
+ Email: Char
+ Contract No: Integer
+ Password: Integer

Admin
+ID: Integer
+ Email: Char
+ Password: Integer

Figure 3.5: Logical Data Model

3.7 External Interface Requirements

3.7.1 User Application Interface

*Login Screen:
Various buttons and fields available on this screen will be:

-Email field
-Password field
-Login button

18 | P a g e
-Register button
*Register Screen:
Various buttons and fields available on this screen will be:
-Course Name
-Batch
-Class Roll
-Registration Phone Number
-Register button
-Login button
*Home Screen:
Various buttons available on this screen will be:
-Navigation drawer
-Massage
-setting
-logout
*Navigation Drawer Screen:
Various buttons available on this screen will be:
Dashboard
- Home (button)
- Class Routine (button)
- Notice Board (button)
- Account Details (button)
- Academic Result (button)
- Academic Calendar (button)
Academics
- Administration (button)
-Academic council (button)
-Board of trustees (button)
-Syndicate (button)
-Vice Chancellor (button)
- Departments (button)

19 | P a g e
 - Students Community (button)
Info
- Admission (button)
- Contact (button)
- Rules & Regulations (button)

3.7.4 Hardware Interface

Any Android based mobile phone with version minimum Android 4.0.3 (IceCreamSandwich).
Higher version will be accepted.

3.7.5 Software Interface

-Any windows based operating system.

-Web Database
-Android Studio

3.8 Functional Requirements

This section gives a functional requirement that applicable to the Student Portal System
application.
There are three two modules in this phase.
- User module.
- Admin module (web).

Summary
The chapter describes the features and behavior of a system or software application. It includes a
variety of elements that attempts to define the intended functionality required to satisfy users. In
addition to specifying how the system should behave, the specification also defines at a high-level
the main processes that will be supported, what simplifying assumptions have been made and what
key performance parameters will need to be met by the system.

20 | P a g e
 CHAPTER

Project Design
4.1 Access application
4.1.1 Login page
4.1.2 Register page
4.1.3 Profile page
4.1.4 Navigation Drawer page

4.2 Dashboard
4.2.1 Home page
4.2.2 Academic Result page
4.2.3 Account Details page
4.2.4 Notice Board page

4.3 Academics
4.3.1 Administration page
4.3.2 Departments page
4.3.3 Students Community page

4.1
4.4 Introduction
Info
4.4.1 Admission page
Our project
4.4.2design
Contactandpage
develop in Android studio. Design layout are .xml file. Layout created for
design purpose. Here we design in two away by coding or drag and drop component. Develop the
Summary
application in java file.

21 | P a g e
4.1 Access application
4.1.1 Login page
When you click in app icon its passes an activity of a log in form.
In the form two field, one is email, another is password. Here also
two button login and register. Figure 4.1 is app icon view & 4.2
describes well the login page views.

Figure 4.1: App Icon Figure 4.2: login Page

4.1.2 Register page

Figure 4.3 is the accurate view of Register page. From sign in page when click in create account
button, it goes to the register activity form. In the activity there are few field such as registration
number, class roll, registration phone number etc. Also contain a login button for back into log in
form.

22 | P a g e
4.1.3 Profile

When users click on profile from navigation drawer, an activity open with login user’s information
with text view. In figure 4.4, displayed all the information like- institute provide info as- roll, reg.,
session-year and personal info as- phone number, gender, address, nationality etc.

4.1.4 Navigation Drawer page

When user login in the application there enable navigation drawer. In this navigation drawer there
are some option menu with some sub-menus. As figure 4.5 the menus are-dashboard, Academics,
Info etc.

23 | P a g e
4.2 Dashboard
4.2.1 Home page

When you click in our application then open home page with various options and a notification
view on upper part. In this page here some advertise for the admission candidate. And a messaging
button for direct massage to the admin panel. Figure 4.6 shows home page view on the right
context.

4.2.2 Academic Result page

When you slide the navigation drawer and click the academic result option from dashboard, then
open home page like-figure 4.7 with various semester result and an average result view on upper
part. In this page, results have shown as credit, letter grade, scgpa, cgpa, total subjects and the
result status as passed or failed according to the institutional rules.

24 | P a g e
4.2.3 Account Details page
When you click the account details option from dashboard and then it opens a page like-figure 4.8
with account summery. For more details, have to click on view transection button. It will reach
you a page as figure 4.9, where transections are shows as a statement with a particular parameter
such as- date, receipt, purpose and amount.

4.2.4 Notice Board page

When you click the notice board option from dashboard and then it opens a page like-figure 4.10
with notices (list). For view the notice, have to click on any of notice from the list according to
own choice or priority. It will reach you a page as figure 4.11, where notices (view) are shows as
an image.

25 | P a g e
4.3 Academics
4.3.1 Administration page

When you click the administration option from academics menu and then it opens a page like-
figure 4.12 administration. For view the list of administration’s parts, have to click on any of notice
from the button own choice. It will reach you a page as figure 4.12, figure 4.13, figure 4.14, 4.15
and figure 4.16, where list of the respected members of academic council, board of trustees,
syndicate and vice chancellors are shows in a dropdown slides view.

26 | P a g e
4.3.2 Departments page

When you click the departments option from academics menu and then it opens a page like-figure
4.17. Here can view the list of departments. Then have to click on any of department from the list
by own choice. It will reach you a page as figure 4.18, where selective department’s information
are viewed as slides view.

4.3.2 Students Community page

When you click the student’s community option, then it opens a page like figure 4.19. Here can
view the list of student’s club and community. Then have to click on any of club from the list by
own choice. It will reach you a page as figure 4.20, where selective club’s information are available
as slides view.

27 | P a g e
4.4 Info
4.4.1 Admission page

Figure 4.21 describe the information about admission. When you click the admission option, then
it opens a page like to the figure below. Here can view the admission eligibility with required
documents.

4.4.1 Contact page

When you click the contact option, then it opens a page like figure 4.22. Here can view the contact
information about the authority. The information categorized according to difference of the
campus places and needs.

28 | P a g e
Summary
This chapter named project design and it describes the user interface of an application. Typically
involves those objects that a user sees and interacts with directly on their screen. However, the
user interface of an application is only one aspect of the overall user experience. Other aspects of
the user experience that are not visible to the user, but are integral to an application and critical to
its usability, include start up time, latency, error handling, and automated tasks that are completed
without direct user interaction.

29 | P a g e
 CHAPTER

WORKFLOW & METHODOLOGY

5.1 Work flow and Methodology

5.2 Activity Lifecycle

5.3 Application Process Model

5.4 Reason of Choosing The Model

5.5 Technical Skills Acquired

5.6 MVC Design Pattern

5.7 Rapid Development

5.7.1 Easier Maintenance
5.7.2 Stronger Teamwork
5.7.3 The Community is there for you

5.8 Some Design and Development Tools

5.8.1 Common Android Tag
5.8.2 API use in application
5.8.4 Navigation Drawer

Summary

30 | P a g e
5.1 Work Flow and Methodology
We are created an institutional service application, which is Student Portal. The application will
have all of the capabilities of serve the institutional support such as students.diu.ac or any other
institute. Thought this application will provide services and maintenance by admin.

5.2 Activity Lifecycle

As a user navigates through, out of, and back to app, the activity instances in app transition through
different states in their lifecycle. The activity class provides a number of callbacks that allow the
activity to know that a state has changed. Figure 5.1 indicates that the system is creating, stopping,
or resuming an activity, or destroying the process in which the activity resides [14].

Figure 5.1: Activity Lifecycle

31 | P a g e
onCreate():
Called when the activity is first created. This is where we should do all of our normal static set up:
create views, bind data to lists, etc. This method also provides us with a bundle containing the
activity's previously frozen state, if there was one. Always followed by onStart().
onRestart():
Called after our activity has been stopped, prior to it being started again. Always followed by
onStart().
onStart():
Called when the activity is becoming visible to the user. Followed by onResume() if the activity
comes to the foreground.
onResume():
Called when the activity will start interacting with the user. At this point our activity is at the top
of the activity stack, with user input going to it. Always followed by onPause().
onPause ():
Called as part of the activity lifecycle when an activity is going into the background, but has not
(yet) been killed. The counterpart to onResume(). When activity B is launched in front of activity
A, this callback will be invoked on A. B will not be created until A's onPause() returns, so be sure
to not do anything lengthy here.
onStop():
Called when we are no longer visible to the user. We will next receive either onRestart(),
onDestroy(), or nothing, depending on later user activity. Note that this method may never be
called, in low memory situations where the system does not have enough memory to keep activity's
process running after its onPause() method is called.
onDestroy():
The final call we receive before our activity is destroyed. This can happen either because the
activity is finishing (someone called finish() on it, or because the system is temporarily destroying
this instance of the activity to save space. we can distinguish between> these two scenarios with
the isFinishing() method.

5.3 Application Process Model

A process model is chosen based on the nature of the project and application, the methods and
tools to be used, and the control and deliverables that are required.

32 | P a g e
5.4 Reason of Choosing the Model
The first increment is a core product. That is basic requirements are addressed, but many
Supplementary features remain undelivered. A plan is developed for the next increment. The plan
consists of modification, additional features and functionality, repeated following the delivery of
each increment, until the complete product is produced.

5.5 Technical Skills Acquired

This project has provided us a wonderful opportunity to acquire various technological skills.
Though it may take some more time to master those skills, at this moment. We are confident to
apply them in any of our projects. Some of the significant technical aspects that we have handled
during the project.

5.6 MVC Design Pattern

Model-View-Controller (usually known as MVC) is an architectural pattern commonly used for
developing user interfaces that divides an application into three interconnected parts. This is done
to separate internal representations of information from the ways information is presented to and
accepted from the user. The MVC design pattern decouples these major components allowing for
efficient code reuse and parallel development. Interactions within the MVC pattern are depicted
in figure 5.2 below.

Figure 5.2: MVC Design Pattern

Traditionally used for desktop graphical user interfaces (GUI), this architecture has become
popular for designing web applications. Popular programming languages like java, c#, python,
Ruby, and PHP have MVC frameworks that are used in web application development straight out
of the box [15].
33 | P a g e
5.7 Rapid Development
In today's startups based on experimentation, rapid prototyping, and getting our minimum viable
product out in the world as fast as possible, development speed is fast.
Android Studio selects the best implementations to common problems from the open-source
community and building on top of them provides us with an application architecture to guide our
development.

5.7.1 Easier Maintenance

By providing a sound structure for our application and nudging us towards software development
best practices and patterns, android studio guides us towards writing code that is loosely coupled
and repeats itself as little as possible. In other words, it's easy to read, test, maintain, and develop
further.

5.7.2 Stronger Teamwork

As a developer, to know used classes and functions by heart and can use them easily. But as we
bring in team members, the situation changes.

5.7.3 The Community is there for you

Finally, a significant benefit of using Android Studio comes from the active communities of
developers and users that gather around them.

5.8 Some Design and Development Tools

We are using some open source design and development tools for developed our application.
Bellow some open source tools description.

5.8.1 Common Android Tag

int describeContents()
-Describe the kinds of special objects contained in this parcelable instance's
marshaled representation.
byte[] getId()
-Get the Tag Identifier (if it has one).

34 | P a g e
 String[] getTechList()
-Get the technologies available in this tag, as fully qualified class names.
String toString()
-Human-readable description of the tag, for debugging.
void writeToParcel(Parcel dest, int flags)
-Flatten this object in to a Parcel.

5.8.2 API use in application

Get the API key. We must have at least one API key associated with our project. An API that has
data in JSON format from where we will fetch [16].
To use an API:
 Create a list view XML file which has a list that will show when we finish it.
 Create an XML file; it will have the element which we want to show in our list. That
means in a section of list what we want to show meant TextView, ImageView and so
on.
 Now we will go to the main activity where we will find how to fetch data from API.
There we should understand two things when we are going to work on networking. We
could not do this on main thread so we will use AsyncTask and we have to get response
from network as it is the response of request.
 AsyncTask- It is nothing but a thread to do process in background and show result in
UI. This is because when we do all network process in the main thread that will crash
the application so we will use this.
 Response in our main activity; there is a code as in the following,
 In our async Task we will get Adapter class which have set adapter method in the
following Adapter. We will make our custom adapter here.
 Adapter class is abstract class in android so we have to implement all our methods
given in that class or make it abstract but we will implement all methods. The method
getview is important because we will write code here to show the second XML file.
 Layout info later class is here to take XML element into android or in scr type to which
we will set our required field. To load image from internet our adapter and the entire
code for this is given in zip file where we have other adapter service handler and

35 | P a g e
 different file for same task. We have not represented it here because it will create
redundancy, so Adapter class for Load image is here.
 View holder class is used to create a static instance of the ViewHolder and attach it to
the view item the first time it is loaded, and then it will be retrieved from that view tag
on the future calls. As we know getView() method is called very frequently, especially
when lots of elements in the listview to scroll, in fact, it is called each time a listview
item becomes visible on scroll.
 We have implemented the data model class in which we write the set and get method.
This will help us to get the element of the array list made very easy and manage projects
and help in the future to handle the project.

5.8.4 Navigation Drawer

The navigation drawer is a UI panel that shows app's main navigation menu. According to figure
5.3, the drawer appears when the user touches the drawer icon in the app bar or when the user
swipes a finger from the left edge of the screen [17].

Summary
This chapter describes well about the workflow and methodology. Where technological skill
requirement is set. Here model-view-controller, activity lifecycle and API briefly discussed. API
uses process is followed in step by step. Following chapter also classifies the design pattern and
some development tools with common development tags of android.

36 | P a g e
 CHAPTER

CONCLUSION & FUTURE SCOPE

6.1 Conclusion and Discussion

6.2 Limitations

6.3 Future Scope

6.4 Security Risks

6.5 Scopes for Future Development

37 | P a g e
Outcomes
It has been a great pleasure for us to work on this exciting and challenging project. This project
proved good for us as it provided practical knowledge of not only programming in java and android
based application, but also about all handling procedure related with “A Complete Android
Application for Student Portal System”. It also provides knowledge about the latest technology
used in developing web-enabled application and android technologies that will be great demand in
future. This will provide better opportunities and guidance in future in developing projects
independently.

6.1 Conclusion and Discussion

Today, almost 90% plus student have mobile devices in their palms as communication technology.
Instead of websites, mobile apps are trending. It is the Era of technology and when it comes to
institutional services and educational care, the institution managements are required to take prompt
decisions and implement them timely in order to fast the information and data pass process. So
here we discussed how the application is helping the educational society as a whole in providing
accurate and prompt services to the students.
These are widely and whole heartedly accepted by society and this happens with only such
facilities which are actually helpful. This application has become the need of the hour as they have
facilitated many students. It has made complex tasks easier and is proved to be beneficial in
decision making without any lapse or error.
We came to know that how the Student Portal application is providing several options which are
not only beneficial to the student but also standard for several facilities which are provided in the
institution. The app is beneficial to not just the students and the institute’s staff and the whole
authority.

6.2 Limitations
 Without create a profile one can’t access the Application services.
 Admin reserve the whole permission to access all steps of this application.
 No live communication panel (As like Live chat).
 App can’t run without internet.

38 | P a g e
6.3 Future Scope
 This can be used in all kind of educational institution as well as in corporate world.
 Can be used anywhere any time as it is a web connected application.
 Design to facilitate administrator and user.
 Add live communication system.
 Create an administrator app.

6.4 Security Risks

Users use the application via a network and that connectivity comes with its own security risks.
Otherwise, not only the user’s registered data but also all of the data is centrally stored in a
dedicated university website linked database. If the software is not kept up to date, or if it is updated
incorrectly, security breaches can occur. Depending on the nature of the business, those security
breaches could involve highly sensitive and protected information, including transaction statement
or bank account information.

6.5 Scopes for Future Development

This project made here only for android mobile application. In future, this project will develop for
different platform. In this project, modern technology will be followed as well as the global
institutional needs and standard.

39 | P a g e
 REFERENCES
[01] App without internet- https://www.opensourceforu.com/2017/01/mobile-app-without-internet [last
accessed time: 22.06.20, 02:32 pm]

[02] SDLC- https://www.guru99.com/software-development-life-cycle-tutorial.html [last accessed time:

09.07.20, 10:17 am]

[03] SDLC Step- https://stackify.com/what-is-sdlc [last accessed time: 09.07.20, 10:23 am]

[04] Activity Lifecycle-https://www.w3adda.com/android-tutorial/android-activity-lifecycle [last

accessed time: 01.07.20, 10:33 am]

[05] Java-https://en.wikipedia.org/wiki/Java_(programming_language) [last accessed time: 09.07.20,

10:37 am]

[06] API-https://www.quora.com/What-is-API-for-android-mean-What-software-apps-do-I-need-to-do-
an-API-programming-Is-there-any-website-for-tutorial [last accessed time: 09.07.20, 10:45 am]

[07] XML-https://en.wikipedia.org/wiki/XML [last accessed time: 01.07.20, 10:48 am]

[08] Android Studio-https://en.wikipedia.org/wiki/Android_Studio [last accessed time: 09.07.20,

10:52 am]

[09] Comparative Studies- https://www.researchgate.net/publication/327992809_Comparative_Study_

of_Mobile_Applications_Testing_Techniques_for_Context_Events [last accessed time: 01.07.20,
4:30 pm]

[10] Process Model-https://www.igi-global.com/dictionary/adaptive-exception-management-uncertain-

environments/23587 [last accessed time: 10.07.20, 11:00 am]

[11] Use Case- http://www.utm.mx/~caff/doc/OpenUPWeb/openup/guidances/concepts/use_case_model

_CD178AF9.html [last accessed time: 09.07.20, 4:53 pm]

[12] DFD-https://en.wikipedia.org/wiki/Data-flow_diagram [last accessed time: 06.07.20, 09:40 am]

[13] ER Diagram-https://beginnersbook.com/2015/04/e-r-model-in-dbms [last accessed time: 10.07.20,

11:20 am]

[14] Activity Manage-https://www.javatpoint.com/android-life-cycle-of-activity [last accessed time:

1.06.20, 10:37 am]

[15] MVC-https://www.geeksforgeeks.org/mvc-design-pattern [last accessed time: 01.07.20, 10:17 am]

[16] Use API- https://www.c-sharpcorner.com/UploadFile/9ab05e/how-to-fetch-data-from-web-api-in-

android [last accessed time: 01.07.20, 05:10 pm]

[17] Navigation-https://developer.android.com/guide/navigation/navigation-ui [last accessed time:

09.07.20, 09:40 am]

40 | P a g e