Organizational Information System at Bright Light Limited Essay
The assignment illustrates the very idea of information system for BLL and to understand from system perspective the various business processes at BLL. Task one stresses on the various system perspective of the BLL business processes. It outlines the various inputs, outputs and other processes that helps in outlining the various system functionalities and encourage the identification of the various system processes. Task two investigates the various CAD/CAM initiatives that would be taken into account for BLL. It would also underline how the system can be developed with the methodology taken into account.
Task three takes into account the various types of systems that are required at every level of the BLL organization so that information can be captured well and analyzed for benefit of the organization. Task four focuses on the various shop floor data collection processes that would be taken up by BLL and also the hardware and software requirements. Task 1 This task outlines the various processes that are defined for BLL in the systems perspective and would encourage better system engineering for its development. Systems Concepts:
The system concept portrays the idea of what is to be processed, the processing block and the final outcome of the processing.
Need essay sample on "Organizational Information System at Bright Light Limited"? We will write a custom essay sample specifically for you for only $ 13.90/page
The processes are in the form of various raw materials processing which ultimately would become final products of the organization for sale to end customers. Also the ordering process and other processes like warehousing, materials management, distribution management and shipment which ultimately are very large and crucial processes for the BLL to finally get the products to its end customers. Output: The final products that are shipped to the various retailers and wholesalers for reaching the final customer for use are the outputs of the organization.
Also the collection of the various feedbacks of the customer would ensure better design and quality of the products. Feedback The feedback is in the form of various customer responses and effective process management of the firm. The feedback can also be in the form of various deviations in meeting production targets, customer demands and better management of financial resources. Boundary The scope is in the production of bulbs and fluorescents only. The idea is to bring in more number of suppliers with the geographic spread. Interaction with the environment
BLL environment is composed of various stakeholders who are directly or indirectly responsible of effective functioning of the business processes. The suppliers, retailers, wholesalers, vendors and customers (both institutional and retail) are its environment with which it needs to interact to function and achieve its goals. Departmental Information flow BLL has lateral communication established in their organization. However the primary design maker is the director who takes the lead control for various productions, marketing and human resource issues.
Once the various process plans are devised, the departments moves accordingly to achieve them and processes the various instructions and reports back for all information access and decision making. Figure 2 : Organizational information flow The reporting structure is bilateral in nature and uniquely determines the success of the various processes in BLL. The below content level DFD explains the various process and the way BLL business process interact for better functioning of the organization. Figure 3 : DFD – Level 0
It discusses the various stakeholders and the processes they have to undergo to underline their business process and to achieve their goals in catering to the final customers. Task 2 BLL has acquired computer aided design and computer aided manufacturing system. It would be used enterprise wide in all the departments so that it is used for proper functioning. Enough networking must be done so that its capabilities can be captured well by the enterprise. CAD/CAM System: Using the software one would be able to design the bulbs and fluorescent of several dimensions.
Adding a third dimension to the design makes it more communicative with respect to propagation of the inner details. The concept of axis applications also makes the product design to track back the changes and provide reflection to the dimension of simultaneous movement. The most striking features are the use of an integrated common database for CAD and CAM which keeps the data compatible at all times. Another interesting feature is the concept of tightly integrated software which makes the system eliminates the translation of files between separate CAD and CAM packages (Hoffer, 2002).
IS Development Process The systems analysis and development methodologies create an automated and intelligent virtual system so that they are able to capture the entire business in the computer software and associate every department and minute processes for the sake of achievement of business functions. The following are the various reasons that can be attributed for exercising the systems analysis and development methods for BLL: • Linking the resources for capitalizing the working of business processes. • Effective utilization of resources.
• To force the organization to plan and organize the business elements. • To enable the enterprise to coordinate activities. • To collaborate the resources for optimum usage • The record for transactions and business process mapping are performed for success The life cycle of information systems impact the organization in several ways and can be summed as follows: • System investigation: The primary analysis of the system is essential for enveloping all the business data and information requirements to map all processes in the organization (Hoffer, 2003).
It is done so that no data is left out and there is 100% coverage of the business requirements. The requirements of this stage demand enough expertise and skill to effectively understand and capitalize on information so that information is captured to its full swing. • Systems analysis and Design: Once all the requirements are collected successfully they are analyzed to their importance and framed into defined design models such as DFD, E-R diagram and others so that their modeling is successfully transformed into a working system (Navathe, 2005).
The entire design reflects the working of the organizational processes and their penetrations with external forces. The capabilities of this stage demands business modeling methods and strategies for developing a suitable data flow diagram to correctly figure out the process. • Systems coding: This is the actual step where the business requirements are actually implemented and taken care to be given a representation. The impact of this stage would result in greater understanding of the business methods and good communication skills with the client.
This stage creates an impact to make a difference to code the system to exact requirements mapped in the planning stages. • Systems implementation: Successful implementation of the system is essential for the system to facilitate working and for the users to take full advantage of the system. The impact of this stage is quite large as improper implementation strategies may affect the working of the organization and processing capabilities. The above four stages impact the working of the organization as they are directly related to create a system to map the organizational processes.
3. IS Methodology with Justification: The methodology to be selected for BLL would be Rapid Application Development (RAD). Rapid application development (RAD) techniques reduce the time complexity of the waterfall methods by prototyping methods and other techniques. Unlike waterfall and information engineering methods it creates joint application development sessions to understand the user requirements better and decide on functionality for design and usability.
In place, RAD addresses the above problems of not involving the users and makes sure that the stakeholders of the system are able to meet and discuss on all grounds including design and look and feel. RAD also encompasses methods which take care of the organizations current processes. The phased approach of RAD makes it unique to address the present and emergency requirements of the organization and segregating the entire system into sections for implementation. In other methods the information system is not broken into parts and developed as a whole.
In comparison, RAD identifies the crucial components which the business requires urgently and develops them first and then takes care of other components in phased manner to complete the entire system. The benefits of such a method can be highlighted as follows: System requirements can be predicted before hand. A model is generated to keep the system synchronized with the changes made. The users get the complete picture of the proposed system. It is quite overlapping in nature which makes the system design and analysis redundant and reviewed time and again.
Following the development stages over again would make the ultimate system rich in design quality and improved maintainability. Reusability factor is the biggest strength. Pressman mentions that the use of tools like database programming language, interface generator, links to office application and report generators make sure that time and effort investment is utilized in a quality fashion. It easily develops the system into components which are focused for a particular objective. Redundant nature of development would make sure that development time is quite wasted in practice.
Effort and time determination is eroded to great extent as mentioned in Sommerville (2005). Design may not be stable even after several prototypes. Challenges to the method are attributed as extensive. Quite challenging to coordinate team based development. No explicit system architecture followed in practice. The tools make sure that ultimate product is derived at the least amount of time without much of development cost and effort. The parts of the software are into complex dependencies which ultimately causes maintainability.