Information System Design in Australian Labs

Question: Discuss about the Case Study for Information System Design in Australian Labs. Answer: Introduction: The study includes the description of implementing the information system in the Australian labs. In addition to that, the analysis of the existing system along with the aspects of the current process that can be improved. Aim: The aim of the report is to provide solutions for improving the current business process in Australian labs. Another aim of the report is to conduct the cost benefit analysis of implementing the information system in Australian system. Objective of the Project: The objective of the report is to create a new system in the organization which will facilitate the process. The Approach to System Development: System Development Approaches: There are two types of system development approaches such as following. Traditional approaches: It is also known as the structured system development. Through following this approach the managers will be able to divide the development of the project in to modules, steps, stages and tasks (Highsmith, 2013). Traditional approach also offers a structure through which the techniques for managing the project successfully can be developed. Object oriented approach: The advantage that the workers can have by building the system by following the OO approach is that the object will be self contained modules in the system. In addition to that, the objects are easy to replace and modify (Larman, 2012). For describing the interface and the development of the interface the manager can make use of the class. A higher level of abstraction can be offered to the project. System Analysis: At first for initiating the system analysis knowing the stakeholder requirements is crucial (Robertson Robertson, 2012). After gathering knowledge of the stake holder requirements the requirement analysis are carried out. An approach of requirement analysis which is problem face analysis is done. Then in the information model analysis the data elements and their behaviors are examined. After that the output of the previous analysis is taken as the input of entity functional analysis. Six Sources of Software: The six sources of the software are as following. Packaged software product Cloud computing In-house development Information technology services firms Open source software Packaged software products. Off the Shelf software: For considering the off the shelf software for the project the manager must make sure that the right equipment must be chosen (Rubython Maiden, 2014). The selection of the software depends on the requirement of the project. For documenting the various activities in the project, off-the-shelf software must be used in the projects. Justification behind choosing the off-the-shelf: The spreadsheets will be used for keeping track of the payments (Gnanasankaran et al., 2013). For writing reports and memos the word processing application will be useful. Systems Requirement: Functional Requirements: The primary purpose of the project is to create a system that will decrease the effort of the staffs and will enhance the capacity of the processes. The automation of most of the process will provide time to managers to concentrate on the core business. Item Requirement Description 1 Registration The function will be incorporated to register new clients in the system. 2 Login The stakeholders will be able to login to the system with the provided id and password. 3 Search 1. The manager will be allowed to search specific staff or client information. 2. The clients will be able to search from several invoices. 4 Logout The session of the stakeholder login will be destroyed. 5 Status The salespersons will be able to see their status. 6 Tracking The organization can answer the can answer where the client request 7 Mail The users will be able to communicate with each other 8 View provided services The managers can gather information of the clients and provided services to those individual clients. 9 Automatic report authentication The reports will be authenticated automatically for giving more time to the managers. 10 Checking and arranging staff schedule The staff schedule will be provided the system will arrange their shifting. Powers will be provided to the managers to overwrite the system specified scheduling. 11 Checking result of test Authorization of checking the result of each test will be provided to the desired staffs along with all the managers. Table 1: Functional Requirements of Australian Labs (Source: Larman, 2012) Nonfunctional Requirements: Item Name Description 1 Security 1. The security to the organizations valuable data. 2. Security to the consumers checkup reports 2 Authorization The authorization is important as it will allow only desired users to access specific information. 3 Storage It will store all the raw data collected from the users as well as the information and business patterns 4 Availability As the service is provided to the consumers 24*7, the system must be able to provide service all the time. Table 2: Non-Functional Requirements of Australian Labs (Source: Chung et al., 2012) Project Cost Benefit Analysis: The financial management and project manager of Australian lab information system project makes use of the cost benefit analysis to justify the implementation of the system (Torritia Ikpeb, 2014). In this analysis the mangers will identify the cost of the system and profit from it. The profit will be examined in terms of five years. Year 0 Year 1 Year 2 Year 3 Year 4 Year 5 Net economic benefit $0 $20,000 $35,000 $42,000 $44,000 $50,000 One time cost $105,000 $0 $0 $0 $0 $0 Recurring cost $0 $35,000 $30,000 $25,000 $22,000 $7,000 Net cash flow $105,000 $55,000 $65,000 $67,000 $66,000 $57,000 Discount factors Discount rate 10% Year Index 0 1 2 3 4 5 Discount factor 1 0.909090909 0.826446281 0.751314801 0.683013455 0.620921323 Discounted flows Cost $105,000 $31,818 $24,793 $18,783 $15,026 $4,346 Benefit $0 $18,182 $28,926 $31,555 $30,053 $31,046 Net $105,000 $50,000 $53,719 $50,338 $45,079 $35,393 Cumulative $105,000 $155,000 $208,719 $259,057 $304,136 $339,529 Net present value $234,528.50 Table 3: Cost benefit Analysis Project Schedule: Project Work Breakdown Structure Figure 1: Work Breakdown Structure (Source: Created by Author) Project Schedule (Gantt chart) Figure 2: Gantt chart for the Project (Source: Created by Author) The tasks as well as deliverable in the project plan are classified by the Work Breakdown Structure. The schedule of the project is prepared from WBS along with identifying critical paths for the activities in project plan (Li et al., 2012). The development of the project schedule is represented by Gantt chart, which is a graphical representation of the activities in project. System Goals The objective of the inventory tracking system is to give the staffs responsibility and minimize the stock outs. It tracks and audits the offers of Australian Labs in general premise (Stair Reynolds, 2013). It likewise results for exactness of inventory systems. It will likely the inventory database up to date. System Requirements The system requirement is to help in the customers query whether the required item is in the stock and the inventory manager views the demand of the items. System Scope The scope of the system is to develop their outdated inventory tracking system in order to develop their daily sales, payment as well as maintenance of the items (Roetzer et al., 2013). It performs the automation of the inventory items in a systematic way. Discussion The project schedule is reasonable, as the goal of the project plan is to finish the project within time as well as budget. It follows all the project guidelines and follows the rules and regulations of the Australian Labs. System Information Requirement Investigation Techniques: Involved stakeholder: Jim Larsen is the main stakeholder in the development of the information system and the head technician in Australian labs. The other stakeholders are inventory manager, system analyst, senior manager, salespersons, project manager, resource manager and customers (Vieru Rivard, 2014). Traditional Investigation Technique: Interview: For collecting the information from the client or the other stake holders it is the best technique. Some specific questions are asked in the interview to get the desired information (Li et al., 2012). This is done periodically, once a month or week, so that the project includes everything that it needs. Questionnaire: A set of predetermined questions are asked in this technique. The users get this question trough electronic medium such as electronic mail (Roetzer et al., 2013). Observation: During the implementation of the system this method is used (Li et al., 2012). Usefulness of the Investigation Technique: Interview: This method provides accurate and complete information about the project requirements and scope. Through conducting interview periodically will provide the project manager to know the little expectations of the client. As the questions and time of the interview is bounded, no useless topics will be discussed (Stair Reynolds, 2013). Irrelevant conversations can guide the project in the wrong way. Questionnaire: It allows the project manger to collect large amount of information within a short span of time. There are differences in the views of the stakeholder (Roetzer et al., 2013). Through this method those differences can be recognized. Observation: As it can be considered as the direct method of gathering information, it is accurate and reliable procedure (Stair Reynolds, 2013). Reflections and Conclusions: The project that the Australian Labs has undertaken is an effective and an efficient one. The onetime investment may seem to be costly but the profit Australian Labs is going to gain from the system is far better. The system will be able to monitor the process of the client request automatically. It will allow the customers know exactly how much time they have to wait to get the reports. As a result the loyalty of the consumers will increase. To create a IS the user and system requirement gathering is a very crucial process. The organization will be able to process its business activates more effectively, efficiently and within less time. References: Chung, L., Nixon, B. A., Yu, E., Mylopoulos, J. (2012).Non-functional requirements in software engineering(Vol. 5). Springer Science Business Media. Gnanasankaran, N., Natarajan, S., Alagarsamy, K., Iyakutti, K. (2013). Commercial Off-The-Shelf (COTS) components in software engineering: The software package SCILAB.International Journal of Computer Technology and Applications,4(1), 68. Highsmith, J. (2013).Adaptive software development: a collaborative approach to managing complex systems. Addison-Wesley. Larman, C. (2012).Applying UML and Patterns: An Introduction to Object Oriented Analysis and Design and Interative Development. Pearson Education India. Larman, C. (2012).Applying UML and Patterns: An Introduction to Object Oriented Analysis and Design and Interative Development. Pearson Education India. Li, X., Xu, X., Wang, J., Yu, H., Wang, X., Yang, H., Huang, L. (2012). A system-level investigation into the mechanisms of Chinese Traditional Medicine: Compound Danshen Formula for cardiovascular disease treatment.PloS one,7(9), e43918. Robertson, S., Robertson, J. (2012).Mastering the requirements process: Getting requirements right. Addison-wesley. Roetzer, A., Diel, R., Kohl, T. A., Rckert, C., Nbel, U., Blom, J., Supply, P. (2013). Whole genome sequencing versus traditional genotyping for investigation of a Mycobacterium tuberculosis outbreak: a longitudinal molecular epidemiological study.PLoS Med,10(2), e1001387. Rubython, A., Maiden, N. (2014). The effect of variability modeling on requirements satisfaction for the configuration and implementation of off-the-shelf software packages. In2014 IEEE 22nd International Requirements Engineering Conference (RE)(pp. 394-401). IEEE. Stair, R., Reynolds, G. (2013).Principles of information systems. Cengage Learning. Torritia, J., Ikpeb, E. (2014). CostBenefit Analysis. Vieru, D., Rivard, S. (2014). Organizational identity challenges in a post-merger context: A case study of an information system implementation project.International Journal of Information Management,34(3), 381-386.