Roles and Activities > Analyst Role Set > Business Designer > Define Automation Requirements
The team must make a rough estimate of what kinds of support the changed business use cases will require. It is important to indicate, at an early stage, which techniques are available for implementing the business. Are your free to support the business use case with new custom business tools? Must you use existing business tools? Or can you purchase off-the-shelf products? Can you find the necessary resources, internally or externally, for the business tools that must be developed? Is the existing configuration of computer systems, terminals, workstations, and networks important? Is compatibility with the existing business tools required?
Many technologies are developing very fast. You must build up a good understanding of available state-of-the-art solutions, generally solutions as well as those specific to your own business domain.
Common to all organizations is the dependence on information technology. For a long time, information technology has been used to improve the performance of the business. However, modern solutions can totally change the way business is done. Before deciding on any new process designs it is important that you understand the potentials of modern information technologies. The following list (see [JAC94]) gives you an idea as to what you can do with technology to improve, or totally revolutionize, the way a business operates.
To identify information-system use cases, begin with the business workers in the business object model. For each business worker, perform the following steps:
See also Guidelines: Going from Business Models to Systems, the section on business models and actors to the system.
If a business worker is to be completely automated by the system, the corresponding system actor can be removed. The system use case corresponding to the business worker still needs a system actor that initiates it. Search for that system actor among the business actors and business workers supported by the to-be-automated business worker. See also Guidelines: Going from Business Models to Systems, the section on automated business workers.
For each business entity, consider the following:
See also Guidelines: Going from Business Models to Systems, the section on business models and entity classes in the analysis model.
There are many sources of knowledge aboutóand requirements foróthe information system outside the business model. Examples of sources are:
See the Requirements Discipline for more details.
As the activity concludes, review the system artifacts that have been sketched, to ensure that they are consistent. As the results of this activity are preliminary and relatively informal, reviews should be informal as well.
Rational Unified Process