Reference no: EM131290751

Discussion Question

Let's discuss the design phase. The design phase decides how the system will operate in terms of the hardware, software, and network infrastructure that will be in place; the user interface, forms, and reports that will be used; and the speci?c programs, databases, and ?les that will be needed. Although most of the strategic decisions about the system are made in the development of the system concept during the analysis phase, the steps in the design phase determine exactly how the system will operate. The design phase has four steps. Please respond to the following prompt:

• Discuss the four steps to the design phase.

o Please be sure to describe each step's purpose.

SDLC Phases Description

Let's start our first assignment off with a general overview of the Systems Development Life Cycle. Complete the following assignment:

o Write a description of the four phases of the SDLC.

- Include each phase and how they build off of each other.
- Your description should end with the analyst team and by discussing the support plan for the system and what this will entail.
- Your assignment should be at least 1 full page.

Business Processes Diagrams

This assignment will give you an introduction to the systems approach and give you the opportunity to practice creating diagrams to model business processes. Complete the following assignment:

o Concepts in Action: 20D Agile Development at Travelers on page 47 of the textbook.

2-D Agile Development at Travelers

Travelers Insurance Company of Hartford, Connecticut has adopted agile development methodologies. The insurance field can be competitive, and Travelers wanted to have the shortest "time to implement" in the field. Travelers set up development teams of six people-two systems analysts, two representatives from the user group (such as claim services), a project manager, and a clerical support person. In the agile approach, the users are physically assigned to the development team for the project. While at first it might seem that the users are just sitting around drinking coffee and not doing their regular jobs, that is not the case. The rapport that is developed within the team allows for instant communication. The interaction is very deep and profound. The resulting software product is delivered quickly-and, generally, with all the features and nuances that the users wanted.

Questions

1. Could this be done differently, such as through JAD sessions or having the users review the program on a weekly basis, rather than taking the users away from their real jobs to work on development?

2. What mindset does an analyst need to work on such an approach?