Software Engineering and Methodology
VerifiedAdded on 2022/12/15
|18
|2871
|52
AI Summary
This document provides an overview of the Sunshine Motors vehicle mechanic management system and its implementation using the Business Enterprise Management System. It includes specification models, system description, scope, feasibility analysis, requirement specification, assumptions and constraints, use cases, context model, and designing models. The subject is Software Engineering and Methodology.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Software Engineering and Methodology
Student Name:
Register Number:
Submission Date:
1
Student Name:
Register Number:
Submission Date:
1
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Table of Contents
Specification model.......................................................................................................................................................... 2
A. Executive summary............................................................................................................................................. 3
B. System description.............................................................................................................................................. 3
C. Scope.................................................................................................................................................................. 3
D. Feasibility analysis.............................................................................................................................................. 4
E. Requirement specification................................................................................................................................... 4
i. Functional...................................................................................................................................................... 4
ii. Non-functional................................................................................................................................................ 5
F. Assumptions and constraints...............................................................................................................................5
G. Use cases............................................................................................................................................................. 5
i. Use case diagram............................................................................................................................................ 6
ii. Use case descriptions............................................................................................................................................. 6
H. Context model..................................................................................................................................................... 8
I. Leveled set functional models..............................................................................................................................9
Designing model............................................................................................................................................................... 9
A. Executive summary............................................................................................................................................. 9
B. Architectural design.......................................................................................................................................... 10
C. Hardware specification..................................................................................................................................... 10
D. Details class diagram......................................................................................................................................... 11
E. Interface design................................................................................................................................................. 11
1. Wireframe design................................................................................................................................................ 12
F. Business process models (utilizing BPMN 2.0)...................................................................................................13
G. Sequence diagram............................................................................................................................................. 14
H. Interaction diagram.......................................................................................................................................... 14
I. State diagram.................................................................................................................................................... 15
Conclusion..................................................................................................................................................................... 16
Reference....................................................................................................................................................................... 18
2
Specification model.......................................................................................................................................................... 2
A. Executive summary............................................................................................................................................. 3
B. System description.............................................................................................................................................. 3
C. Scope.................................................................................................................................................................. 3
D. Feasibility analysis.............................................................................................................................................. 4
E. Requirement specification................................................................................................................................... 4
i. Functional...................................................................................................................................................... 4
ii. Non-functional................................................................................................................................................ 5
F. Assumptions and constraints...............................................................................................................................5
G. Use cases............................................................................................................................................................. 5
i. Use case diagram............................................................................................................................................ 6
ii. Use case descriptions............................................................................................................................................. 6
H. Context model..................................................................................................................................................... 8
I. Leveled set functional models..............................................................................................................................9
Designing model............................................................................................................................................................... 9
A. Executive summary............................................................................................................................................. 9
B. Architectural design.......................................................................................................................................... 10
C. Hardware specification..................................................................................................................................... 10
D. Details class diagram......................................................................................................................................... 11
E. Interface design................................................................................................................................................. 11
1. Wireframe design................................................................................................................................................ 12
F. Business process models (utilizing BPMN 2.0)...................................................................................................13
G. Sequence diagram............................................................................................................................................. 14
H. Interaction diagram.......................................................................................................................................... 14
I. State diagram.................................................................................................................................................... 15
Conclusion..................................................................................................................................................................... 16
Reference....................................................................................................................................................................... 18
2
Specification model
A.Executive summary
The main goal of this project is to implement the Sunshine Motors vehicle mechanic
management system by using the “Business Enterprise Management System”. The improvement
in the process of vehicle mechanic system which follows the following stages of analyzing of the
relationship process (company service to customer), process stages, Redesigned process (work
order) will be done. The proposal to use the case diagram which is denoted as simple
representation of the customer’s interaction with the vehicle management service system that
identifies the methodology and process step of business enterprise system will be carried out.
The analysis process of the feasibility that follows the three stages includes, technical feasible,
estimate cost feasible and profit feasible will be completed. Analyzing of the Sunshine Motor
vehicle record service is based on 300 clients but Investment on increasing the efficiencies of the
production had the greatest impact on company profitability by 10%.
B. System Description
The system description structure has been used for developing the Sunshine Motors
Vehicle mechanical service company using business process model system. The new system for
improving the Sunshine Motors management system has records that includes add and update the
client information (name, address, conduct details), service information (model, color,
registration), and mechanic information of the system. The company’s system also contains the
records of employees of the company management system. The mechanical service company of
the current system is specifically for the increase in the work flow demand and improves the
company’s growth for the system. Analyzing process of sunshine’s motors current company of
the manual based vehicle system, which is specific for the good of the company, now is impacted
and damaged by additional demand and growing customers of the company.
C.Scope
The scope of this project to enhance the facilities available in the motors vehicles
management current database system and different security measures would be applicable in the
3
A.Executive summary
The main goal of this project is to implement the Sunshine Motors vehicle mechanic
management system by using the “Business Enterprise Management System”. The improvement
in the process of vehicle mechanic system which follows the following stages of analyzing of the
relationship process (company service to customer), process stages, Redesigned process (work
order) will be done. The proposal to use the case diagram which is denoted as simple
representation of the customer’s interaction with the vehicle management service system that
identifies the methodology and process step of business enterprise system will be carried out.
The analysis process of the feasibility that follows the three stages includes, technical feasible,
estimate cost feasible and profit feasible will be completed. Analyzing of the Sunshine Motor
vehicle record service is based on 300 clients but Investment on increasing the efficiencies of the
production had the greatest impact on company profitability by 10%.
B. System Description
The system description structure has been used for developing the Sunshine Motors
Vehicle mechanical service company using business process model system. The new system for
improving the Sunshine Motors management system has records that includes add and update the
client information (name, address, conduct details), service information (model, color,
registration), and mechanic information of the system. The company’s system also contains the
records of employees of the company management system. The mechanical service company of
the current system is specifically for the increase in the work flow demand and improves the
company’s growth for the system. Analyzing process of sunshine’s motors current company of
the manual based vehicle system, which is specific for the good of the company, now is impacted
and damaged by additional demand and growing customers of the company.
C.Scope
The scope of this project to enhance the facilities available in the motors vehicles
management current database system and different security measures would be applicable in the
3
future and growing the customer list which shall improve the business process management. The
scope of process is to analyze the project, to involve planning and organization of the vehicle
mechanic company resources to complete the allocated task event, and service delivery to be on
time for the customer. Also, find the risk of the project which satisfies the condition of the
company. The vehicle mechanic is to satisfy the customer’s car service and provide good quality
service to the customer and after that improve the good market stages of the company.
D.Feasibility analysis
The feasible study of the vehicle management system includes the following stages,
Technical feasibility
Operational feasibility
Economic feasibility
Legal feasibility
Technical feasibility
Technical Feasibility of the business enterprise system can specify the software
equipment which shall successfully satisfy the customer (car service) and also the company
(delivery process) requirement for the system.
Operation feasibility
Analyzing of the operation feasibility can measure customer solving problems and in turn
can help for the new proposed system. The operation feasibility of the initial stages is analyzing,
planning, and implementing on the business process model system. The process of the operation
fulfills the customer requirements and identifies the duration of the development of the economic
profit service.
Economic feasibility
Economic feasibility analysis is the most commonly used method for determining the
efficiency of new services.
Legal feasibility
Legal Feasibility can be used for checking the each stage of the process model to occur
and the risk to correct the service of the system.
4
scope of process is to analyze the project, to involve planning and organization of the vehicle
mechanic company resources to complete the allocated task event, and service delivery to be on
time for the customer. Also, find the risk of the project which satisfies the condition of the
company. The vehicle mechanic is to satisfy the customer’s car service and provide good quality
service to the customer and after that improve the good market stages of the company.
D.Feasibility analysis
The feasible study of the vehicle management system includes the following stages,
Technical feasibility
Operational feasibility
Economic feasibility
Legal feasibility
Technical feasibility
Technical Feasibility of the business enterprise system can specify the software
equipment which shall successfully satisfy the customer (car service) and also the company
(delivery process) requirement for the system.
Operation feasibility
Analyzing of the operation feasibility can measure customer solving problems and in turn
can help for the new proposed system. The operation feasibility of the initial stages is analyzing,
planning, and implementing on the business process model system. The process of the operation
fulfills the customer requirements and identifies the duration of the development of the economic
profit service.
Economic feasibility
Economic feasibility analysis is the most commonly used method for determining the
efficiency of new services.
Legal feasibility
Legal Feasibility can be used for checking the each stage of the process model to occur
and the risk to correct the service of the system.
4
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
E. Requirement specification
i. Functional
The functional model of the business analysis is to specify the motor vehicle servicing
system. The process for the vehicle company has fifteen days and a pool data base connection of
ten mechanics. So, creating a list of dynamics for ensuring that the system always has at least
five mechanics working in day shift and one mechanic for any emergency Calls (for purpose of
mechanic work). The process of mechanic work is that all terminals can place in the workshop
area and find the information from front and outside the office for the terminal process. The
vehicle company of the process system includes the payment system, ordering system, providing
loan system, purchasing system, delivery system, of the organization.
ii. Non-functional
Non-functional requirement are the properties that specify the part number of the work
items that must have. Think of these properties as the characteristics or qualities of the service
like attractive, usable, fast, or reliable. The business process model is not required because
they’re fundamental activities of the services. They are denoted as storing the service records,
and identified serving data, and so on. The customer wants to make a function for the activities to
perform them in a certain manner. The nonfunctional requirement does not alert the service
functionality.
F. Assumptions and constraints
Assumption is that there will be car servicing of the mechanical management system.
Assumption is defined as the act of taking on new responsibilities. An example of assumption is
the fulfillment of the duties of another person who has been fired from company.
G.Use cases
The unified modeling language of the use case diagram that specifies the behaviors of each
process operation can be used to describe the goals of the customer and other services that
interact with the company system that is being modeled. They are used to describe the functional
requirement of the system, sub systems, entity and present process of each stages will be used.
5
i. Functional
The functional model of the business analysis is to specify the motor vehicle servicing
system. The process for the vehicle company has fifteen days and a pool data base connection of
ten mechanics. So, creating a list of dynamics for ensuring that the system always has at least
five mechanics working in day shift and one mechanic for any emergency Calls (for purpose of
mechanic work). The process of mechanic work is that all terminals can place in the workshop
area and find the information from front and outside the office for the terminal process. The
vehicle company of the process system includes the payment system, ordering system, providing
loan system, purchasing system, delivery system, of the organization.
ii. Non-functional
Non-functional requirement are the properties that specify the part number of the work
items that must have. Think of these properties as the characteristics or qualities of the service
like attractive, usable, fast, or reliable. The business process model is not required because
they’re fundamental activities of the services. They are denoted as storing the service records,
and identified serving data, and so on. The customer wants to make a function for the activities to
perform them in a certain manner. The nonfunctional requirement does not alert the service
functionality.
F. Assumptions and constraints
Assumption is that there will be car servicing of the mechanical management system.
Assumption is defined as the act of taking on new responsibilities. An example of assumption is
the fulfillment of the duties of another person who has been fired from company.
G.Use cases
The unified modeling language of the use case diagram that specifies the behaviors of each
process operation can be used to describe the goals of the customer and other services that
interact with the company system that is being modeled. They are used to describe the functional
requirement of the system, sub systems, entity and present process of each stages will be used.
5
i. Use case diagram
ii. Use Case descriptions
The business process for Sunshine Motors of the use case model is to specify the four factors that
includes,
Customer service,
Mechanic service,
System use service,
System admonitory services
Customer Service Use Case Description
The process for the customer is to check the car for any problem. Then it is to provide car
6
ii. Use Case descriptions
The business process for Sunshine Motors of the use case model is to specify the four factors that
includes,
Customer service,
Mechanic service,
System use service,
System admonitory services
Customer Service Use Case Description
The process for the customer is to check the car for any problem. Then it is to provide car
6
service from the sunshine motor company. The system allows the company records to keep the
information of the client details that specified the name address contact details in the system.
Servicing request,
The customer has to bring the car to the service. Than to come at payment service and the
service writer shall prepare the service work order. The service writer to assign the work on the
mechanic system. The company also provides loan cars to clients on request and so must keep
information on when loan cars are available for clients and who has a loan car at the given time.
The customer has to arrive to pick the vehicle they have the invoice for which they can check
when payment is received and enter into the system against the invoice. The customer has to pay
the full amount as invoice and then it is flagged as closed. Some customers invoice will be partly
paid and the invoice system remains till the full payment is received in seven days.
Login and logout system
The service manager has to login into the system and which stores all the records on
database. The service manager maintains the records and this includes,
Client details that contains the name, address, contact number records
Vehicle details that contains the model, registration, color records,
Service history that contains the service date, odometer readings, labor tasks, allocate
mechanic work order records
Employee detail that contains the personal details, qualification, special licenses, contact
details, supervisor details records on the administer service database.
Mechanic service use case description
The Mechanic then begins the work on the vehicle. The Work Order will contain a
number of standard Work Items corresponding to the particular service being undertaken, along
with any specific faults noted by the customer. The service manager has to check the account
department for any pending and whether the customer list payment has been verified. The
mechanic assigned for this work has Bay for the day, but may move between the work bays for
different work orders. Sunshine motors maintain the 10 work Bays with in the workshop area.
The work items that has to be completed by the mechanic, checks these off on the system. The
progress on the work order customer rings for the updates on expected completion time.
System uses service use case Description
During servicing, the mechanic may require a new part will be needed on the work items.
7
information of the client details that specified the name address contact details in the system.
Servicing request,
The customer has to bring the car to the service. Than to come at payment service and the
service writer shall prepare the service work order. The service writer to assign the work on the
mechanic system. The company also provides loan cars to clients on request and so must keep
information on when loan cars are available for clients and who has a loan car at the given time.
The customer has to arrive to pick the vehicle they have the invoice for which they can check
when payment is received and enter into the system against the invoice. The customer has to pay
the full amount as invoice and then it is flagged as closed. Some customers invoice will be partly
paid and the invoice system remains till the full payment is received in seven days.
Login and logout system
The service manager has to login into the system and which stores all the records on
database. The service manager maintains the records and this includes,
Client details that contains the name, address, contact number records
Vehicle details that contains the model, registration, color records,
Service history that contains the service date, odometer readings, labor tasks, allocate
mechanic work order records
Employee detail that contains the personal details, qualification, special licenses, contact
details, supervisor details records on the administer service database.
Mechanic service use case description
The Mechanic then begins the work on the vehicle. The Work Order will contain a
number of standard Work Items corresponding to the particular service being undertaken, along
with any specific faults noted by the customer. The service manager has to check the account
department for any pending and whether the customer list payment has been verified. The
mechanic assigned for this work has Bay for the day, but may move between the work bays for
different work orders. Sunshine motors maintain the 10 work Bays with in the workshop area.
The work items that has to be completed by the mechanic, checks these off on the system. The
progress on the work order customer rings for the updates on expected completion time.
System uses service use case Description
During servicing, the mechanic may require a new part will be needed on the work items.
7
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Will be required to check the inventory database stock for the item if it is available or not. The
inventory level of the mechanic decrement depends on the parts and customizable. The
purchasing office has to check the inventory level order for additional stock though email to the
suppliers. The purchase officer has to receive the warning mail for the threshold limit. The
system holds 5000 part numbers that includes the name, number, supplied order minimum
quality. The Service Manager will also notify the Mechanic who is servicing the vehicle for the
outcome. This may require the Mechanic to be assigned to another Work Order until the Part
arrives.
System admonitory services use case Description
Financial manager has to keep all the servicing records and maintain them on Microsoft Excel
sheet and MYOB database. The financial manager has to check the car service and bills from the
account department, same to be verified and pending payment invoice message to be send to the
customer. The customer has to pay the amount in the front office, same to be checked and
verified. Marketing manager has to maintain the car servicing new system and it has to establish
and provide special offers to the customer. This will improve the business process model system.
The process of the system admin is to back up all the records and also to set the access
permission on the service management system.
H.Context model
The context model diagram is also defined as the data flow diagram, a visible process to
the represent the function of sunshine motors and vehicle mechanic service that contains the
process for the system to model. The customer who will interact with the system is called as the
external entities. The customer and the mechanic has to interact with the entities, and specify as
to who shall interact will the system. In between the process and the external entities, there is
data flow (service system) that indicates the existence of information exchange between the
entities and the system. The context model diagram is given below,
8
inventory level of the mechanic decrement depends on the parts and customizable. The
purchasing office has to check the inventory level order for additional stock though email to the
suppliers. The purchase officer has to receive the warning mail for the threshold limit. The
system holds 5000 part numbers that includes the name, number, supplied order minimum
quality. The Service Manager will also notify the Mechanic who is servicing the vehicle for the
outcome. This may require the Mechanic to be assigned to another Work Order until the Part
arrives.
System admonitory services use case Description
Financial manager has to keep all the servicing records and maintain them on Microsoft Excel
sheet and MYOB database. The financial manager has to check the car service and bills from the
account department, same to be verified and pending payment invoice message to be send to the
customer. The customer has to pay the amount in the front office, same to be checked and
verified. Marketing manager has to maintain the car servicing new system and it has to establish
and provide special offers to the customer. This will improve the business process model system.
The process of the system admin is to back up all the records and also to set the access
permission on the service management system.
H.Context model
The context model diagram is also defined as the data flow diagram, a visible process to
the represent the function of sunshine motors and vehicle mechanic service that contains the
process for the system to model. The customer who will interact with the system is called as the
external entities. The customer and the mechanic has to interact with the entities, and specify as
to who shall interact will the system. In between the process and the external entities, there is
data flow (service system) that indicates the existence of information exchange between the
entities and the system. The context model diagram is given below,
8
I. Leveled set functional models
The functional model of the structure representation specifies the function activities with
the interrelationship between the customers and the sunshine motor vehicle mechanic system.
The interrelation between the customer and mechanic service function model, customer service
department model, IT administer model of the company system. The relationship between the
customer and service mechanic can be used by the Mechanic for servicing the vehicle. New parts
may be needed for a particular Work Item. The inter relationship between the customer and the
Service Manager will notify the Customer about the delay and may have to arrange for a
replacement car until the part arrives.
Designing model
A. Executive summary
The analyzing process of the business designing model of the motor vehicle company
9
The functional model of the structure representation specifies the function activities with
the interrelationship between the customers and the sunshine motor vehicle mechanic system.
The interrelation between the customer and mechanic service function model, customer service
department model, IT administer model of the company system. The relationship between the
customer and service mechanic can be used by the Mechanic for servicing the vehicle. New parts
may be needed for a particular Work Item. The inter relationship between the customer and the
Service Manager will notify the Customer about the delay and may have to arrange for a
replacement car until the part arrives.
Designing model
A. Executive summary
The analyzing process of the business designing model of the motor vehicle company
9
shall follow various types of model that are specified as Class diagram, interface design,
wireframe model, Enterprise business process model, state diagram, Interaction diagram will be
done.
B. Architectural design
The architectural model is used for the design of the service. To develop the architectural
model of the motor vehicle mechanic system, specify the inventory control levels, purchasing
part number ordering, bill payment list, loan list, service assistants, mechanic service, manage
service, customer and IT administer database information. The Process of the Architectural
diagram is given below,
C. Hardware specification
The hardware specification of the motor vehicle mechanic includes the computer
hardware specification which is the collection of physical parts of a computer system. This
includes the computer case, monitor, keyboard, and mouse. The computer hardware that is used
for the car vehicle is all the information that can be stored in the system database. The IT
10
wireframe model, Enterprise business process model, state diagram, Interaction diagram will be
done.
B. Architectural design
The architectural model is used for the design of the service. To develop the architectural
model of the motor vehicle mechanic system, specify the inventory control levels, purchasing
part number ordering, bill payment list, loan list, service assistants, mechanic service, manage
service, customer and IT administer database information. The Process of the Architectural
diagram is given below,
C. Hardware specification
The hardware specification of the motor vehicle mechanic includes the computer
hardware specification which is the collection of physical parts of a computer system. This
includes the computer case, monitor, keyboard, and mouse. The computer hardware that is used
for the car vehicle is all the information that can be stored in the system database. The IT
10
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
administers which can use the system and specifies the process of backup, access permission of
the database (Shankararaman, Zhao and Lee, 2016).
D. Details class diagram
The Class diagram defines the attributes and operations of a class and also the constraints
imposed on the system by the business process enter price model. The attribute of the class
diagram has been denoted as login (), validate, connection pool database, system admin
operation (), customer information (), service inventory (), mechanic information (), and service
request of the business process company (Liu, 2013).
E. Interface design
The motors vehicles mechanic service management for the interface design is given below,
11
the database (Shankararaman, Zhao and Lee, 2016).
D. Details class diagram
The Class diagram defines the attributes and operations of a class and also the constraints
imposed on the system by the business process enter price model. The attribute of the class
diagram has been denoted as login (), validate, connection pool database, system admin
operation (), customer information (), service inventory (), mechanic information (), and service
request of the business process company (Liu, 2013).
E. Interface design
The motors vehicles mechanic service management for the interface design is given below,
11
1. Wireframe design
The motors vehicles mechanic service management for the wireframe design diagram is
given below,
12
The motors vehicles mechanic service management for the wireframe design diagram is
given below,
12
F. Business process models (utilizing BPMN 2.0)
The business process model of the vehicle mechanic service company’s business processes or
workflows, as a means of identifying potential improvements and the process of payment are
credit card, PayPal, cash amount of the service management system. The motors vehicles
mechanic service management of the business model diagram is given below,
13
The business process model of the vehicle mechanic service company’s business processes or
workflows, as a means of identifying potential improvements and the process of payment are
credit card, PayPal, cash amount of the service management system. The motors vehicles
mechanic service management of the business model diagram is given below,
13
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
G. Sequence diagram
The motors vehicles mechanic service management of the sequence diagram is given below,
H. Interaction diagram
The motors vehicles mechanic service management of the interaction diagram is given below,
14
The motors vehicles mechanic service management of the sequence diagram is given below,
H. Interaction diagram
The motors vehicles mechanic service management of the interaction diagram is given below,
14
I. State diagram
The motors vehicles mechanic service management of the state diagram is given below
15
The motors vehicles mechanic service management of the state diagram is given below
15
Conclusion
The main goal of this project was to implement the sunshine motors vehicle mechanic
management system by using Business enterprise management system (BPMN 2.0) and same
has been completed. The vehicle mechanical business process analyzes each stage of process
planning, servicing of the task, event to complete on the particular time and delivery to the
customer. It was used for increasing the customer growth of the company enterprise by analyzing
design models that include, use case diagram, state diagram, interaction diagram, wireframe
diagram, business process model diagram, architecture diagram and same has been completed.
Analyzing of the vehicle mechanic part number is 5000 on the inventory control stock levels of
the service management and same has been completed. IT administrator, finance manager and
marketing manager are generally fairly IT illiterate and so need very simple user interfaces.
16
The main goal of this project was to implement the sunshine motors vehicle mechanic
management system by using Business enterprise management system (BPMN 2.0) and same
has been completed. The vehicle mechanical business process analyzes each stage of process
planning, servicing of the task, event to complete on the particular time and delivery to the
customer. It was used for increasing the customer growth of the company enterprise by analyzing
design models that include, use case diagram, state diagram, interaction diagram, wireframe
diagram, business process model diagram, architecture diagram and same has been completed.
Analyzing of the vehicle mechanic part number is 5000 on the inventory control stock levels of
the service management and same has been completed. IT administrator, finance manager and
marketing manager are generally fairly IT illiterate and so need very simple user interfaces.
16
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Sunshine Motors has a client base of 300 clients but is hoping to grow this by 10% and same has
been completed.
17
been completed.
17
Reference
Liu, L. (2013). A New Software Development Methodology for Clinical Trial
Systems. Advances in Software Engineering, 2013, pp.1-13.
Shankararaman, V., Zhao, J. and Lee, J. (2016). Business enterprise, process, and technology
management.
18
Liu, L. (2013). A New Software Development Methodology for Clinical Trial
Systems. Advances in Software Engineering, 2013, pp.1-13.
Shankararaman, V., Zhao, J. and Lee, J. (2016). Business enterprise, process, and technology
management.
18
1 out of 18
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024 | Zucol Services PVT LTD | All rights reserved.