Notes for BSc CSIT

 No. of pants=500 the cost price of 1 pant= Rs 800 The cost price of 500 pants = Rs 800*500 = 400000 Transportation cost = Rs 1500 Total investment = CP + Transportation cost                            = 400000 + 1500 = Rs 401500 S.P of 1 pant = Rs 1000 S.P of 500 pant = Rs 1000*500 = Rs 500000 Profit = S.P - Total investment             = 500000 - 401500 = Rs 98500 Now, ROI =( Profit/Total investment ) *100%         = (98500/401500)*100%        = 24.53%

 Priorities can be set up in deciding the levels of monitoring in the following ways:- Critical Path activities Any delay in an activity on the critical path will cause a delay in the completion date for the project. Critical path activities are likely to have a very high priority for close monitoring. Activities with no free float   A delay in any activity with no free float will delay at least some subsequent activities even though if the delay is less than the trial float, it might not delay the project completion date. Free float is the amount of time an activity may be delayed without affecting any subsequent activity. High-risk activities A set of high-risk activities should be identified as part of the initial risk profiling exercise. If we are using the PERT three-estimate approach we will designate as high-risk activities duration varianceThese activities will be given close attention because they are most likely to overrun or overspend. Activities using critical resources Act

 Uniform Gradient Cash Flow If the cash flow has the proper form its present worth can be determined by using the uniform gradient factor(P=G(P/G, i, n). The uniform gradient factor finds the present worth a uniformly increasing cash flow. For example, if the cash flow in period 1 is 2000 and in period 2 is 2100. it would be uniform if the subsequent amounts increased by 100 in each subsequent period. This gradient in this example would be equal to 100. PERT A PERT chart is a project management tool that provides a graphical representation of a project's timeline. The Program Evaluation Review Technique (PERT) breaks down the individual tasks of a project for analysis. PERT charts are considered preferable to Gantt charts in some cases because they identify task dependencies, but they're often more difficult to interpret. A PERT chart allows managers to evaluate the time and resources necessary to manage a project. the Project Evaluation Review Technique, or PERT, is used to id

The importance of software quality is:-   Increasing criticality of the software  The final customer or user is naturally anxious about the general quality of software, especially its reliability. This is increasingly the case as organizations become more dependent on their computer systems and software is used more and more in areas that are safety-critical, for example, to control aircraft.  The intangibility of software  This makes it difficult to know that a particular task in a project has been completed satisfactorily. The results of these tasks can be made tangible by demanding that the developer produce 'deliverables' that can be examined for quality. Accumulating errors during software development  As computer system development is made up of a number of steps where the output from one step is the input to the next, the errors in the earlier deliverables will be added to those in the later steps leading to an accumulating detrimental effect. In general, the later in a

Significance of float on project management are:- It ensures projects stay on track.  Monitoring the total float of a project can help project managers determine whether a project is on track. It can also help them determine what tasks they can delay and how they can adjust their schedule to ensure they meet their project deadline. It improves teamwork and collaboration.  Understanding what the total float of a project is can provide teams with a clear schedule that makes it easy for them to collaborate. This can improve productivity and morale. It makes it easier to prioritize tasks.  Project managers can use float to outline each phase of a project and determine the order their team needs to complete tasks. This can help them delegate tasks more effectively and improve communication. It can decrease stress.  Calculating float time can decrease stress because it helps you identify how flexible you can be with the deadline for a specific task. This can assure you that as long as you co

 Software Configuration Management (SCM)  Software Configuration Management (SCM) refers to a process for maintaining computer systems, servers, and software in a desired, consistent state.  Sometimes called software change management or IT automation, the idea is to have a system in place to track and compare changes made across a system throughout the development process and also identify who made these revisions. The purpose is to make project management easier, minimize errors, increase traceability, and improve overall software quality.  The software configuration management process is a series of steps designed to track and manage all the defects, resources, codes, documents, hardware, and budgets throughout a project. SCM is an interdisciplinary process involving people at every level, including DevOps, developers, project managers/owners, SysAdmin, and testers.  The 5 steps of an SCM plan 1. Planning and Identification 2. Version Control and Baseline 3. Change Control 4. Config

 Work break down structure  Work breakdown structure is a visual, hierarchical, and deliverables-oriented deconstruction of a project. A WBS includes dividing a large and complex project into a simpler manageable and independent task. The root of this tree (structure) is labeled by the project name itself. For constructing a WBS, each node is recursively decomposed into smaller sub-activities until at the leaf level the activities become undividable and independent, It follows a top-down approach. WBS is the method for time scheduling cost estimation and error handling. Example:- Product breakdown structure The product breakdown structure is a hierarchical structure of things that the project will make or outcomes that it will deliver, It begins with the final product at the top of the hierarchy followed by the sub-categories element of the product. the product breakdown structure is similar to the work breakdown structure. The PB is supported by a product log and associated product de

 The differences between software project management and other types of project management are given below:- 1. Software projects are based on logical work, Other types of projects are based on physical work. 2. We can't measure the complexity of software projects, We actually work on other types of projects. 3. There is no fixed production plan, difficult to monitor and track., There is a fixed production plan that can be tracked. 4. Productivity varies greatly with changes in technology or worker., The Productivity does not vary much 5. Managing a software project is more about managing interpersonal communication and less administration ., It is more about maintaining a schedule and good administration. The phases of the project management life cycle are explained below:- Project initiation Project planning Project execution Project monitoring and performance Project closure 1. Initiation Phases This is where we can define what the project actually is we can outline our objectiv

 Risk:  Risk is a problem that could cause some loss or threaten the progress of the project, but this has not happened yet. These potential issues might harm the cost, schedule, or technical success of the project and the quality of our software device, or project team morale. A risk is an uncertain event or condition that, if occurs, has a negative on a project's objective.  The objective of risk management is to avoid or minimize the adverse effect of unforeseen events by avoiding the risk of drawing up contingency plans for dealing with them. The above figure shows a task breakdown structure of Barry Boehm:- Risk identification consists of a listing of all the risks that can adversely affect the successful execution of the project. Risk estimation consists of assessing the likelihood and impact of each hazard. Risk evaluaton consss of rank9ing the rsik  an d detemining risk aversion stragteigies. Risk planning consists of drawing up contingency plans and where appropriate addin

 Planning is necessary because:- IT boosts project performance and success rates. It saves money It improves team communication. IT ensures the best use of resources. The steps of activity planning are given below:- Set up activities Define the relationship between activities Estimate resources required for performing activities Estimate durations for activities Step 1: Set up activities The first step of project activities planning and scheduling requires the project manager to define what amount of actons and tasks are necessary for producing project deliverables in a timely manner. The input for his process will be the project deliverables statement. The project managers can use this document to define high-level activities that will be used later in creating the project implementation schedule. The project managers should also work on developing project activities templates that helps simplify the process of project scheduling and planning. Step 2: Define Relationship The next step