diagram of payroll

Lecture Notes in Computer Science, 2000

Use cases are the modeling technique of UML for formalizing the functional requirements placed on systems. This technique has limitations in modeling the context of a system, in relating systems involved in a same business process, in reusing use cases, and in specifying various constraints such as execution constraints between use case occurrences. These limitations can be overcome to some extent by the realization of multiple diagrams of various types, but with unclear relationships between them. Thus, the specification activity becomes complex and error prone. In this paper, we show how to overcome the limitations of use cases by making the roles of actors explicit. Interestingly, our contributions not only make UML a more expressive specification language, they also make it simpler to use and more consistent.

Lecture Notes in Computer Science, 2003

Errors in a requirements model have prolonged detrimental effects on reliability, cost, and safety of a software system. It is very costly to fix these errors in later phases of software development if they cannot be corrected during requirements analysis and design. A Use Case diagram, as a requirements model, plays an important role in giving requirements for a software system. It provides a communication tool between software requirements developers and prospective users to understand what requirements of a software system are. However most descriptions of a use case diagram are written in some informal language, leading to possible misunderstanding between developers and users. In this paper, we propose a new rigorous review technique which can be applied to software requirements models. Using this new technique before a software system is fully designed will help us find some potential errors in a requirements model, resulting in reduced time, labor and expenditure in software development.

Recently, the use of scenarios for requirements acquisition has gained a lot of attention in the research community. Yet, the transition from scenarios to formal specifications, the target of the requirements engineering process, remains ill-defined. Over the past decade, the rapid prototyping of user interfaces has become quite a common technique in industry; however, prototyping remains weak in linking the application domain with the user interface, and automated prototyping is mostly limited to database-oriented applications. Most importantly, the prototyping and the scenario approaches lack integration in the overall requirements engineering process. In this paper 1 , we suggest a requirement engineering process that generates a user interface prototype from scenarios and yields a formal specification of the application. Scenarios are acquired in the form of collaboration diagrams as defined by the Unified Modeling Language (UML), and are enriched with user interface (UI) inform...

Requirements Engineering, 1998

Lecture Notes in Computer Science, 2006

Use Cases are widely used for specifying systems, but their semantics are unclear in ways that make it difficult to apply use cases to complex problems. In this paper, we suggest clarifications to use case semantics so that use case modeling can be applied to relate automated systems to business processes and process specifications, particularly in situations where we need to integrate multiple systems in support of a business process. We discuss the original intentions of Ivar Jacobson and UML and we find out that use case specifications, whether written in natural language or as interaction diagrams, are misleading as to what is a use case (instance). We consider then a more natural modeling technique, and establish a relation between a use case, a joint action, and a role.

Iceis, 2007

The identification of use cases is one key issue in the development of interactive information systems. User participation in the development life cycle can be seen as critical to achieve usable systems and has proven its efficacy in the improvement of systems appropriateness. Indeed, the involvement of users in the requirements definition can add a significant improvement in both consecutive/interleaved tasks of: (i) understanding and specifying the context of use, and, (ii) specifying the user and organizational requirements, as defined in Human-Centered Design (HCD) (Organizations, 1999). Existing solutions provide a way to identify business processes and/or use cases in order to achieve system definition, but they don't do it in an agile and structured way that helps to efficiently bridge between Business Process Management and Software Engineering. Process Use Cases is a methodology, defined in the Goals software construction process, for the identification of use cases and information entities during the modeling and reorganization of business processes focusing the results in the identification of the functional requirements for the correct development of an interactive information system.

Lecture Notes in Computer Science, 2001

Use case models are used in object-oriented analysis for capturing and describing the functional requirements of a system. Use case models are also used in communication between stakeholders in development projects. It is therefore important that the use case models are constructed in such a way that they support the development process and promote a good understanding of the requirements among the stakeholders. Despite this, there are few guidelines on how to construct use case models.

Proceedings of Technology of Object-Oriented Languages and Systems - TOOLS 30 (Cat. No.PR00278), 1999

Use case modeling has become the foundation of the most popular de facto standard technique for performing software requirements analysis and specification. However, use case modeling has its well-known problems, and different requirements engineers typically perform use case modeling differently. This paper provides a hierarchically organized set of detailed guidelines for use case modeling.

The object oriented development paradigm has attracted many supporters in the Software Engineering community. One of the most important advances was the Unified Language Modeling (UML), a standard for visual modeling. Use Case Diagrams have been used for capturing system functional requirements. However, the system development occurs in a context where organization processes are well established. Therefore, we need to capture organizational requirements to define how the system fulfils the organization's goals, why it is necessary, what are the possible alternatives, what are the implications to the involved parts, etc. Unfortunately, UML is ill equipped for modeling organizational requirements. We need other techniques, such as i*, to represent these aspects. Nevertheless, organizational requirements must be related to functional requirements represented as Use Cases. In this paper we present some guidelines to assist requirement engineers in the development of Use Cases from t...

International Journal of Computer Applications, 2014

Establishment of institutions of higher learning requires massive amount of different resources which are always in short supply. The delivery of learning material and tests to the students has become very easy with the facility of uploading the same on the web irrespective of the number of students. The assessment part could be a deterrent as far as willingness of learned faculty members to participate in the whole process is concerned. If assessment will become automated then it will be easier for any teachers to evaluate any number of students. This paper presents a proposed architecture of automated assessment of Use-Case Diagram. The essence of this architecture is to assess large number of students very easily in short duration. This proposed work is going to be very useful for the needy students by assisting in evaluation of their performance.