aiahned's picture
From aiahned rss RSS  subscribe Subscribe

Software Project Management 

Software Project Management

 

 
 
Tags:  risk management software  project management software  online project management software  web project management software 
Views:  229
Downloads:  1
Published:  November 02, 2011
 
0
download

Share plick with friends Share
save to favorite
Report Abuse Report Abuse
 
Related Plicks
Visions For the Project Management Software Industry

Visions For the Project Management Software Industry

From: davidm8
Views: 726 Comments: 0

 
Business Management Software BIZixx

Business Management Software BIZixx

From: rajneesh1
Views: 88 Comments: 0
As a best business management software, BIZixx helps make your complex business processes simpler and your lives more aligned and cohesive. It makes your business systems and channels more effective and error free.
 
Project management software

Project management software

From: albertoy
Views: 526 Comments: 0
Project management software
 
Software Project Management For Dummies

Software Project Management For Dummies

From: anon-390119
Views: 558 Comments: 0
Software Project Management For Dummies ,60 hikes within 60 miles ebooks, church media library tools supplies, garland north branch library, appomattox regional library libbie dragoo
 
See all 
 
More from this user
Oracle compra Sun

Oracle compra Sun

From: aiahned
Views: 272
Comments: 0

Web2.0 and Warfighter Training

Web2.0 and Warfighter Training

From: aiahned
Views: 238
Comments: 0

Roi measurement of social media press releases

Roi measurement of social media press releases

From: aiahned
Views: 138
Comments: 0

Exam 70-642 Preparation Questions

Exam 70-642 Preparation Questions

From: aiahned
Views: 427
Comments: 0

Building Your Online Brand - Ad Club 101 Series

Building Your Online Brand - Ad Club 101 Series

From: aiahned
Views: 390
Comments: 0

The Great Documents About Finance,Collection 210

The Great Documents About Finance,Collection 210

From: aiahned
Views: 317
Comments: 0

See all 
 
 
 URL:          AddThis Social Bookmark Button
Embed Thin Player: (fits in most blogs)
Embed Full Player :
 
 

Name

Email (will NOT be shown to other users)

 

 
 
Comments: (watch)
 
 
Notes:
 
Slide 1: CIS224: Software Projects: Software Engineering and Research Methods Software Project Management 1. The Project Management Spectrum Project management involves the planning, monitoring and control of the people, process, and events that occur as software evolves. 1.1. The People - senior manager : coordinates the connection between the business and the software professionals. - project manager : plans, monitors, and controls the work of a team of software engineers. - software practitioner (engineer) : manages his day to day activities, planning, and managing technical tasks. 1.2. The Product Product is the software project plan, which defines the tasks to be conducted, the people who are going to do the work, the mechanisms for assessing risks, controlling change and evaluating quality.
Slide 2: 2. Organization of the Software Management Process 2.1. Beginning a Software Project Initially objectives and scope should be established before planning. The developer and customer meet to define the objectives and scope. Objectives are the overall goals of the software projects. Scope are the primary functions which the software is to accomplish. 2.2 Measures and Metrics Project measures and metrics are taken to provide insights into the organization of the software engineering. The software process is measured in order to improve it. The software product is measured in order to improve its quality. 2.3 Project Estimation - Planning requires estimates of the: - human effort- in person-months - chronological project duration- in calendar time - cost The estimation usually requires to broke the project into pieces.
Slide 3: In practice, past experience is often used as a guide.
Slide 4: 3. Software Decomposition Software decomposition includes product and process decomposition which occur simultaneously as the project plan evolves. 3.1. Software Problem Decomposition Software problem decomposition is usually performed according to the divide and conquer strategy: that is, a complex problem is partitioned in smaller problems which are easily manageable. 3.2. Software Process Decomposition For example, the work tasks for the communication activity could be: - review the customer request - plan and schedule a meeting with the customer - conduct research to propose solutions - prepare a working document - conduct another meeting - jointly develop a specification - improve the specification and make a scoping document.
Slide 5: 4. Project Management Metrics The software metrics are quantitative measures that enable software engineers to gain insight into the efficacy of the software process. Software measurement is important as it helps to identify trends in the engineering process with which true improvements can be made over time, without relying on subjective judgements. Reasons for measuring the software: to indicate the quality of the product to assess the productivity of the people to assess the benefits from the new methods to form a baseline for estimation to help justify the needs for new tools
Slide 6: 4.1. Direct and Indirect Software Metrics The direct software metrics are: - lines of code - memory size - defects reported over a period of time The indirect software metrics are: - functionality - quality - complexity - efficiency - reliability - maintainability
Slide 7: 4.2. Size-Oriented Metrics Size-oriented metrics are derived by normalizing the productivity measures considering the size of software that has been produced. Productivity = KLOC / person-month, Quality = defects / KLOC Cost = $ / KLOC Documentation = pages of documentation / KLOC where: KLOC- thousand lines of code
Slide 8: 4.3. Function-Oriented Metrics Function-oriented metrics use as a normalization value the functionality delivered by the application. Since the functionality can not be measured directly, estimates called function points are derived based on countable information in the software domain and assessments of the software complexity. Five information domain characteristics are determined as follows: - number of user inputs: each user input provides distinct data; - number of user outputs: each output provides different information to the user, like reports, screens and messages; - number of user inquiries: these are on-line inputs that require immediate response from the software program; - number of files: each file is counted; - number of external interfaces: all readable interfaces are counted.
Slide 9: Function points are computed according to the following equation: FP = count-total × [ 0.65 + 0.01 × SUM( Fi ) ] where: count-total is the sum of all FP entries obtained Fi - are complexity adjustment values Productivity = FP / person-month, Quality = defects / FP Cost = $ / FP Documentation = pages of documentation / FP
Slide 10: Example: Perform software project estimation using the FunctionPoints metric, assuming the following software information domain characteristics: Measurement parameter number of user inputs number of user outputs number of user inquiries number of files number of external interfaces count 20 15 28 5 3 factor 4 5 5 10 7 Suppose that the software complexity adjustment factors are as follows: Complexity adjustment Backup and recovery Data communications Distributed processing Performance critical Existing operating environment On-line data entry Input transaction over multiple screens Master files updated on-line Information domain values complex Internal processing complex Code designed for reuse Conversion/installation in design Multiple installations value (Fi) 5 4 2 5 3 3 5 2 4 5 3 4 5 Application designed for change 5
Slide 11: a) Estimated number of function points FPest = count-total × [ 0.65 + 0.01 × SUM(Fi) ] FPest = 366 × [ 0.65 + 0.01 × 55 ] = 439.2 b) Productivity of the team for 3 person-months using the derived function points Productivity = FPest / person-month Productivity = 439.2 / 3 = 146.4 [function points per person month] c) Quality of this software having 5 defects using the derived function points Quality = defects / FPest Quality = 5 / 439.2 = 0.011 [defects per function point] d) Software cost using the derived function points if there have been spend 3000 pounds Cost = $ / FPest Cost = 3000 / 439.2 = 6.83 [pounds per function point] e) Documentation size using these function points if 100 pages have been produced Documentation = pages of documentation / FPest Documentation = 100 / 439.2 = 0.228 [pages per function point]

   
Time on Slide Time on Plick
Slides per Visit Slide Views Views by Location