Slide 1: Assalamuoalikum Everyone .

Welcome to our presentation Determining system

requirements

Slide 2: My self Pranto Dutta .ID 201002109. And my teammembers are Labib Coudhuri Ayon
and Readul Islam Niyon.

Slide 3 : Here is our table of contents. At first we Brifly Introduce Determining system
requirements. After that We discuss the importance ,Key Steps,Tools, challenges and Lastly
Conclution.

Slide 4: Introduction: Determining system requirements is a critical phase in the development

of any software or information system. It involves identifying, analyzing, and documenting the
needs and constraints that the system must fulfill to meet the objectives of the stakeholders.
The success of a system largely depends on how well its requirements are understood,
documented, and managed throughout the development lifecycle.

Slide 5: Importance of System Requirements: "Let's start by understanding why determining

system requirements is so critical."

1. Alignment with Stakeholder Needs: "First and foremost, it ensures that the system
aligns with the needs and expectations of our stakeholders. Without this alignment,
project success is at risk."

2. Avoiding Scope Creep: "By having clearly defined requirements, we can prevent scope
creep – those unexpected changes that can complicate and delay our development
process."

3. Budget and Resource Planning: "Accurate system requirements facilitate effective

budgeting and resource allocation, ensuring that we have what we need to bring our
project to success."

4. Risk Mitigation: "Additionally, by identifying potential challenges early in the process,

we can proactively mitigate risks and increase the likelihood of a successful project
outcome.

That’s all My part . Labib Coudhuri Ayon continue from Next.

Slide 6: Key Steps: "Now, let's explore the key steps in determining system requirements."

1. Stakeholder Analysis: "Engaging all relevant stakeholders is the starting point. We need to
gather insights from end-users, management, and any other parties invested in the success of
our project."

2. Requirement Elicitation: "Next, we employ various techniques, such as interviews and surveys,
to gather detailed and comprehensive requirements."

Slide 7: Key Steps (Cont.):

3. Documentation: "Clear and concise documentation is crucial. This includes creating documents
and using visual aids to ensure everyone understands the requirements."

4. Prioritization: "Prioritizing requirements based on importance and feasibility helps us focus on

what truly matters."

5. Validation: "Finally, validating requirements with stakeholders ensures accuracy and

completeness."

Slide 8: Tools for Requirement Determination: "Equipping ourselves with the right tools enhances the
requirement determination process."

1. Use Case Diagrams: "Visual representations of system interactions help us understand the flow
and dynamics."

2. Data Flow Diagrams (DFD): "DFDs illustrate how data moves within the system, providing a
comprehensive view of information flow."

3. Prototyping: "Developing a working model allows us to validate and refine requirements in a

tangible way."
 4. Requirement Management Tools: "Utilizing software for documentation and tracking changes
streamlines the management of requirements."

Slide 9: Challenges in Requirement Determination: "While understanding the importance of

determining system requirements is crucial, we also need to be aware of the challenges that may arise."

1. Changing Stakeholder Needs: "Stakeholder needs may evolve. Open communication is key to
address these changes effectively."

2. Ambiguity: "Ambiguous requirements can create confusion. Collaboration and clarity are
essential in resolving ambiguity."

3. Scope Creep: "Establishing a change control process helps manage scope changes effectively."

4. Communication Gaps: "Regular updates ensure continuous communication, minimizing the risk
of misunderstandings."

Slide 10: Best Practices in Requirement Determination: "As we navigate through these challenges, let's
also explore some best practices in requirement determination."

 Regular Stakeholder Involvement: "Keeping stakeholders involved throughout the process

ensures that their evolving needs are considered."

 Clear and Precise Documentation: "Clear, concise, and well-organized documentation is the
backbone of successful requirement determination."

 Iterative Validation and Adjustments: "Validating requirements iteratively allows us to make

adjustments as needed, ensuring continuous improvement."

Slide 11: Conclusion: In summary, the pivotal role of system requirements cannot be overstated when it
comes to achieving project success. A comprehensive grasp of the entire process, coupled with
meticulous and effective documentation, is indispensable for ensuring the triumph of our projects. By
recognizing system requirements as the cornerstone of our endeavors, we underscore their crucial
significance in guiding and shaping the project towards successful outcomes. Clearly defined and well-
documented requirements serve as a robust foundation, contributing significantly to the seamless
planning, development, and implementation of our projects.