Software project activity plan

Notes by Adil Aslam 58 Notes by Adil Aslam 62 Another Example Notes by Adil Aslam 63 Draw a Network Notes by Adil Aslam 64 Check in Previous Network Diagram. Notes by Adil Aslam 66 Notes by Adil Aslam 67 Notes by Adil Aslam Total views 27, On Slideshare 0. From embeds 0. Number of embeds 8. Downloads 0. Shares 0. Comments 0. Likes You just clipped your first slide! Clipping is a handy way to collect important slides you want to go back to later. Now customize the name of a clipboard to store your clips.

For effort estimation software size should be known. Once size and efforts are estimated, the time required to produce the software can be estimated. Efforts required is segregated into sub categories as per the requirement specifications and interdependency of various components of software.

The tasks are scheduled on day-to-day basis or in calendar months. The sum of time required to complete all tasks in hours or days is the total time invested to complete the project. This might be considered as the most difficult of all because it depends on more elements than any of the previous ones.

For estimating project cost, it is required to consider -. We discussed various parameters involving project estimation such as size, effort, time and cost.

This technique uses empirically derived formulae to make estimation. This model is made by Lawrence H. Putnam model maps time and efforts required with software size. It divides the software product into three categories of software: organic, semi-detached and embedded. Project Scheduling in a project refers to roadmap of all activities to be done with specified order and within time slot allotted to each activity.

Project managers tend to define various tasks, and project milestones and arrange them keeping various factors in mind.

They look for tasks lie in critical path in the schedule, which are necessary to complete in specific manner because of task interdependency and strictly within the time allocated. Arrangement of tasks which lies out of critical path are less likely to impact over all schedule of the project.

For scheduling a project, it is necessary to -. All elements used to develop a software product may be assumed as resource for that project.

This may include human resource, productive tools and software libraries. The resources are available in limited quantity and stay in the organization as a pool of assets. The shortage of resources hampers the development of project and it can lag behind the schedule. Allocating extra resources increases development cost in the end. It is therefore necessary to estimate and allocate adequate resources for the project. Risk management involves all activities pertaining to identification, analyzing and making provision for predictable and non-predictable risks in the project.

Risk may include the following:. Execution needs monitoring in order to check whether everything is going according to the plan. Project planning activities are essential to understand for effective project management. There are different project planning activities in software engineering all the way through to planning a new marketing campaign- project planning activities are essential for every type of project.

In this article, we will understand Project Planning and we will take a look at the different project planning activities, activity planning in project management , activity planning with Sinnaps project management software and activity planning in SPM.

Project planning activities and scheduling project activities is essential for effective project time management. It is the first process of the planning stage of any type of project and steps should be followed as art of pre project planning activities.

Project activities planning involves the second step of project time management and developing the project implementation schedules involves the third step. What is project planning? This is the first step. Sinnaps, project planning software and easy activities management tool. In order to carry out effective project planning activities the following four steps should be considered and can be performed effectively with a project management software such as Sinnaps:. The activity planning stage is very important for any type of project.

Identification of threats and valuation of their impact on assets impact valuation. Identification and assessment of vulnerabilities to threats. Risk assessment. Risk Analysis — Defining the Scope. Draw a context diagram. Decide on the boundary. It will rarely be the computer! Make explicit assumptions about the security of neighbouring domains.

Verify them! Risk Analysis - Identification of Assets. Types of asset. Software: purchased or developed programs. People: who run the system. Documentation: manuals, administrative procedures, etc. Supplies: paper forms, magnetic media, printer liquid, etc. Risk Analysis — Impact Valuation. Identification and valuation of threats - for each group of assets.

Identify threats, e. Loss of confidentiality. Loss of integrity. Loss of completeness. Loss of availability Denial of Service. For many asset types the only threat is loss of availability. Assess impact of threat. Assess in levels, e. This gives the valuation of the asset in the face of the threat. Risk Analysis — Vulnerabilities. For risk analysis of an existing system. Windows NT. BS recommendations of good practice.

For each threat. Identify vulnerabilities. How to exploit a threat successfully;. Assess levels of likelihood - High, Medium, Low. Of attempt. Expensive attacks are less likely e. Successful exploitation of vulnerability;. Combine them. Risk Assessment. Assess risk. If we had accurate probabilities and values, risk would be. Impact valuation x probability of threat x probability of exploitation. Plus a correction factor for risk aversion.

Since we haven't, we construct matrices such as. Responses to risk. Avoid it completely by withdrawing from an activity. Accept it and do nothing. Reduce it with security measures. Risk management. Risk management is concerned with identifying risks and drawing up plans to minimisetheir effect on a project.

A risk is a probability that some adverse circumstance will occur. Project risks affect schedule or resources;. Product risks affect the quality or performance of the software being developed; Business risks affect the organisation developing or procuring the software. The risk management process. Risk identification. Identify project, product and business risks;. Risk analysis. Assess the likelihood and consequences of these risks;. Risk planning. Draw up plans to avoid or minimise the effects of the risk;.

Risk monitoring. Monitor the risks throughout the project;. Systematic Processes. What Constitutes a Hazard? A real or potential condition that, when activated, can transform into a series of interrelated events that result in damage to equipment or property and or injury to people. Safety Managers View.

An implied threat or danger, a potential condition waiting to become a loss. Required to initiate action from potential to kinetic. May be a:. Component out of tolerance. Maintenance failure. Operator failure. Any combination of other events and conditions. When Do We Look for Hazards?

Conceptual - Research. Operational Deployment. Hazard Severity. A key factor in establishing a common understanding of a safety programs goal. Cat 1: Catastrophic. Cat 2: Critical. Cat 3: Marginal. Cat 4: Negligible. Hazard Analysis Methods.

Systematic look at hardware piece by piece. Review of how each component could fail. Considers how a failure effects other components, sub-systems and systems as a whole. Detailed review of a specific undesirable event. Deductive in nature. Top-down effort. Normally reserved for critical failures or mishaps. May be qualitative or quantitative. Integrates people and procedures into the system. Diagrams the flow or sequence of events. Risk Management is the process of identifying, assessing, responding.

Appropriate protective measures must be taken to safeguard sensitive IT system or application weaknesses or vulnerabilities from unauthorized disclosure. For each major risk, one of the following approaches will be selected to address it:.

Avoid — Eliminate the threat or condition or to protect the project objectives from its impact by eliminating the cause. Mitigate — Identify ways to reduce the probability or the impact of the risk. Accept — Nothing will be done. Contingency —Define actions to be taken in response to risks. Transfer — Shift the consequence of a risk to a third party together with ownership of the response by making another party responsible for the risk buy insurance, outsourcing, etc.

The level of risk on a project will be tracked, monitored and controlled and reported. Risks will be assigned a risk owner s who will track, monitor and control and report on the status and effectiveness of each risk response action to the Project Manager and Risk. All project change requests will be analyzed for their possible impact to the project risks. As Risk Events occur, the list will be re-prioritized during weekly reviews and risk.