Answer to Question #229315 in English for Dee

Question

Question 1: Plan the assembly by completing the following steps. (US14939 SO1)

• Identify and explain the feasibility of the specifications provided above (US14939 SO1/AC1).

• Provide an estimate of the effort, duration and resources required for the assembly

(US14939 SO1/AC2).

a. List Individual components to be used, specify which components are associated with

LAN (US14913 SO2/AC2)

b. Provide a detailed description of each component (e.g. capacity, speed, ports,

connections, cable types, serial numbers, etc.)

c. Outline the role of each component to be used. (US14917 SO2/AC1, SO2/AC2)

• Develop a review procedure (checklist) which you will use to ensure that the final outcome

meets the user requirements / specifications (US14939 SO1/AC3).

Answer 1

Feasibility

a)A feasibility study is an assessment of the practicality of a proposed plan or project. A feasibility study analyzes the viability of a project to determine weather the project or venture is likely to succeed. The study is also designed to identify potential issues and problems that could arise from pursuing the project.

Once you understand the effort that's required, you can assign resources to determine how long the project will take (duration), and then you can estimate labor and non-labor costs.

b) the following process to estimate the total effort required for your project:

1. Determine how accurate your estimate needs to be. Typically, the more accurate the estimate, the more detail is needed, and the more time that is needed. If you are asked for a rough order of magnitude (ROM) estimate (-25% - +75%), you might be able to complete the work quickly, at a high-level, and with a minimum amount of detail. On the other hand, if you must provide an accurate estimate within 10%, you might need to spend quite a bit more time and understand the work at a low level of detail.
2. Create the initial estimate of effort hours for each activity and for the entire project. There are many techniques you can use to estimate effort including task decomposition (Work Breakdown Structure), expert opinion.
3. Add specialist resource hours. Make sure you include hours for part-time and specialty resources. For instance, this could include freelance people, training specialists, procurement, legal, administrative, etc.
4. Consider rework (optional). In a perfect world, all project deliverables would be correct the first time. On real projects, that usually is not the case. Workplans that do not consider rework can easily end up underestimating the total effort involved with completing deliverables.
5. Add project management time. This is the effort required to successfully and proactively manage a project. In general, add 15% of the effort hours for project management. For instance, if a project estimate is 12,000 hours (7 - 8 people), a full-time project manager (1,800 hours) is needed. If the project estimate is 1,000 hours, the project management time would be 150 hours.
6. Add contingency hours. Contingency is used to reflect the uncertainty or risk associated with the estimate. If you're asked to estimate work that is not well defined, you may add 50%, 75%, or more to reflect the uncertainty. If you have done this project many times before, perhaps your contingency would be very small -- perhaps 5%.
7. Calculate the total effort by adding up all the detailed work components.
8. Review and adjust as necessary. Sometimes when you add up all the components, the estimate seems obviously high or low. If your estimate doesn't look right, go back and make adjustments to your estimating assumptions to better reflect reality. I call this being able to take some initial pushback from your manager and sponsor. If your sponsor thinks the estimate is too high, and you don't feel comfortable to defend it, you have more work to do on the estimate. Make sure it seems reasonable to you and that you are prepared to defend it.
9. Document all assumptions. You will never know all the details of a project for certain. Therefore, it is important to document all the assumptions you are making along with the estimate

c)Role of capacity Is for storage of files ,speed is to regulate the speed.

d)Analyzing Existing Documents:

Analyzing existing documents can prove to be a useful technique in requirement gathering, on its own as well using it to supplement other techniques. Reviewing the current process and documentation can help the analyst understand the business, or system, and its current situation. Existing documentation will provide the analyst the titles and names of stakeholders who are involved with the system. This will help the analyst formulate questions for interviews or questionnaires to ask of stakeholders, in order to gain additional requirements