Great Day Fitness Tracking Final Plan
Journey50
Katherine_Askew_Week4_CIS568_informationsystemplanning.pptx
Information systems Planning
Katherine Askew
CIS/568
Ezam Mohammed
Concept of information systems planning
Information system planning is a systematic approach developed by IBM to help firms establish a plan to meet their short- and long-term information requirements (Cassidy, 2016).
It involves preparing systems and processes within a firm to create and utilize corporate information.
Information systems planning is vital in creating and implementing successful strategic plans for global firms (Alamri et al., 2016).
ISP enables an organization to meet its future objectives and reach where it intends to fulfill its mission.
Information systems planning includes policies that act as general guidelines that direct decision making in a firm (Alamri et al., 2016).
Concept of information systems planning
Some of the information management planning involves
Identifying stages of information system in the firm
Identifying applications of firm information systems
Evaluating each of the applications
Establishing a priority ranking for the applications based on established evaluation criteria
Determining the optimum architecture of an information system for serving the top priority applications. (Alamri et al., 2016).
Information systems planning involve key processes for success and competitive advantage of firms in the business environment
It describes the content and structure of the information system, as well as how it is developed (Cassidy, 2016).
It aims at recognizing the stages of information system planning in the firm.
Information Systems Planning
Information Systems Planning
Stage Model of Information Systems Planning
The first stage is strategic planning. It involves
Deriving from organizational plan
Fitting it strategically to the organizational culture
Strategy set transformation (Akbarifar & Hamdi, 2016).
The second stage is information requirement analysis which includes
Defining organizational requirements
Developing subsystem matrix
Defining and evaluating information requirement for the subsystems
The third stage is resource allocation. It includes
Determining return on investment
Steering committees
Developing charge out
Developing a portfolio approach
The fourth stage is the project milestone which involves
Defining milestones
Developing a Gantt chart
Developing a critical path
(Akbarifar & Hamdi, 2016)
Information Systems Development Planning Methods
One of the methods is business systems planning which focuses on automating existing processes in the organization
The second one is critical success factors that analyze information needs in critical areas for business growth and survival
Business systems planning claims that understanding an organization’s information requirement is followed by examining business units, processes, functions, and data elements (Cassidy, 2016).
It calls for taking managers and enquiring from them where they get information, how they use it, their objective, how decisions are made, and their data needs (Cassidy, 2016).
On the other hand, the critical success factors method claims that a firm’s information requirement is determined by a few factors of the critical success of managers (Alhassan, Sammon & Daly, 2019).
It claims that when the factors are attained then organization success is assured
Some of the elements that shape critical success factors are the firm, industry, the manager as well as the general environment
Therefore the information systems focus should be on providing information that enables and organization to reach these goals (Alhassan, Sammon & Daly, 2019).
Appropriateness of critical success factors and business systems planning
The critical success factor method is appropriate in that it produces fewer data in analyzing information systems planning
Only top managers interviewed, and the focus of the interview is on few critical factors
It requires managers to assess their environment and consider how the analysis shapes information needs
It is best for top managers, development of decision support systems and executive support system (Cassidy, 2016)
It is also appropriate as it focuses the attention of the firm on how to handle the information.
Business systems planning is appropriate as it provides information systems with a developmental blueprint.
With business systems, planning opportunities and issues with current applications are well understood
Business systems planning is appropriate since it gives executives direction and a decision-making framework for IT expenditures and makes it easy to develop future technology supporting the organization (Alhassan, Sammon & Daly, 2019).
Agile Methodology Designing the Information System
Agile methodology is a design framework that was initially used in software development but now used in completing large tasks such as project management.
The Agile design methodology based on core principles including
Individual and interactions over tools and processes
Customer collaboration over contract negotiation
Working software over comprehensive documentation
Responding to change over following a plan
Agile methodology is founded on iterative and incremental approach supporting delivery in small increments (Gurusamy, Srinivasaraghavan & Adikari, 2016).
The required functionality is divided into iterations, and after each iteration, the output delivered to the customers.
Iterative concept of agile design involves refining the system through repetition and moving towards the goals
The development cycle is running, areas of improvement identifies, and the cycle is repeated to improve the system (Gurusamy, Srinivasaraghavan & Adikari, 2016)
The Agile design uses various steps including requirement definition, design, development, testing, deployment, and review and goes through the steps in a repetitive manner
Agile Design Methodology
Reason for the Agile Design methodology
Making changes during design is more comfortable and cheaper as the process is repetitive
It is easy to know what customers want in time rather than providing a complete prototype than ask for feedback.
The implementation is fast when done in small tasks; an implementation does not wait for complete design (Dhir, Kumar & Singh, 2019)
It is transparent since customers are involved throughout the process
It is easier to attain quality as projects when divided into smaller units that are manageable
It enables team collaboration as various designers can work on multiple sub-units (Dhir, Kumar & Singh, 2019)
Customer Involvement ensures better customer satisfaction throughout the process.
Option to Acquire (instead of build in-house) Information Systems
Instead of building in-house information systems, the information system can be acquired from external sources that are leasing
Leasing means transferring information systems components such as telecommunications, data centers, and software development and maintenance to a company that specializes in providing services under contracts that specify levels of service (Busby, 2017).
The services can be moved abroad
The responsibility for acquiring information systems moves to the external company
A company can outsource only development or maintenance of information systems with the external company only handing system development
This is done at a cost depending on the agreement between the company and the external source (Busby, 2017)
Other options include the operation of an Application service provider and software as a service provider
Software as a Service Model
This is a cloud model where a company can access the information system as software via a third party over the internet (Naqvi et al., 2018).
This means that a company does not need to have its information system on the computer rather have an account with a provider from where they can access information systems online.
Application Software Provider
In this model, information systems and related services offered over the internet at a fee.
The system can be accessed remotely through a web browser and, therefore, no need to install local drives (Pearlson, Saunders, & Galletta, D. F. (2019).
14
Tools that might be used in the acquisition of a new Information System
Prototyping- this is a model that is built, tested and improved until an acceptable system developed
An important tool as only models are made until the needed information system is developed, thereby reducing wastage in terms of cost and time Mejía-Gutiérrez & Carvajal-Arango, 2017).
Integrated computer-assisted software engineering- these are tools that offer automated assistance in developing information systems
They are essential tools in reducing the time and money used in acquiring a new information system as well as ensuring quality.
CASE tools automate the system development life cycle to uncover faults and deliver quality systems (Tula et al., 2017)
Component-based engineering- this is a tool that helps to acquire of new information system through re-usable components such as network, internet and system services components (Vale et al., 2016)
Object-oriented development tools use system objects in developing an information system as well as rebuilding old ones
Its advantage is that it allows the separation of duties in developing information systems as different individuals can be assigned different roles (Scaglioni & Ferretti, 2018).
References
Akbarifar, I., & Hamdi, K. (2016). IT Strategic Planning with the Approach of Enterprise Architecture. International Journal of Humanities and Cultural Studies (IJHCS) ISSN 2356-5926, 1(1), 1733-1746.
Alhassan, I., Sammon, D., & Daly, M. (2019). Critical success factors for data governance: a theory building approach. Information Systems Management, 36(2), 98-110.
Cassidy, A. (2016). A practical guide to information systems strategic planning. CRC press.
Gurusamy, K., Srinivasaraghavan, N., & Adikari, S. (2016, July). An integrated framework for design thinking and agile methods for digital transformation. In International Conference of Design, User Experience, and Usability (pp. 34-42). Springer, Cham.
Dhir, S., Kumar, D., & Singh, V. B. (2019). Success and failure factors that impact on project implementation using agile software development methodology. In Software Engineering (pp. 647-654). Springer, Singapore.
Busby, D. (2017). Adopting the best approach for a digital banking solution: Combine the benefits of the ‘build’,‘buy’or ‘outsource’options. Journal of Digital Banking, 2(1), 43-50.
Vale, T., Crnkovic, I., De Almeida, E. S., Neto, P. A. D. M. S., Cavalcanti, Y. C., & de Lemos Meira, S. R. (2016). Twenty-eight years of component-based software engineering. Journal of Systems and Software, 111, 128-148.
Scaglioni, B., & Ferretti, G. (2018). Towards digital twins through object-oriented modelling: a machine tool case study. IFAC-PapersOnLine, 51(2), 613-618.
Tula, A. K., Babi, D. K., Bottlaender, J., Eden, M. R., & Gani, R. (2017). A computer-aided software-tool for sustainable process synthesis-intensification. Computers & Chemical Engineering, 105, 74-95.
Mejía-Gutiérrez, R., & Carvajal-Arango, R. (2017). Design Verification through virtual prototyping techniques based on Systems Engineering. Research in Engineering Design, 28(4), 477-494.
References
Naqvi, H. F., Chandio, F. H., Soomro, A. F., & Abbasi, M. S. (2018, November). Software as a Service Acceptance Model: A User-Centric Perspective in Cloud Computing Context. In 2018 IEEE 5th International Conference on Engineering Technologies and Applied Sciences (ICETAS) (pp. 1-4). IEEE.
Pearlson, K. E., Saunders, C. S., & Galletta, D. F. (2019). Managing and using information systems: A strategic approach. John Wiley & Sons.
Cassidy, A. (2016). A practical guide to information systems strategic planning. CRC press.
Alamri, S., Almutiri, N., Ballahmar, H., & Zafar, A. (2016). Strategic information system planning: A case study of a service delivery company. Int. Adv. Res. J. Sci. Eng. Technol, 3(5), 78-84.
