BCO6185 Mobile and Executive Computing For Web Application

Answer:

Introduction

The roster is an efficient method for the organizations to keep track of the employees and the staffs of the company. The method is adopted by several organizations for their benefits but this can very effortful work that has to be performed by a staff. Hence, in place of the manual roster system it is beneficial if there is computerized system that would maintain the roster automatically. This project is related to the development of such an application that would help the HR manager and the staffs that are maintaining the roster can very easily maintain the roster with the help of the mobile application.

This report provides the information about the development of the application and the specific requirements needed for the development of the application.

The project aims and objectives the and the need for the project is provided in this report. The project schedule and the documentation of the application is also provided in this application.

Needs Statement

The manual adjustments of the roster are a very difficult task for the business that are big. Hence, this application helps the staffs and the admin to maintain the roster more efficiently. This application is very efficient in case of the smaller businesses. The independent businesses would also have benefited from this application.

Project Aims and Objectives

The main aim of this project is to develop a solution for the for the small business and the medium sized organizations that would provide the options of handling the roster system of organization very efficiently.

The main objectives of the project are:

• To simplify the scheduling roster for the HR managers.
• To change the availability of the job using mobile very easily.
• To provide efficient notification procedures for the users of the application.
• To provide efficient performance for various type of users.

Project Scope

The application is very useful for the organization for the maintains of the roaster system.  There are various number of task that are within the scope of the project. It can perform the task of scheduling the shifts for the staffs of the company. The application will also provide the facilities of viewing the availability of the employee. It can also notify the employees about the weekly schedule automatically.  This project also provides an application that is affordable for the small scale businesses. the facility of adding a new staff for the organization is also provided in this application.

In addition to this, there are various tasks that are out of the scope of this project. The project does not provide any type of desktop version or mobile version for the software. For the interface of the system the web application has to be used. This software might be available for the medium and large sized businesses but would not impact the effectiveness to the level it would in a small sized business. The application would not be able to maintain the number of hours the employee is working in the company and legal problems regard the same.

Project Schedule

The schedule for the project is provided below.

Project Requirements

Functional Requirements 

The major functional requirements of this project are:

• Accessing the application both as an employee and an employer: the application provides the user the option to log in into the system both as an employee and also as an employer.
• Editing the roster: the employer would be able to edit the roster according to his requirements. This would also provide the employee the option of editing the details about the employees in the department.
• Login and Sign Up: The employers and the employees should be able to login and the register into the systems with the proper authentication data. In addition to this, the they application should also provide the security of the passwords in the system.
• Change availability: The employees of the system should be able to change their availability status according to the needs and also this data would be forwarded to the administrator.

Non-Functional Requirements

The non-functional requirements for the application that is being developed are:

• Access Security: The degree to which the framework is shielded against ponder and meddlesome flaws from interior and outer sources. The optimum security for the system is one of the major requirements as the application would be handling a large amount of user data.
• Availability: How much clients can rely upon the framework to be up (ready to work) amid "typical working circumstances". The system would be available to the HR managers on their systems. 

• Usability: The simplicity with which the client can learn, work, get ready sources of info, and translate yields through association with a framework. The system would be very useful for the small scale businesses.
• Accessibility: The degree to which the product framework can be utilized by individuals with the most stretched out scope of abilities to accomplish a predefined objective in a indicated setting of utilization. The system should be accessible by both the employee and the employers as well.
• Efficiency: The degree to which the product framework handles limit, throughput, and reaction time. The framework should be able provide sufficient as the requirement of the administrator.
• Integrity: How much the information kept up by the product framework are exact, valid, and without defilement. The data integrity is one of very important factor the system should be maintaining.
• Confidentiality: How much the product framework ensures touchy information and enables just approved access to the information. The system should be able to maintain the confidentiality of the staffs of the company and the company as well.
• Reliability: The degree to which the product framework reliably plays out the predefined capacities without disappointment. The system should reliable and should not crash unexpectedly.
• Safety: How much a product framework averts mischief to individuals or harm to the earth in the proposed setting of utilization. The system should be safe and have no point of access for the external intruders on the system.
• Flexibility: The simplicity with which the product can be changed to adjust to various situations, designs, and client desires. The system be able to increase and decrease according to requirement of the users.
• Maintainability: The straightforwardness with which blames in a product framework can be found and settled. The cost and effort required for the maintenance of the application should not be exceeding the capability of the company.
• Scalability: How much the framework can extend its preparing capacities upward and outward to help business development. The system should able expand and contract easily and should be possessing the responsive features.
• Portability: The simplicity with which a product framework can be exchanged from its present equipment or programming condition to another. The system can be accessed on any type of device and hence, the portability of the system is to be maintained.

Software requirements

The software that are being used for the application are a web development tool. The full stack development for the application can be done in visual studios and the Microsoft SQL Server is required for the development of the database for the system. The wireframe diagrams for the system are being constructed using the pencil application. In addition to this, the front end development and the prototype are being developed by the html and the JavaScript and the Jason Queries. The project only provides the demo instances of the actual application and not the actual instances. It is recommended that the back end coding for the software to be done in .aspx and C# methods. This would require object oriented coding for the development and the security of the application has to be coded in the web.config for the system.

Hardware Requirements

For the development of the system the machine has to possess a dual core processor that would be able to handle the processes that take place in the visual studio software. The system also needs to support a database application this would require at least 4 GB of primary memory and also it would require a sufficient amount of secondary storage.

Wireframe descriptions

The Wireframes for the applications have been developed on the tool named pencil. 

The loading page of the application would look like the figure above. It would contain the poster of the Roster system and in addition to this the name of the company can also be included in the poster of the application of the company. The page will also provide two option for the users. This would have to be enabled using the user controls features and this has to be implemented in the application by the use of any type of object oriented platform.  The user would be provided with the option of employee or an employer. After the selection of the correct option the user would be guided to the next page where the user would be able to log into the system and perform the tasks accordingly. 

The employer would be able to log into the system by the use of proper authentication data. The user credential is to be implemented in the validation of the submit button that is being used. The page also provides the option of forgot password for the user. The user would be able to recover the passwords to the recovery page they are redirected to. The user would be able to recover the details from that page. In addition to this, the page also redirects the users to the Sign Up page where the user would be able register into the system. 

After logging into the system the employer would be able to view the details of the roster and also would be having the option to edit the roster according the requirements. The employer would be able to access the data of the staffs using the Employee name and the ID of the employees. The employer would also be able to search the name of the employee using the keywords. 

The above figure provides the instance of a login of an employee. This is the dynamic representation of the web application designed for the companies. The employee would be able to login into the system and also they would be able to edit the details about their availability. 

It provides the instance of an employer checking out the details of an employee and also edit the roster according the demand of the company. The employee would be able to search the employee using the name of the employee. The employer then would be able to edit and details and save it accordingly.

Conclusion and Recommendations

For conclusion it can be said that the designing of the application has been done keeping in mind about the smaller organization and also the efficiency of the businesses for the companies. This report provides the information about the development of the application and the specific requirements needed for the development of the application. This paper is also to be treated as the documentation of the designed application. 

Bibliography

Bang, S.K., Chung, S., Choh, Y. and Dupuis, M., 2013, October. A grounded theory analysis of modern web applications: knowledge, skills, and abilities for DevOps. In Proceedings of the 2nd annual conference on Research in information technology (pp. 61-62). ACM.

Bensley, R.J., Hovis, A., Horton, K.D., Loyo, J.J., Bensley, K.M., Phillips, D. and Desmangles, C., 2014. Accessibility and preferred use of online Web applications among WIC participants with Internet access. Journal of nutrition education and behavior, 46(3), pp.S87-S92.

Benson, E., Zhang, A.X. and Karger, D.R., 2014, October. Spreadsheet driven web applications. In Proceedings of the 27th annual ACM symposium on User interface software and technology (pp. 97-106). ACM.

Jayakumar, S.K.V., Singh, J. and Joseph, K.S., 2014. Suitable QoS parameters survey for standard web services & web applications to understand their cloud deployability. Int J Comput Intell Inf, 4, pp.1-18.

Jiang, J., Lu, J., Zhang, G. and Long, G., 2013, May. Optimal cloud resource auto-scaling for web applications. In Cluster, Cloud and Grid Computing (CCGrid), 2013 13th IEEE/ACM International Symposium on (pp. 58-65). IEEE.

Li, D., Tran, A.H. and Halfond, W.G., 2014, May. Making web applications more energy efficient for OLED smartphones. In Proceedings of the 36th International Conference on Software Engineering (pp. 527-538). ACM.

Mansour, E., Sambra, A.V., Hawke, S., Zereba, M., Capadisli, S., Ghanem, A., Aboulnaga, A. and Berners-Lee, T., 2016, April. A demonstration of the solid platform for social web applications. In Proceedings of the 25th International Conference Companion on World Wide Web (pp. 223-226). International World Wide Web Conferences Steering Committee.

Mikowski, M.S. and Powell, J.C., 2013. Single page web applications. B and W.

Milani Fard, A., Mirzaaghaei, M. and Mesbah, A., 2014, September. Leveraging existing tests in automated test generation for web applications. In Proceedings of the 29th ACM/IEEE international conference on Automated software engineering (pp. 67-78). ACM.

Popa, R.A., Stark, E., Helfer, J., Valdez, S., Zeldovich, N., Kaashoek, M.F. and Balakrishnan, H., 2014, April. Building Web Applications on Top of Encrypted Data Using Mylar. In NSDI (pp. 157-172).

Roy Choudhary, S., Prasad, M.R. and Orso, A., 2014, July. Cross-platform feature matching for web applications. In Proceedings of the 2014 International Symposium on Software Testing and Analysis (pp. 82-92). ACM.

Trinh, M.T., Chu, D.H. and Jaffar, J., 2014, November. S3: A symbolic string solver for vulnerability detection in web applications. In Proceedings of the 2014 ACM SIGSAC Conference on Computer and Communications Security (pp. 1232-1243). ACM.

Weissbacher, M., Robertson, W.K., Kirda, E., Kruegel, C. and Vigna, G., 2015, August. ZigZag: Automatically Hardening Web Applications Against Client-side Validation Vulnerabilities. In USENIX Security Symposium (pp. 737-752).

Zhou, Y. and Evans, D., 2014, August. SSOScan: Automated Testing of Web Applications for Single Sign-On Vulnerabilities. In USENIX Security Symposium (pp. 495-510).