Justify the prioritization of the system requirements within the document 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 toward the system supporting the job function.Ĭreate 15 to 20 system requirements based on the scope of the project discussed in the requirements meeting.Īpply Agile or Waterfall methodologies in creating requirements that meet quality standards in priority order, addressing how the SDLC will impact the form of the requirements The WeLoveVideo project team met with the business owners last week in a structured requirements gathering meeting. Review the Comp 1 Reflection about what makes well-written requirements. A user story focuses on different types of system users and outlines more of a workflow that organizations expect. Another approach taken, often with Agile-run projects, is to create a user story. 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. Depending on the SDLC applied, requirements can be written in different forms. As you learned in the previous course content, requirements are a fundamental component of any project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |