Is a strategy in systems analysis and design in which the project is reviewed after each phase and continuation of the project is Rejustified?

Business caseA written report that outlines the justification for an information system. This reporthighlights economic benefits and costs and the technical and organizational feasibility of the proposedsystem.Page23of76

Economic feasibilityA process of identifying the financial benefits and costs associated with adevelopment project.Incremental commitmentA strategy in systems analysis and design in which the project is reviewedafter each phase, and continuation of the project is rejustified in each of these reviews.Recurring costA cost resulting from the ongoing evolution and use of the system.Discount rateThe interest rate used to compute the present value of future cash flows.Intangible benefitA benefit derived from the creation of an information system that cannot be easilymeasured in dollars or with certainty.Schedule feasibilityThe process of assessing the degree to which the potential time frame andcompletion dates for all major activities within a project meet organizational deadlines and constraintsfor affecting change.Tangible costA cost associated with an information system that can be easily measured in dollars andwith certainty.Electronic commerceInternet-based communication and other technologies that support day-to-daybusiness activities.WalkthroughA peer-group review of any product created during the systems development process.Technical feasibilityA process of assessing the development organization’s ability to construct aproposed system.One-time costA cost associated with project initiation and development, or system start-up.Present valueThe current value of a future cash flow.Page24of76

Tangible benefitA benefit derived from the creation of an information system, that can be measured indollars and with certainty.Legal and contractual feasibilityThe process of assessing potential legal and contractual ramificationsdue to the construction of a system.Intangible costA cost associated with an information system that cannot be easily measured in terms ofdollars or with certainty.Baseline project plan [BPP]One of the major outcomes and deliverables from the project initiation andplanning phase. It contains the best estimate of the project’s scope, benefits, costs, risks, and resourcerequirements.Operational feasibilityThe process of assessing the degree to which a proposed system solves businessproblems or takes advantage of business opportunities.Time value of moneyThe process of comparing present cash outlays to future expected returns.Break-even analysisA type of cost-benefit analysis to identify at what point [if ever] benefits equal costs.

Chapter 4Review Questions4-10.Describe the concept of the time value of money. How does the discount rate affect the value of $1today versus one year from today?

Upload your study docs or become a

Course Hero member to access this document

Upload your study docs or become a

Course Hero member to access this document

End of preview. Want to read all 76 pages?

Upload your study docs or become a

Course Hero member to access this document

TO BE SUBMITTED BEFORE FRIDAY - Feb [2nd week 2nd class meeting] , 2017

Print out your answers in A4 Size Bond Paper.  Place your Assignment in your ClearBook.  It should contain BOTH QUESTIONS and ANSWERS.

I - Create a Report 

     By giving a Brief and Complete Discussion of Alternative Approaches to System Development.

    Present also a Flow Diagram for each.

Prototyping, computer-aided software engineering [CASE] tools, joint application design [JAD], rapid application development [RAD], participatory design [PD], and the use of Agile Methodologies represent different approaches that streamline and improve the systems analysis and design process from different perspectives.

II - 

Match each of the key terms below with the definition that best fits it.    [

Topic on  Systems Planning ]

1. Baseline project plan [BPP] 
2. Break-even analysis 
3. Business case
4. Discount rate 
5. Economic feasibility 
6. Electronic commerce
7. Electronic data interchange [EDI]
8. Extranet 
9. Incremental commitment
10. Intangible benefit 
11. Intangible cost 
12. Internet 
13. Intranet
14. Legal and contractual feasibility
15. One-time cost
16. Operational feasibility 
17. Political feasibility
18. Present value
19. Project scope statement
20. Recurring cost
21. Schedule feasibility 
22. Tangible benefit
23. Tangible cost
24. Technical feasibility 
25. Time value of money [TVM]
26. Walkthrough 

1. The process of evaluating how key stakeholders within the organization view the proposed system.
2. A document prepared for the customer that describes what the project will deliver and outlines generally at a high level all work required to complete the
      project.
3. A written report that outlines the justification for an information system. This report highlights economic benefits and costs and the technical and
     organizational feasibility of the proposed system.
4. A process of identifying the financial benefits and costs associated with a development project.
5. A strategy in systems analysis and design in which the project is reviewed after each phase, and continuation of the project is rejustified in each of these
     reviews.
6. A cost resulting from the ongoing evolution and use of the system.
7. The interest rate used to compute the present value of future cash flows.
8. A benefit derived from the creation of an information system, that cannot be easily measured in dollars or with certainty.
9. A network of interconnected individual networks that use a common protocol to communicate with each other; a global computing network to support              business-toconsumer electronic commerce.
10. The process of assessing the degree to which the potential time frame and completion dates for all major activities within a project meet organizational
     deadlines and constraints for affecting change.
11. A cost associated with an information system, that can be easily measured in dollars and with certainty.
12. Internet-based communication and other technologies that support day-to-day business activities.
13. A peer group review of any product created during the systems development process.
14. A process of assessing the development organization’s ability to construct a proposed system.
15. A cost associated with project initiation and development, or system start-up.
16. The current value of a future cash flow.
17. Internet-based communication to support business activities within a single organization.
18. A benefit derived from the creation of an information system, that can be measured in dollars and with certainty.
19. The process of assessing potential legal and contractual ramifications due to the construction of a system.
20. A cost associated with an information system, that cannot be easily measured in terms of dollars or with certainty.
21. One of the major outcomes and deliverables from the project initiation and planning phase. It contains the best estimate of the project’s scope, benefits,
     costs, risks, and resource requirements.
22. The process of assessing the degree to which a proposed system solves business problems or takes advantage of business opportunities.
23. The process of comparing present cash outlays to future expected returns.
24. A type of cost-benefit analysis to identify at what point [if ever] benefits equal costs.
25. Internet-based communication to support business-to-business activities.
26. The use of telecommunications technologies to transfer business documents directly between organizations

III - 

Match each of the key terms below with the definition that best fits it.    [

Topic on  Systems Analysis ]

1. Business process reengineering [BPR]
2. Closed-ended questions 
3. Disruptive technologies 
4. Formal system
5. Informal system 
6. JAD session leader 
7. Key business processes 
8. Open-ended questions 
9. Scribe

Match each of the key terms above with the definition that best fits it.
1. The search for, and implementation of, 

radical change in business processes to 

achieve breakthrough improvements in 

2. The person who makes detailed notes of the happenings at a joint application design session.
3. Technologies that enable the breaking of long-held business rules that inhibit organizations from making radical business changes.
4. The way a system actually works.
5. The official way a system works as described in organizational documentation.
6. The structured, measured set of activities designed to produce a specific output for a particular customer or market.
7. Questions in interviews and on questionnaires that ask those responding to choose from among a set of specified responses.
8. Questions in interviews and on questionnaires that have no pre-specified answers.
9. The trained individual who plans and leadsjoint application design sessions.

IV - 

Match each of the key terms below with the definition that best fits it.    [

Topic on  Systems Analysis]

1. Agile Methodologies
2. Application software
3. Boundary 
4. Cohesion
5. Component
6. Computer-aided software engineering [CASE] 
7. Constraint 

8. Coupling 

9. Decomposition
10. Environment 
11. Information systems analysis and design 
12. Interface 
13. Interrelated 
14. Joint application design [JAD]
15. Modularity 
16. Participatory design [PD] 
17. Prototyping 
18. Purpose 
19. Rapid application development[RAD] 
20. Repository 
21. System 
22. Systems analysis 
23. Systems analyst 
24. Systems design 
25. Systems development life cycle [SDLC] 

26. Systems development methodology
27. Systems implementation and operation 
28. Systems planning and selection
1. The first phase of the SDLC in which an organization’s total information system needs are analyzed and arranged, and in which a potential information systems project is identified and an argument for continuing or not continuing with the project is presented.
2. The process of developing and maintaining an information system.
3. A systems development approach that originated in northern Europe, in which users and the improvement of their work lives are the central focus.
4. Software designed to process data and support users in an organization. Examples include spreadsheets, word processors, and database management systems.
5. The organizational role most responsible for the analysis and design of information systems.
6. A structured process in which users, managers, and analysts work together for several days in a series of intensive meetings to specify or review system
requirements.
7. Building a scaled-down version of the desired information system.
8. A group of interrelated procedures used for a business function, with an identifiable boundary, working together for some purpose.
9. An irreducible part or aggregation of parts that make up a system, also called a subsystem.
10. Dependence of one part of the system on one or more other system parts.
11. The line that marks the inside and outside of a system and that sets off the system from its environment.
12. The overall goal or function of a system.
13. Phase of the SDLC, in which the system chosen for development in systems analysis is first described independently of any computer platform and is then transformed into technology-specific details from which all programming and system construction can be accomplished.
14. Phase of the SDLC, in which the current system is studied and alternative replacement systems are proposed.
15. Everything external to a system that interacts with the system.
16. Point of contact where a system meets its environment or where subsystems meet each other.
17. A limit to what a system can accomplish.
18. Final phase of the SDLC, in which the information system is coded, tested, and installed in the organization, and in which the information system is systematically repaired and improved.
19. A standard process followed in an organization to conduct all the steps necessary to analyze, design, implement, and maintain information systems.
20. The series of steps used to mark the phases of development for an information system.
21. The process of breaking the description of a system down into small components; also known as functional decomposition.
22. Dividing a system up into chunks or modules of a relatively uniform size.
23. The extent to which subsystems depend on each other.
24. The extent to which a system or subsystem performs a single function.
25. Software tools that provide automated support for some portion of the systems development process.
26. A centralized database that contains all diagrams, forms and report definitions, data structures, data definitions, process flows and logic, and definitions of other organizational and system components; it provides a set of mechanisms and structures to achieve seamless data-totool and data-to-data integration.
27. Systems development methodology created to radically decrease the time needed to design and implement information systems.
28. Current approaches to systems development that focus on adaptive methodologies, people instead of roles, and an overall self-adaptive development process.

Which planning methodology determines information systems projects based on taking advantage of business opportunities or solving business problems?

Are peer group reviews of any product created during the systems development process?

What is value chain analysis quizlet?