A finished DBA-955 Topic 7 access feasibility plan example, mapping each kind of access an insider study of technicians needs to the person entitled to grant it, with a fallback for refusal. Searches like "dba 955 topic 7 assignment example", "dba955 topic 7 sample" and "dba-955 topic 7 example" land here.
What a finished DBA-955 Topic 7 access feasibility plan looks like
The finished plan is a table with a short argument around it, and it describes what the eventual permission documents must cover without drafting any of them. Each row names one thing the study needs: interviews with technicians, interviews with dispatch supervisors, aggregated app usage logs and internal rollout documents. Against each sits the person with authority to approve it, which is rarely the candidate's own manager. Technician participation needs the vice president of field operations and, because the technicians are represented by a union, a conversation with the local representative. The usage logs need the data governance office and legal review. The plan also separates what the candidate may see in his job from what he may use as a researcher, and lists the records he will not touch even though his login reaches them.
How a DBA-955 Topic 7 example is structured
The plan is laid out in five parts. It opens by listing the data the proposed design requires, taken directly from the method section so the two documents cannot drift apart. The second part is the access table, pairing each data source with the role entitled to approve it, the conditions that role is likely to set and the current status of the conversation. A third part addresses the insider boundary, stating which records the candidate can reach through his job and committing not to use them without separate approval. The fourth part plans for refusal, describing how the design would change if one region, the union or the legal review said no. The last part sets out a sequence for obtaining approvals, with institutional review and organizational permission each placed where the university's process requires them, described without drafting any letter.
Data needs drawn from the method
Each row of the access table traces to a data source named in the proposed design, so the method and the access plan describe the same study.
Approval authority matched to each source
Technician interviews, supervisor interviews, usage logs and rollout documents each need a different approver, and the plan names the role rather than a friendly contact.
The union as a gatekeeper
Because the technicians are represented, the plan anticipates a conversation with their local representative about voluntary participation before any invitation goes out.
Job access separated from research access
Records the candidate can open through his operational login are listed and excluded from the study unless the data governance office approves their use separately.
Refusal planned before it happens
For each approver the plan describes how the design would adapt to a refusal, so one lost region does not end the study in the middle of collection.
Where marks go in DBA-955 Topic 7
The weakest access plan leans on a friendly manager's spoken assurance, which lapses with that manager's next reassignment and was rarely theirs to give. A second loss is treating job access as research access, where the candidate plans to analyze records he can already open without asking whether he may use them for a dissertation. Plans listing one approver for the whole study usually miss that interviews, operational data and documents fall under different authorities. Omitting a gatekeeper the setting plainly has, such as a union, a legal office or a works council, reads as unfamiliarity with the organization the candidate claims to know. Plans with no fallback treat approval as certain. Where a plan describes permission documents as already drafted and signed at the proposal stage, a committee will ask to see them.
Get a DBA-955 Topic 7 example written to your instructions
Send the DBA-955 Topic 7 instructions and your classroom rubric. We write a custom structural example to them, showing access mapped to the people entitled to grant it, in 24 to 48 hours, and the first one is free. Your dissertation is your own work: we never write chapters for a reader, and site permission letters, your IRB application, committee correspondence and signatures stay yours.
DBA-955 Topic 7 questions, answered
Who should approve access to my own company?
Whoever holds authority over the specific data or people involved, which is rarely the manager who likes the study. Interviews with employees, operational records and internal documents often sit under different approvers, sometimes including legal, data governance or employee representatives. The example maps each source to its approver so the eventual permission covers exactly what the study will use and survives a change of contact.
Can I use data I already access in my job?
Not simply because you can reach it. Operational access is granted for your role, and using the same records for research usually needs separate approval from the organization and review through the university's process. The example lists the records the candidate can open at work and excludes them from the study unless their research use is approved, which is the question a committee will ask.
Will you draft my site permission letter?
No. Site permission letters, institutional review applications and committee correspondence are the candidate's own documents, and they carry signatures that must be genuine. The example on this page describes, at a structural level, what an access plan typically covers and how it connects to the method, using a composite telecommunications case. Your dissertation and every approval behind it remain yours.