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 requirement 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. .
When choosing the RAD team, it is recommended to be approximately of 6 people (including developers and system analysts). The "team" should be multi-talented and different roles. RAD will deploy visual tools and other methods to convey and to assist in developing the product. One important product will be version control since many versions of the product will be generated. .
b. Identify which business process mapping methods you recommend for use in design activities.
