Explore BrainMass

Systems Analysis and Design Concepts

This content was STOLEN from BrainMass.com - View the original, and get the already-completed solution here!

1. Describe three approaches to organizing programming teams. For what types of projects or development activities is each approach best suited?

2. How does implementing a maintenance change differ from a new system development project?

3. List and briefly describe implementation phase QA activities other than software testing. What is the effect on software testing of not performing non-testing QA activities?

4. Briefly describe direct, parallel, and phased installation. What are the advantages and disadvantages of each installation approach?

© BrainMass Inc. brainmass.com October 25, 2018, 5:16 am ad1c9bdddf

Solution Preview

1. Describe three approaches to organizing programming teams. For what types of projects or development activities is each approach best suited?

One approach would be a cooperating peer team which consists of members of similar skills and experience along with extending specialties. The cooperating peer team is best suited for projects that include experimentation and creative problem solving.

A second approach is the chief developer team which has a single leader that is responsible for all of the important decisions. The chief developer team is best suited for projects with objectives that have been sufficiently defined along with a concise path of completion.

The third approach is the collaborative specialist team that includes team members with a vast set of skills and experience along with less extensive overlapping. The collaborative specialist team is best suited for ...

Solution Summary

This MS Word Document answers four questions surrounding the following IT areas; approaches to organizing programming teams, comparing a maintenance change to a new system development project, discussing the implementation phase QA (Quality Assurance) activities and describing some of different system installation approaches.

See Also This Related BrainMass Solution

Create A System Design Document

System Design is a critical phase of the system life cycle. Poorly designed systems often do not achieve the intended goals. The proper design of inputs, outputs and interfaces play a key roll in system success. The goal of the design phase is to create an interface that is intuitive, logical, and easy to use while achieving the operational goals for the system.

For this project, you will submit a System Design document in MS Word that includes the following:

A title page
A business letter introducing the contents of the document
A visual representation of your system interface. You can prepare this using a drawing package and embed the graphic or MS Word's drawing features. Your interface should include the main screen of your solution and show the main features.
A summary of the proposed program operation
A summary of the implementation plan timeline.

View Full Posting Details