Course Syllabus: Week One: Systems Development Life Cycle
Course Syllabus: Week One: Systems Development Life Cycle
Course Syllabus: Week One: Systems Development Life Cycle
Course Syllabus
College of Information Systems & Technology BSA/375 Version 12 Fundamentals of Business Systems Development
Copyright 2011, 2010, 2009, 2008, 2007, 2006, 2005, 2004, 2003, 2001, 2000, 1999 by University of Phoenix. All rights reserved.
Course Description This course introduces the fundamental, logical, and design considerations addressed during system and application software development. It provides a solid background in information systems analysis and design techniques through a combination of theory and application. The Systems Development Life Cycle will be fundamental to the course. Policies Faculty and students/learners will be held responsible for understanding and adhering to all policies contained within the following two documents: University policies: You must be logged into the student website to view this document. Instructor policies: This document is posted in the Course Materials forum.
University policies are subject to change. Be sure to read the policies at the beginning of each class. Policies may be slightly different depending on the modality in which you attend class. If you have recently changed modalities, read the policies governing your current class modality. Course Materials Dennis, A., Wixom, B. H., & Roth, R. M. (2009). Systems analysis and design (4th ed.). Hoboken, NJ: John Wiley & Sons. Valacich, J. S., George, J. F., & Hoffer, J. A. (2009). Essentials of systems analysis and design (4th ed.). Upper Saddle River, NJ: Prentice Hall. Software Microsoft Visio Microsoft Project (Recommended) All electronic materials are available on the student website.
Due
Points
Essentials of Systems Analysis and Design. Reading Reading Reading Reading Reading Reading Participation Discussion Questions Learning Team Instructions Learning Team Charter Learning Team Instructions Service Request SR-kf-013 Paper and Presentation (Preparation) Read Ch. 2, The Sources of Software, of Essentials of Systems Analysis and Design. Read Ch. 3, Managing the Information Systems Project, of Essentials of Systems Analysis and Design. Read Ch. 4, Systems Planning and Selection, of Essentials of Systems Analysis and Design. Read Ch. 1, The Systems Analyst and Information Systems Development, of Systems Analysis and Design. Read Ch. 2, Project Selection and Management, of Systems Analysis and Design. Review the Week One podcast lecture. Participate in class discussion. Respond to weekly discussion questions. You are only required to respond to 2 questions. Begin creating a Learning Team Charter. DAY 7 DAY 7 2 2 NA
Complete Service Request SR-kf-013. Develop requirements for the Kudler Fine Foods Frequent Shopper Program. Prepare a 12- to 16-page paper and a 10- to 12-slide Microsoft PowerPoint presentation of the project, due in Week Five. Assume that you are delivering the paper and presentation to an executive management committee. At a minimum, the paper and presentation must include the following: Business objectives with supporting measures of success for the project A description of the current business process or system Identification of the scope or boundaries of the project Project constraints, including finances, time, resources, and organizational policies or culture Business functional requirements Description of the new business process or system Use the process objectives model and the system objectives model. Design requirements, including input or output design, interface design, data model, and network model A costbenefit analysis
NA
Resources: Element K and University of Phoenix Material: Software Development Models Complete the Introduction to Software Life Cycle Models module in Element K. To find the module: click on the Element K Tutorials link on the left column of Course Material page and place Software Life Cycle Models in the search box within the Element K window. Create a screenshot of the last Element K page of each lesson in the module showing the checkmarks for each section on the lefthand navigation bar. 1. Press Alt + Print Screen on your computer keyboard to create a screenshot. 2. Open a blank Microsoft Word document. 3. Press Ctrl + V on your keyboard to paste the screenshot into the document. The Introduction to Software Life Cycle Models Element K tutorial discusses a variety of software development models, including the following: waterfall model, spiral model, Rapid Application Development (RAD), and agile model. Select one of the following proposed systems that are slated to be developed by your IT department. Payroll Loan processing Risk management Financial investment Web design List the software development model you would use to develop that system and provide an explanation for your choice. Complete and submit into the ASSIGNMENT section of eCampus.
DAY 7
Resource: University of Phoenix Material: Successful Software Development Review the following assignment options: Option 1: Software Development Presentation Option 2: Create a Work Breakdown Structure
DAY 7
11
Follow the instructions in the University of Phoenix Material: Successful Software Development, located on the Course Materials page, to complete the assignment, then submit into the ASSIGNMENT section of eCampus. Weekly Summary Post weekly summary. Day 7 1
Due
Points
Reading Reading Reading Reading Reading Reading Reading Participation Discussion Questions Learning Team Instructions Learning Team Charter Learning Team Instructions Service Request SR-kf-013 Paper (Preparation)
Day 7
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. Complete and submit into the ASSIGNMENT section of eCampus.
Resource: Element K Complete The Fundamentals of Requirements Elicitation (Inquestra) (Part 1 of 8) and Determining a Project's Objectives (Inquestra) (Part 2 of 8) modules in the Element K Oracle Fundamentals (Second Edition). Note: Use the search box within Element K, specifying Inquestra to find the modules. Create a screenshot of the last Element K page of each lesson in the module showing the checkmarks for each section on the lefthand navigation bar. Imagine you have been hired by the University of Phoenix IT department. Your first task is to determine the business requirements for enhancing the Online Learning System. To do this, you decide to hold a brainstorming session. Answer the following questions about your brainstorming session: Which stakeholders will you invite to your brainstorming session? Why? What questions you will ask them? Why are these questions important? Complete and submit into the ASSIGNMENT section of eCampus.
Day 7
The final individual paper for this class includes three sections; the final section is due in Week Four. One section of the paper is due each week. Complete Section 1 of the Service Request SR-rm-004 paper.
Day 7
11
Using the Service Request SR-rm-004, Analyze HR system, prepare a 4- to 6-page paper that accomplishes the following: Describe the information-gathering techniques and design methods you would propose for the project. Identify the key factors that help ensure the information required for the project is gathered successfully. Explain the scope and feasibility of the project. Cite and discuss 3 to 4 references, in addition to the required readings, that are relevant to the assignment. Include citations and references using the University of Phoenixapproved style guide format. Submit Section 1 of the final paper into the ASSIGNMENT section of eCampus. Weekly Summary Post weekly summary. Day 7 1
Due
Points
Discussion Questions Learning Team Instructions Service Request SR-kf-013 Paper (Preparation)
Respond to weekly discussion questions. You are only required to respond to 2 questions. Draft the next 4- to 6-page section of the Service Request SR-kf013 Paper, due in Week Five. This section must 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. Complete and submit into the ASSIGNMENT section of eCampus.
DAY 7 Day 7
2 2
Resource: Principles of User Interface Design presentation (link on the Course Materials page) Review the Principles of User Interface Design presentation located in the Week Three section of the student website. Evaluate a website of your choice for adherence to the six design principles outlined in the presentation. Write a 350- to 700- word critique. Some things to consider as you write your critique are: Which of the six design principles do you see being utilized in this website? Provide examples. What are some changes that could be made to the design of the website to better incorporate the six design principles? Do you think this website does a good job following the six design principles? Why or why not? Complete and submit into ASSIGNMENT section of eCampus.
Day 7
Complete Section 2 of the Service Request SR-rm-004 paper. This weeks assignment incorporates the transition from analysis to design. Consider revising Section 1 based on faculty feedback. Prepare a 4- to 6-page paper that includes the following:
Day 7
11
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. Draw the physical data flow diagrams. Use Microsoft Visio to prepare examples of flow charts and data flow diagrams. Cite and discuss 3 to 4 references, in addition to the required readings, that are relevant to the assignment. Include citations and references formatted consistent with APA guidelines. Submit Section 2 of the paper into the ASSIGNMENT section of eCampus.
Weekly Summary
Day 7
Due
Points
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.
Begin work on the Microsoft PowerPoint presentation. Complete and submit into ASSIGNMENT section of eCampus. Supporting Activity Element K Resources: Element K and University of Phoenix Material: Software Testing. Note: Use the search box within Element K, specifying Introduction to Software Testing to find the module. Complete the Introduction to Software Testing module in Element K. Create a screenshot of the last Element K page of each lesson in the module showing the checkmarks for each section on the lefthand navigation bar. Complete the table found in University of Phoenix Material: Software Testing. Discuss the test cases posted by your classmates. How is your test case similar to theirs? What steps did you take to develop yours? After reviewing the test cases that others have developed, is there anything you would change about yours? Explain your answer. Complete and submit into ASSIGNMENT section of eCampus. Individual Service Request SR-rm-004, Part 3 Complete Section 3 of the Service Request SR-rm-004 paper. This section incorporates the transition from design to implementation. Consider revising Sections 1 and 2 based on faculty feedback. Prepare a 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 o o Coding Testing Installation Day 7 11 Day 7 2
10
o o o
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 3 to 4 references, in addition to the required readings, that are relevant to the assignment. Include citations and references using the University of Phoenixapproved style guide format. Compile Sections 1 through 3 into one final paper and submit into ASSIGNMENT section of eCampus. Day 7 1
Weekly Summary
Due
Points
11
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 resources software, hardware, and networksnecessary to support and maintain the proposed system.
Finalize and submit the paper into ASSIGNMENT section of eCampus. Learning Team Service Request SR-kf-013 Presentation Course Summary Submit the Microsoft PowerPoint presentation under the designated thread posted in the MAIN forum. Day 7 5
Day 7
NA
Copyright
University of Phoenix is a registered trademark of Apollo Group, Inc. in the United States and/or other countries. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation in the United States and/or other countries. All other company and product names are trademarks or registered trademarks of their respective companies. Use of these marks is not intended to imply endorsement, sponsorship, or affiliation. Edited in accordance with University of Phoenix editorial standards and practices.