Development Of Equipment Rental System: Requirements, Development Approach, And Work Breakdown Structure

1) Determine the functional and non-functional requirements of your proposed system.
2) Justify the system development approach (Adaptive or Predictive)
3) Create a work breakdown structure based on SDLC.

The report is concerned with the development of the current project at hand. The current project is involved with the development of Equipment Rental System (Alter, 2014). The Equipment rental requires a web based application where the users can login and request for the equipment and can very easily check out from the services.

The report provides the documentation of the information about the development of the project.

The report contains the objectives and the aims of the project, the Work Break down structure of the project, Assumptions that were done during the development of the project, the issues that were faced with the development of the project. In addition to this the functional and the non-functional requirements of the software were also provided and the development approach that was undertaken for the development of the project is also provided in the report. In addition to all these some recommendations are provided for the further advancement of the report.

The main aim of the project is to develop an efficient software for the equipment rental check out system and also to develop a web based solution so that the users can easily check out from the rental service.

The objectives of the project are:

• To develop a software that would be used for the checkout function.
• To develop a software that would provide an efficient user Interface.
• To develop the project within the stipulated time.
• To develop the project within the allocated budget.
• To cover all the functionalities by the software.

Before the implementation of the system, several assumptions about the organizational requirements and the requirements of the staffs have to be made. In addition to this, the system development approach that was required for the software is also to be assumed.

The functional and the requirements of the system are identified as the following:

Functional Requirements

The functional requirements of the software are:

• The system should be accessible by the customers, staffs and the administrator.
• The user should be able to log in. The system should have proper authentication procedure for the log in process.
• The customers should be able to access the main menu and surf the whole system from there.
• In addition to this the customers should be able to view the status of the equipment and check if they are available or not. In case the equipment are available they should be able to rent the equipment and check out.
• In addition to this, staffs should be able to view the status of the items and also the details of the users. They should be able to enter new customer details manually and also update the customer details.
• The admin should be able to have an overview of the whole structure. In addition to this, they should be able to validate the request by the users.

In addition to the functional requirements the system should also be able to perform the non-functional requirements. The non-functional requirements of the system are:

Performance: The performance of the system should be very efficient. The time complexity of the codes used for the system should be very efficient.

Efficiency: The system should be very efficient functionally and also should be cost efficient. Hence, the design of the system should not be complex.

Reliability: The system should be very reliable and also provide efficient functionality to the users and the staffs.

User Interface: The interface of the system should be very simple and easy to access by all the groups of the users. In addition to controls of the staffs and the administrator should also be defined efficiently.

Maintenance: The system should be very easy to, maintain. In addition to this, the cost of maintenance and the procedure for the maintenance should be very easy and should be less complex.

Objective of the project

Scalability: The system should be scalable and can be expanded easily and should be flexible  and can be used for different type of options.

The system development approach that is used for the development of the system is the Predictive model for the development of the software (Pendharkar et al., 2015). The predictive model is the sequential designing of the software that is to be developed. In addition to this all the steps of the model are defined from start and also the planning of the system is done prior to the start of the implementing procedure of the system. In addition to this, the requirements of the system is assumed form the start. The cost for implementing the project and also the time required for the project is to be defined in this model. As this, project is not a very huge project hence, the predictive method is selected as the most useful model for the development of the project. In addition to this the approach that is applied for the implementation of the project is the predictive approach.

The main stages of the Predictive approach for designing of the requirements, designing, implementation, verification and maintenance. In the requirements phase the system requirements are defined. The requirements are of two types: the hardware requirements and the software requirements (Goyal et al., 2016). The hardware requirements specify the system requirements such as the memory of the machine and the processing speed of the machine on which the system is to be developed and it also to be kept in mind about the machines on which the system would be run. In addition to this, the software requirements provide the information about the software by which the system would be implemented. After the requirements of the system are decided the design or the plan of the software is decide upon in the designing phase. In addition to this, in this phase the overall outlook of the system is decided upon. Based on this design the outlook of the software would be reviewed. In addition to this, after the review of the design is done and the hardware and the software that are required are available the implementation phase of the software starts. In this phase the user interfaces are designed and also the backend coding of the software is done. In addition to this the integration of the software with the system is also done. After the implementation of the software is over it enters into the testing phase. In the testing phase the, the software that is implemented is tested. In his phase the issues that arises with the software are identified and solution for the issues that have come up are decided. After the decision about the solutions of the problems are decided the updating phase is started. In the updating phase the solutions of the problems that were decided upon are implemented. After the implementation of the solutions successfully the maintenance phase is started. After this the software would be dispatched to the organization from where they would be responsible for the further maintenance of the system.

Assumption about the System

The system that is implanted should be analyzed properly. The issues and the risks that are to be issues that are to addressed would be identified in this section of the report.

The issues that would be coming up for the current that is in place are:

In the current system there are no proper documentation about the checkout procedure. And hence, there can be loss of data form the current system.

In addition to this current system would be less efficient. The current system involves a long process for the customer to check out of the system. This can be very irritating for the staffs and the as well as the customers.

The retrieval of the data from the current system would also be very slow.

The system would also raise various kind of difficulties for the system administrator in looking over the whole system.

In addition to this, the system is not suitable for storing the data efficiently. Hence there are no security of the data that is provided by the customers.

In addition to this the overall procedure of the organization is also very inefficient. As they would be requiring more staffs to make their processing faster and also many customers would not be able to access the system.

In addition to this, the remote access to the system would also be not available.                                             

The following recommendation can be provided to the system for the further improvement of the system.

• The system should be allowing the members to view all the items of the store but only the people with the valid ID should be able to hire the items.
• The system should allow the users to create their profiles themselves and also provide the options of updating their details.
• In addition to this security constrains of the system can be increased to increase the overall security efficiency of the system.
• There should be an account page for the users where they can check their information and also details of the previous transactions.
• In addition to this there should be options for the users to retrieve the passwords in case they have forgotten their passwords.

Conclusion

For conclusion it can be said that, the report has been used to display the different kinds of requirement for the rental check out system. A detailed information about the system has been provided in the report. In addition to this the report is used to successfully to identify the functional and the non-functional requirements of the report. In addition to this for the implementation of the software the predictive model has been selected. The report provided an important insight on the predictive model of software development life cycle. In addition to this, the issues of the current system has also been provided and the recommendations for the further improvement of the system has also been provided.

Al-Nasrawi, S., & Ibrahim, M. (2014, June). Enabling e-Government Interoperability: EA-SDLC Mapping Approach. In European Conference on e-Government (p. 284). Academic Conferences International Limited.

Alshamrani, A., & Bahattab, A. (2015). A comparison between three SDLC models waterfall model, spiral model, and Incremental/Iterative model. International Journal of Computer Science Issues (IJCSI), 12(1), 106.

Alter, S. (2014, July). Potentially valuable overlaps between work system theory, DEMO, and enterprise engineering. In Business Informatics (CBI), 2014 IEEE 16th Conference on (Vol. 2, pp. 25-32). IEEE.

Arora, R., & Arora, N. (2016). Analysis of SDLC Models.

Goyal, R., Chandra, P., & Singh, Y. (2016). A Review of Metrics and Modeling Techniques in Software Fault Prediction Model Development. Covenant Journal of Informatics and Communication Technology, 3(2).

GUPTA, R. S., & LAXMI, V. (2015). Software Development Life Cycle (SDLC) Implementationin Information Technology & Management. International Journal of Recent Advances in Information Technology & Management, 1(1).

John, S. K., & Swapna, K. (2017). A New SDLC Frame Work for Website Development. AADYA-National Journal of Management and Technology (NJMT), 7, 132-142.

Khan, P. M., & Beg, M. M. (2014). Measuring Cost of Quality (CoQ) on SDLC Projects is indispensible for effective software quality assurance. arXiv preprint arXiv:1405.4824.

Khan, P. M., & Beg, M. S. (2013, April). Extended decision support matrix for selection of sdlc-models on traditional and agile software development projects. In Advanced Computing and Communication Technologies (ACCT), 2013 Third International Conference on (pp. 8-15). IEEE.

Kumar, N., Zadgaonkar, A. S., & Shukla, A. (2013). Evolving a new software development life cycle model SDLC-2013 with client satisfaction. International Journal of Soft Computing and Engineering (IJSCE), 3(1), 2231-2307.

Mahalakshmi, M., & Sundararajan, M. (2013). Traditional SDLC Vs Scrum Methodology–A Comparative Study. International Journal of Emerging Technology and Advanced Engineering, 3(6), 192-196.

Pandey, A., & Banerjee, S. (2015). Search based software testing: An emerging approach for automating the software testing phase of SDLC. Proc. ICRCWIP.

Pendharkar, P. C., Subramanian, G. H., & Rodger, J. A. (2015). A probabilistic model for predicting software development effort. IEEE Transactions on software engineering, 31(7), 615-624.

S., Kumar, S. D., & Thamaraiselvi, G. (2015). e-Governance Service Delivery Platform–Platform to Optimize SDLC, Re-engineering Application Architecture and Elimination of Processes. Indian Journal of Science and Technology, 8(15).

Wakchaure, M. M. A., & Joshi, S. D. (2015). A Framework to Detect and Analyze Software Vulnerabilities: Analysis Phase in SDLC. Journal of Modern Electronics, 4-1.