Mamba Dedan R.
Permit different parts of the system to be built at the same time by the same person. Allow attention to be concentrated on the part of the system pertinent to a particular audience, without confusing people with details irrelevant to their interests. Facilitate the focusing of attention on one area (subsystem) at a time without interference from other parts. Break a system into smaller, more manageable, and understandable subsystems. Build different parts of the system at independent times and have the help of different analysts. |
joint application design. prototyping. information systems analysis and design. information technology infrastructure development. systems implementation. |
Conflict management Risk and change management Team management Customer relations Technical problem solving |
a project workbook. a schedule book. a project planner. project management software. an electronic calendar. |
Hardware costs Labor costs Employee morale Operational costs Internet service setup fee |
improved organizational planning. ability to investigate more alternatives. improved asset control. lower transaction costs. first to market. |
Interviewing Questionnaires Observations Joint application design Document analysis |
enable the analysts to gather information on what the system should do from as many sources as possible. enable the analysts to develop a baseline project plan quickly. enable the large amount of information gathered during requirements determination to be organized. enable the analysts to identify several feasible alternatives. |
a tendency to avoid creating formal documentation of systems requirements which can then make the system more difficult to develop into a fully working system. prototypes becoming very idiosyncratic to the initial user and difficult to diffuse or adapt to other potential users. prototypes are often built as stand-alone systems. checks in the SDLC are bypassed so that some more subtle, but still important, system requirements might be forgotten. all of the above. |
technology barrier breakers. reengineered technologies. disruptive technologies. state-of-the-art technologies. innovative technologies. |
context diagram. level-1 diagram. level-0 diagram. level-00 diagram. logic diagram. |
cardinality. domain. ternary occurrence. participation level. join level. |
Midrange alternative design strategies often do not involve computer technology; instead they focus on making paper flows more efficient or reducing redundancies in current processes. Midrange alternative design strategies represent compromise solutions. Functionality is the primary focus of midrange alternative design strategies. Midrange alternative design strategies provide all the required functionality users demand with a system that is minimally different from the current system. Midrange alternative design strategies provide all the desired features using advanced technologies that often allow the system to expand to meet future requirements. |
transposing. transcripting. appending. truncating. hashing. |
normalized relations. design specifications. an updated Baseline Project Plan. a list of alternatives design strategies. a production system. |
reverse video. boxing. spacing. underlining. all capital letters. |
Unified Modeling Language. Structured English. pseudocode. logic modeling. structured design. |
the ability to tackle more challenging problem domains. improved communication among users, analysts, designers, and programmers. reusability of analysis, design, and programming results. increased consistency among the models developed during object-oriented analysis, design, and programming. all of the above. |
acceptance testing. alpha testing. beta testing. system testing. stub testing. |
phased installation. single location installation. parallel installation. direct installation. rotation installation. |
|
|
Question 1.1. (TCO 1) List and briefly describe the four major SDLC phases. (Points : 10)
|
|
Question 2.2. (TCO 2) Discuss the six major categories of feasibility. (Points : 10)
|
|
Question 3.3. (TCO 3) Identify and describe the traditional methods for determining requirements. (Points : 10)
|
|
Question 4.4. (TCO 4) Discuss how DFDs can be used as analysis tools. (Points : 10)
|
|
Question 5.5. (TCO 5) Define the following key data modeling terms: entity, attribute, relationship, degree, cardinality, and associative entity. (Points : 10)
|
|
Question 6.6. (TCO 6) briefly discuss generating alternative design strategies. (Points : 10)
|
|
Question 7.7. (TCO 7) Identify and describe validation tests and techniques used to enhance the validity of data input. (Points : 10)
|
|
Question 8.8. (TCO 8) Describe four benefits of the object-oriented modeling approach. (Points : 10) |