Enterprise system development
a. Describe which design methods you prefer for developing an enterprise-level information system.The purpose of the design phase is to transform all the requirements gathers form the previous phases into blueprints of the product. In order to accomplish that, analysts and project managers have many design methods to choose from. The success of the project, however, will not only rely on the design methods chosen, but the efficient and the level of detail gathered during the requirements phase. As mentioned there are several methods of that can be utilized in designing an enterprise-level system. It seems to the nature of the methodology, RAD or rapid application development seems to be merged more often nowadays as the preferred designing method. RAD is a software development process that allows technicians to built a project in a relatively short time, depending the project, of course (between 60-90 days). Some of the main advantages of RAD is the fact that less time is required to produce the total project, because it is done mostly in a “rapid” fashion. As a result of that, of course, the final project or the customer get to see the results before time (not long delays). Because of our current financial, technical requ
f. Discuss design trade-off issues within a final design BPM (business process mapping) or also know as business process redesign most of the time occurs when the developer/analyst team is asked to re-examine the current business flow and a greater detail scope and find out which areas can be modify or tuned to supercede the current performance and flow of the business. Usually, the re-examination can find political challenge on the way, since many employees, are reluctant in disclosure all the aspects of the job and by fearing a job replacement or something similar. irement change so rapidly, RAD is fairly simple to adjust to new business requirements. Because RAD is based interactively on prototyping, the customer or end-user get to see the “project” before it is totally done allowing a chance to identify and correct changes. The trade-offs will vary depending of the situation and the project in question. The project manager, while using his/her technical skills will balance the all the benefits and loss in making some of the design trade-offs. Some of other common tradeoff parameters are operation system process speed, memory usage of the application, I/O consumption, overall bandwidth, in summary performance. That’s not the main goal in several cases. In the process of redefining (or
Some topics in this essay:
Rational Rose,
,
Oracle Workflow,
Interface Design,
Financial ERP,
interface design,
human interface,
human interface design,
business process,
rational rose,
business process mapping,
design methods,
project managers,
process mapping,
developers project managers,
successful project,
project manager,
design interface,
user interface design,
Join now to see the rest of the essay!
Approximate Word count = 1468
Approximate Pages = 6 (250 words per page double spaced)
More Essays on Enterprise system development Professional Papers: |
CUSTOMER SERVICES
|
|
Saved Papers
You haven't saved any papers.
|