Work Breakdown Structure
WORK BREAKDOWN STRUCTURE (WBS)
The description of the WBS is as follows: 1. SIMS 1.1 Feasibility Study (Phase 1)
Activities in this phase are carried out to understand the potential of the project taken. This phase uncovers the strengths and weaknesses of the project. 1.2.1 Monitor Progress (Task A)
The information that we have at the start of the project is taken into account to evaluate and analyze the project. 1.2.2 Estimate Resources(Task B)
Resources required to do the project are estimated. It is important to do in the sense that if we don’t have enough of material or human resources to complete the project then we’ll drop this project. 1.2.3 Assess Risks(Task C)
The risks involved with the project. It is taken care that the project is the kind of project that if company accepts then it would lift the reputation of the company and would help in its growth. 1.2.4 Evaluate Results(Task D)
The methodology adopted would yield the desired output or not. And also if the target of the company that is to earn profit is matched or not. 1.2 Requirements (Phase 2) 1.3.5 Analyze Functional Requirements(Task E)
On the basis of the Software Requirements Specifications from the Software Development Life – Cycle Model the Requirements are analyzed and prioritized. 1.3.6 Analyze Non – Functional Requirements(Task F)
On the basis of the Software Requirements Specifications from the Software Development Life – Cycle Model the Requirements are analyzed and prioritized. These are those requirements which are not explicitly asked by the client but given in software by the programmers / managers as additional features. 1.3 Design (Phase 3)
Design phase is where all the requirements analyzed are modeled to be seen closer to the reality. 1.4.7 Prototype (User Interfaces) (Task G)
Prototype or dummy user interfaces help the user/ client to understand what he asked is what
The description of the WBS is as follows: 1. SIMS 1.1 Feasibility Study (Phase 1)
Activities in this phase are carried out to understand the potential of the project taken. This phase uncovers the strengths and weaknesses of the project. 1.2.1 Monitor Progress (Task A)
The information that we have at the start of the project is taken into account to evaluate and analyze the project. 1.2.2 Estimate Resources(Task B)
Resources required to do the project are estimated. It is important to do in the sense that if we don’t have enough of material or human resources to complete the project then we’ll drop this project. 1.2.3 Assess Risks(Task C)
The risks involved with the project. It is taken care that the project is the kind of project that if company accepts then it would lift the reputation of the company and would help in its growth. 1.2.4 Evaluate Results(Task D)
The methodology adopted would yield the desired output or not. And also if the target of the company that is to earn profit is matched or not. 1.2 Requirements (Phase 2) 1.3.5 Analyze Functional Requirements(Task E)
On the basis of the Software Requirements Specifications from the Software Development Life – Cycle Model the Requirements are analyzed and prioritized. 1.3.6 Analyze Non – Functional Requirements(Task F)
On the basis of the Software Requirements Specifications from the Software Development Life – Cycle Model the Requirements are analyzed and prioritized. These are those requirements which are not explicitly asked by the client but given in software by the programmers / managers as additional features. 1.3 Design (Phase 3)
Design phase is where all the requirements analyzed are modeled to be seen closer to the reality. 1.4.7 Prototype (User Interfaces) (Task G)
Prototype or dummy user interfaces help the user/ client to understand what he asked is what