Project!

Section 1 Business Requirements Document

Student’s Name:

Institutional Affiliation:

Section 1 Business Requirements Document

The scope of the project

The scope of the project is to enable the creation and implementation of the information systems infrastructure of a company. The information system of an organization is crucial to the organization, and thus, the IT network and system needs to be improved such that efficiency of the entire IT system is enhanced. Procuring quality business requirements is an essential step towards the design of quality information systems. The completion of a quality requirements documents allows the user needs, as well as expectations to be captured such that the infrastructure and information system can be designed properly.

Justifications for the scope

The infrastructure of an information system should entail relevant security mechanism that protects critical information in an organization. Information system security can be evaluated using CIA or Confidentiality, Integrity, and Availability triangle, which mainly define the security policy of an organization. A network solution is always chosen so as to support the conceived information systems, as well as allow for scalability.

How to control the scope

The design of a respiratory data collection system, it involves a combination of Data Warehouses, OLTP, OLAP and Data Mining. It is essential to acknowledge that relational database, which is to be implemented in this case is designed for a certain purpose. Essentially, the purpose of data ware house certainly differ from OLTP is due to the characteristics of a relational data supports data warehouse, while on the other OLTP database has a different design. In this case, Data warehouse database is usually designed for the purpose of analysis of different business measures by both categories and attributes (Silberschatz et al., 2011). They will be able to optimize bulk loads, complex and unpredictable queries that are accessed through many rows per table. Also, its loading is consistent and gives valid data, which does not necessarily require real-time validation (Connolly & Begg, 2014). Unfortunately, Data warehouses only support a few concurrent users. OLTP database, on the other hand, is designed for real-time operations of the business. Moreover, it is optimized for only common transaction sets, which is attained by adding or retrieving single rows at a time per table. Interestingly, OLTP database can support thousands of concurrent users. The organizations data collection and analysis system will involve and incorporation of OLPT system for purposes of providing a user interface while at the same time using data warehouse databases for storage purposes (Vaisman & Zimányi, 2014).

Possible risks, constraints, and assumptions

The recommended option for the development of the data collection system is ware house database. However, there are various issues that are likely to be characterized by the use of the data warehouse database for analysis and storage of information. The user interface of the company’s system will largely depend on an OLTP system to provide access to multiple users, while at the same time utilizing data warehouse databases for effective storage. The risks that will be associated with the design will be as follows; firstly, the incorporation of OLTP system on one end and a data ware house database, on the other hand, will be extremely complex to implement (Connolly & Begg, 2014). There is a likelihood of scrubbing data in the merge between the OLTP system and data warehouse, which may lead to inconsistency of data being stored in the system.

The needed integration with other systems and infrastructure

The design of the data collection and analysis system will involve an integration of an OLTP system into data warehouse database to offer excellent and acceptable performance. This incorporation of OLTP systems and data warehousing is aimed at meeting specific needs of the company in data collection and analysis. The relationship that exists in this hybrid system is that OLTP system will only be used for providing an excellent user interface. Hence, an exciting user experience is achieved. The data warehouse on the other hand is used to make collection and analysis of different data by both categories and attributes, which ensures that the data stored is segmented into different categories (Hellerstein, 2005). This shows that the infrastructure of the system will entail two ends of the OLTP system and a data warehouse database. The Meta data will represent the data and application organization of different OLTP components, and which has a direct link to the user experience.

The relational data, in this case, is organized in such a way that make analysis and collection more effective, since the OLTP system will enable thousands of users into the organization’s system. When the OLTP data moves to the data warehouse, it must then be transformed into warehouse data for storage purposes. The process of building the data warehouse will involve reorganization of the OLTP data stored in the relational tables into multidimensional cubes (Silberschatz et al, 2011). This is regarded as transformation stage as OLTP data is changed into warehouse data for storage. It will involve three phases, which include extraction of data from the OLTP system, transformation of the data into usable OLTP system, and finally loading of the data into the data ware house or data mart. Once the data is finally loaded into the data warehouse, there will be decision makers that will be used to access and analyze the data in the data marts or data warehouses (Hellerstein, 2005). The diagram above show the structure of the entire system suitable for the company’s needs.

Potential outsourcing/offshoring needs

The company might need to outsource services in order to attain effectiveness in improving its productivity. Some of the outsourcing needs might include including a third party to manage their user interface, and hiring the services of outside servers companies to run their data. This means that the company can dedicate the marketing aspect of their site to other parties to manage in increase the company’s relevance in the competitive market. This is crucial in meeting the different needs of potential consumers, as parties contracted for marketing purpose will greatly entail more excess to the user interface. Essentially, it means that a third party will be needed to outsource for more customers, as the company’s data collection and analysis is improved (Khan, 2003). Contracting third party to manage and host the company’s system will entail a cut in the production cost as the contracted party will solely provide the infrastructure for running of the site and all servers.

Justify the necessary resources

Since the company anticipates for 20 percent annual increase in data warehouse storage space, the company will require increasing its storage capacity into order to be able to accommodate huge volumes of data. With the 20 percent increase each year, the company should also make places to increase its capacity to accommodate more customers at its user interfaces. Notably, this will involve enlarging the capacity of the OLTP system to handle more users without frequent failures (Khan, 2003). The system servers on the hand should be regularly upgraded to handle the projected increase of users to the company’s system every year.

References

Connolly, T. M., & Begg, C. E. (2014). Database systems: A practical approach to design, implementation, and management.

Hellerstein, J. M. (2005). Readings in database systems. Cambridge, Mass. [u.a.: MIT Press.

Khan, A. (2003). Data warehousing 101: Concepts and implementation. San Jose, Calif: Khan Consulting and Publishing.

Silberschatz, A., Korth, H. F., & Sudarshan, S. (2011). Database system concepts. New York: McGraw-Hill.

Vaisman, A., & Zimányi, E. (2014). Data warehouse systems: Design and implementation.