The document outlines a software engineering project for a Jukebox desktop app designed for offline music streaming, highlighting features such as user-friendly interface, playback control, and customization options. It discusses constraints like limited local music access and storage requirements, alongside non-functional requirements focused on usability and performance. The team emphasized effective communication, collaboration, and time management as key lessons learned during the project development.

1. Fundamentals of
Software Engineering
Group Members:
Abdul Moiz 22l-7468
Affan Malik 22l-7533
M.Fahad Hussain 22l-7463
Noveen Leghari 22l-7495

2. JukeBox
A desktop app!!!

3. Abdul Moiz
Work Divison
M.Fahad Hussain
Affan Malik
Noveen Leghari
Team Lead, Developer
Requirment Elicitation
Tester
Software design

4. Project Introduction
Juke Box:
• Offline music streaming app
• Enjoy favorite tunes without internet
• User-friendly interface
• Access music anytime, anywhere

5. Advantages:
Offline Music Streaming: Listen to music without internet, enhancing accessibility.
User-Friendly Interface: Seamless navigation for enjoyable music experiences.
Customization: Import songs, mark favourites for personalized experience.
Playback Control: Play/pause, skip, adjust volume, loop, and shuffle for full control
Lyrics Display: View song lyrics for enhanced listening experience.

6. Constraints:
• Limited to Local Music: App plays only locally stored music, limiting library.
• Storage Space Requirement: Requires ample device storage for music files.
• Metadata Management: Accuracy depends on imported song metadata.
• Offline Limitations: Initial import and updates may need internet.
• Compatibility Concerns: Features may be limited by device specs.

7. Non-functional Requirments
Interface must be intuitive,
requiring minimal training
for new users.
System should operate
efficiently with no delays in
data display or operations.
Performance Usability

8. Software Design
Class Diagram
Activity Diagram

9. Sequence Diagram
Use Case Diagram

10. Level 1
Level 0
Data Flow Diagram

11. Level 2

12. Architecture
Repository Architecture

13. Actual Implementation Screenshots

14. Actual Implementation Screenshots

15. Actual Implementation Screenshots

16. Actual Implementation Screenshots

17. Actual Implementation Screenshots

18. Actual Implementation Screenshots

19. • Effective Communication: Regular updates kept the team on
track and solved problems, helping us stay focused on our project
goals
• Collaboration: Using our individual strengths improved our
efficiency and problem-solving, creating a great team environment.
• Time Management: By setting achievable deadlines and
arranging tasks, we were able to reach project milestones on time
Lesson Learnt!!

20. Thanks!!!!