http://www.se.cs.put.poznan.pl These are the search results for the query, showing results 6 to 17. 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/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-engineering-blog/enhancing-use-case-based-effort-estimation-with-transaction-types Recently we have conducted some research regarding use-case-based effort estimation. Results were presented at CEE-SET'09 conference. If you would like to read how knowledge about use-case transactions semantics can help in estimating effort, go ahead and see the presentation. If you like the idea you can find more information in the paper. No publisher mochodek effort estimation use case points ttpoints requirements engineering use cases use-case transaction 2010-09-04T11:21:15Z Blog Entry http://www.se.cs.put.poznan.pl/knowledge-base/forum-english/inzynieria-wymagan Tutaj możesz dyskutować na tematy związane z inżynierią wymagań No publisher mochodek requirements engineering 2009-10-16T12:25:46Z Forum http://www.se.cs.put.poznan.pl/knowledge-base/forum-english/requirements-engineering Here you can discuss all topics related to requirements engineering No publisher mochodek requirements engineering 2009-10-16T12:23:15Z Forum http://www.se.cs.put.poznan.pl/publications/olek2005 Agile methodologies are based on effective communication with the customer. The ideal case is XP s on-site customer. Unfortunately, in practice customer representatives are too busy to work with the development team all the time. Moreover, frequently there are many of them and each representative has only partial domain knowledge. To cope with this we introduced to our projects a proxy-customer role resembling RUP s Analyst and we equipped him with a tool, called UC Workbench, that supports the communication with the customer representatives and the developers. Analyst collects user stories from customer representatives and translates them into use cases. UC Workbench contains among other things a use-case editor and a generator of mockups (a mockup generated by UC Workbench animates use-cases and illustrates them with screen designs). No publisher mochodek requirements engineering uc workbench use cases 2009-09-09T06:54:37Z Inproceedings Reference http://www.se.cs.put.poznan.pl/publications/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-12-28T11:22:07Z Inproceedings Reference http://www.se.cs.put.poznan.pl/publications/Olek-2008 This paper presents a language called ScreenSpec that can be used to specify screens at requirements elicitation phase. ScreenSpec was successfully applied in 8 real projects. It is very effective: average time needed to specify a screen is 2 minutes, and takes an hour to become proficient in using it. Visual representation generated from ScreenSpec can be attached to requirements specification (e.g. as adornments to use cases). No publisher mochodek prototyping requirements engineering use cases 2011-08-11T07:44:32Z Inproceedings Reference http://www.se.cs.put.poznan.pl/publications/ochodek-2008 Since the early 90's of the previous century, use cases have became informal industry standard for presenting functional requirements. The rapid popularity growth stimulated many different approaches for their presentation and writing styles. Unfortunately, this variability makes automatic processing of use cases very difficult. This problem might be mitigated by the use of transaction concept, which is defined as an atomic part of the use case scenario. In this paper we present approach to the automatic transaction discovery in the textual use cases, through the NLP analysis. The proposed solution was implemented as a prototype tool UCTD and preliminarily verified in a case study.  No publisher mochodek effort estimation use case points requirements engineering natural language processing use cases use-case transaction 2009-09-08T06:25:23Z Inproceedings Reference http://www.se.cs.put.poznan.pl/projects/sotware/uc-workbench-i UC Workbench is a tool assisting analysts in requirements engineering. It allows analyst to create use cases easily, manage them, maintain changes, sketch user interface and generate simple prototypes that can be shown to customers and thus enhance their imagination about future system. No publisher mochodek requirements engineering uc workbench use cases mockup 2017-04-03T07:50:59Z Software Project