MAHARASHTRA STATE BOARD OF TECHNICAL

EDUCATION

VIVEKANAND EDUCATION SOCIETY’s

POLYTECHNIC
Capstone Project Diary (Log Book)

Academic year: 2022- 2023

Program: Computer Engineering

Program code: CO6I
Course: Capstone Project Diary (Log book)
Course code: 22060

1
 INDEX

Academic year: 2022-23 Name of the faculty: Vaishali Bodhale

Program code: CO6I Course & code: Capstone Project Diary (22060)

Roll No: 45 Enrollment No: 2000040379

Semester: 6th Name of the Candidate: Vedant Navani

Sr. No. Week Activity to be performed Page no.

1 1st Defining scope and requirement analysis 3

2 2 nd Planning the process flow 4

rd
3 3 and 4th User Interface design 5

th
4 5 and 6th Front End Development (coding) 6

th th
5 7 and 8 Back End Development (database designing) 7

th th
6 9 and 10 Integration of API 8

th th
7 11 and 12 Testing of the application and bug resolving 9

th
8 13 Paper Publication and Final Presentation 10

9 14th Final Project Report Submission 11

2
Week no:- 1

Activities Planned:-Defining scope and requirement analysis

Activities Executed:-

1. The first step is to identify the overall goals and objectives of the project. In this case, the
goal is to create Application for Music Player System.
2. The next step is to identify the stakeholders who will be involved in the project, such as the
project team and also the target audience.
3. Based on the goals and objectives of the project, define the features and functionalities that
the Application should have. This could include features such as creating albums, creating
playlist, having left right audio balance, background Image and a powerful UI.
4. Determine the technology stack that will be used to build the application. This could
include android, frameworks, databases, and other tools.

Reason for delay if any:- No Delay.

Corrective measures adopted:-

1. The purpose of the application is to provide users with a convenient and easy-to-use
platform for listening to music.
2. The application should have a responsive design that works well.

Remark :-

Signature of the Guide:-

Week no:- 2

3
Activities Planned:- Planning the process flow

Activities Executed:-

1. The first step in the process flow would be user registration. Users would need to create
an account on the application to access the various features and functionalities.
2. Once the user has registered, they can play any song by searching and creating playlists.
3. User can listen to it by single ear by using left right audio balance feature.
4. User can create playlist and albums of their choices and the songs will play in queue.

Reason for delay if any:- No Delay

Corrective measures adopted:-

1. Break down the process flow into smaller steps & identify the dependencies between them.
2. Look for opportunities to optimize the process flow and reduce the number of steps where
possible.

Remark :-

Signature of the Guide:-

Week no:- 3 & 4

4
Activities Planned:- User Interface design

Activities Executed:-

1. The user interface should be simple, making it easy for users to navigate and complete
tasks.
2. The interface should be responsive and work well on all devices.
3. Design an easy-to-use navigation system that helps users find the songs or album they are
looking for quickly.
4. Create a visual hierarchy in the design, placing important information and features and
clearly.
5. Provide feedback to users when making a payment. This helps to build trust and
confidence in the application.

Reason for delay if any:- No Delay

Corrective measures adopted:-

1. Conduct user research to understand their needs, preferences, and main points. This will
help you design an interface that meets their requirements.
2. Simplify the design by removing unnecessary elements and reducing confusion. Focus on
the core features and functions that users need to accomplish their goals.

Remark :-

Signature of the Guide:-

Week no:- 5 & 6

5
Activities Planned:- Front End Development (coding)

Activities Executed:-

1. Ensure that the front-end design is responsive, and works well on all devices including
desktops and laptops.
2. Use optimized images, and avoid using unnecessary items.
3. Testing your app on a physical device or emulator can help you catch bugs and issues
early on. Android Studio comes with an emulator that you can use to test your app on
different Android versions and device configurations.
4. Use a style guide to maintain consistency across the application, and ensure that the UI
elements are designed and coded consistently..
5. Test the code thoroughly to ensure that it works as expected, and is bug-free.

Reason for delay if any:- No Delay

Corrective measures adopted:-

1. Optimize the code for speed, and minimize the load time of the application.
2. Simplify the code structure, and make it more maintainable.
3. Improve accessibility by ensuring that the application is accessible

Remark:-

Signature of the Guide:-

Week no:- 7 & 8

6
Activities Planned:- Back End Development (database designing)

Activities Executed:-

1. Determine the requirements for the database, including the data to be stored, the
relationships between different entities, and the performance requirements.
2. Choose a database management system (DBMS) based on the requirements, such as
FireBase.
3. Design the database schema based on the requirements, including creating tables, defining
relationships, and determining the data types for each field.
4. Implement security measures such as data encryption, access control, and regular backups to
ensure the security and integrity of the data.
5. Optimize the queries to improve the performance of the database, including using joins,
avoiding subqueries, and using stored procedures.
6. Test the database to ensure that it meets the requirements and is free of errors.

Reason for delay if any:- No Delay

Corrective measures adopted:-

1. The database schema removes redundant data, simplifies the relationships between entities,
and makes it more maintainable.
2. Use the appropriate (DBMS) based on the requirements of the application, such as FireBase.
3. Implement load balancing techniques to distribute the load across multiple database servers,
and improve the scalability and availability of the application.

Remark:-

Signature of the Guide:-

Week no:- 9 & 10

7
 Activities Planned:- Integration of API

Activities Executed:-

1. Choose an API that fits your needs and requirements. There are many APIs
available for different purposes such as payment gateways, social media platforms,
weather data, and more.
2. Most APIs require you to register for an API key to access their services. Follow
Week no:- 11 &provider's
the API 12 documentation to register and obtain an API key.
3. Use the API data in your application's UI or business logic. if you integrate a
Music Player API, you can display the songs and playlists in your app's UI.
Activities Planned:-anTesting
4. Integrating API ofcantheprovide
application
yourandapplication
bug resolving
with access to additional
functionality that you might not have been able to implement on your own. For
example, integrating a payment gateway API can allow your application to process
payments
Activities securely and efficiently.
Executed:-

1. Install the newly created app on an Android device or emulator.

Reason
2. Testfor
thedelay
basiciffunctionality
any:- of the app, such as opening the app, navigating
through the different screens, and playing a song.
3. Test the playback controls, such as play, pause, and skip buttons. Check if the
playback
Corrective controls adopted:-
measures are working correctly.
4. Test the volume controls, such as increasing or decreasing the volume while a
APIsong is playing.
requests Check
can fail if the volume
for various reasons,controls
such asare functioning
network issues as
or intended.
invalid API keys.
5. Test the app on different devices, such as phones and tablets,
Handle these errors gracefully in your app by displaying an error message to ensure
to that the
the user
andapp is responsive
providing optionsand looksthe
to retry good on all
request ordevices.
take alternative actions.
6. If any bug arises, identifying the bug and understanding the root causes of how to
fix it
Remark :-

Reason for delay if any:-

Signature of the Guide:-

Corrective measures adopted:-

1. If any bug arises , identifying the type of bug and how to fix it
2. Resolving the bug by identifying the root causes of it

Remark :-

8
Signature of the Guide:-
Week no:- 13

Activities Planned:- Paper Publication and Final Presentation

Activities Executed:-

1. Published the paper and submitted the certificates and paper to our respective
mentors.
2. Performed Final presentation of our project Application of Music Player
System

Reason for delay if any:-

Corrective measures adopted:-

Remark :-

Signature of the Guide:-

9
Week no:- 14

Activities Planned:- Final Project Report Submission

Activities Executed:-

Submitted the final Report to our respective mentors.

Reason for delay if any:-

Corrective measures adopted:-

Remark :-

Signature of the Guide:-

10