You are on page 1of 9

OSEC_CS&E_H

PROJECT MANAGEMENT

2.0

PROJECT MANAGEMENT:-

2.1 PROJECT PLANNING:2.1.1 Project Development Approach and Justification: The first we have done analysis of the system what are the requirement of the market and what is the market value for this system and how it will be help full to the user. We have used the SPIRAL model to implement this system and working and the advantage and the disadvantage of the SPIRAL model is as the follows:THE SPIRAL MODEL: The spiral model is an evolutionary software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the waterfall model. It provides the potential for rapid development of increasingly more complete versions of the software. A spiral model is divided into a set of framework activities defined by the software engineering team. Each of the framework activities represents one segment of the spiral path as shown in fig.

OSEC_CS&E_H

PROJECT MANAGEMENT

As this evolutionary process begins, the software team performs activities that are implied by a circuit around the spiral in a clockwise direction, beginning at the center. Risk is considered as each revolution is made. The first circuit around the spiral might result in the development of a product specification; subsequent passes around the spiral might be used to develop a prototype and then progressively more sophisticated versions of the software. Cost and schedule are adjusted based on feedback derived from customer evaluation.

The spiral model is a realistic approach to the development of large - scale systems and software Because software evolves as the process progresses, the developer and customer better understand react to risk at the each evolutionary level. The spiral model demands a direct consideration of technical risks at all stages of the project and, if properly applied, should reduce risks before they become problematic.

OSEC_CS&E_H

PROJECT MANAGEMENT

Advantages: In this model, requirements of customer can be changed. If developer has less experience on project, then this model is useful. In this model, user can involve in all phases. If requirements are highly reliable and project schedule is tight then this model is useful. Dis -Advantages: If funding is stable, then it is not feasible to use spiral model. If requirements are not easily understand and define, then not use this model.

OSEC_CS&E_H

PROJECT MANAGEMENT

2.1.2 Project Plan:The basic reasons for delayed completion of any project are:
Unrealistic deadline estimations under excitement of getting a project or under some other pressure. Changing user requirement that are not reflected in schedule changes Conceptual change requirement during the course of the project An underestimation of amount of effort and / or the numbers of resources that will be required for the job

2.1.3 Milestones and Deliverables:The system will be completed in the two parts as the Following ways: Theoretical: In this part all the detailed analysis of the project has been completed as per the system requirements the first we have designed the GUI and then database and the uml diagram. It is developed in the 7th semester

2.1.4 Roles and Responsibilities: System analysis : requirement analysis : Database Designer : Interface design : Coding : Testing : Testing team and Jaydeep Ratanpara Bug solving : Documentation :

OSEC_CS&E_H

PROJECT MANAGEMENT

2.2 PROJECT SCHEDULING Table 2.2:Date 21/07/11 to 30/08/11 01/09/11 to 25/09/11 26/09/11 to 02/10/11 03/10/11 to 10/10/11 11/10/11 to 14/10/11 Work Done Oral Description Analysis GUI Database Design Uml Diagram

10

OSEC_CS&E_H

PROJECT MANAGEMENT

2.3 RISK MANAGEMENT: Project Risk Management involves conducting risk management planning, engaging in risk Identification, completing risk analysis, creating a risk response action plan, and monitoring and controlling risk on a project. Project Risk Management is a continuous process to be engaged in throughout the entire project. A key point to remember is that risk is not always bad. There are opportunities and there are threats. The opportunities are the good risks. The threats are the bad risks. The purpose of project risk management is to increase the likelihood and impact of positive events and to decrease the probability and impact of negative events Each Risk Management process results in a specific deliverable which is used as the foundations for the subsequent process. Combined the risk management processes provide a best practice pattern for managing risk on a project. 2.3.1 Risk Identification Risk Identification is a systematic attempt to specify threats to the project plan. By identifying the known and predictable risks, the project manager takes a first step towards avoiding them when possible and controlling them when necessary. One method of identifying risks is to create a risk item checklist. The checklist can be used for risk identification and focuses on some subset of known and predictable risks in the following subcategories.

2.3.2 Risk Analysis Regardless of the prevention techniques employed, possible threats that could arise inside or outside the organization need to be assessed. Although the exact nature of potential disasters or their resulting consequences are difficult to determine, it is beneficial to perform a comprehensive risk assessment of all threats that can realistically occur to the organization.

11

OSEC_CS&E_H

PROJECT MANAGEMENT

Types of Risks: Performance Risk The degree of uncertainty that the product will meet its requirements and be fit for its intended use. As I am team leader, the expectation risk is there in our project.

Cost Risk The degree of uncertainty that the project budget will be maintained. The cost of our project is already decided by management.

Support Risk The degree of uncertainty that the resultant software will be easy to correct, adapt, and enhance. Client of this project is in different premises.

2.3.3 Risk Planning To mitigate the risks, project management must develop a strategy for reducing turnover. Among the possible steps to be taken are: Meet with current staff to determine causes for turnover (e.g. poor working conditions, low pay competitive job market). Mitigate those causes that are under our control before the project start.

12

OSEC_CS&E_H

PROJECT MANAGEMENT

2.4 Estimation:2.4.1 Effort Estimation: After gathering all the requirement of the software and complete the analysis of the software, the effort estimation will be done. Effort estimation means how much time will required for the complete the project, and how much amount will required for the development of the project. Effort estimation as per the cocomo model can be find out from the following equations E= ab (KLOC)bb. D = Cb(E)db. P= E/D.

Where E= effort applied in person-months. D= development time in chronological months. KLOC= kilo line of the code for the project.

Table 2.4:Software Projects Organic Semi-detached Embedded Ab 2.4 3.0 3.6 Bb 1.05 1.12 1.20 Cb 2.5 2.5 2.5 Db 0.38 0.35 0.32

13

OSEC_CS&E_H

PROJECT MANAGEMENT

2.4.2 Cost Analysis: In the cost estimation, the cost of the project will be defined. In this stage, for example, for any project there 10 developers are working and company have to pay 10,000 to each developer and the project must complete to in four months. So that money plus the maintenance and the profit of that project will be added to the cost.

14

You might also like