Teacher Evaluation Sheet

Name of Student: Borse Shubham Sanjay

Enrolment No: 2100790204
Name of Program: Computer Technology Semester:- IV
Course Title: Software Engineering Code: -22413
Title of the Micro Project: Mobile Shopee Management System

Course Outcomes Achieved:-

CO-a. Select suitable Software Process model for software development.

CO-b. Prepare software requirement specifications.
CO-c. Use Software modeling to create data designs.
CO-d. Estimate size and cost of software product.
CO-e. Apply project management and quality assurance principles in software
development

Evaluation as per Suggested Rubric for Assessment of Micro-Project:

Sr.
Characteristic to be Poor Average Good Excellent
No.
assessed (Marks 1-3) (Marks 4-5) (Marks 6 - 8) (Marks 9-10)
(A) Process and Product Assesssment (Convert above total marks out of 6 marks)
1 Relevance to the Course
Literature Survey /
2
Information Collection
Completion of the Target as
3
per project proposal
Analysis of data and
4
representation
5 Quality of Prototype / Model
6 Report Preparation
(B) Individual Presentation / Viva (Convert above total marks out of 4 marks)
8 Presentation
9 Viva
Micro – Project Evaluation Sheet:
Process Assessment Product Assessment
Part Project Part Individual Total
A – project Methodology B – Project Presentation / Marks 10
Name of Student Proposal (2 marks) Report / Working Viva (4 marks)
(2 marks) Model(2 marks)

Bhadane Roshan Kiran

Comments / Suggestions about team work / leadership / inter – personal communication (if any) Any
Other Comment

Name and designation of the faculty Member: Mr.G.M.Lodha Signature

1
 MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION

SHRI H. H. J. B POLYTECHNIC,
CHANDWAD-423101 (Nashik)

MICRO PROJECT
Academic year 2022-23

TITLE OF PROJECT
Mobile Shopee Management System

Program:Computer Technology Program Code:CM

Course: Software Engineering Course code: 22413

2
MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

Sr.No. Name of Student Roll No Enrollment No Seat No

1. Borse Shubham Sanjay 14 2100790204

CERTIFICATE
This is to certify
Borse Shubham Sanjay
of 4rd Semester of Diploma in Computer Technology of Institute, SHHJB
POLYTECHNIC, CHANDWAD (Code: 0079) has completed the Micro-Project
satisfactorily in Subject Software Engineering(22413) for the academic year 2022- 2023 as
prescribed in the curriculum.

Place: CHANDWAD

Date: / 5 /2023

Subject Teacher Head of the Department Principal

(Mr.G.M.Lodha) (Mr.P.R.Sali) (Dr. V.A.Wankhede)

3
 INDEX

SR_NO. CONTENT PAGE NO.

Part A

1.0 Brief Introduction

2.0 Aim of Micro Project

3.0 Action Plan

4.0 Resources Required

Part B

1.0 Brief Description

2.0 Aim of Micro Project

3.0 Course Outcome Integrated

4.0 Actual Procedure Followed

5.0 Actual Resource Used

6.0 Outputs of the Micro-projects

7.0 Skill Developed

8.0 Applications of this Microproject

4
 PART A-Plan

Title of micro-project: Mobile Shopee Management System

1.0 Aim/Benefits of the Micro-Project-Information Technology has been growing rapidly,

with the course of time, as technology and human knowledge converge to a twilight, the
need for the betterment of their own sustaining life also increases. Rapid need of high speed
data access and faster delivery is one of the major requirement of a product. Technology has
given many gifts to the human race to lead a sophisticated life. One of the fabulous gifts was
Mobile Phone which was invented by Joel Engel and Richard Frenkiel in 1983.

2.0 Course Outcomes Addressed-

CO-a. Select suitable Software Process model for software development.

CO-b. Prepare software requirement specifications.
CO-c. Use Software modeling to create data designs.
CO-d. Estimate size and cost of software product.
CO-e. Apply project management and quality assurance principles in
software development
3.0 Proposed Methodology-

 The proposed system is computerized and has been developed using

advance language therefore it gives more facilities than present system.
It provides quick access to any data. In this system user have to enter the
data only once and then it get linked with all files. This reduces the
workload of user and it is also a time saving process. The information
about any Subscriber can be easily retrieved. The system maintains all
records easy.

 The new system will convert manual work to the computerized work.

 By converting manual work to the computerized work in that case it will

remove all paper work.

 By maintaining all the work on computer will increase our accuracy as

well as speed of our work.

 It will easily used and the time consuming is decreased

5
4.0 Action Plan-

SR.NO NAME OF CONTENT POOR(1-3) AVG(4-5) GOOD(6-8) EXC(9-10)

1 Relevance to the
course.
2 Literature survey /
information collection.
3 Project proposal.

4 Completion of the
target as per project
proposal.
5 Analysis of data and
representation.
6 Quality of prototype /
model.
7 Report preparation.

8 Presentation.

9 Defense.

5.0 Resources Required:

- Name of Resource/Material Specification Quantity Remarks
1. Computer (Desktop/Laptop) I5,RAM 8GB 1 Available
2. Microsoft office word 2017 1 Available
3. Books - - Available
4. Websites - - Available

6
 PART B-Plan

Title of micro-project: Mobile Shopee Management System

1.0 Brief Description:-Information Technology has been growing rapidly, with the course of
time, as technology and human knowledge converge to a twilight, the need for the betterment
of their own sustaining life also increases. Rapid need of high speed data access and faster
delivery is one of the major requirement of a product. Technology has given many gifts to the
human race to lead a sophisticated life. One of the fabulous gifts was Mobile Phone which
was invented by Joel Engel and Richard Frenkiel in 1983

2.0 Aims/Benefits of Micro Project: Information Technology has been growing rapidly,
with the course of time, as technology and human knowledge converge to a twilight, the
need for the betterment of their own sustaining life also increases. Rapid need of high speed
data access and faster delivery is one of the major requirement of a product. Technology has
given many gifts to the human race to lead a sophisticated life. One of the fabulous gifts was
Mobile Phone which was invented by Joel Engel and Richard Frenkiel in 1983.

3.0 Course Outcomes Achieved:

CO-a. Select suitable Software Process model for software development.
CO-b. Prepare software requirement specifications.
CO-c. Use Software modeling to create data designs.
CO-d. Estimate size and cost of software product.
CO-e. Apply project management and quality assurance principles in software
development
4.0 Actual Methodology/Procedure Followed:

1.Me and the subject teacher, we decide the topic of the micro project.

2. After reading some of the books of the software engineering as well as referring some of
the websites we gather useful information about the project which was mobile shopee
management system.

3.I'm made the proposal for the project at the starting period which contain brief description,
aim resource required.

4.I'm starting the use case diagram, class diagram as well as activity diagram of my project.

5. All the related data about the project is in the output section itself.

5.0 Actual Resources Used:

Sr.No Name of Resource/Material Specification Quantity Remarks

1. Computer (Desktop/Laptop) I5,RAM 8GB 1 Available
2. Microsoft office word 2010 1 Available
3. Books -- -- Available
4. Websites -- -- Available

7
Introduction
The Current System is the manual one, hence is not speedy, accurate, efficient
as well as time consuming. An essential part of the system analysis, which
enables the developer to understand & the system correctly. It is undertaken to
obtain details of the system. To understand the physical flow of the information
through the current system. Collect various information through. various fact
finding techniques. Identify the procedural difficulties experienced by the user.
Study the bottlenecks find out the redundant work being performed in the
system.

Brief description:
Information Technology has been growing rapidly, with the course of time, as
technology and human knowledge converge to a twilight, the need for the
betterment of their own sustaining life also increases. Rapid need of high speed
data access and faster delivery is one of the major requirement of a product.
Technology has given many gifts to the human race to lead a sophisticated life.
One of the fabulous gifts was Mobile Phone which was invented by Joel
Engel and Richard Frenkiel in 1983

Aim Of Micro project :

1. To know how requirements are gathered for any kind of software.
2. To understand how SRS is created from all s/w requirements and its
procedures , protocols.
3. To understand how UML diagrams are created for particular topic.
4. To understand how mobile shopee management system works.

PROCEDURE:
1. With all team members and the subject teacher we decided the topic of the
micro-project.
2. After reading some of the books of the software engineering as well as
referring some of the websites we gather useful information about the project
which was mobile shopee management system.
3. We made the proposal for the project at the starting period which contains
brief description, aims and resources required.

8
Action plan:

Sr. no. Details of activity Planned Planned finished Name of

start dated dated responsible
team member
1 Discussion and Shubham Borse
finalization of topic

2 Preparation and Shubham

submission of abstract Borse

3 Literature view Shubham

Borse
4 Collection of data Shubham
Borse
5 Formulation of content Shubham
Borse
6 Compilation of report Shubham
& presentation Borse

7 Seminar/ viva Shubham

Borse
8 Final submission of Shubham
microproject Borse

USE CASE DIAGRAM FOR mobile shopee

management system
9
This use case diagram is a graphic description of interactions among
the elements of mobile shopee management system. It represent the
methodology used in system analysis to identify, clarify, and organize
requirements of mobile shopee management system

THE ACTIVITY DIAGRAM :

10
This is the Login Activity Diagram of Mobile Shop Management System, which
shows the flows of Login Activity, where admin will be able to login using their
username and password. After login user can manage all the operations on
Brand, Payment Mobile, Customeloden All the pages such as Mobile Customer,
Models are secure and user can access these page after login. The diagram
below helps demonstrate how the login page works in a Mobile Shop
Management System. The various objects in the Customer, Brand, Payment
Moble and Models page-interact over the course of the Activity, and user will
not be able to access this page without ventying their identity

CLASS DIAGRAM:
11
Mobile Shop Management System Class Diagram describes the structure of a
Mobile Shop Management System classes, their attributes, operations (or
methods), and the relationships among objects. The main classes of the Mobile
Shop Management System are Mobile. Customers Brands, Sells. Payment,
Stock

E-R DAIGRAM :

12
This ER (Entity Relationship) Diagram represents the model of Mobile Shop Management
System Entity. The entity-relationship diagram of Mobile Shop Management System shows
all the visual instrument of database tables and the relations between Customers, Sells
Mobile, Stock etc. It used struc ture data and to define the relationships between structured
data groups of Mobile Shop Management Systern functionalities. The main entities of the
Mobile Shop Management System are Mobile, Customers, Brands Sells, Payment and Stock

Sequence Diagram :

13
This is the Login Sequence Diagram of Mobile Shop Management System
where admin will be able to login in their account using their credentials After
legin user can manage all the operations on Brand Mobile, Stock, Payment, Sell
All the pages such as Stock Payment Sell are secure and user can access these
page after login. The diagram below helps demonstrate how the login page
works in a Mobile Shop Management System. The vari ous objects in the
Payment, Brand Mobile, Stock and Sell pago-interact over the course of the
sequence, and user will not be able to access this page without verifying their
identity

Data Flow Diagrams :

14
Level 0 DFD :

This is the Zero Level DFD of Mobile Store System, whore we have eloborated the high level
process of Mobile. It's a basic overview of the whole Mobile Store System or process being
analyzed or modeled. It's designed to be an at-a-glance view of Payments, Stock and Login
showing the system as a single high-level process, with its relationship to external entities of
Mobile, Customer and Brands it should be easily understood by a wide audience, including
Mobile Brands and Payments in zoro leve DFD of Mobile Store System, we have described
the high level four of the Mobile system

Level 1 DFD :

15
First Level DFD (1ot Level) of Mobile Store System shows how the system is divided into
sub-systems (processes) each of which deals with one or more of the data flows to or from an
extemal agent, and which together provide all of the functionality of the Mobile Store Systern
systems as a whole It also identifies internal data stores of Login, Stock, Payments, Solls,
Brands that must be present in order for the Mobile system to do its job and shows the flow of
data between the various parts of Mobile, Brands Stock Login Payments of the system DFD
Level 1 provides a more detailed breakout of pieces of the 1st level DFD. You will highlight
the main functionalities of Mobile

Level 2 DFD :

16
DFD Level 2 then goes one step deeper into parts of Level 1 of Mobile. It may require more
functionalities of Mobile to reach the necessary level of detail about the Mobile functioning.
First Level DFD (1st Level) of Mobile Store System shows how the system is divided into
sub-systems1

Test Case Result :-

Login Form :-

17
SR.N Test Case Expected Actual Result Test Result
O Result
1 Enter valid name and Software As expected, Successful
password & click on should give user gets
login button alert of logged in.
invalid data.
2 Enter Invalid name Software As expected, Successful
and password. should get the alert
user logged message is
in. displayed.
Main Page :-
Sr. Test Case Expected Result Actual Result Test Result
No.
1 Verify Menu All Menu Functions As expected, All Successful
Buttons should Work properly Menu Functions
Functioning. are working
properly.
2 Verify All Departments As expected, All Successful
departments sections information Department
section. should display sections info is
displayed
3 Verify available All the Data of model As expected, All Successful
model mobile/mobile Data Data is
mobile/mobile should be displayed. displayed.
data.
4 Verify mobile All the Data of model As expected, All Successful
entries/data should be displayed. Data of mobile
model is
displayed
5 Verify available All the Data of As expected, All Successful
mobile/mobile available mobile Data of
data available
mobile.
6 Verify Payments All the Data of The system does Fail
Data Payments should be not displays the
displayed. data of
Payments

Functional Requirements :

18
 Prds are to these requirements shop management system lost for all of.
Expire shortly after a functional for shop
 management system will greatly reduce the application may want a time.
Indication of requirements mobile shop
 management will limit access to verify the system could have a role in their
use our system has a development? Prepare
 your digital and requirements for shop management system should you to
manage stock records and basic project is
 designed to security and can used. Without any specialized media
capabilities of the offline mode or android that your prd
 requires you thoughts from which platform. Instruments performance
requirements for mobile management system with
 corresponding brands, attitudes and files that version of items and
resource. Documents directly to our requirements shop
 management system for example, document management system as
intentional or by email. Handling has both and
 requirements for mobile hardware specifications, vb project online
shopping system considers things are the product vision
 statement and non functional and customer. Generation and functional
requirement document management systems have
 to develop comprehensive definitions for running for contributing an
urgent problem with our project speed and easy. Spent
 on it a functional requirements shop management software, user
requirement as your email confirmation of the office.
 Expressed the functional requirements for shop purpose of advertisement
in your requriments and includes an online
 verification. Philosopher with an interview for mobile shop management
software library authors. Submit requirements

COCOMO MODEL :-

19
It is the one type of static model to estimates software development effort
quicklyand roughly. It mainly deals with the number of lines of code and the
level of estimation accuracy is less as we don’t consider the all parameters
belongs to the project. The estimated effort and scheduled time for the project
are given by the relation:

Effort (E) = a*(KLOC)b MM

Scheduled Time (D) = c*(E)d Months(M) Where,

• E = Total effort required for the project in Man-Months (MM).

• D = Total time required for project development in Months (M).
• KLOC = the size of the code for the project in Kilo lines of code.
• a, b, c, d = The constant parameters for a software project.

Project type A b c d
Organic 5.4 1.05 2.5 0.83
Semidetached 3 1.12 2.5 0.35
Embedded 3.6 1.2 2.5 0.32

For a given project was estimated with a size of 300 KLOC. Calculate the
Effort, Scheduled time for development. Also, calculate the Average resource
size and Productivity of the software for Organic project type.

Effort (E) = a*(KLOC)b = 2.4*(300)1.05 = 957.61 MM

Scheduled Time (D) = c*(E)d = 2.5*(957.61)0.38 =33.95 Months(M)
Avg. Resource Size = E/D = 957.61/33.95 = 28.21 Mans
Productivity of Software = KLOC/E = 300/957.61 = 0.3132 KLOC/MM = 313
LOC/MMs

Decision table:

20
 condition 1.if mobile is available yes

2.if mobile is not available no yes

3.if model is available. no yes

4.if boking is available yes

5.if cancel the boking. yes

action 1.respond customer mobile yes

available

2.respond not available no yes

3.respond available. yes

4. respond available pay fare yes

for it.

5. refund the money. yes

Skill Developed/ learning out of Microproject:

1. We learn how to gather requirement of the software.

2. We learn how to create the SRS using given requirement and by adding
protocols and the procedures in it.

3. We learn how to draw the use case diagrams, class diagrams as well as the
activity diagram of any software.

4. In overall we learn that how software engineering is very much important for
developing the software

21
22