"FRONT OFFICE AUTOMATION SYSTEMCost Based:Within the manual system a perennial amount of the finance are incurredcontinuously upon the extra staff, maintaining the data manually on paper for all the data- integrated jobs. The information has put through many hands at proper time to apply theconsistency standards, which is the backbone for any company this application.Consistency is increased with the designed software, which eliminates the actualinvestment upon the employee’s salaries and purchasing the products. Operational feasibility It refers to the feasibility of the product to be operational. Some products may workvery well at design and implementation but many fail in the real time environment. Itincludes the study of additional human resource required and their technical expertise. Technical feasibility The system is self explanatory and does not need any extra sophisticated training. Asthe system has been built by concentrating on the graphical user interface concept, theapplication can also be handled very easily with a now wise user.The software’s that were used to develop are already used by the customers. The nettime the customer should concentrate is on the installation time. That’s what we are givingin the form of manual. Use Case AnalysisUse case: Use case diagrams are one of the five diagrams in the UML for modeling thedynamic aspects of the systems (activity diagrams, sequence diagram, state chart diagram,collaboration diagram are the four other kinds of diagrams in the UML for modeling thedynamic aspects of systems). Use case diagrams are central to modeling the behavior of thesystem, a sub-system, or a class. Each one shows a set of use cases and actors and relations.DEPT OF IT, PDCE 2009-2010 Page 16 FRONT OFFICE AUTOMATION SYSTEMCommon properties:A use case diagram is just a special kind of diagram and shares the same commonproperties, as do all other diagrams –a name and graphical contents that are projections intothe model. What distinguishes a use case diagram from all other kinds of diagram is itsparticular content.Contents:Use case diagrams commonly contain:? Use cases? Actors ? Dependency, generalization, and association relationshipsLike all other diagrams, use case diagram may contain nodes constraints. Use casediagram may also contain packages, which are used to group element of your model intolarge chunks.Occasionally, you will want to place instances of use case in your diagram,as well, especially when you want to visualize a specific executing system.Use case: A use case specifies the behavior of the system or part of the system and is adescription of a set of sequence of actions that a system performs. Graphically use case isrendered as an ellipse with dashed lines, usually including only its name as shown below.AdministratorActor:An actor is a human user or external system with which a system being modeledand interacts. It needs some information from current system. Graphically it is representedas follows.DEPT OF IT, PDCE 2009-2010 Page 17 FRONT OFFICE AUTOMATION SYSTEMACTOR? An actor models an external entity which communicates with the system by sendingand receiving messages, and exchanging data and events.User, external system, physical environment.? An actor has a unique name and an optional description to represent roles, people ordevices play as the system functions.? Users can play a number of different roles, a type of user of the system, for a givenscenario.Examples:? Passenger: A person in the train.? GPS Satellite: Provides the system with GPS co-ordinates.? ATM, the client is an actor who can withdraw money from an account, transfer money to an account or check balance of anaccount. DEPT OF IT, PDCE 2009-2010 Page 18 "