Choose language:
» Personal Loan No Credit Check, Online Economics » Planning and organization » Topics begins with A » Application
An application, also in German rather under the English expression use case admits to reach defines the interactions between participants and the regarded system, who take place, in order a certain technical goal (English business goal). Applications describe only exactly one expiration or a process.
Applications are often confounded with business processes, however business processes contain also actions, persons, roles or resources, which are not part of the system which can be modelled.
"A Use Case describes an final, continuous succession of actions of a participant at the system with result of technical value"
The can be different. On very high level an application describes only very roughly and abstractly, which happens. The technology of the application letter can be refined however up to level by IT-processes, so that the behavior of an application is described in detail. This contradicts the original intention of Use Cases, is however sometimes appropriate.
Applications were already used before establishment of the UML. Coherent applications can be represented in an application diagram.
The structure of an application can look about in such a way:
Name and Identifier of applications have a name and arranged according to special's groups are durchnummeriert, e.g. UC 2.01. Here description (description) takes place a short description, which happens in the application. That there is two or three lines, rarely more means briefly. Participants involved (actors) of participants are persons or systems involved. E.G. user, logged in user, customer, system, account process. The participants are explained before in their own section. Status the status states, how far the work on the application prospered. In work, ready for the Review, in the Review rejected and removed the usual status is. Used applications (includes) if the application to other applications falls back, these other cases are enumerated here. To enumerate are name and identification number. If necessary it is a good idea to arrange the reference interactive to insert i.e. a left (and/or interactive cross reference). Trips (rational) the reason and/or the reasons for the fact that this application is implemented. Preconditions (preconditions) all conditions, which must be fulfilled, so that this application can be implemented. There are no preconditions, then here "none" stands. Nachbedingung/result (post office conditions) the result, which is expected after a successful run of the application. Here steps (normal flow) the actual normal operational sequence is represented. With normally the straight flight is meant, thus the ideal case and/or most frequent regular expiration. The steps are nummeriert and described usually in structured German and/or English. Flow diagrams can be used however likewise, if it appears appropriate. By means of the UML these steps in activity diagrams can or application-oriented sequence diagrams to be represented. Alternative steps (alternative flow) this are expirations outside of the straight flight. They represent deviations or bypasses of the normal steps. Exceptions (exception) this are the hard exceptions, which are however still formulated on technical level. Instead of to e.g. write "data base available", rather "customer object is not written not available". Points of extension (extensions) these make the formulation of extensions for the functionality possible of an application under certain conditions. When occurring the respective condition the functionality of a further case of application is then taken up (that to be naturally likewise modelled must). Refers to short explanations necessarily to assist in the understanding, references to side effects, application statistics so far and everything else, which does not continue to can to be represented above. Change history (use case history) Versionierung, name of the author, dateAn application describes the series of interactions between users and system, who are necessary to carry out a technical goal of the user. The described operational sequence may not become too complex. As reference point the coffee tracing test described of Cockburn can serve: as long as the application is not too complex, will would the question "insert the user during the interactions a coffee "also "no" answers.
We found here 6 articles.
A» Actual condition» Adhocratie » Advanced Planning and Scheduling » Aktuariat » Application » Authority (organization) |
We found here 6 related websites.
Index | Privacy | Terms Of Use | Sitemap | Feedback
Printer Friendly Format
Bookmark this page
Back to "Planning and organization"
Back to top