Information systems analysis and design
Vocabulary Bank Unit 22
Task 1. Read, write the translation and learn the basic vocabulary terms:
12. acceptance testing
13. adjusted
14. application specification
15. checkout clerk
16. conversion software
17. cutover
18. discrete step
19. entire
20. estimate (n)
21. evaluating hardware solution
22. evaluation checklist
23. expert system shells
24. extranet
25. from scratch
26. help desk
27. implementation phase
28. in-depth training
29. intranet
30. maintenance phase
31. misleading
32. on the contrary
33. ongoing activity
34. outline (n)
35. overall
36. peak data load
37. peer-to-peer environment
38. point-of-sail
39. pressure-sensitive digitalizing pad
40. Project Development Plan
41. request for proposal (RFP)
42. request for quotation (RFQ)
43. scope
44. signature
45. system development life cycle (SDLS)
46. System Requirements Report
47. to approve
48. to assemble the team
49. to be usable by
50. to combat
51. to convert
52. to deduct
53. to eliminate
54. to excel
55. to finalize documentation
56. to fix a problem
57. to imply
58. to justify project
59. to prohibit
60. to retire
61. to satisfy
62. to stretch throughout
63. to undergo
64. trial version
65. turnkey system
66. waterfall SDLS
67. written change request
Text 22A. SYSTEMS ANALYSIS
Whether you are a part of a team that is developing a complex corporate information system, or you are developing a small information system for your own use, you will be more likely to succeed if you analyze the purpose of the information system, carefully design the system, test it thoroughly, and document its features. In this text you’ll learn about the planning and analysis that’s required for an information system.
SYSTEM DEVELOPMENT LIFE CYCLE
An information system progresses through several phases as it is developed, used, and finally retired. These phases are referred to as a system development life cycle – usually referred to as SDLC.
Planning
Phase Analysis
Phase Design
Phase Implementation
Phase Maintenance
Phase
The original waterfall SDLC, shown above, approaches each phase as a discrete step in the development process. One phase is supposed to be completed before the next phase can begin.
The SDLC is an outline of a process that helps develop successful information systems. The process of planning and building and information system according to the SDLC is referred to as systems analysis and design.
|
|
|
Planning Phase
For creating an information system it’s important to have a plan. Initial plans for an information system are developed during the planning phase. The planning phase for an information system project includes the following activities:
Assemble the project team
Justify project
Choose development methodology
Develop a project schedule
Produce a Project Development Plan.
The main goal of these activities is to create a Project Development Plan. Before the project proceeds beyond the planning phase, the Project Development Plan must typically be reviewed and approved by the management. This planning document includes:
A short description of a project, including its scope
A justification for the project, which includes an estimate of the project costs and potential financial benefits
A list of project team participants
A schedule for the project, including an outline of its phases
Project planning begins in the planning phase but stretches throughout the entire project.
As the project takes shape, project managers break down the work into tasks and milestones, which can be scheduled and assisted. As tasks are completed, the schedule can be updated and adjusted. Project management software is an effective tool for planning and scheduling. It helps manages track and visualize the complex interactions between tasks. Popular examples include open source software, such as Open WorkBench, and commercial software, such as Microsoft Project.
Analysis phase
The analysis phase begins after the project team selects a development methodology, draws up the Project Development Plan, and receives permission to proceed from management. The goal of the analysis phase is to produce a list of requirements for a new or revised information system.
Typically, a new information system is designed to replace a system or process that is already in place. It is important to study the current system to understand its strengths and weaknesses before planning a new system.
|
|
|
System requirements are the criteria for successfully solving problems identified in an information system. There requirements guide the design and implementation for a new or updated information system. They also serve as an evaluation checklist at the end of the development project, so they are sometimes called success factors. A new or updated information system should meet the requirements the project team defines.
The project team determines requirements by interviewing users and studying successful information system that solve problems similar to those in the current system. Another way to determine requirements is to construct a prototype as an experimental or trial version of an information system. Often the prototype is not a fully functioning system because it is designed to demonstrate only selected features that might be incorporated into a new information system. A systems analyst shows the prototype to users, who evaluate which features of the prototype are important for the new information system.
After the project team studies the current system and then determines what the new system should do, system requirements are incorporated into a document called a System Requirements Report that describes the objectives for an information system. If management or the project sponsor approves the report, the project can move on to the design phase.
Дата добавления: 2018-10-26; просмотров: 591; Мы поможем в написании вашей работы! |
Мы поможем в написании ваших работ!