Info. Systems Analysis & Design Tackeld Organisation

Question: Discuss about the Info. Systems Analysis Design for Tackeld Organisation. Answer: Introduction In todays present competitive scenario, all business endeavor to enhance its service quality, and therefore, they constantly evolve their systems. The paper based tracking system is being used in Australian labs which is to be replaced by an automated system. The following report analyzes the feasibility of the project for Australian Labs. Firstly, the problems being tackled by the organization because of manual work will be analyzed and after that, the proper methodology for system development will be chosen. Then, the system requirements will be identified and cost-benefit analysis will be performed. Possible Approaches to System Development and Justification A project is explained as defined commitment that has a starting and an end via which an item is developed. System development can be described as a kind of agreement which comprises of a big job which provides an original information system. A successful system development project involves well-organized and systemized processes that offer highlights such as accuracy, efficiency, and trustworthiness. Traditional Predictive Approach All projects comprise of actions associated with location, execution, design, startups, and pre-determination. Various project activities are called phases. Additionally, a phase known as support is implemented. This maintains the actions changeable within a system. Newer Adaptive Approach In accordance with the System Development Life Cycle, the action that is modified within a project is required to be integrated as progress. In the beginning, all aspects are not properly defined and it is quite important. SDLCs first genre is called the Spiral Model that analyzes the project and until completion, modifies the content. The information system utilized for Australian Labs are (Hazaveh. ,2014) System Requirements According the analysis, the underlying system requirements are performed (Pendharkar, Rodger and Subramanian, 2008) Functional Requirements Functional or operational requirements are described as the requirements of the system which are to be accomplished so that the system can undertake real actions and offer required results. According to the history of the organization and requirements, the underlying functional requirements are noted Registration A process of registration which will be used by the system and both superior and subordinate employees. The process provides an exclusive ID and password to each employee for proper security. Authentication/Login After registering, the employees need to login to the system via their ID and password. Track inventory It allows users to track the inventory on the basis of order id. Report generation The user can generate, save and print reports. Track requests The technicians can track the requests i.e. pending request. Non-functional Requirements The non-functional necessities show the behavior of the system by providing some restrictions on the behavior of the system. Non-functional requirements are assumed to be assurance of proper system quality. The non-functional requirements are (ReQtest, 2012) Performance Static volumetric, time acknowledgement, optimum utilization, etc. Scalability The system needs to be adaptable to new spaces without much modifications in the suggested system. Reliability The system needs to be available 24x7. Sources of Software There are numerous software sources that are given below, in addition to their advantages Packaged Software Products These are also known as off-the-shelf software since organizations provide these packages for commercial usage. They are quite cheaper and are made available immediately. Enterprise Solutions Software These are widely utilized sources of software since it offers full integration with the organizations present business processes. Cloud Computing - These sources are newer kind of software since it is provided freely from the necessity of a computing foundation. The software is offered via the internet and the consumers can easily utilize it over the internet. In-House Development Organization might opt for in-house development of the necessary software if the necessary skill set is available. This type of software is always designed in such a manner so that the necessary specifications are accomplished. There are various off-the-shelf software packages which are present. The selection will be performed according to the requirements and needs of the specific project, in addition to project budget and skill set which is present with the organization. For the Australian Labs project, the underlying off-the-shelf software can be used to remain with budget and provide high availability and requirements (Riffel, and Levin, 1997) MS-Project for managing and designing schedule of the project. Adobe Dreamweaver for coding. MySQL Database for storing and management of consumer and vendor information. Project cost benefit analysis 2009 2010 2011 2012 2013 2014 Cost involved Costs -$80,000 -$25,000 -$25,000 -$25,000 -$25,000 -$25,000 Benefits $0 $40,000 $40,000 $40,000 $40,000 $40,000 Net Cash Flow -$80,000 $15,000 $15,000 $15,000 $15,000 $15,000 Discount Factors Discount Rate 6.0% Year (base) 2009 Year Index 0 1 2 3 4 5 Discount Factor 1.0000 0.9434 0.8900 0.8396 0.7921 0.7473 Discounted Flows Costs -$80,000 -$23,585 -$22,250 -$20,990 -$19,802 -$18,681 Benefits $0 $37,736 $35,600 $33,585 $31,684 $29,890 Net -$80,000 $14,151 $13,350 $12,594 $11,881 $11,209 Cumulative -$80,000 -$65,849 -$52,499 -$39,905 -$28,023 -$16,815 Net Present Value $11,384 Internal Rate of Return 10% Table 1: Cost Benefit analysis Cost benefit analysis is a process which is performed to find the economic feasibility of the project i.e. whether the cost invested will provide required benefits. In the given scenario, the total one-time cost is $80,000 and recurring cost for 5 five years is $25,000. The Net Present Value and Return on Investment are calculated. The NPV is positive and Rate of Return is 10% and break down occurs after 5 years i.e. payback period of the project is 5+ years with 6% discount. The following table is with 10% discount rate and NPV comes out to be negative. 2009 2010 2011 2012 2013 2014 Costs -$80,000 -$25,000 -$25,000 -$25,000 -$25,000 -$25,000 Benefits $0 $40,000 $40,000 $40,000 $40,000 $40,000 Net Cash Flow -$80,000 $15,000 $15,000 $15,000 $15,000 $15,000 Discount Factors Discount Rate 10.0% Starting Year 2009 Year Index 0 1 2 3 4 5 Discount Factor 1.0000 0.9091 0.8264 0.7513 0.6830 0.6209 Discounted Flows Costs -$80,000 -$22,727 -$20,661 -$18,783 -$17,075 -$15,523 Benefits $0 $36,364 $33,058 $30,053 $27,321 $24,837 Net -$80,000 $13,636 $12,397 $11,270 $10,245 $9,314 Cumulative -$80,000 -$66,364 -$53,967 -$42,697 -$32,452 -$23,138 Net Present Value ($23,138) Internal Rate of Return -2% Project Schedule The Project Management Body of Knowledge signifies the work breakdown structure as a deliverable related ranking decomposition of the work to be initiated by the team. In the following figure, the WBS is given. The actions are segmented into implementation, documentation, coding, testing, requirements, analysis, execution, design, and bonds. The actions are also segmented into sub-tasks which provide a summary of the actions that are required to be finished within the process. Figure 1: Gantt chart Most actions are broken up in the Gantt chart. These action are completed within the scheduled time. According to the initiation plans and requirements, the actions can be finished due to the appropriate amount of time. This is a less complicated manner in which the planned processes can be achieved. After analysis, the project can be finished in the time given 47 days. The Gantt chart given above explains the organizations status on which every tasks within the processes are finished. System Information Requirement Investigation Techniques Stakeholders In simple terms, the stakeholders are individuals or organization that are involved financially, physically, or in some manner, with the project. They will be affected in every manner such as profit, loss, drop down, etc (Systems Analysis and Design in a Changing World, 2016). Internal Stakeholders are as follows: Project Manager Developer Designer Database Administrator Test Engineer Implementation manager External Stakeholders are as follows: Project Sponsor Jim Larsen and his team Suppliers Vendors Customers Technicians Investigation Techniques 3 investigation techniques can be utilized for collecting information to begin the systems development procedures that will fulfill the requirements and desires of employees, shareholders, and members. Techniques of investigation are critical for the organization since it assist in determining the perspective of the stakeholders, employees, and investors. Questionnaire Method In this method, the investigator asks a series of preset questions. In consideration of the cost factor, it is quite cost-efficient and doesnt take up much capital. The questions depend on the project requirements. These questions will assist the organization in confirming the desires and necessities of the respondents for regulating the organization in accordance with the requirements to be fulfilled (Yuen, Law and Wong, 2003). Personal Interview Via this process, the investigator can individually investigate another individual in a 1:1 conversation. Then, the conclusions are drawn upon the answers received. These conversations assist the investigator in knowing about the respondents ideas and this leads to further progress. Secondary Sources This method comprises of analyzing historical data that is already present. These sources comprise of prior employee records of the jobs performed. All the positive and negative aspects are provided in the documents so that better understanding can be had (Valacich, George, and Hoffer, 2001). Reflections and Conclusions Australian Labs require a renovation of their present information system. Via this system, the consumer details can be maintained in an optimal manner. It manages and modifies the books of accounts. An option for online payment is available to the consumers. The projects main aim is to accomplish the customers requirements by offering them easy-to-use and advanced technologies. This automated system offers a turning point for laboratories and enhances their skills and manner of operations. Additionally, it assists in raising the business funds and profits. Thus, all problems will be recognized and solved by the application of a proper system development methodology that will be chosen so that grievances can be avoided. Sorting of the system requirements have been performed and all necessary analysis is done. The result of the analysis is that the project is feasible and can be accomplished. References Mahdi Hazaveh. (2014). What is an Expert System? Advantages and Disadvantages of it.. [online] Available at: https://blog.hazaveh.net/2014/08/what-is-an-expert-system-advantages-and-disadvantages-of-it/ [Accessed 19 Aug. 2016]. Pendharkar, P., Rodger, J. and Subramanian, G. (2008). An empirical study of the CobbDouglas production function properties of software development effort. Information and Software Technology, 50(12), pp.1181-1188. ReQtest. (2012). Functional Requirements vs Non Functional Requirements. [online] Available at: https://reqtest.com/requirements-blog/functional-vs-non-functional-requirements/ [Accessed 19 Apr. 2016]. ME, (2012).à ¢Ã¢â€š ¬Ã‚ ¯MLE11 - Communicate information and knowledge. [online] SQA. Available at: https://www.sqa.org.uk/files_ccc/MLE11CommunicateInformationandKnowledge.pdf [Accessed 21 Dec. 2015]. Riffel, J. and Levin, B. (1997). Schools Coping with the Impact of Information Technology.Educational Management Administration Leadership, 25(1), pp.51-64. Systems Analysis and Design in a Changing World. (2016). 6th ed. Webber, C. (2003). New technologies and educative leadership.à ¢Ã¢â€š ¬Ã‚ ¯Journal of Educational Admin, 41(2), pp.119-123. Yuen, A., Law, N. and Wong, K. (2003). ICT implementation and school leadership.à ¢Ã¢â€š ¬Ã‚ ¯Journal of Educational Admin, 41(2), pp.158-170. Valacich, J., George, J. and Hoffer, J. (2001).à ¢Ã¢â€š ¬Ã‚ ¯Essentials of systems analysis and design. Upper Saddle River, N.J.: Prentice Hall.