Titolo

SOFTWARE presentazione– FINAL PROJECT

ENGINEERING
sottotitolo
• Omar Makni 10713017
Milano, XX mese 20XX
• Marcelo Andre Muro Alvarado 10682124
• Robby Izaty Ramadhan 10655158
AGENDA

1. INTRODUCTION

2. REQUERIMENTS ANALYSIS AND SPECIFICATION DOCUMENT

3. DESIGN DOCUMENT

4. IMPLEMENTATION DOCUMENT

5. TESTING DOCUMENT

6. CONCLUSIONS

Software Engineering Project

AGENDA

1. INTRODUCTION

2. REQUERIMENTS ANALYSIS AND SPECIFICATION DOCUMENT

3. DESIGN DOCUMENT

4. IMPLEMENTATION DOCUMENT

5. TESTING DOCUMENT

6. CONCLUSSIONS

Software Engineering Project

 INTRODUCTION/Smart Service Center

What is Smart Service Center (SSC)?

SSC is a platform designed to help:
electronic device users (EDU)
local electronic service centers owners (SCO)
SSC will connect customers and companies in an easier way.

How SSC starts?

SSC idea was born as a solution for different problems that many people find
when it comes to repair or maintain their electronic devices.

Software Engineering Project

AGENDA

1. INTRODUCTION

2. REQUERIMENTS ANALYSIS AND SPECIFICATION DOCUMENT

3. DESIGN DOCUMENT

4. IMPLEMENTATION DOCUMENT

5. TESTING DOCUMENT

6. CONCLUSSIONS

Software Engineering Project

 RASD/Actors

Electronic Device User Service Center Owner

The Electronic Device User (EDU) is any The Service Center Owner (SCO) is the
person who is looking for a maintenance person who owns a Service Center and
service of his/her electronic device offer his/her services through Smart
through Smart Service Center system. Service Center System. This person has
This person has the possibility to create the possibility to request admission to the
an account, sign in and apply to the system, sign in and apply to the different
different functionalities of the system, functionalities of the system, according to
according to his profile. his profile.

Software Engineering Project

 RASD/Goals

• Registration and access of users • Get the service status

• Visualize the location of service centers • Update the service status
• Choose a service center • Create a Claim
• Create a service request • Communication between both type of users
• Accept, or not a service request • Communication through a common forum
• Create a proposal
• Accept, or not a proposal

Software Engineering Project

 RASD/Functional Requirements

EDU SCO
• Register an electronic device • Evaluate request
• Send a service request • Send a proposal
• Get service history • Exchange messages with EDU
• Evaluate a proposal • Update service status
• Pay service • Post messages in Forum
• Get service status
• Review a Service
• Request a Claim
• Exchange messages with SCO
• Post messages in Forum

Software Engineering Project

 RASD/Non Functional Requirements

• The system must be acceptable to guarantee a good grade of usability, in particular every kind of
API request must be completed within 1 second. [Performance]

• The system must function 24/7/365 shall have an availability of 99.99% (two nines) which imply
a 52.56 minutes downtime per year. [Reliability]

• The system can be easily used by every person who can access to a web browser.
[Accessibility]

• The web application must be compatible with the most popular browsers: Google Chrome,
Mozilla Firefox, Safari and Microsoft Edge. [Supportability]

• The communication among user and system must be encrypted in order to protect every kind of
transaction. [Security]

Software Engineering Project

 RASD/Use Case EDU

• EDU signs up • EDU pays for the service

• EDU signs in • EDU gets service status (invoice status)
• EDU registers a electronic device • EDU sends messages to SCO
• EDU visualize SC map • EDU reviews service
• EDU gets service history • EDU requests a claim
• EDU sends request • EDU sends messages to Forum
• EDU evaluates proposal

Software Engineering Project

 RASD/Use Case SCO

• SCO sends admission request • SCO sends message to EDU

• SCO signs in • SCO takes SOR from buffer
• SCO evaluates SOR • SCO sends messages to Forum
• SCO updates service status

Software Engineering Project

 RASD/Use Case Diagram

Software Engineering Project

 RASD/Use Case Description (I)

Name: EDU sends request

Use Case: Use Case: UC4

• EDU sends a request Actors: EDU

EDU must be on the homepage for EDU.

Pre-Conditions:
EDU must have at least one registered ED.
Flow of events:
1. EDU clicks on one service center in the homepage map.
• Select one service center Flow of events:
2.
3.
The system returns an interface to create a service request
EDU fills all mandatory fields.
4. EDU clicks “Create”.
• Fill in required information. 5. The system shows “Successful creation” message.

The database save the information of the request and it is sent

• Clicks on “Create” Post-Conditions:
to the SCO inbox.

1. EDU enters invalid data.

• Generation of SOR Exception:
2. EDU doesn’t fill all mandatory fields.

Software Engineering Project

 RASD/Sequence Diagram (I)

Software Engineering Project

 RASD/Use Case Description (II)

Name: SCO sends proposal

Use Case: Use Case: UC13
• SCO sends proposal Actors: SCO
SCO must be in proposal page.
Pre-Conditions:
SCO must have at least one SOR accepted.
Flow of events:
1. SCO fills out all the mandatory fields.
• Fill in required information. Flow of events:
2.
3.
SCO clicks “Create”.
The system shows “Successful Proposal” message.
4. The system generates a proposal.
• Clicks on “Create”
Post-Conditions: SCO is in the home page for service centers.
• Generation of proposal Exception:
1. SCO enters invalid data.
2. SCO doesn’t fill all mandatory fields.

Software Engineering Project

 RASD/Sequence Diagram (II)

Software Engineering Project

 RASD/Class Diagram

Software Engineering Project

AGENDA

1. INTRODUCTION

2. REQUERIMENTS ANALYSIS AND SPECIFICATION DOCUMENT

3. DESIGN DOCUMENT

4. IMPLEMENTATION DOCUMENT

5. TESTING DOCUMENT

6. CONCLUSSIONS

Software Engineering Project

 DD/System architecture

1. Presentation tier: the entry point of the user

interaction with the central system. The web application
is considered in this tier. It is used to invoke the main
server for storing and retrieving from database.

2. Logic tier: It communicates between the website and

the database. This tier is implemented using JavaScript.

3. Data tier: The data tier includes the data persistence

mechanisms (database servers, file shares, etc.). This tier
is based on Google Firebase API connected to the
application tier that exposes methods of managing the
stored data without exposing or creating dependencies on
the data storage mechanisms.

Software Engineering Project

 DD/Component View (I)

SSC Business Logic

 Authentication Manager  Mailing Manager
 Network Manager  Payment Manager
 EDU Manager  Review Manager 
 SCO Manager  Claim Manager 
 Electronic Device Manager  Forum Manager 
 Service Manager  Buffer Manager
 Proposal Manager  Data Store Manager
 Invoice Manager

Software Engineering Project

 DD/Component View (II)

External Interfaces

 Places API
 Geocoding API
 Maps JavaScript API Maps JavaScript
Geolocation
 Google Firebase API (Database) API API

Places API

Software Engineering Project

 DD/Deployment View

Software Engineering Project

 DD/Runtime View (I)

Activity:
• EDU sends a request

Main Components:
• Service Manager
• Data Storage Manager
• Mailing Manager
• Database

Software Engineering Project

 DD/Runtime View (II)

Activity:
• SCO sends proposal

Main Components:
• Proposal Manager
• Data Storage Manager
• Mailing Manager
• Database

Software Engineering Project

 DD/Component Interfaces

Software Engineering Project

 DD/User Interface Design (I)

Electronic Device User

Software Engineering Project

 DD/User Interface Design (II)

Service Center Owner

Software Engineering Project

AGENDA

1. INTRODUCTION

2. REQUERIMENTS ANALYSIS AND SPECIFICATION DOCUMENT

3. DESIGN DOCUMENT

4. IMPLEMENTATION DOCUMENT

5. TESTING DOCUMENT

6. CONCLUSSIONS

Software Engineering Project

IMPLEMENTATION
 ID/Tools and Framework

Software Engineering Project

 ID/Source Code Structure – Application Planning

Software Engineering Project

 ID/Project Program Directory

Software Engineering Project

 ID/Firebase Services Directory - Cloud Firestore Directory

Cloud Firestore Directory

Firebase Services
Directory

Software Engineering Project

 ID/Installation Instructions

Website Application in Local Server:

3. Enter to
1. Open Visual 2. Import the React 4.Write
Studio Code project application in commands
the folder

Software Engineering Project

 ID/Installation Instructions

Website Application:
Visit the following URL: https://smart-service-center.web.app/

Software Engineering Project

 ID/Functionalities and Interfaces

Home page of Electronic Device User

Software Engineering Project
 ID/Functionalities and Interfaces

Home page of Service Center Owner

Software Engineering Project
 ID/Functionalities and Interface

Register a device interface

Software Engineering Project
 ID/Functionalities and Interface

Request a new service interface

Software Engineering Project
 ID/Functionalities and Interface

Inbox message interface

Software Engineering Project
 ID/Functionalities and Interface

Create Proposal interface

Software Engineering Project
 ID/Functionalities and Interface

EDU Proposal interface

Software Engineering Project
 ID/Functionalities and Interface

Payment interface
Software Engineering Project
 ID/Functionalities and Interface

New forum post interface

Software Engineering Project
 ID/Functionalities and Interface

Observing forum interface

Software Engineering Project
 ID/Functionalities and Interface

New message interface

Software Engineering Project
 ID/Functionalities and Interface

EDU History interface

Software Engineering Project
 ID/Functionalities and Interface

Invoice interface
Software Engineering Project
 ID/Functionalities and Interface

Contact Us interface
Software Engineering Project
AGENDA

1. INTRODUCTION

2. REQUERIMENTS ANALYSIS AND SPECIFICATION DOCUMENT

3. DESIGN DOCUMENT

4. IMPLEMENTATION DOCUMENT

5. TESTING DOCUMENT

6. CONCLUSSIONS

Software Engineering Project

TESTING
 TD/Integration and Testing Strategy

All functionality tested by directly applying to the app

Software Engineering Project

 TD/Test Procedure

Requirement in RASD

44 Test cases in TD

Software Engineering Project

 TD/Tools and Test Equipment Required

Test status result:

a. Passed
b. Failed

Software Engineering Project

 TD/Testing by the professor

Smart Service Center Website:

https://smart-service-center.web.app/

Software Engineering Project

AGENDA

1. INTRODUCTION

2. REQUERIMENTS ANALYSIS AND SPECIFICATION DOCUMENT

3. DESIGN DOCUMENT

4. IMPLEMENTATION DOCUMENT

5. TESTING DOCUMENT

6. CONCLUSSIONS

Software Engineering Project

 CONCLUSIONS

• Although some functionalities were not mention in the RASD, our team decided to include in the
implementation in order to develop a more completed software. Experience in the definition of the
requeriments is highly important.
• Every goal of the project was implemented and tested successfully.
• Every requirement of the project was implemented and tested successfully.
• From this point is posible to continue improving the features of the software, some of them are:
- Manage the personal information of the users.
- Manage the electronic device information.

Software Engineering Project