Proposed Technology

I. Proposed Technology Solution

The proposed solution in consideration will be used for:

a)Scheduling- eliminate any of duplication of duty through proper scheduling. This helps in avoiding conflicting employee attendance, ad also help the management control cost overruns associated with overtime

b)Time Clock

The employees can clock online to help the management save time on paper work and track the employees work hours in real time

c)Human Resources- the management will also carry out in targeted staff training, performance rating and appraisal and employee development at a centralized place. Management of HR document is also easy as it is done in a centralize place


All the employee salaries are managed in a centralized payroll system with less effort and in real time in robust system


The proposed solution also provides a system for HR reporting as it includes modules for communicating, and HR analytics


Management employee data and communicate their performance for adjustment or corrections as a way of assessing employee job satisfaction

I. Project Management

A. Project team

Project Manager: These personnel oversee the whole project from the beginning to the end. Hold the team accountable and manage the project resources both physical and financial resources

Executive Sponsor: this personnel is in charge of the project coordination between eh project team and the client here is known as UMUC

Project Team Members: these are the people directly involved in the project such as software programmers, technical assistant, project accountant, quality analysts, and testers

Supplementary Staff; these will be hired as needed to offer casual labor

B. Schedule

The project schedule is as indicated bellow. It will require further approval and ratification

The project schedule indicates the project phases, the tasks, and responsibilities of each group of personnel assign wed, the direction of each phase, the cost of funds allocated for each phase, and the goals of each phase (Assigned to: Yxx Zxxx; Estimate: 6 hours; Dependencies: Confirmation from all Development Staff; Completion: Jan 7 /14

The schedule will also indicates the milestone of the Systems development life-cycle from


The physical resources will include the software development kit, the office, and other utilities required

The human resources will be the project staff and this project team will be composed of 22 people

An estimate of the financial resources will be provided ad is estimated at $120,000

A test environment will be provided by the client after installation and the test will be arrived by the project team and the clients on site

In the store, access to the test environment must be available on identified nights to duplicate actual operation (Marakas, &, George, 2010, pp. 485–489).

C. Deliverables

Deliverables include the amount of work to be completed at each stage of software development life cycle

The SDLC include: System investigation, System analysis, Design, Environments, Testing, Training and transition, Operations and maintenance and Evaluation:

Employee or staff training

Support, repairs and maintenance


A. Planning

Developing a project management plan that will provide the framework within which the project is done and act as a roadmap for the project team in creating a shift planning software

B. Analysis

Determine the use or clients specific need and determine how these needs are met. Develop a blueprint indicating all the need, resources required and the provide a conceptual framework of the problem. A simple use case will suffice

C. Design

Hypothesize and document all the potential featured desirable to the client, and the other system users. Simple ER- diagram, use cases, and flow charts will also suffice here

Create a test plan, project code, documentation and support system for both sustainability and stability

D. Development

Transform the information into a shift planning software taking into consideration all the client specification and client specific system requirements

Obtain approval from the project management and quality analysis departments

E. Testing

Conduct alpha test to determine any form of vulnerability, risk, and problems

Repair, re-code and re-engineer. Then conduct an alpha test

Document all reports and carry out further research on the vulnerabilities and conduct beta test (Post, & Anderson, 2006).

F. Implementation

Install the shift planning software customized to the specific UMUC business

Hand over, and sign off to allow for complete program roll out

G. Operations And Maintenance

Provide periodic analysis, and support to staff

Provide occasional maintenance, coding and report to the system administrator.

III. Change Management And Employee Training

The project team will furnish the client’s staff with a blue print, user manual and training.

Onsite training and support will be provided for one month and later once a month for one year (Cummings, 2006).

There will be constant support for one year. The project support will be terminated at the end of one year

IV. Leadership Expectations

The project milestone will be achieved as indicated in the project charter. Time, cost, and quality factors will be considered based on the benchmarks. All project team will be required to report on the quality of work against the specifications and certify that the project delivery meets the client’s specification (Beynon, 2009).

V. Defining Success

All the clients specification must be met within time, budget, and quality without any cost overruns

Client acceptance will signify satisfaction with the project quality.


Beynon-Davies P. (2009). Business Information Systems. Palgrave, Basingstoke

Cummings, Haag (2006). Management Information Systems for the Information Age. Toronto, McGraw-Hill Ryerson

Post, G., & Anderson, D., (2006). Management information systems: Solving business problems with information technology. (4th ed.). New York: McGraw-Hill Irwin.

Marakas, James A. O’Brien, George M. (2010). Management information systems (10th ed. ed.). New York: McGraw-Hill/Irwin. pp. 485–489.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s