Quality management plan
The quality management plan would be based over how important it is to maintain the quality of the any project that is being undertaken. Software development procedure without the management plan for maintaining quality is not possible (Weinberger et.al, 2011, September). The sole purpose of this particular agenda is to define the quality standard along with the pathway for maintaining the quality. The team members including administrative to developers, each one of the workers are bound to comply with the rules, regulations and the standards of this particular plan. The fundamental of this plan revolves around certain perspectives and purposes, including:
- Ensuring quality standard has been adhered
- Defining the way quality is to be managed
- Defining quality assurance activities
- Implementing acceptable or reasonable quality standards
Closure checklist and project evaluation
This particular document would consist of a checklist regarding if every task and activity has been accomplished or not. This is a document that every software development project manager has to present upon completion of the entire project. It is one of the most important and obvious roles of the project manager to ensure that each and every task that has been included in the WBS (Work Breakdown Structure) and following documents have been achieved and fulfilled successfully (Winesett, 2012). This particular document can also be referred as the evidence showcasing a successful achievement of the complete project. The closure checklist for this project would certainly follow the fundamental or conventional template and would include the following aspects:
- Handing over total deliverables
- Each of the deliverables have been signed off and have also been acknowledged by the client or sponsor
- The final status of the project is complete
- Every financial process and the report is complete
- Assessing the project post complete is also complete
- Assessing staff presentation is approved and complete
- Staff unemployment over the termination of the project
- Every procedure and the contract have been terminated post completion of the project
- Every site and their operations initiation are shut down
- Discarding materials and equipments is finished
- Making announcement regarding conclusion of the final project
- Storage upon conclusion of the project
Budczies, J., Klauschen, F., Sinn, B. V., Gy?rffy, B., Schmitt, W. D., Darb-Esfahani, S., & Denkert, C. (2012). Cutoff Finder: a comprehensive and straightforward Web application enabling rapid biomarker cutoff optimization. PloS one, 7(12), e51862.
Charland, A., & Leroux, B. (2011). Mobile application development: web vs. native. Communications of the ACM, 54(5), 49-53.
Corral, L., Sillitti, A., & Succi, G. (2012). Mobile multiplatform development: An experiment for performance analysis. Procedia Computer Science, 10, 736-743.
Espie, C. A., Kyle, S. D., Williams, C., Ong, J. C., Douglas, N. J., Hames, P., & Brown, J. S. (2012). A randomized, placebo-controlled trial of online cognitive behavioral therapy for chronic insomnia disorder delivered via an automated media-rich web application. Sleep, 35(6), 769-781.
Felt, A. P., Greenwood, K., & Wagner, D. (2011, June). The effectiveness of application permissions. In Proceedings of the 2nd USENIX conference on Web application development (pp. 7-7).
Finifter, M., & Wagner, D. (2011, June). Exploring the relationship between Web application development tools and security. In USENIX conference on Web application development.
Han, W., Yang, Z., Di, L., & Mueller, R. (2012). CropScape: A Web service based application for exploring and disseminating US conterminous geospatial cropland data products for decision support. Computers and Electronics in Agriculture, 84, 111-123.
Heitkötter, H., Hanschke, S., & Majchrzak, T. A. (2012, April). Evaluating cross-platform development approaches for mobile applications. In International Conference on Web Information Systems and Technologies (pp. 120-138). Springer Berlin Heidelberg.
Horner, J. (2011). RApache: Web application development with R and Apache.
Osentoski, S., Jay, G., Crick, C., Pitzer, B., DuHadway, C., & Jenkins, O. C. (2011, May). Robots as web services: Reproducible experimentation and application development using rosjs. In Robotics and Automation (ICRA), 2011 IEEE International Conference on (pp. 6078-6083). IEEE.
Singhal, M., & Shukla, A. (2012). Implementation of location based services in Android using GPS and Web services. IJCSI International Journal of Computer Science Issues, 9(1), 237-242.
Subashini, S., & Kavitha, V. (2011). A survey on security issues in service delivery models of cloud computing. Journal of network and computer applications, 34(1), 1-11.
Tipton, H. F., & Nozaki, M. K. (2012). Information Security Management Handbook, Volume 6. Auerbach Publications.
Weinberger, J., Saxena, P., Akhawe, D., Finifter, M., Shin, R., & Song, D. (2011, September). A systematic analysis of XSS sanitization in web application frameworks. In European Symposium on Research in Computer Security (pp. 150-171). Springer Berlin Heidelberg.
Winesett, J. (2012). Web Application development with Yii and PHP. Packt Publishing Ltd.