Version 1.0
Sophistication value of the Project + Applicability of the Project(Usefulness)
Here, we are going to discuss what all parameters we have considered while building our product and how many parameters we have been able to cover actually.
We promised our customers that we will be building a prototype of a self driving car which can be scaled for production.
According to whatever has been mentioned above, we have been successfully able to build our software, which meets all the requirements.
- argparse
- io
- vision
- types
- json
- urllib
- sys
- time
- com.google.android.gms.maps.model.LatLng;
- com.google.android.gms.common.ConnectionResult;
- com.google.android.gms.common.api.GoogleApiClient;
- com.google.android.gms.location.LocationListener;
- com.google.android.gms.location.LocationRequest;
- com.google.android.gms.location.LocationServices;
- com.google.android.gms.maps.CameraUpdateFactory;
- com.google.android.gms.maps.GoogleMap;
- com.google.android.gms.maps.OnMapReadyCallback;
- com.google.android.gms.maps.SupportMapFragment;
- com.google.android.gms.maps.model.BitmapDescriptorFactory;
- com.google.android.gms.maps.model.LatLng;
- com.google.android.gms.maps.model.Marker;
- com.google.android.gms.maps.model.MarkerOptions;
- com.google.android.gms.maps.model.PolylineOptions;
- com.google.android.gms.tasks.OnFailureListener;
- com.google.android.gms.tasks.OnSuccessListener;
- com.google.firebase.storage.FirebaseStorage;
- com.google.firebase.storage.OnPausedListener;
- com.google.firebase.storage.OnProgressListener;
- com.google.firebase.storage.StorageMetadata;
- com.google.firebase.storage.StorageReference;
- com.google.firebase.storage.UploadTask;
- org.json.JSONObject;
- java.io.*;
- java.net.HttpURLConnection;
- java.net.URL;
- java.util.ArrayList;
- java.util.HashMap;
- java.util.List;
Complexity Adjustment Values (F_i) are used on a scale of 0 (least important) to 5(most important):
-
Does the system require reliable backup and recovery? Value: 4
-
Is data communication required? Value: 5
-
Are there any distributed processing functions? Value: 0
-
Is performance critical? Value: 2
-
System to be run in an existing, heavily utilized environment? Value: 3
-
Does the system require on-line data entry? Value: 5
-
On-line entry requires input over multiple screens or operations? Value: 5
-
Are the master files updated on-line? Value: 0
-
Are the inputs, outputs, files, or inquiries complex? Value: 3
-
Is the internal processing complex? Value: 3
-
Is the code designed to be reusable? Value: 5
-
Are conversion and installation included in the design? Value: 3
-
Multiple installations in different organizations? Value: 4
-
Is the application designed to facilitate change and ease-of-use? Value: 2