For a small project, requirements analysis, performing design, code generation and test conduction can be done by a single person but as the size of the project increases, more people get added. Adding people later in the project often has a disruptive effect on the project causing schedules to slip even further. If more people are added to a late project, be sure that you have assigned them work that is highly compartmentalized.
The people who are added later in the project should know the system properly. In addition to the time that it takes to learn the system, it also increases the number and complexity of communication paths. Every communication path requires additional effort and time.
Project schedules are elastic. It is possible to compress or extend a desired project completion date to some extent. If delivery can be delayed, the PNR curve indicates that project costs can be reduced substantially. As the project deadline becomes tighter and tighter, you reach a point at which the work cannot be completed on schedule, regardless of the number of people doing the work. The reality should be faced and a new delivery date should be defined.
Effort should also be distributed across the software process workflow. Recommended effort distribution is referred as 40-20-40 rule. Front end analysis and design and back end testing are allocated 40% of all effort while 20% of effort is allocated to coding. The characteristics of each project must dictate the distribution of effort. Requirement analysis may comprise 10-25 percent of project effort. Effort on analysis or prototyping should increase in direct proportion with project size and complexity.
Monday, October 17, 2011
Project Scheduling - Relationship between people and effort
Posted by
Sunflower
at
10/17/2011 04:44:00 PM
1 comments
Labels: Analysis, Code, Communication, Completion, Complexity, Cost, Deadline, Design, Distribution, Effort, Paths, People, Project scheduling, Relationships, Schedule, Test conduct, Time
|
| Subscribe by Email |
|
Wednesday, September 21, 2011
Task Set of Project Planning - Estimating resources
The software development effort requires to estimate resources. There are three categories of software resources:
- people
- reusable software components
- development environment.
A resource has four characteristics:
- resource description
- availability
- time when resource will be required
- time duration in which resource can be applied.
TYPES OF RESOURCES ARE:
- Human Resources
The organizational position and specialty are specified. The location for each human resource is specified. After determining the estimate of development effort, the number of people required for a software project is determined.
- Reusable Software Resources
Re-usability is the creation and reuse of software building blocks which are called components and are cataloged for easy reference and standardized for easy application and validated for easy integration. Four software resource categories that are considered are :
Off the shell components
Full experience components
Partial experience components
New components
- Environmental Resources
Software engineering environment includes hardware and software. Hardware involves tools to produce work products. The software team require access to hardware elements developed by other engineering teams.
Posted by
Sunflower
at
9/21/2011 08:50:00 PM
0
comments
Labels: Application, Categories, Characteristics, Development, Effort, Environment, Estimation, People, Planning, Project Planning, Resources, software engineering, Task set, Tasks, Time, Types
|
| Subscribe by Email |
|
Monday, September 19, 2011
A general overview of software estimation techniques...
Few things should be kept in mind while the software project planner begins the project:
- how long will it take?
- how much effort is required?
- how many people are involved?
- what resources are required?
- what kind of risk is involved?
The statement of scope helps the planner develop estimates using one or more techniques that fall into two broad categories:
- decomposition
- empirical modeling.
Decomposition techniques require a delineation of major software functions followed by estimates of either:
- the number of lines of code.
- selected values within the information domain.
- number of use cases.
- number of person months required to implement each function.
- number of person months required for each software engineering activity.
Empirical techniques use empirically derived expressions for effort and time to predict these project quantities. Automated tools can be used to implement a specific empirical model.
By comparing and reconciling estimates derived using different techniques, the planner is more likely to derive an accurate estimate. Software project can never be an exact science but it is a combination of good historical data and systematic techniques that helps in improving estimation accuracy.
Posted by
Sunflower
at
9/19/2011 02:01:00 PM
0
comments
Labels: Accuracy, Decomposition, Effort, Empirical, Estimates, Estimation, Expressions, Overview, People, Planner, Project Planning, Requirements, Resources, Risks, software engineering, Techniques, Time
|
| Subscribe by Email |
|
Monday, August 29, 2011
What are different process metrics and software process improvement?
Process metrics have long term impact. Their intent is to improve the process itself. These metrics are collected across all projects. To make an improvement in any process, develop metrics based on attributes and then use these attributes as indicators leading a strategy for improvement.
The three factors people, product and technology are connected to a process which sits at the center. The efficiency of a software process is measured indirectly. A set of metrics is derived based on the outcomes derived from process. These outcomes include error measures that are uncovered before the release of software, defects reported by end users and other measures. The skill and motivation of the software people doing the work are the most important factors that influence software quality.
Private metrics are private to an individual and serve as an indicator for individual only. It includes defect rates by individuals and software components and the errors that are found during development. Private data can serve as an important driver as individual software engineer works to improve.
Public metrics assimilate the information that was private to individuals and teams. Calendar times, project level defect rates, errors during formal technical reviews are reviewed to uncover indicators improving team performance.
Software process metrics benefits the organization and improve its overall level of process maturity.
Posted by
Sunflower
at
8/29/2011 05:43:00 PM
0
comments
Labels: Attributes, Development, Domain, Efficiency, Improvement, Measure, Metrics, Organization, People, Performance, Private Metrics, Product, Public Metrics, Quality, Software Process Metrics, Technology
|
| Subscribe by Email |
|
Thursday, March 31, 2011
What kind of people are involved in development process?
People play an important role in the development process. One should understand the people involved in the software development process, particularly, their interest regarding the system and the software that needs to be developed.
End-users are the people who will be using the end-product. Some end users are directly involved and some are indirectly involved. Those who are directly involved are:
- Operational Job: They perform the operational functions of the system. They are concerned with the human interface component of the system like what keyboard, display screen you are using? They have the local view of the system. They tend to think of the system in physical terms.
- Supervisor Job: They perform supervisory actions on daily operations of the system. They are most likely to be concerned with the operational efficiency of the functions that needs to be performed such as more output in less time. They also tend to have same local and physical view of the system similar with the operational users. they are the users who have more contact with the software engineers.
- Executive Job: They generally provide the initiative and serve as the funding authority of the system development project. They are less likely to be concerned with the day to day activities. They are more concerned with strategic issues and long term profit and loss. They are more interested in global view of the system. They are generally able to work with abstract models of the system rather than the physical terms.
Posted by
Sunflower
at
3/31/2011 06:28:00 PM
0
comments
Labels: Efficiency, End product, End-users, Executive, Functions, Jobs, Operational, Operations, People, Software, Software Development process, Strategy, Supervisor, Users
|
| Subscribe by Email |
|
Thursday, March 25, 2010
Some cases in which there is low or negligible benefit of going in for automation of test cases
Automation of test cases can lead to major benefits for teams that implement the automation of their test cases in an effective way, and with a proper strategy. However, this is not an absolute, and there are many situations when it may not be worth the effort to do an automation. One needs to do an analysis of the cost / benefits of going in for automation (but be sure to include long term benefits as well - such as for a regular long cycle, it may be worth going in for automation if it is beneficial in the long term). Some of the situations in which it may not be beneficial to go in for a test automation strategy are:
- Calculate the effort required for writing the test cases for automation: Just because you have test cases for manual testing does not mean that you can go in for automated testing. You would need to convert those test cases into automation script, and depending on the size of the product, this can be a sizable effort. The effort required for this (converted into number of people required) is a prime input into the calculation of whether test automation should be done.
- How likely is it that there will be a need for automation in the future. Automation has much more value if there is a constant ongoing effort for testing. If there is not likely to be much more need of testing of the product, then the benefit that you can get by automating the test cases is significantly reduced.
- Diversity of cases. This is related to the overall effort required for automation. If there are less chances of situations of load testing or testing of multiple input parameters, then some of the benefits of going in for automation of testing reduce
- When the test software is expensive. Say you have a small product or project that sells for a few hundred dollars or less, and is also not sold in appreciable numbers, then it does not make sense to go in for the more commercially available automation softwares that can be fairly expensive
- When the test case is likely to change during the cycle. If you consider the case of an automation software that is UI based, and the UI of the target application keeps on getting modified, then the cost of modifying the automation test scripts to take the changes in the UI can increase the costs involved in an automation strategy
- Getting people to use these automation testing tools is expensive. Using these automation testing tools can take some level of expertise, and it can take some amount of experience to master using such tools (even though many of them claim that they are simple to use). People who are skilled in using such tools can be expensive to hire, and retain.
Posted by
Ashish Agarwal
at
3/25/2010 11:00:00 PM
0
comments
Labels: Automated Testing, Automation, Automation Software, Expensive, People, Resources, Software, Testing
|
| Subscribe by Email |
|