Ch 2: Understanding and Modeling Organizational Systems Flashcards
What are the three groups of organizational fundamentals that carry implications for the deveopment of information systems?
- The concept of organizations as systems
- The various levels of management
- Overall organizational culture
-Ch 2, pp. 43
What is meant by saying the organizational subsystems are interrelated and interdependent?
When any element of a system is changed or eliminated, the rest of the system’s elements and subsystems are also significantly affected.
-Ch 2, pp. 20
Define the term organizational boundary.
All systems are contained by boundaries separating them from their environment. Organizational boundaries exist on a continuum ranging from permeable to impermeable.
-Ch 2, pp. 21
What are the two main purposes of feedback in organizations?
- Control
- Planning
Ch 2, pp. 20
Define openness in an organizational environment.
Openness refers to the free flow of information within the organization.
-Ch 2, pp. 21
Define closedness in an organizational environment.
Closedness refers to the policies, procedures, and culture that restricted the free flow of information within the organization.
-Ch 2, pp. 21
What is the difference between a traditional organization and a virtual one?
Traditional organization are brick and mortar whereas virtual ones use technology to bring people with specific skills togther electronically to work on projects that are not physically located in the same place.
-Ch 2, pp. 22
What are the potential benefits and drawbacks of a vitual organization?
Give an an example of how systems analysts could work with users as a virtual team.
An analyst can still complete the full SDLC in a vitual organization, but the tools and methods employed to gather feedback from users should be in line with how users already operate. For example, platforms such as MS OneNote and blogs to facilitate conversation; video tutorials on YouTube for training new systems; and, as always, examing the back and front ends of the system through an HCI-paradigm are examples.
What are enterprise resource planning (ERP) systems?
Information system software that is integrated organization-wide (enterprise-wide) and helps companies in the coordination of critical organizational processes between functional areas. Software packages are purchased from companies such as SAP or Oracle and customized for a specific organization’s needs.
-Ch 2, pp. 23, 503
What is the main difference between doing business process analysis for ERP and other types of systems?
An ERP brings with it a set of business processes native to the software itself that usually require an organization to adapt new business procedures and policy. Wheras a networked information system allows the analyst to shape and refine the system to meet the needs of the employees. In other words, an analysts looks for how the organization must change it’s practices to conform to the ERP instead of looking at how to tailor the system to conform to the human information requirement.
-Ch 2, pp. 24
What problems do analysts often encounter when they try to implement an ERP package?
- User acceptance
- Integration with legacy systems
- Integration with the supply chain
- Upgrading functionality and complexity of ERP modules
- Reorganizing work life of users and decision makers
- Expanding reach across several organizations
- Strategic repositioning of the company adopting ERP
-Ch 2, pp. 24
What are the two symbols on a use case diagram, and what do they represent?
- Stick Figure (aka. actor): Something that exist outside of and interacts with the system. Can be a human, another system, device, or web connection.
- Oval (aka. event): An actor action that begins a related series of interaction in the system that map out the overall use case.
-Ch 2, pp. 32
What is a use case scenario?
Provides developers with a view of what the user wants. Always describes three things: an actor that initiates an event, the event that triggers a use case, and the use case that performs the action triggered by the event.
-Ch 2, pp. 32
What are the three main parts of a use case scenario?
- An actor that initiates an event
- The event that triggers a use case
- The use case that performs the action triggered by the event
-Ch 2, pp. 32