Program and Interface Design

The Proposed Payroll System

The proposed payroll system aims to automate all payment processes within the company. This would increase productivity and reduce job redundancy, allowing the club’s operations to run smoothly.

Work Breakdown Framework and Software Creation Life Cycle Documentation

The device would record the employee’s information. This paper describes the proposed information system’s work breakdown framework and illustrates the software creation life cycle documentation at the end of each module. Ray R Venkataraman and Jeffrey K Pinto (2013) highlights the activities in the preparation, review, design, and implementation phases, as well as the related SDLC documentation, at each assigned module.

Planning Stage

In the planning stage, a request is made to come up with an information system that will ensure all transactions of the organization are automated. This will reduce the costs of manual data entry and redundancy. The client thus delivers a Statement of Work. This will also boost the functionality of the existing systems thus an improvement in overall decision making in financial matters. Analysis of the possibilities of success in this project is conducted. This will determine if the proposed project is viable and whether it should execute or not. This will generate much focus to the project and give a clear outline of project alternatives. A feasibility study may include technical, financial, economic, and legal feasibility. The project plan can be developed for determining the viability of the project. This will include outlining the key objectives of the project to potential stakeholders, describing various roles and responsibilities of each stakeholder, determining the scope of the project and baselines. A quality and test plan document are expected here.

Analysis Stage

At the analysis stage, requirements of the proposed documents are specified. A requirement specification document is obtained. It combines the efforts of the client and the management team. Several use cases that are relevant to the system are created. This is also a combined effort of the customer and the management team, and a use case document is obtained. A requirement traceability matrix document is created that defines the different applicable process models. Data models such as relational tables, columns, object-oriented classes, and objects are also set up to capture the relevant details such as employee name, number, and other pertinent information in the analysis phase. A test plan document can be used to check changes in individual requirements.

Design Phase

The design phase aims at transforming the business requirements in the planning and analysis stage into a system architecture that meets the desired objectives of the organization. (Andrew Stellman; Jennifer Greene, 2006). The project development team creates a document that defines the design pattern and guidelines of the system. The report also includes user interface standard maintenance. It is known as a design document. A requirement traceability matrix document outlines an alternative model of the system and the architectural report as specified in the analysis stage. This document is subject to change based on the system design and User interface guidelines. Since requirements in SDLC change often, a test plan document is created. Program units and related processing logic are defined in the physical plan process model which will lead to the design of the program and specifications for files and databases. These are captured in the design document.

Implementation Phase

During the implementation phase, the desired system is worked on physically. This involves installation and training of users on how the system is used. Andrew Stellman; Jennifer Greene, (2006), highlights that a code review document is created to analyze what was done during the coding period. The test plan document is examined to determine if there are changes. A test review is conducted, and the organization changes the management plan. A business contingency plan is then devised for risk management purposes. Training of users on the use of the system is conducted. (Basu, 2015)

References

Andrew Stellman; Jennifer Greene. (2006). Applied software project management. Beijing ; Farnham: Farnham : O’Reilly.

Jeffrey K Pinto; Ray R Venkataraman. (2013). Cost and value management in projects. Hoboken, N.J.: Wiley.

Basu, A. (2015). Software quality assurance, testing and metrics. india: Prentice-Hall Of India.

Gregory, P. H. (2015). CISSP guide to security essentials. Australia : Cengage Learning.