Use Coupon Code: MarchMadness for 10% off Entire Cart! Coupon Code expires: March 31, 2015

BSA/375 Week 1 - Software Development Resources: University of Phoenix Material: Recording a Narration Read the following scenario:

Senior management at your company is concerned about why so many software development efforts fail. They have asked you to develop a presentation that explains the activities that take place during each phase of the SDLC to ensure software development success.

Create an annotated or narrated 7- to 10-slide presentation that includes the following:

An introduction slide The activities that take place during each phase of the SDLC to ensure successful software development A conclusion slide

Week 1 DQ#1

Review the agile and systems development life cycle (SDLC) software development methodologies in your readings and in the podcast for this week. Explain the main differences between the agile and SDLC (waterfall) methodologies.

Week 1 DQ#2

Why is the role of the systems analyst so critical in a systems development project? Explain what skills and knowledge are required to be effective.

BSA/375 Week 2 - Riordan Manufacturing SR-rm-022 (Section 1) Complete Section 1 of the Service Request SR-rm-022 paper. Using the Service Request SR-rm-022, analyze the HR system. Prepare a 4- to 6-page paper that accomplishes the following:

What key stakeholders in Riordan Manufacturing would you gather requirements from? Describe the information-gathering techniques and systems analysis tools you would propose for the

project. Identify the key factors that help ensure the information required for the project is gathered

successfully. Explain what project scope is and why it is important. Describe the areas of project feasibility that are

examined in the analysis phase of the SDLC. Cite and discuss 2 to 3 references, in addition to the required readings, that are relevant to the

assignment. Include citations and references formatted consistent with APA guidelines.

Week 2 DQ#1

Describe how joint application design (JAD) might be considered a better information-gathering technique than the traditional method of requirements gathering? What are its shortcomings?

Week 2 DQ#2

You have been asked to interview the HR manager of Riordan Manufacturing about business requirements for the new HR system. What best practices for interviewing would you employ for an effective interview?

BSA/375 Week 3 - Riordan Manufacturing SR-rm-022 (Section 2) Complete Section 2 of the Service Request SR-rm-022 paper. Prepare an additional 4- to 6-page paper that includes the following:

Describe the application architecture and process design. Include a high-level description of the security controls you recommend for the design of this HR system.

Apply the tools of systems analysis to describe the information systems architecture in terms of data, processes, interfaces, and network. You can use a Microsoft Visio diagram to draw examples of flow charts, data flow diagrams, and any other design tools.

Cite and discuss 2 to 3 references, in addition to the required readings, that are relevant to the assignment. Include citations and references formatted consistent with APA guidelines.

Week 3 DQ#1

Principles of User Interface Design Critique - Review website.

Week 3 DQ#2

What are issues to consider when deciding to build software in-house or purchase commercial off-the-shelf software (COTS)? If you were asked to evaluate several COTS applications, list and explain the criteria you would use to select the best one for your organization.

BSA/375 Week 4 -Riordan Manufacturing SR-rm-022 (Section 3) Complete Section 3 of the Service Request SR-rm-022 paper. This section incorporates the transition from design to implementation.

Prepare an additional 4- to 6-page paper that accomplishes the following:

Describe the implementation stage for this project. Include a discussion of the six major activities for the implementation stage as described in the text:

o Coding o Testing o Installation o Documentation o Training o Support

Describe in the discussion of these six activities how each activity would be specifically planned for the individual project situation.

Discuss the benefits of using defined and repeatable processes for accomplishing these activities for the implementation stage.

Cite and discuss 2 to 3 references, in addition to the required readings, that are relevant to the assignment. Include citations and references formatted consistent with APA Guidelines.

Week 4 DQ#1

As you read and reflect on your assignments this week discuss why a feasibility study must be performed and find out how IT determines the feasibility of a system.

Week 4 DQ#2

As you explore the six areas of implementation (coding, testing, installation, documentation, training, and support plan creation) reflect on how each is integrated with one another. Poor execution in any one area can sabotage the success of the system. Think about computer systems that were implemented in your organization that were not very successful. Which aspects of implementation were the contributing factors to the problems encountered?

BSA/375 - Week 5 - Kudler Fine Foods

Service Request SR-kf-013 TEAM Final Project

Learning Team Service Request SR-kf-013 Paper and Presentation

WEEK 2 - Draft the first 4- to 6-page section of the Service Request SR-kf-013 Paper, due in Week Five. Include the following:

Statement of scope and goals: Specify which functions will be included in the project. Identify the goals and include accomplishments, not a solution.

Supporting measures for success: Specify tangible measures for determining the relative degree of success of the completed project. The measures must correlate with the goals specified in the first section of this deliverable.

Summary of project feasibility: Include specific operational, technical, and economic feasibility analyses. Operational and technical issues should specify how each issue will be addressed. The economic analysis must include quantified specific benefit and cost areas.

Current business process summary: Provide a flowchart and a separate high-level logical data flow diagram of the current process.

Proposed system requirement list: List specific individual requirement needs in measurable and objective terms.

WEEK 3 - Draft the next 4- to 6-page section of the Service Request SR-kf-013 Paper, due in Week Five. Include the following:

Determination of requirements: Identify specific analysis methods used to determine user needs. List of confirmed requirements: Categorize each system requirement identified for the Week Two

milestone as mandatory or optional. Proposed system process view: Provide a flowchart of the proposed process. Functional allocation modeling: Specify how each proposed system function would be allocated in

terms of the required hardware, software, and humancomputer interface (HCI). Logical model of the system: Provide a high-level logical data flow diagram of the proposed system.

WEEK 4 - Draft the next 4- to 6-page section of the paper, due in Week Five. Include the following:

Preliminary design model: Provide a diagram that illustrates the overall logical information architecture.

Design trade-off approach: Specify the tradeoffs among cost, schedule, and performance. For example, a fast, inexpensive solution may not address performance requirements adequately.

Detailed design process and design specifications: Specify separate recommended decisions for software design, hardware, and networks. Include resolution of HCI considerations.

Physical model of the system: Illustrate the recommended decisions in information architecture diagrams.

WEEK 5 - Draft the final 4- to 6-page section of the paper. Include the following:

Testing process summary: Define a test plan or script that identifies major software functionality and hardware to be tested with the required outcomes.

Installation process and training plan summary: Provide a time line that identifies the specific stepsincluding trainingand related resources required to implement the recommended system. Include a narrative explanation that discusses the effects of project constraints, such as time and conversion method, and include a description of the recommended training plan.

Documentation plan summary: Specify and explain each type of documentation required for ongoing technical and user support for the proposed system.

Support and maintenance plan summary: Provide a plan that outlines responsibilities and related resourcessoftware, hardware, and networksnecessary to support and maintain the proposed system.

Check out Brand New Tutorials @

UOP-Tutorials.info

Use Coupon Code: MarchMadness for 10% off Entire Cart!