Great Day Fitness Tracking Final Plan
Ruxpin65
InformationSystemsPlanningwk4.pptxInformation Systems Planning
Michael Murdock
CIS/568: Information Systems Concepts
Ezam Mohammed
08/10/20
Information Systems Planning
Information systems planning is essential in helping the company plan for both long and short term goals.
Information systems will be used by the tracking company to easily collect and share data.
Information systems planning will also help the firm link IT and business aspects.
All IT infrastructure will be a vital force in the business option of the company.
Explain the concept of information systems planning.
Information Systems Planning
The integration of IT and business involves the following;
Identifying challenges and objectives
Planning about the devices to be used during integration
Identifying alternatives of the infrastructure that will be used during the process.
Determining all the priorities.
Drawing operational plan.
Explain the concept of information systems planning.
Development Planning Method
Waterfall
This system requires all the requirements of the system to be defined before the project begins.
Design and development all focus on the requirements tabled before the beginning of the project.
After development, testing is done to ascertain if the requirements were all fulfilled
Agile
All the requirements are treated as a continuous process where all developers are connected in making the whole project a success.
Design, testing and all the project requirements fall into one big ongoing process.
All the tasks are broken into segments commonly referred to as sprints.
Compare at least two development planning methods.
Development Planning Method
Waterfall
Essential in big companies that deal with government projects
Flexibility is paramount.
During the testing process any deficiency ensures that the project returns to the first phase.
After verification, the system undergoes maintenance.
Agile
Suitable for small businesses .
Flexibility and speed in this system is robust.
Responsible teams usually tackle the requirements of each client
Testing is performed periodically while the project is still on.
Compare at least two development planning methods.
Advantages of Waterfall Methodology
It’s the only methodology with a clear structure from beginning to the end.
The end goal is usually determined before the project begins.
Information is transferred successfully
Testing is usually delayed after the project is completed in order to make the system robust.
Making changes to the finished product is usually a hard task thus ensuring the project is successful
Clarify why each planning method is appropriate for new system implementation.
Design
Implementation
Maintenance
Planning
Analysis
Advantages of Agile Methodology
Improved quality
Business value forms the main focus
Transparency is guaranteed
Predictable delivery of the final project
Stakeholder engagement
Focus is made on all users
Clarify why each planning method is appropriate for new system implementation.
Enhanced quality
Transparency
Customer Experience
Predictable
Structured Methodology
Structured methodology will be used by the tracking company to fully accomplish all the projects requirements.
The methodology is selected because of its unique approach.
Structured methodology involves the project being broken down into small phases.
The small phases define the decision tables, data structure diagrams, data flows as well as decision trees.
Select a methodology for designing the information system.
Structured Methodology
Structured methodology involves a single structure that surrounds the system.
The process runs sequentially from the top to the last process in the organizational tree.
The methodology can be used at any time during the project development cycle.
Select a methodology for designing the information system.
Structured Methodology
Structured methodology is usually easier to understand and read.
It uses less effort while developing
It depends on the machine for development
The methodology is user friendly at all times
It is also easier to debug when an issue arises.
Explain the reason for the selected methodology
Structured Methodology
Structured methodology provides planning to the design process.
It is very applicable at any stage of the system development.
The system is usually moderate and consumes less time.
Explain the reason for the selected methodology
Design
Implementation
Maintenance
Planning
Analysis
Outsourcing
Outsourcing is the method to be used to acquire new information systems.
Outsourcing is an essential aspect that will be used to achieve the goals of the company.
New systems acquired via outsourcing are usually robust and efficient.
Address the option to acquire (instead of build in-house) information systems.
Outsourcing
Outsourcing method is efficient due to its low cost.
Outsourcing helps bring new ideas to the firm (Sako 2006).
Outsourcing is a methodology for saving overall time used in the project.
Experts find way to the firm and help build a robust system for the organization.
Address the option to acquire (instead of build in-house) information systems.
Acquisition Tools
Prototyping: A system is build based on the specifications of the users.
Helps users visualize how operational the new system will be (Jarzabek & Huang 1998).
Emphasis is placed on the beginning phases of the project
The model is used to test all the systems and ascertain if they are working successfully.
Identify and discuss the tools that might be used in the acquisition
of a new information system..
Acquisition Tools
CASE Tools: an automated system that will be used to specifically enhance the acquisition process.
It focuses more on long term prospects of the company.
This tool helps in automation of all the products in the system.
It also contains analysis tools that could be efficient in the development stage.
Identify and discuss the tools that might be used in the acquisition
of a new information system..
References
Jarzabek, S., & Huang, R. (1998). The case for user-centered CASE tools. Communications of the ACM, 41(8), 93-99.
Sako, M. (2006). Outsourcing and offshoring: Implications for productivity of business services. Oxford Review of Economic Policy, 22(4), 499-512.
