1. IT 499 Bachelor Capstone Week 8

2. Adgenda Administrative Review UNIT Seven UNIT Eight Project UNIT Nine Preview Project Status Summary

3. Administrative Seminar – Course is project based, 85% for project, 15% for discussion. Seminars are not graded. Project overview: In this Unit, students conduct a technology or design needs analysis within an organization in which a problem or need has been identified. They will develop and implement a solution to this problem or need later in the course. Students submit a PowerPoint Presentation containing a summary of identified needs and a preliminary system specification of their proposed solution to meet the identified needs. All papers submitted should be in proper APA format.

4. Administrative Remember that as we conclude week seven, the projects are due in UNIT nine and ten. We are quickly closing in on the final submissions. The Discussion Board Requirement: – Students are to post a minimum of three posts per discussion thread. One initial response and two replies to their classmates – Posting on a minimum of three different days, for example: Wednesday, Friday and Monday – The first post must be made by Saturday.

5. Week Seven Review Reporting Progress – In this Unit, you will continue development and implementation work on your Capstone Project. You will conduct a client review of the project to date, and you will report progress to your instructor and the class. – Conduct a client review of the project to date. – Report any issues or possible problems. – Include any client feedback.

6. UNIT Eight Updating System Specifications – In this Unit, you will revise your specification and project documentation to include changes made to the project to date. Next, you will create a PowerPoint presentation to report those changes. The presentation should include a time-line listing the tasks/milestones accomplished to date, and pending, started, or in- progress tasks remaining.

7. UNIT Eight Updating System Specifications The specification is used to communicate to all stakeholders the exact nature and low-level details of the project. As development proceeds, the specification may have to be revised due to project changes that necessitate design or detail changes. Depending upon the sector of information technology in which you are working, the specification may be called by different names; SDD (System Design Specification), SRS (Systems Requirements Specification), Business Case, Project Charter, etc. However, the function of the specification document is essentially the same: it clarifies, for all stakeholders, exactly what product is to be developed (network design, Web page, software application, database, design project), what that product will contain/look like, who will be involved in creating it, the materials required (hardware, software, etc.), and the resources (personnel) needed to complete the project within the defined timeframe and budget.

8. UNIT Eight Updating System Specifications In networking and Web development, the Specification Document is usually called a Design Specification. In programming, it is referred to as a Software Requirements document, and in database and systems analysis/design, it is usually called a System Specification. The Specification Document is usually developed incrementally. A completed specification is fully produced and signed-off before work on the project begins. The specification informs clients of what you are proposing to do based on the needs analysis, and it gives clients a chance to clarify what their expectations and needs are. After getting your client's approval of the project, you are expected to deliver what is agreed upon. Other times, for business reasons, it is decided to make some basic assumptions from the needs analysis, and to proceed with planning and development, revising assumptions and project details as the project unfolds. This approach is referred to as an iterative project. The specifications for the system being built is revised as the product is actually produced and documented

9. UNIT Eight Updating System Specifications In Unit 3, you developed a presentation of a preliminary system specification, and you outlined your proposed solution. Since then, as you have developed your project, you have had to make revisions to those ideas – some from this course, others from the client. Hopefully, as the project develops, you are keeping good documentation of the changes. Key Concepts – Different specification documents include SDD (System Design Specification), SRS (Systems Requirements Specification), Business Case, and Project Charter. – In networking and Web development, the Specification Document is usually called a Design Specification. – In programming, the Specification Document is referred to as a Software Requirements document. – In database and systems analysis/design, it is usually called a System Specification.

10. Seminar This week's Seminar session is about how you will present your final project. In this week's Seminar, we will discuss ways to gather and present material about the project, and if graphs, flowcharts, PowerPoint presentations, etc. should be used to help communicate and share project information with other members of the team. In preparing for the chat, review the information from the sources listed under Project Resources and think about the following questions: What specific content should be included in a System Specification, Design Specification, or Software Requirements Document? What tools can be used to complete this phase and generate a clear specification stating the project's goals? The Seminar session is your opportunity to ask any questions or to clarify material that has been presented in this week’s learning outcomes or readings. If you have specific questions or topics that you would like to see addressed in the Seminar session, please email your instructor prior to the day of your chat.

11. Week Eight Project Prepare a PowerPoint presentation reporting progress to date on your Capstone Project. Use the general template below as a guide. – Contact information. – Description of project being developed. – Original Project needs and goals. – Show changes that have happened since Unit 3. – Diagrams, flow charts, page screen shots or mockups, etc. (Use as many slides as needed.) – Revised timeline with dates for remaining development and deliverables. (Use as many slides as needed.)

12. Week Nine Preview In this Unit, you will complete development and implementation work on your Capstone Project. During this Unit, we will discuss strategies that you can implement to complete the project on time.

13. Week Nine Project This week you will complete your network, software application, website, or database and deploy it within your client organization. Your project should meet all of the requirements outlined in the project descriptions in Units 1 and 2. Your project submission will vary depending upon the type of project you chose. Discuss options for submission with your instructor before submission, and carefully review any submission guidelines posted by your instructor as a class announcement or on the Discussion Threads. Note: If you are working on the website development project, you must publish it to a Web server for review by your instructor.

14. Project Status Status Issues Concerns

15. Questions Summary