Essays collection 2012
Home Home SK
"use case points"
Jurčák Ondrej

Abstract. Monitoring and controlling of project in every phase of development process is important task of management. For the best project control, planning and control its performance, provide sufficiency of resources, is important estimate size and required effort of project in early phases of development.

Use cases play important role in software development. They depend from software requirements and describe its functionality. Making points of Use Cases we can estimate size and effort needed for software development, what is sufficient amount of information to create main line of project. Use Case Points outgoing from Function points and was first presented by Gustav Karner at 1993. However this method is known quite long time, it’s using on different types of projects point on success usage of this method. So UseCase points have advantages and disadvantages. In the essay below is described disadvantages and advantages of using this method on different kind of projects.



Polakovič Patrik

Abstract. Academic environment is always taken with reserve. Students make up their own duties as to be able to achieve the desired goal. And so even promising and well-developed student projects often end unsuccessfully or incomplete. One of the reasons is the weak scheduling tasks figuring in poor self-control, or control by the other members of the project team. In practice, this problem of software projects solves monitoring management, which oversees the process of project creation. In student environment is sometimes problem to integrate the monitoring management from time-management reasons, or lack of human resources. This essay will attempt to discover whether it is possible to create a monitoring management in student team. What should be noted during realization of methods for monitoring the project and what problems to expect in the integration of specific methods of monitoring into the student project team environment.


Left Separator
monitoring software project metrics function points plan planning software product risk management test driven development error effective communication sofware metrics software development team problems development software quality development support management extreme programming pair programming Scrum communication relations control progress subversion git critical path method project planning estimation agile development risks motivation requirement collection testing use case points support tools support tools outsourcing team size estimation version management quality cooperation risk documentation project software versioning conflict