system analysis and design part2
TRANSCRIPT
![Page 1: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/1.jpg)
System Analysis and Design
![Page 2: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/2.jpg)
System Development Life Cycle
![Page 3: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/3.jpg)
Systems Planning and Selection
![Page 4: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/4.jpg)
The first activity of the systems planning and selection phase of the SDLC is project identification and selection.
Organizations vary in their approach to identifying and selecting projects.
In some organizations, project identification and selection is a formal process in which projects are outcomes of a larger overall planning process.
Identifying and Selecting Projects
![Page 5: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/5.jpg)
Three key sources for information systems projects
![Page 6: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/6.jpg)
Project identification and selection consists of three primary activities:- Identifying potential development projects- Classifying and ranking projects- Selecting projects for development
The Process of Identifying and Selecting Information Systems Development Projects
![Page 7: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/7.jpg)
Organizations vary as to how they identify projects. This process can be performed by:- A key member of top management, either the CEO of a small or
medium-size organization or a senior executive in a larger organization
- A steering committee, composed of a cross section of managers with an interest in systems
- User departments, in which either the head of the requesting unit or a committee from the requesting department decides which projects to submit (as a systems analyst, you will help users prepare such requests)
- The development group or a senior IS manager
Identifying potential development projects
![Page 8: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/8.jpg)
Common Characteristics of Alternative Methods for Making
Information Sytems Identification and Selection Decisions
![Page 9: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/9.jpg)
Assessing the merit of potential projects is the second major activity in the project identification and selection phase.
The criteria used to assign the merit of a given project can vary based on the size of the organization.
The relative ratings of projects are used to guide the final activity of this identification process—project selection.
Classifying and ranking IS development projects.
![Page 10: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/10.jpg)
Possible Evaluation Criteria When Classifying and Ranking Projects
![Page 11: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/11.jpg)
The selection of projects is the final activity in the project identification and selection phase.
As business conditions change over time, the relativeimportance of any single project may substantially change.
Thus, the identification and selection of projects is an important and ongoing activity.
Selecting IS development projects.
![Page 12: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/12.jpg)
Numerous Factors must be considered when selecting a
project
![Page 13: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/13.jpg)
The primary deliverable, or end product, from the project identification and selection phase is a schedule of specific IS development projects.
These projects come from both top-down and bottom-up sources, and once selected they move into the second activity within this SDLC phase—project initiation andplanning.
Deliverables and Outcomes
![Page 14: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/14.jpg)
Schedule of Projects
![Page 15: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/15.jpg)
An outcome of this activity is the assurance that people in the organization gave careful consideration to project selection and clearly understood how each projectcould help the organization reach its objectives.
Incremental commitment means that after each subsequent SDLC activity, you, other members of the project team, and organization officials will reassess your project.
Incremental Commitment
![Page 16: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/16.jpg)
End of Module
![Page 17: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/17.jpg)
System Analysis
![Page 18: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/18.jpg)
![Page 19: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/19.jpg)
1. Requirements Determination2. Requirements Structuring
Two Parts of Systems Analysis
![Page 20: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/20.jpg)
- At the end of the systems planning and selection phase of the SDLC, management can grant permission to pursue development of a new system.
- A project is initiated and planned (as described in Chapter 4), and you begin determining what the new system should do.
The Process of Determining Requiremments
![Page 21: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/21.jpg)
1. Impertinence. You should question everything.2. Impartiality. Your role is to find the best solution
to a business problem or opportunity.3. Relaxing of Constraints. Assume anything is
possible and eliminate the infeasible.4. Attention to Details. Every fact must fit with
every other fact.5. Reframing. Analysis is, in part, a creative
process.
Characteristics of a System Analyst needed during R.D.
![Page 22: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/22.jpg)
- The primary deliverables from requirements determination are the types of information gathered during the determination process.
- The information can take many forms: transcripts of interviews; notes from observation and analysis of documents; sets of forms and other documents.
Deliverables and Outcomes
![Page 23: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/23.jpg)
![Page 24: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/24.jpg)
Analysis Paralysis - coined to describe a project that has become bogged down in an abundance of analysis work.
Techniques that can be used to structure requirements1. JAD2. Prototyping3. Agile Methodologies
Requirements Structuring
![Page 25: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/25.jpg)
Collection of information is at the core of systems analysis
One of the best ways to get this information is to talk to those directly or indirectly involved in the different parts of the organization affected by the possible system changes.
Traditional Methods in Determining Requirements
![Page 26: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/26.jpg)
Traditional Methods
![Page 27: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/27.jpg)
![Page 28: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/28.jpg)
- Joint Application Design- Prototyping
Modern Methods in Determining Requirements
![Page 29: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/29.jpg)
The primary purpose of using JAD in the analysis phase is to collect systems requirements simultaneously from the key people involved with the system.
Joint Application Design
![Page 30: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/30.jpg)
- JAD Session Leader. - Users. - Managers.- Sponsor- Systems Analyst(s)- Scribes- IS Staff
JAD Participants
![Page 31: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/31.jpg)
JAD Session
![Page 32: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/32.jpg)
Prototyping is most useful for requirements determination when: - User requirements are not clear or well understood, which is often the case for totally new systems or systems that support decision making. - One or a few users and other stakeholders are involved with the system. - Possible designs are complex and require concrete form to evaluate fully.
Prototyping
![Page 33: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/33.jpg)
- Communication problems have existed in the past between users and analysts, and both parties want to be sure that system requirements are as specific as possible. - Tools (such as form and report generators) and data are readily available to rapidly build working systems.
Prototyping...
![Page 34: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/34.jpg)
- A tendency to avoid creating formal documentation of system requirements, which can then make the system more difficult to develop into a fully working system.
- Prototypes can become idiosyncratic to the initial user and difficult to diffuse or adapt to other potential users.
Prototyping Drawbacks
![Page 35: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/35.jpg)
- Prototypes are often built as stand-alone systems, thus ignoring issues f sharing data and interactions with other existing systems. - Checks in the SDLC are bypassed so that some more subtle, but still important, system requirements might be forgotten (e.g., security, some data-entry controls, or standardization of data across systems).
Protyping Drawbacks..
![Page 36: System analysis and design Part2](https://reader036.vdocuments.us/reader036/viewer/2022062522/587a415b1a28ab00148b4835/html5/thumbnails/36.jpg)
End of Module