Albrecht Function points Unadjusted

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Document requirements specification or description of problem.

Box-Out.png
Exit

  • Direct measures:
    • Estimating software
    • Function points
  • Indirect measures:
    • Productivity
    • Quality
    • Cost
    • Documentation
    • Code lines

Star.png
Solution

process-descending-24px.png
Process

Albrecht Function points Unadjusted.png

time-24px.png
Development time

    • To acquire the necessary knowledge to develop the software product: 4 hours.
    • To create the Product Pattern: 2 days.
    • To apply the Product Pattern: 2 hours.

video-24px.png
Explanatory Video

    • Not applicable

Search-32px.png
Quality Controllers

  • None

tool.png
Support Tools

start-flag.png
Initial Context

This product can be used in the first stage of project management that requires an estimation process for measuring the software qualifying the functionality, provided externally, based on the logical design of the system.

If a system has multiple subsystems they must be estimated separately and then add them.

end-flag.png
Result Context

A prediction of personnel, effort, cost and time required to perform all activities and build all products associated with a project, will be obtained.

cloud.png
Problem

It is desired to create a document detailing precisely the estimation of the project being developed. Personnel involved in this task must be able to identify inputs, outputs and queries to the system, amount of internal logical files and external logical files.

forces.png
Restrictions (Forces)

  • Characteristics of organizations: This pattern can be used in existing projects in any company.
  • System Type to develop: This product can be used in projects in which user requirements are changing.
  • Type of customer: It must exist or be achieved, the target area development business being involved in achieving it.
  • Heuristics for use: If you need urgent application or dispose of some of its functionality.

roles.png
Roles

  • Project Manager

lightbulb.png
Lessons Learned

  • ILF and EIF are type data elements that are related to system data
  • In ILF data are maintained and used within the application unlike EIF that is maintained by another system
  • If an entry does not modify ILF is not an entry
  • Rules for identifying DET:
    • Count every single field and nonrecursive
    • Count one DET for each existing data on an EIF
  • Rules to identify RET:
    • Count a RET for each group of TEDs.
    • Count always a RET by default
  • Rules for identifying FTR:
    • Number of accesses to data when processing the function transaction type

award.png
Capability Level

  • Not applicable

Options.png
Basic Knowledge and Skills

board-24px.png
Knowledge

  • Software requirements definition
  • Background information on Logic Programming and Software Engineering I
  • Knowledge in Design Databases
  • Accustomed to using a particular paradigm

help-24px.png
Abilities

  • Capacity of abstraction.
  • Capacity of Analysis.

Information-Sources.png
Information Resources

  • Gonzalo, Agustín y de Amescua Antonio.Gestión del proceso software. Ed. Centro de Estudios Ramón Areces. 2002.
  • DeMarco, Tom. Controlling software projects. Ed Yourdon Press. 1982.
  • Sommerville, Ian. Ingeniería del software. Ed. Addison-Wesley. 2002.
  • Dolado, J.L. y Fernández, L. Medición para la gestión en la ingeniería del software. Ed. RAMA. 2000.
  • McConell, Steve. Desarrollo y gestión de proyectos informáticos. Ed. Mc Graw Hill. 1997.
  • Pressman, R. Ingeniería del Software, Un enfoque práctico, 6ª edición. Ed. Mc Graw Hill. 2005.
  • López-Cortijo y Amescua. Ingeniería del Software: Aspectos de Gestión. Ed. Instituto Ibérico de la Industria del Software. 1998.
  • Garmus, David y Herron, David. Measuring the software process: a practical guide to functional measurements. Ed. Yourdon Press computing series. 1995.