http://www.se.cs.put.poznan.pl These are the search results for the query, showing results 1 to 15. http://www.se.cs.put.poznan.pl/publikacje/h4u2013   Completeness is one of the main quality attributes of requirements specifications. If functional requirements are expressed as use cases, one can be interested in event completeness. A use case is event complete if it contains description of all the events that can happen when executing the use case. Missing events in any use case can lead to higher project costs. Thus, the question arises of what is a good method of identification of events in use cases and what accuracy and review speed one can expect from it. The goal of this study was to check if (1) HAZOP-based event identification is more effective than  ad hoc  review and (2) what is the review speed of these two approaches. Two controlled experiments were conducted in order to evaluate  ad hoc  approach and H4U method to event identification. The first experiment included 18 students, while the second experiment was conducted with the help of 82 professionals. In both cases, accuracy and review speed of the investigated methods were measured and analyzed. Moreover, the usage of HAZOP keywords was analyzed. In both experiments, a benchmark specification based on use cases was used. The first experiment with students showed that a HAZOP-based review is more effective in event identification than  ad hoc  review and this result is statistically significant. However, the reviewing speed of HAZOP-based reviews is lower. The second experiment with professionals confirmed these results. These experiments showed also that event completeness is hard to achieve. It on average ranged from 0.15 to 0.26. HAZOP-based identification of events in use cases is an useful alternative to  ad hoc  reviews. It can achieve higher event completeness at the cost of an increase in effort. No publisher mochodek requirements engineering software quality controlled experiment use cases 2016-08-20T17:31:17Z Article Reference http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/uc-sketch-dostepny-online Właśnie opublikowaliśmy nowe narzędzie wspierające analityków w pisaniu scenariuszy przypadków użycia. No publisher mochodek pattern use-case transaction use cases 2012-07-28T20:15:38Z Blog Entry http://www.se.cs.put.poznan.pl/publikacje/alchimowicz-2008 In the paper an approach to developing a use-cases benchmark is presented. The benchmark itself is a referential use-case-based requirements specification, which has a typical profile observed in real projects. To obtain this profile an extensive analysis of 432 use cases coming from 11 projects was performed. Because the developed specification represents those found in real projects, it might be used in order to present, test, and verify methods and tools for use-case analysis. This is especially important because industrial specifications are in most cases confident, and they might not be used by researchers who would like to replicate studies performed by their colleagues. No publisher mochodek metrics requirements engineering benchmark use cases 2011-08-11T07:44:14Z Inproceedings Reference http://www.se.cs.put.poznan.pl/knowledge-base/software-projects-database/use-case-based-effort-estimation This database provides data required to estimate effort based on use cases (Use Case Points, Transactions, TTPoints etc.) No publisher mochodek use case points ttpoints use-case transaction use cases 2011-01-11T16:15:07Z Folder http://www.se.cs.put.poznan.pl/publikacje/ra4-10 No publisher mochodek ttpoints domain model requirements engineering SRS use cases model 2010-09-13T12:44:26Z Techreport Reference http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/transactions-in-use-cases-nfr-and-architectural-decisions Architectural decisions are usually considered to be influenced mainly by non-functional requirements (NFRs). It is difficult to disagree with such thesis. However, some of the decisions are not directly driven by NFRs, but by the functionality of the system. It can also happen that some of the NFRs are not explicitly defined. In this entry, you can find a checklist containing 20 questions regarding functional requirements that can help you investigate required capabilities of a system architecture. No publisher mochodek requirements engineering architectural knowledge architecture evaluation use cases 2010-09-04T12:25:44Z Blog Entry http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/specyfikacja-wymagan-dla-systemow-informatycznych-1 Właśnie otrzymaliśmy zgodę na publikację wyników projektu realizowanego we współpracy z Urzędem Miasta Poznania, którego celem było dostarczenie zestawu wytycznych odnośnie tworzenia specyfikacji wymagań dla systemów informatycznych (zwłaszcza w modelu przetargowym) No publisher mochodek quality attributes requirements engineering use case diagram SRS use cases ieee830:1998 2010-03-25T11:23:00Z Blog Entry http://www.se.cs.put.poznan.pl/projekty/konsulting/um-srs Celem projektu, realizowanego we współpracy z Urzędem Miasta Poznania, było dostarczenie zestawu wytycznych odnośnie tworzenia specyfikacji wymagań dla systemów informatycznych (zwłaszcza w modelu przetargowym) No publisher mochodek requirements engineering iso9126 use cases 2011-05-08T19:45:22Z Rich document http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/crud-pattern-in-use-cases If you have ever been writing use cases for a data-oriented system (i.e. CMS), you have probably noticed that there is a problem with the large number of use cases like "Add an article", "Remove an article" etc. If you have all CRUD operations available for all objects in the system, you can finish with up to 4 x number-of-objects of use cases. You can reduce this number by introducing the CRUD pattern, which I would like to present you in this blog entry. No publisher mochodek pattern use case diagram requirements engineering use cases uml 2010-04-07T19:35:00Z Blog Entry http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/ucd-and-uc In this blog entry, I would like to show you how the relations (include, and extend) between use cases are presented on use case diagrams and how to use them in textual representations of use cases. No publisher mochodek requirements engineering use cases use case diagram uml 2010-01-24T09:11:47Z Blog Entry http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/ucp The Use Case Points (UCP) method, proposed by Gustav Karner can be used to estimate effort early in the project life-cycle, with relatively low cost. It is based on two main inputs which are actors complexity, measured based on the interface actor uses to communicate with the system; and use-case complexity measured in the number of so-called transactions in use-case scenarios. Here, I would like to present you basic information about the original method proposed by Karner. No publisher mochodek effort estimation use case points metrics use cases use-case transaction 2010-09-01T10:12:30Z Blog Entry http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/use-case-diagram Use cases were Ivar Jacobson's contribution to the UML notation. Although they are in most cases presented in a textual form, there is a special diagram in UML called Use Case Diagram (UCD), which is used to present their structure and associations with actors. In this article I will try to present you all necessary information to use UCD effectively. No publisher mochodek requirements engineering use cases use case diagram uml 2009-12-22T09:54:15Z Blog Entry http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/introduction-to-use-cases Use cases, introduced by Ivar Jacobson more than 20 years ago, are used to capture user (actor) point of view while describing functional requirements of the system. In this brief article I would like to present you an overview of them (what are they, what are the most important parts of use-case model etc.) No publisher mochodek requirements engineering use cases 2009-12-19T12:05:19Z Blog Entry http://www.se.cs.put.poznan.pl/knowledge-base/software-projects-database/use-cases-database-ucdb/use-cases-database-ucdb The goal of UCDB is to collect use-case-based requirements specification from real software projects. No publisher mochodek metrics benchmark use cases 2009-12-09T07:28:47Z Rich document http://www.se.cs.put.poznan.pl/knowledge-base/software-projects-database/use-cases-database-ucdb The goal of UCDB is to collect use-case-based requirements specification from real software projects. No publisher mochodek benchmark use cases 2009-11-05T11:38:12Z Folder