Q1: How Are Business Processes, IS, and Applications Developed?
An application is a combination of hardware, software, and data components that accomplishes a set of requirements. Business processes, information systems, and applications have different characteristics and components. The relationship of business processes to information systems is many-to-many. A business process need not relate to any information system, but an information system relates to at least one business process. Every IS has at least one application because every IS has a software component. A business analyst is someone who is well versed in Porter's models and in the organization's strategies and who focus, primarily, on ensuring that business processes and information systems meet the organization's competitive strategies. Systems analysts are IS professionals who understand both business and information technology.
Q2: How Do Organizations Use Business Process Management (BPM)?
A business process is a network of activities, repositories, roles, resources, and flows that interact to accomplish a business function. Roles are collections of activities, and resources, which are people or computer applications that are assigned to roles. A flow is either a control flow that directs the order of activities or a data flow that shows the movement of data among activities and repositories. Businesses need management to improve process quality, changes in technology, and changes in business fundamentals. A business process management (BPM) is a cyclical process for systematically creating, assessing, and altering business processes. This cycle begins by creating a model of the existing business process, called an as-is model.
Q3: How Is Business Process Modeling Notation (BPMN) Used to Model Processes?
Object Management Group (OMG), a software-industry standards organization, created a standard set of terms and graphical notations for documenting business processes. The swim-land layout gives each role in the business process is given its own lane. It simplifies the process diagram and draws attention to interactions among components of the diagram.
Q4: What Are the Phases in the Systems Development Life Cycle (SDLC)?
The systems development life cycle (SDLC) is the traditional process used to develop information systems and applications. The systems development life cycle consists of a five-phrase process: define systems, determine requirements, design system components, implement system, and maintain system. In defining systems, the first step is to define system goals and scope. The second step is to access feasibility. The third step is to form a project team. In determining requirements, the steps needed to be taken are determine sources of requirement, determine the role of a prototype, and approve requirements. In designing system components, each of the five components is designed in this stage. In system implementation, testing and system conversion are done. In maintaining systems, the work done is either to fix the system or adapt it to changes in requirements.
Q5: What Are the Keys for Successful SDLC Projects?
There are five keys to success: create a work breakdown structure, estimate time and costs, create a project plan, adjust the plan via trade-offs, and manage development challenges. The key strategy for SDLC projects is to divide and conquer. Successful project managers break projects into smaller and smaller tasks until each task is small enough to estimate and to manage. Every task should culminate in one or more results called deliverables.
Q6: How Can Scrum Overcome the Problems of the SDLC?
According to the SDLC, progress goes in a linear sequence from requirements to design to implementation. Sometimes this is called the waterfall method because the assumption is that once you've finished a phase, you never go back. The SDLC is very risky. The people for whom the system is being constructed cannot see what they have until the very end. Numerous alternatives to the SDLC include rapid application development, the unified process, extreme processing, scrum, and others.
No comments:
Post a Comment