Featured Post

Consumer Electronics for the 21st Century

There can be no doubt that one of the defining characteristics of the 21st century is the seemingly insatiable thirst for more and more advanced technology. Consumers are willing to wait on long lines for endless hours for the privilege of spending hundreds of dollars on the latest iPad, iPhone or other...

Read More

Hierlemann DoubleSlash

IT location Munich strengthens business field mobile IT of company Munich, as a major economic hub in Germany and Europe, offers attractive conditions for the company in Friedrichshafen: international companies, large corporations and a lively middle class reside here and promote the emerging industry...

Read More

Software Cases

Posted by Wii-Wii | Posted in General | Posted on 29-10-2014

0

That is, the process is decomposed in a relatively small set of tasks and the effort necessary to carry through each task is estimado' ' As well as in the technique based on the problem, the estimate based on the process starts with the delineation of the functions of software from the target of the project. After that, for the development of each function she is necessary to attribute the execution of a series of activities (communication with the customer, planning, analysis of risk, engineering and construction/delivery). (PAGNO, 2010). After the attribution of activities, the planner of the project consults given historical of the team and esteem the effort/necessary cost for each involved activity. Combining the functions of the problem with the involved activities of the process, the estimates of size and necessary effort for the accomplishment of each activity of the software process are carried through, and as last step, the estimates for each function of software are carried through.

(PRESSMAN, 2006). Resumidamente, the size and/or demanded total effort for the conclusion of the project is given by the addition of the effort necessary to execute all the activities of each function, followed of the addition of the size and effort of all the functions of software. (PAGNO, 2010). 2.1.3 ESTIMATE WITH USE CASES the method Points for Case of Uso (PCU) was considered by Gustav Karner, in 1993, it allows esteem the size of a project on the basis of use cases, considering the complexity of the actions and an analysis of high level of the steps executed in each task. (RASP, 2007). According to Pressman (2006), one is about one used technique esteem costs of projects of software Guided Objects, on the basis of the model of cases of use generated at the beginning of the project. Dekkers (1999) apud Andrade and Oliveira (2004), affirms that the boarding based on Points of Cases of Uso (PCU) allows to make estimates of the project at the beginning on the basis of the model of use cases.

Comments are closed.