Question 1.
If someone at a party asked you what a systems analyst (SA) was and why anyone would want to be one, what would you say?
Write your answer in a 400-word essay. Include a discussion of IT project failure rates, key activities of an SA in systems analysis and in systems design and the impact on the business outcomes.
Question 2.
a) Explain this statement: "We need to institutionalize the SDLC as our organizational project management methodology."
b) Describe two advantages and two disadvantages of using interviews in requirements gathering.
c) Explain the difference between a waterfall and an iterative/incremental agile method. Illustrate your answer with diagrams.
d) Compare the use of a DFD model with a UML activity diagram for modeling business processes (No need to show diagrams).
Question 3.
Draw a use-case diagram for the following scenario:
You are at a restaurant and you need a ride home. You heard about Unter...the on-demand car services company. You down load the mobile app, which supports multiple operating system versions, onto your smart phone and set up an account including credit card information. Once the app is setup, you enter your pickup location and your destination address. When a nearby Unter driver accepts your request, the app displays an estimated arrival time. The driver arrives and takes you home. When you at your home, the fare is automatically and securely billed to your credit card on file with Unter. Before leaving the car, you provide feedback on the driver's performance via the Unter app. Once Unter has its commission, the remaining fare is deposited automatically and securely into the driver's account. Your trip has ended.
(Use MS Office tools, Visio or a free tool from Creately.com; no hand-drawn maps).
Question 4.
a) Explain the difference between functional and non-functional requirements. Using the scenario in Question 3, provide two examples of each.
b) Explain two reasons why the object-oriented techniques have improved systems analysis and design.
c) Give an example of an output bias and two strategies to avoid UI design output bias.
d) What is the significance of defining forward facing "to-be" functionality.