CMGT 555 Wk 3 Individual
As you learned in Week 2, requirements are a fundamental component to any project. Depending on the SDLC applied, requirements can be written in different forms. For example, some requirements will be very technically focused (technical requirements) and are written in a manner that dictates what a stakeholder expects the system to accomplish. Another approach taken, often with Agile-run projects, is to create a user story. A user story focuses on different types of system users and outlines more of a workflow that organizations expect.
Review the Wk 2 Discussion 1 about what makes well-written requirements.
The WeLoveVideo, Inc. project team met with the business owners last week in a structured requirements-gathering meeting. In this meeting, they discussed that the requirements should focus on certain users, such as customer support representatives and inside-sales representatives, as well as be geared towards the system supporting the job function.
Create 15 to 20 system requirements based on the scope of the project discussed in the requirements meeting. Ensure the requirements meet quality standards and are outlined in priority order. Provide a justification behind the prioritization within the document. You may use any Microsoft® program, such as Excel® or Word, to create the list of requirements.
Students are often burdened with the task of writing essays. They need to master various academic topics, understand how to integrate facts and arguments, and organize all of this information in a clear and logical way. This is not an easy task for many students. But fear not! We’ve got your back. Here at MoreEssays.com, we offer professional academic help that can take on all these tasks on your behalf. All you need to do is fill out the Order form with your paper’s details, and we will get started on it right away!