We Have Numbers Of Free Samples

8.1 Testing Overview

8.1.1 Test Strategy – Unit Testing

Unit testing is a part of the software development process during which the smallest testable components of a software which are known as units are independently and individually scrutinized. The purpose of unit testing is to ensure that a particular software or application is able to operate successfully after roll out. In this context, Johnson (2014), mentioned that the unit testing is pivotal to ensure that a concerned application is able to meet customer expectation through detection of even smallest defects and correcting the same before rolling out of the application. Here, in current scenario, it is important to note that the unit testing for NJ transit app can be done manually or automatically.

In present context, the following tests would be performed as a part of unit testing for NJ transit app:

Module Interface Test:

Under the module interface test, it would checked if the information related to transportation is flowing properly into the module or program unit and also whether the same is able to be out of the unit as well or not. This testing can help in detecting the stability in information flow of the system.

Local data structures:

In the view of Zhen et al. (2016), storage of data is an essential part of software development process. Local data structures of the NJ transit app would be tested to ensure that the same is capable of storing the data properly within the module or unit. This is essential to deliver the best quality transport automation services to the customers.

Boundary conditions:

One of the most common reasons for the failure of many software is the failure of the same in respect of conditions related to boundary. Hence, in current scenario, the boundary related conditions of the NJ transit app would be tested. The purpose of the boundary testing would be to ensure safety of the program along with its functioning at the boundary level conditions.

Independent paths:

The NJ transit app has several independent paths that runs without any dependence on others. It would be tested to ensure that the independent paths of the NJ transit appare working properly, meeting objectives and also terminating properly after the end of the program. This is essential for ensuring uninterrupted functioning of the transit app.

Error handling paths:

Errors can occur during the functioning of an app. However, error handling units of the NJ transit app would be tested to ensure that the same is capable of rectifying errors properly and quickly to ensure that the NJ transit app is able to keep pace with real time transport data.

8.1.2 Test Strategy – Integration Testing

Integration testing is just the opposite of unit testing approach. Under integration testing, various software modules are combined and tested as a group. In current scenario, integration testing of the NJ transit app would be conducted before validation testing and after unit testing. The purpose of integration testing is to check if the NJ transit app is able to perform as a whole and deliver the expected results.

The objective of integration testing is to detect faults in the interaction between integrated units. In this context, Esplugues et al. (2014), stated that test drivers and test stubs are mainly used to perform integration testing. Thus, integration system would be performed in current scenario to identify defects in the interfaces and also those which are lying in the interactions between integrated systems or components. In present context, two different aspects of integration testing of NJ transit app would be component integration testing and system integration testing. Component integration testing would be used to identify defects existing in the interfaces and interaction among integrated components. On the other hand, system integration testing of NJ transit app would involve examining the integration of packages and systems along with testing the concerned interfaces to external organization. Examples of the same are internet, electronic data interchange and others.

In present context, independent testers would be hired to perform integration testing. The following are the common approaches that could be used for integration testing of NJ transit app:

Big bang:

Under big bang testing approach, all or almost all the components of a software are combined and tested at one go. This testing technique can be used only when the software is received entirely by the testers. Here, in this context Benner et al. (2014), stated that the main difference between system and big bang testing method is that the former tests a software entirely whereas the later one tests the interactions among the components of a software.

Top down:

The top down approach of testing is a process of software testing under which units at the top level are tested first whereas the units at the lower level are tested later on step by step. Here, it is important to note that the top down testing approach is used when the concerned software is also developed following a top down software development approach. In this process, the test stubs are required to stimulate units at the lower level which might not have been available during initial phases.

Bottom up:

Bottom-up approach is just the opposite of top-down approach as under this technique, lower level units are tested first whereas the top level units are tested subsequently later stepwise. This approach can be used only when bottom-up testing approach is followed for software development. Unlike top-down approach where test stubs are required, this approach needs test drivers for stimulating high level units.

Hybrid:

Hybrid strategy is the combination of both top-down and bottom-up integration testing strategy.

In current scenario, Bottom-up testing strategy would be used to test the transport app in Srilanka. Hence, the lower order units of the app would tested first followed by the lower order units as the app is developed in the same way as well.

8.1.3 Test Strategy – Functional Testing

Functional testing can be defined as a quality assurance process and a sort of black box testing which is based on the specifications in respect of the software component under test. In other words, under this testing facility, the transport app would be tested against the specific criteria or functional requirements. In present context, functions of the transport app would be tested through feeding the required input and generating outputs. These would help in understanding if the outputs are capable of meeting the expected standards. In this context, Neves et al. (2014), mentioned that functional testing ensures that the needs are well met by the concerned application. Here, it is important to note that functional testing is concerned with testing the processes of a software rather it is concerned with the outcomes or results of the software. The focus is hence on content and not process.

In present context, the testers would use black box testing technique to test the transport app. Under this strategy, the internal logic of the transport system app would be tested without any knowledge to the tester. In addition, the testers would test the transport app during the period of conducting of acceptance testing and systems testing.

In current scenario, the transport app for Srilanka would involve the following steps:

• Identification and determination of functions that the software is expected to deliver
• The functional specifications would be used to create input data for functional testing
• Determination of outputs to be generated by the transport app
• Execution of the test case
• Comparison of actual outputs against expected results

In the view of Von Krogh et al. (2012), the main benefit of functional testing is that the same stimulates actual system package. In addition, functional testing does not require any systems structure assumptions. On the contrary, functional testing bears a high possibility of redundant testing. In addition to this, it has strong chances of missing the logical errors in the software.

Functional testing is best effective when the test conditions are generated directly from the business needs. On the other hand, if test conditions are generated from system documentation, design documents, system requirements then functional testing would not be able to detect the defects present in the documentation part. Such defects can only be detected by the end users when they use the product. Hence, in present context, the testers would conduct functional testing based on the basis of test conditions that are created directly from the business needs. This would help in detecting maximum possible functional errors of the transport app which can be rectified prior to launching the app in the market as a whole. The experience of the end users is expected to improve by this and result in greater satisfaction level of the users.

 8.1.4 Test Strategy – Regration Testing

Regression process in context of software development and testing refers to the systematic process of testing changes in respect of computer programs to ensure that the older programming skills work properly with the newly implemented changes. Regression testing is a normal part of the program development process. Regression testing is a kind of software testing which seeks to verify that the previously developed software and currently developed software performs in a correct way even if the same was replaced or interfaced with some other software. Such changes can include software enhancements, configuration related changes, patches and similar others.

In present context, the likelihood of the impact of changing codes on the functionalities which are not directly related to the code would be tested through regression testing. In other words, regression testing in present context would seek to ensure that resolving a particular problem has not led to creation of another problem. Here, it is important to note that in case of the transport app, new test cases would not be used rather, the test cases used earlier would be re-executed in case of conducting regression testing on the transport app.

The good thing about regression testing is that the same can be executed at any level of testing like the acceptance testing, systems testing or unit testing. In current scenario, regression testing would be conducted during the acceptance testing phase. On the other hand, Thiels et al. (2015), mentioned that regression testing requires considerable time which is a main limitation to this testing form. In order to cope with time limitation, the testers would conduct an impact analysis in respect of the changes to highlight areas of the transport app that have the highest chances of getting affected by the change and also the ones that have high level of impact on the end users. In other words, the testers would identify such areas of the software and focus regression testing on these areas only.

8.1.5 Test Strategy – Load/Performance Testing

Performance testing mainly involves determination of the effectiveness or speed of a particular software, computer program or app. In current scenario, performance testing would be conducted on the transport app through quantitative test forms through measuring response time of the system. Here, the Millions of Instructions per Seconds (MIPS) would be used to test the effectiveness of the transport app.

In present context, the following types of testing would be used to conduct performance test on the transport app:

Load testing:

Load testing would be used to assess the behavior and working capability of the transport app at increasing workload level.

Stress testing:

Stress testing would be conducted on the transport app to understand the working capacity and behavior to meet workloads that are beyond its existing capacity.

Endurance testing:

Endurance would help in testing the performance of the transport app when a significant volume of workload is given on a continuous manner.

Spike testing:

Spike testing would be useful in understanding the behavior of the transport app when a workload is given suddenly or when the workload is increased substantially.

8.2 Test Plan And Test Cases

A test case can be defined as the set of different variables or conditions under which a tester will decide if a particular system work in a proper way and also meets the desired working criteria:

In present context, the test case in context of testing the transport app would contain the following:

Test suit ID	The number of the test suit under consideration
Test case ID	The ID of the particular test case
Test case summary	The main objectives of the test case
Associated requirements	The requirements to which the test case relates to
Prerequisites	Pre-conditions which need to be met prior to conducting the test
Test procedure	Stepwise process of the test
Test data	Test data in respect of transport app that are to be used for test
Expected result	The desired outcome from the test
Actual result	Actual outcome from the test post completion of the test
Status	Pass or Fail
Created by	Name of the person prepared the test case
Creation date	Date on which the test case has been created
Executed by	Person who conducted the test
Execution date	Date on which the test is carried on
Test environment	The environment  under which the test was conducted

 

8.3 Test Results

Test results in respect of the transport app would be prepared and communicated to the concerned people in the following template:

• Executive Summary
• Major issues
• Other issues
• Coverage
• Possible alternatives
• Our test strategy
• Justification for chosen test strategy
• Test outcomes
• Interpretation
• Limitation of test strategy

 Chapter 9: Maintenance

9.1 Overview of Maintenance

In the words of Thüm et al. (2014), the term software maintenance refers to all the updations of the software and the modification of the same after the software has been delivered to the users. The modification made to the application software is because of a number of reasons. The maintenance of the software is also divisible into various categories depending upon the nature of the same. The maintenance may be a regular one or it might be based on detection of a threat to the software. The maintenance of the software on the basis of the nature, character or feature of the same may be illustrated as follows:

Corrective maintenance

The following category of maintenance is applicable in case of the software breakdown. According to Von Krogh et al. (2012), the process involves the task undertaken to return the software equipment to its proper working condition or order. This system of correcting the application can either be planned or it may be unplanned. The planned system of maintaining the software is the resultant of a run to failure plan of maintenance. It can be stated here that the planned structure of maintenance is a part of the preventive maintenance plan.

On the contrary, the unplanned maintenance plan is the resultant of a system breakdown that could not be controlled by the preventive maintenance plan. The following may also be a result of a failed maintenance plan or absence of the same. As stated by Crowston et al. (2014), the unplanned planning of maintenance is higher than the planned maintenance in terms of cost. The planned maintenance is often regarded as the most ideal plan of maintenance. The planned maintenance of the software is the resultant performance of the program requiring condition monitoring. The following maintenance plan is triggered because of specified conditions. In the planned maintenance of the software the structure focuses on addressing the root cause of the requirement of the maintenance plan and hence considered to be ideal.

Adaptive maintenance

The following method of software maintenance is applied for the purpose of modifying and updating the software in order to keep it up dated in the new era of changing technologies. The updation of the software is required to make innovative changes in the application that may benefit the users along with the makers in luring more consumers.

Perfective maintenance

The following system of maintenance aims at making the applicable for a longer time period. In other words, it works towards refining the existing software in order to enhance its performance and make it reliable as per the requirement of the users. It also includes development of new features in the software that may be helpful for the users of that particular software.

Preventive maintenance

As the name suggests, the following category of software maintenance is aimed at preventing the future problems that have the possibility of occurring in the future. The stated problems may appear to be insignificant at the prior moment but result to some maintenance issues in the future.

9.2 Deployment/Release Plan

In order to make a suitable release plan, it is highly important for the software company to make a clear set of guidelines for the purpose of releasing the software. Few important things that company may focus upon can be the frequency of the release of the software. In this context a separate guideline may be framed by the company to meet the deadlines of the software release. As observed by Benner et al. (2014), the next part of the release plan includes creation of a template for the software that contains the necessary guidelines for the software engineers and developers to assist the individual release of the software. The company also requires stressing associated with the release plan to improve the efficiency in which the software can be released to the users. The creation of the strict guidelines may help the company to frame an efficient plan of release.

For the following purpose the managers of the company associated with project, marketing and sales may help in development of the new features that may added to the application upon its release.

The next step would be communicating the date of release agreed upon by the company to all staffs. The last step of the release plan would be assigning the duties to the staffs of the company according to their abilities for the execution of the software release.

9.3 User Manual

At first user residing in Srilanka requires to download the transport application in its android phone. As observed by Dingsøyr et al. (2012), after downloading the first time users need to register themselves by providing the necessary information such as the first name and last name of the user, the email id of the user to send in the notifications, the phone number to make contacts with the user and setting the desired password by the user to protect the profile of the user. On the completion of the registration process, the user may login the application.

The first part of the application will provide the options of viewing the bus schedule along with the train schedule of the city. Once the user selects the mode of transportation, the option of pickup location and drop location is provided. The user requires filling in the columns of the required destination. After selecting the venue, the mode of payment option is provided where in the users may choose to make online payments or pay cash on reaching the destination. The bus or train id along with the seat numbers will be provided to the users for easy accessibility.

9.4 Roll Out

The roll out involves the identification of the specific requirements of the software that is to be deployed. This includes the use of the application, the training topic associated with it, the departments of the same and the users. The roll out plan also consists of communicating the benefits of the launch of an application to the users of the country. Through the way of specifically addressing the concerns related to the software, the discomfort of the users linked to the usage of the application may also be mitigated. This software company may aim to provide early training to the employees and staffs and to keep a check that they are targeting the correct users as per their destination requirements. Along with this, sufficient IT support may be available to check the technological errors that may occur in the online services and the application.

Chapter 10: Risk Management

Risk is an integral part of life. The Risk Management is essential part of all the steps of life. The normal life processes are also intertwined with a series of risks which is not that evident to us since the art of managing the risks is already learnt with the advent of time. The risks need to be overcome and subdued in such a way that the potential benefits from the total process can be extracted without being impacted by the threats associated with the processes. In the words of Neves et al. (2014), presently, all the existing functions and operations pertaining to daily life need assistance from the perspective of health and safety, insurance and various others. Enterprise Risk Management is also a part of many organizations at maintain risk at minimal level in the organization and the associated networks also. The transit application of Sri Lanka is based on the total transportation systems across the country.

Risk is inherent in nature and is associated with each of the things done. The Inherent risk management is most essential to manage the rising level of risk in any project (Johnson, 2014). The uncertainty of results or incidents that can have any effect on the result of the project both positively or even negatively actually leads to risk.

Steps of risk management:

The main steps of risk management can be understood with vivid understanding.

Risk Identification:

The process of risk in identification involves actually knowing the project from very detailed angle. Here, Islam et al. (2014) mentioned that the team members working on the project, planning for the project, defining the aspects of the project can be most aware of the processing and the risk associated with the same. The risks need to be identified, recognized and detailed so that the other people can also be aware of the risks and take preventive measures accordingly. Risk identification can be managed by different techniques among which, the most popular one is risk register. The 7 Cs that defines the working benefits of Risk Register can be identified as: Consistency, Concision, Compactness, Control, Commitment, Completeness and Communication (Bansal, 2014).

Risk Analysis:

The Next step for Risk management is Risk Analysis which involves understanding the probability of occurrence of risk and the significance of the risk. The chances and the weightage of the risk on the application is very important to be evaluated (Cat et al. 2016).

Evaluation of the Risk:

The magnitude of the risk is used to evaluate the risk. Probability of occurrence and the significance of the associated risk on a combined basis give the risk value to the process. The risk score has a prescribed acceptable limit. Each risk has to be gauged whether within or above the acceptable limit and the steps are taken accordingly.

Response to Risk:

The next most important part is responding to the risk. Planning is essential for risk mitigation. Zhenshan et al. (2014) mentioned that the risk management deals with implementation of effective tools to mitigate the significance or at least the chances of occurrence of the risk. The risk mitigation planning and action protocol is efficiently done in this step.

Monitoring the risk:

Once the risk mitigation procedure is implemented, the constant monitoring is needed for ensuing the risk does not get chance to re-enter in the system. The performance of the risk mitigation procedure is to be monitored at constant level. Thiels et al. (2015) mentioned that the most significant part is monitoring as this can identify any further chances of entering into another risky zone of operations. The effectiveness of monitoring the risk is essential for keeping the application free from further risks.

Risk management of the mobile transport transit application:

The Risk associated with the present transport transit can be understood in details after analyzing the working criteria, performing mechanics and the result declaration capacity. Some of the risks can be identified as below:

Technical Risk:

The most important risk associated with the application is proper functioning of the application. The applications that have malicious codes in the applications can access the data and all details on the phone at which the same is installed. This creates a huge problem for the users to control the data leakages. The technical risk is even associated with the application. The most disappointing situation occurs when a passenger tries to find out the next transportation and gets the information only after the transport has left the station or stand. This is the most harassing situation and can impact the acceptance and popularity of the application.

Johnson (2014) stated that the technical team working on the application designing and maintenance has to be very efficient in streaming all the data coming from different sources in the form of queries get diverted to correct pathway for deriving at the required answer. The updating of all the information has to be done in real time basis so that the application can be actually helpful in the time of getting a proper transport option.

The navigation option of the application has to be strengthened to identify the location of the user and inform the appropriate transport option for the same. The maps available in the application have to be capable of showing direction for reaching the bust stoppage or station from the current location of the user. Provided the technical strength of the application is enhanced, the popularity and mass usage will be just a stoppage away.

Device Risk:

The application is maximally functional in android mobiles. The risk of loss of device or non-functioning of the device can be most high in risk impacting to the performance of the software at present. The GSM mobiles used can use the signal strength of the telecom service providers’ network. But accessibility of Wi-Fi can also be helpful in getting connected to the application. But once getting connected to unprotected Wi-Fi can call a huge volume of malwares in the system. The malwares or viruses slowly or even instantly get control on all the applications at the phone. The data get lost or get stolen once for all. Memory corruption of mobile can also lead to the complete loss of data from the software even can just stop the functioning of the mobile. Sudden accidents can cause physical damage to the mobile handset that can cause complete stop of the functioning of all the programs including the application. Risk of the device can be considered as one of the most potential risk of the application. Irretrievability of data, memories is a major loss with device damage.

Bansal et al. (2014) suggested that proper handling of all the devices can combat the situation of being hampered by such loss or risk. The presently available insurance to mobile handsets can be applicable to fight the loss of data and device. There is different software that even allows retrieving deleted data from the phone memory. Software and hardware experts can work together to mitigate the device risk associate with the transport transit application.

Risk of Inappropriate information:

The Transport transit application has been implemented for gathering and delivering appropriate information related to transportation systems available at the required location. Here, the most important function is of the back end team with complete coordination with the real time information system of the related transportation systems. The information management system is very important in this aspect as only when correct information will be available the same can be percolated to the users.

The system updating officers handling the information management system is very important in this segment. The correct information has to be extracted and the same has to be published in web so that the authenticity and dependability of the application is beyond question.

Financial Risk:

The software designing has a predefined estimate prior to approval from the Sri Lankan Government. The risk becomes eminent when the estimate is crossed while designing, implementation and launching the application. Once the investment on the application designing has started, the process cannot be stopped as then the whole money will drain out. The only way is to maintain an expense monitoring system to control on the extra money usage. The risk also remains in irretrievability of the expensed money. Popularity is solely uncertain as that depends on the capability of the application to produce authentic and real time data. Zhen et al. (2016) mentioned that the most significant part is popularity as then only the application will be extensively used leading to different ways like pop up advertisement through the application which can ensure expected returns.

Marketing Risk:

The marketing capability of the application has to be efficient enough to ensure proper popularity of the application. The risk of improper marketing strategy may lead to the lower acknowledgement and acceptance of the applications for the Sri Lankan public transport users. Reaching the potential users remains a challenge in all cases. Transport application can be sent to maximized users by push SMS and push mails. Forced SMS can contain the link of the application and flash the special features that can be most beneficial for the users. However, the policy has to be implemented keeping in mind not all users have android phones. In such cases, the link cannot be operative. The unavailability of the suitable platform for installation remains a risk. Also, the customers registered in Do not disturb services cannot be sent such push marketing policies. Ability to reach all potential users is a risk for the application.

The most efficient marketing can be done through social media with two way communication among the users and the launchers. This can provide the platform for the marketing risk to be reduced to a major fraction. The social media can act as a marketing tool as a single user who has enjoyed the benefit of the application has the potential to like the service on the social media letting a huge number of followers get aware and interested in the application leading to downloading the application and using the same.

Risk related to Network unavailability:

The application is completely based on internet. The facilities, functions, features are all available and applicable only when connected to internet. The most concern pertaining to internet is availability of network. The most necessity to get the update of transport arises when the availability of transport get hindered due to poor weather condition. Now, the most important part related to weather condition is that, poor weather condition caused transport delay which leads to excess traffic pressure in the transportation system. The risk arises when during the poor weather condition, the network connectivity is disrupted. Esplugues et al. (2014) emphasized that during the hours of need, the availability of the network can impact on the acceptability of the application.

In such cases, the application can be used for sending the users text SMS related to all available transports near the last identified location of the user with the contact number of the transport person to be contacted by calling. The facility can be used immensely in the emergency hours. The rider can check the required bus or any other public transport details and call the travel coordinator in person. The connectivity can be issue, but still this extra step taken can be of great help.

Goodwill risk:

The transportation transit application is launched as a part of the Sri Lankan Government. The application can be endorsed with the symbol of the Sri Lankan Government.  The most risky part remains maintaining good will of the application. This can be achieved by proper functioning of the application, real time data updating, correct and authentic data available in the portal and the availability of link of the website during any online transactions like online booking, ticket can collations and others. Here, the most important part is that proper maintenance and constant monitoring of all the data streaming functions available at the site. Once the proper care is taken on maintaining and updating, good will automatically starts on developing. Maintaining the goodwill is again a constant job that the persons at the back end of the application have to ensure.

Chapter 11: Critical Evaluation And Conclusion

11.1 Summary of the Project

The following project is focused on the development of the transportation application software in Srilanka. The application has been developed and formed by the software engineers and through testing has been concluded to testify the applicability and user benefit of the software. The different categories of test strategy have been use in this regard that consists of unit testing, integration testing, functional testing, regration testing, performance testing, the plan of testing and the results of the test. In addition to this, the maintenance of the application software has also been added along with its various types being corrective, adaptive, preventive and perfective plan of maintenance. The release plan of the transport application software has also been structured well and the responsibilities in this regard have been allocated among the employees of the software company. The user manuals have also been structured to facilitate the use of the software application by the users.

11.2 Evaluation Of The Solution

As the transportation system of Srilanka was based on manual support it wasted a lot of time of the passengers as well as the officials that were engaged in providing such services. In order to avail the buses or trains earlier, the passengers had to reach the bus depot or station before down to stand in the queue of ticket. This wastes a lot of time of the passengers and also requires more labor. On the other hand the online system of access to the vehicles reduces the wastage of time and labor.

11.3 Limitations Of The System

The following system of the software application is applicable only for few sections of the society. As the usage of this transportation requires using the android application base the old age generation may not be able to use it. The application is aimed at serving the tech savy generation and not the whole lot. Therefore, the following technology may not benefit all people. Furthermore, the following system of applicable is dependent on the internet services. The speed and availability of the internet services may vary due to the geographical factors.

The internet services are greatly affected by the weather conditions of the particular locations. A heavy rainfall or cloudy and windy weather may lower down the frequency of the internet services and in such a case the transport application may turn out to be useless. It should be noted here that at time of bad weather conditions the passengers are in more need of the transportation facility and in such a situation, the application may fail to serve the passengers and turn out to be a total failure.

The maintenance of the transportation vehicles is another contributing factor to the limitations of this software facility. There are chances that the vehicles so provided may not be well maintained leading to its stoppage in the middle of the process of transportation. This may affect the brand image of the software and have an adverse effect on the quantity of consumers.

11.4 Future Enhancements

The software company may focus on the development of the software that may reduce the impact of bad weather conditions on the working efficiency of the transport application. The application should be developed in a way that it may be able to function even in slow internet speed. This way the company may be able to provide the transportation facilities to the passengers even during bad weather conditions. Further, the software may be developed in a way that the users are provided with the numbers of the drivers or conductors of the vehicles that the passengers will avail to. This way the passengers may be able to communicate with the drivers and will not have to be dependent on the internet services.

11.5. Lessons Learned Report

The older generation of people residing in Srilanka has to face a lot of trouble in the absence of the online facilities of transportation system. The old people have to wait in the queue standing for long period of time which has a bad effect on their health. In the presence of online facilities such will not be the case. In times of emergency the vehicles may not be available whereas the presence of transportation software may facilitate an easy access to the vehicles.

11.6 Conclusion

The following piece of research work is conducted by the researcher to aim at the development of the application software to facilitate the transport facilities. In this context, the researcher has framed a strategic plan of action regarding the designing, testing, managing and maintenance of the software. The researcher has provided a detailed description regarding the design of the software. The usage of the same by the users and the relationship that will exist between the provider and the user has also been explained. The chain of communication between the service provider and the passengers has been discussed along with the ways of communication. In addition to this, the researcher has also stated the various ways of maintaining the software and ascertains the use of the same for a long period of time. The release plan of the software company for the release of the transportation software has been structured by the researcher. This may be of much benefit to the company.

Besides, the researcher has also stated the possibilities of the various limitations that can have an adverse impact on the applicability and usage of the software by the user. The suggestible remedies for the said limitations have also been provided by the researcher the implementation of which may benefit the software company.

[Download not found]

Download