Model Status Report #1

First I want to thank Yanqui and Andrew for their "clarifing" questions especially in the area of objectivity. As I develop my model, you will see a system of "checks and balances" which will keep my objectivity in place. Much of this is on the front end but before approval is given some a means to "clearly evaluate" has to put in place. Yes, I did not address this very well at this time but it is a concern and as you follow it will be addressed.

Here is the report!

Background Information
Context: The Office of Disability Services alternate format operation will be undergoing a relocation and change in process delivery from a PDF process to Daisy process. It will require new software and new processing procedures.

The Developer: The developer will be the overseer of the transformation from PDF to Daisy. He will have to present to the staff as well prepare the staff and production workers for the change. Objectivity will be a concern due to the dual role.

The Intended Audience for the report (formal) will be the Office of Disability Services Staff as major changes need to be approved by the whole staff. Informally, will be the production workers and the funding source.


Analysis and Design

Rationale for ID: The rationale for ID is that the whole office has to know what we are doing and why. They also need to be able to explain to end users (students). Because there is a change in process not only are manuals required but a fair amount of training (hands-on) will be required.

Activities of the developer for each step.
i) First step is gather information concerning Daisy. Why is it better? What is the cost? How much more work is involved if any? Who is using it? How long to put it in place? What does the end product look like? Can it be easily taught to students? Can it contracted out to do? These and other questions need to be addressed before the Persuasion step can begin. Can be information from professional trainings, software manufactures information, information from other colleges. The result will be reducing the information to a simple written proposal.
ii) Second step is Persuasion step! This is presenting your idea to the whole staff. Any body can ask a question or present an alternative plan to yours. You need to anticipate those types of questions by either asking those parties in advance of the meeting for their opinion or ask colleagues from other colleges what obstacles did they encounter in getting it approved. The staff is looking at this for the benefit to the whole Office of Disability Services program, not just a stand alone service. You have put some effort into how this is going to implemented and how you are going to evaluate it. I may not have every manual written or purchased any equipment but I am presenting the plan. The result be answering all the questions and getting a vote.
iii) The next step is the decision. Creating a clear image of what you are going to do and addressing the staff’s concerns will help move the project to a positive decision. The majority of the staff must approve the project. If there is a major expenditure, the funding source needs to approve the project, hence for a will written proposal. The result will be project approval and funding.
iv) Implementation: This will require a change in process. The student workers are good with change if they understand why we are doing it. They even help finding ways to improve the process once they understand the beginning and the end product as most are graduate engineering students and have access to different information than I have. Training and manuals are written and done while equipment arrives.
v) Confirmation: Is it working or do we need to adjust something? Is the end product satisfactory? (readable, searchable and complete). Checking the first conversions closely will let me know if there are problems. Find source of problems and correct.