IS 401 CH. 1 (Terms) Flashcards
systems analysis
Systems analysis consists of those activities that enable a person to understand and specify what the new system should accomplish. The operative words here are “understand” and “specify.” Systems analysis is much more than simply a brief statement of the problem.
For example, a customer management system must keep track of customers, register products, monitor warranties, and keep track of service levels, among many other functions—all of which have myriad details. Systems
analysis describes in detail the “what” that a system must do to satisfy the need or to solve the problem.
systems design
Systems design consists of those activities that enable a person to describe in detail the system that solves the need. The operative word in this case is “solves.” In other words, systems design describes “how” the system will work. It specifies in detail all the components of the solution system and how they work together to provide the desired solution.
Systems Development Life Cycle
The Systems Development Life Cycle (SDLC) identifies all
the activities required to build, launch, and maintain an information system. Normally, the SDLC includes all the activities that are part of systems analysis, systems design, programming, testing, and maintaining the system as well as other project management processes that are required to successfully launch and deploy the new information system. There are many approaches to the SDLC and many variations for projects that have various needs. However, there is a core set of processes that is always required, even though there is also an incredible number of variations of these core processes—in how each process is planned and executed and in how the processes are combined into a project.
Systems Development Life Cycle (Core Processes)
- Identify the problem or need and obtain approval to proceed.
- Plan and monitor the project—what to do, how to do it, and who does it.
- Discover and understand the details of the problem or the need.
- Design the system components that solve the problem or satisfy the need.
- Build, test, and integrate system components.
- Complete system tests and then deploy the solution.
information systems development process
.
There are many ways to implement these six core processes of the SDLC. An information systems development process is the actual approach used to develop a particular information system. (methodology)
Most information systems you will develop are conceived and built to solve organizational problems, which are usually very complex, thus making it difficult to plan and execute a development project. Most processes/ methodologies now use Agile and Iterative development
Agile Development. (an information systems development process)
The basic philosophy of Agile Development is that neither team members nor the user completely understands the problems and complexities of a new system, so the project plan and the execution of the project must be responsive to unanticipated issues. It must be agile and flexible. It must have procedures in place to allow for, anticipate, and even embrace changes and new requirements during the development process.
Iterative development
is an approach to system development in which the system is “grown” in an almost organic fashion. Core components are developed first and then additional components are added. It is called “iterative” because
the six core development processes are repeated over and over again to add additional functionality to the overall system. In other words, there is one big
project, which consists of many mini-projects, and the information system is grown piece by piece.
An iteration is like a mini-project in that it has a completed result and a constrained time frame. Often, it will last two to four weeks.
Iterative development drawing
left: core processes
right: iterations (1-6)
rounded mounds: the amount of effort for that core process during that iteration
Benefits to Iterative development
- Portions of the often system can sometimes be deployed sooner. If there are core functions that
provide basic support, these can be deployed in an early iteration. - A second benefit is that by taking a small portion and developing it first, many tough problems can be addressed early in the project. By focusing on only a small portion, the requirements are fewer and easier to grasp and solve.
- Developing a system in iterations makes the entire development process much more flexible and able to address new requirements throughout the project.
More details on Iterative development
A key element of iterative development is choosing a part of the solution system that can be done in two to four weeks. During one iteration, often all the core development processes are involved, including programming and system-wide testing, so the result is a part of the working system, even though it may only have a portion of the functionality that is ultimately required.