Data gathering is a significant process that is fundamental to the process of developing information systems. With the fact that there are different information systems that are in use, the ways and methodologies that are used in gathering the data is also seen to be different. Data gathering process for a data warehouse is different from data gathering for operational systems. The difference is that the data gathering for operational is done is such a manner that there is support for transaction processing (Peña-Siles, del Mar González-Zamora, & Machuca, 2012). The data that involves the transactions that are being undertaken are being gathered and analyzed and assessed. The patterns on the use of the data is found to be different in the two data gathering procedures. The data that is gathered for operational systems is voluminous and less on the back-end when compared to the report processing data that has to be collected and considered for data warehousing systems. The operational systems focus on the business processes. The data that is being gathered is the for the business process. The data gathering for the data warehouse is for the specific subject area. It is subject-oriented. The subject areas are usually populated with the data that come from the various business processes (Peña-Siles, del Mar González-Zamora, & Machuca, 2012). The data that is being gathered for the operational; systems is for current system while that of the data warehousing is for data that has been collected in the past. In gathering data for the operational systems, there will be the need to have updates for the data gathered from time to time. The data in the data warehouse is rarely updated as the changes are not done on a regular manner.
Joint application development is a data accumulation approach which is result situated. The methodology is principally used to gather exclusive expectation data and create venture deliverable in a constrained time period with the guide of encouraged workshop. This some piece of the paper List, give a brief depict, and give samples of the potential advantages of utilizing joint application plan.
The main advantage of utilizing JAD is the change of correspondence between the venture group and the business clients and thus lessens the time taken in building up a framework. The methodology empowers the gathering and approval of data inside of the briefest time period by including the partners. It expansion, the undertaking procedure deferrals are disposed of.
Utilization of JAD likewise decreases the expense of a framework. This alludes to the worker hours of both the business clients included and the framework designers. The work expense will lessen when the advancement time is decreased (Davidson, 2009). The JAD methodology gives more fixation to discriminating which obliges duty and contribution, for example, prerequisite social event. The expense diminishment likewise comes in the disposal of mix-ups, misconception and lapses. Preferably, a joint application outline session empowers the clients and creators to begin cooperating in the exact early framework improvement stages.
JAD additionally enhances the profitability and nature of the framework. The nature of a framework altogether relies on upon the obliged assembled. As being what is indicated, JAD connect with clients in the framework improvement handle and empowers them to determine their framework necessities, and henceforth encourages fulfillment of business goals (Carmel, Whitaker, & George, 2003).
Requirements gathering is a significant process that helps in understanding what the users will want to be achieved in the development of the system. The user requirements are important in development stage and process of the entire process. Getting enough information about the system will help in understanding the requirements of the system and will help in getting what will have to be changed according to the user requirements. Requirement gathering is useful as it helps the developers to be able to tailor the requirements and make it to align with what the client will want to be achieved in the entire development process (Wang, & Wang, 2012). All these issues will have to be developed and enhanced in order to have the required aspects of the development process.
One difference between building an operational system and that of building a data warehouse is that operational systems are built to enable the company take small volumes of data. It is done in order to be optimized in getting small regular updates. On the other hand, data warehouse is built in order to be able to get fast retrieval of data from large volumes of data which are normally stored in a database.
Another difference is that the operational systems are built in order to focus on applications and not on related data. One aspect of the non-relational model is that the applications which are built are not at all related and will not be done in order to have the required aspects and management of the data. On the other hand, the data warehouse systems have data that are related so that the data are related and have the same information. The data layer is placed at the top of the application layer.
Another difference is with operational systems, the users will not need to have high-end skills and knowledge. The data warehouse systems are developed by people who have a wide range of computing skills. The users of the data warehouse will have to have high level skills. Any change that will have to be made on the data warehouse will have to be done by experts and people who have the needed skills.
Information package diagram is a significant tool that is used to get the subject matter of the data warehouse and the key performance. It has purpose that is highly targeted. It defines the scope of the user requirements that are needed.
One of the benefit of using JAD is that the users will be able to give their requirements and will interact with the developers. The interaction between the users and the developers is simpler and easier to use in the entire process (Rosenblatt, 2013). JAD is also beneficial in requirements gathering because it enables the developers to get an interaction with the developers and in the process they will get eth details and information that they need. In this interaction, the data gathering process will be simple. The development process will be simpler with the use of JAD because it enables the developers have the needed information that will enable them to develop the systems according to the users of the system.
In comparison with the waterfall model, the JAD model takes a shorter period of time because the developers will get the user requirements through a series of interviews. The interviews will be used to get the right information and will, therefore, help reduce the time period that is used in the development process (Rosenblatt, 2013). The user involvement is simpler in JAD because there is constant interaction with the developers. Also, the requirements gathering takes a shorter period of time when compared to waterfall model. It is because of the process and the procedures that are involved in the two aspects. The development process is simpler with the JAD because the development is based on the current user interaction through interviews. In the waterfall model, there is minimal time that the developers will interact with the users of the system.
References
Peña-Siles, J., del Mar González-Zamora, M., & Machuca, J. A. (2012). Specifying business services: learning from software engineering. Journal of Service Management, 23(1), 97-119.
Rosenblatt, H. J. (2013). Systems Analysis and Design. Cengage Learning.
Wang, S., & Wang, H. (2012). Information Systems Analysis and Design. Universal-Publishers.
