Use Case: Project Progress ReportsOne of the biggest problems in project management is updating, tracking and reporting progress of a project. How often should progress be updated? How often should progress reports be distributed? Who should progress reports be distributed to? In what form should progress reports be distributed? What software can or should be used? How secure is the project progress? As part of the development of the requirement during the initial investigation stage of the Systems Development Life Cycles (SDLC) process, a constructive method is the use case. Use case is a technique for capturing requirements with scenarios written in non-technical terminology that describe how a system interacts with a user or another system (University of Phoenix, Course Syllabus, 2006). There are two fundamental elements, and their relationships, to keep in mind: actors and objectives. Stakeholders are everyone and everything that will use (or be used) by the project progress reports, as well as the goals, which are what the stakeholders want to achieve. The use case will describe the objectives achieved by the actors carrying out the tasks (Carr & Meehan, 2005). Applying Use Cases to Project Progress Reports Project progress reports allow those moving a project forward to record what and how much has been accomplished. the project, managers to track progress for decision making, and those who rely on project progress for interrelated tasks, to inform and be informed of the progress of the project. Actors' tasks include completing project work, recording and editing the project. work accomplished and review of project progress to achieve objectives, as well as administration... middle of document ...... project progress? were discussed.ReferencesCarr, N. & Meehan, T., (2005). What's the problem? Retrieved October 14, 2006, from http://alistapart.com/articles/whatstheproblemCockburn, A. (2006). Use case fundamentals. Retrieved October 14, 2006, from http://members.aol.com/acockburn/papers/AltIntro.htmStair, R. & Reynolds, G. (2003). Fundamentals of Information Systems, Second Edition. [Electronic text from the University of Phoenix custom edition]. Boston. MA: Course Technology, a division of Thomson Learning, Inc. Retrieved October 1, 2006 from University of Phoenix, resource, CIS564 ¡V Information Management in Business Course Web site.University of Phoenix. (2006). Course program. Retrieved September 26, 2006, from University of Phoenix, CIS/564.4 - Business Information Management Website, https://classroom.phoenix.edu/afm203/secure/view-thread.jspa?threadID=1176244